As Microsoft Dynamics 365 CRM apps mature, can we still talk customization?

The latest release the Microsoft Dynamics 365 customer engagement app suite have brought even more functionality to the application that customers can utilise right out of the box. Though this is obviously a fantastic thing, though it can raise the question of whether customising the system by adding complex workflows and other features still makes sense.

The out of the box, standard functionality has grown at an unrelenting pace in recent years. The introduction of a comprehensive service module, for example, allows many more customers to use Dynamics 365 for customer queries and complaints right out of the box. The rich knowledge article functionality allows businesses to digitise their knowledge and expand it across their business, emailing it to their customers at a click of a button. And with Dynamics 365 we saw the introduction of two new tools, Microsoft Flow and Power Apps, which aim to connect the applications up with more standard templates and functionality than ever before.

Since Dynamics 365 customer engagement apps are so functionally expansive, it raises the question (as it has done Here and Here) if the XRM platform, a term given to underlying customisation framework of the solution, is even required anymore for a business to get value out of the application.

The answer is the same as it always has been when building solutions for businesses: utilise standard functionality where you can, and build up from there using standard platform customising methods such as workflows, dialogs, and actions. Then move up to code if you need to.

This approach is one I will be arguing in favour of during my Workflow 101 sessions at