Well, first of all what does it mean to use “unsupported by Microsoft” Customizations in Dynamics CRM?
“Unsupported by Microsoft” means exactly what it says: you can’t get support about APIs or programming practices from Microsoft. They (Microsoft) don’t test them and they don’t know if something they change will break them. They can’t predict what will happen if someone changes code in the application. The developer who uses unsupported APIs and programming practices assumes the responsibility to support their code. They will need to test their code to make sure it works. If you choose to use unsupported customizations in your CRM deployment you should be sure to document what was done and have a strategy to remove those customizations before you contact Microsoft Dynamics CRM Technical Support. If you need help with unsupported customizations, contact the developer or organization who prepared the customizations.
Second, which common customization practices are not supported?
- Directly changing files in the application
- Retrieving data directly from database tables
- Updating data directly in the database tables
- Changing the database tables, stored procedures, or views
This is not a complete list. This post for example describes how you could import a CRM 2011 managed solution in to CRM 2015, but is definitely not supported!
Disclaimer: this text is part of the “Administering CRM 2015 for online and on-premises”-Guide, I have not written this myself and do not claim any ownership of it. Moreover this document is provided “as-is”.