At BPM Company, we have built the D365 Connector, a Mendix module that offers a connector to Microsoft Azure and Dynamics 365. We established an out-of-the-box method which provides connectivity capabilities for several Microsoft Dynamics 365 modules and editions. This blog will cover the steps you must take before you can start developing a Mendix application integrated with Dynamics 365.

ERP in the cloud is becoming mainstream. As a major player, Microsoft launched the cloud version of its cloud ERP platform, Dynamics 365, in 2016. Dynamics 365 runs on the Azure Platform, the cloud computing service created by Microsoft. 

Dynamics 365 is Microsoft’s product line of enterprise resource planning (ERP) and customer relationship management (CRM) applications, announced in July 2016. It is sold in two editions, the Business Edition for small and medium businesses (SMBs), and the Enterprise Edition for medium to large organizations.

The cloud applications are highly configurable, but at the same time less open for customization. The good thing is that Dynamics 365 is a very open platform, with a lot of integration capabilities. This offers new opportunities to implement complementary functionalities.

The Mendix Platform offers a very efficient way to implement these functionalities, but how do you start with this? BPM Company has built the D365 connector: A Mendix module that offers a connector to Microsoft Azure and Dynamics 365.

Below the high level steps to do the deployment. For a working example, we refer to our D365 Connector available in the Mendix App Store.

Step 1 -  Generate an Azure app key

You must start with the configuration of the application permissions in the Azure cloud. The Azure Platform generates an app key which you must insert into the Dynamics 365 application environment.

Step 2 - Registration of the app in Azure AD

Dynamic 365 connector

Any application that wants to have access to Azure resources must first be registered in the tenant. This registration process is feeding Azure AD with details about your application, such as the URL where it’s located, the URL to send replies after a user is authenticated, and so on.

Step 3 - Look after the Dynamics 365 service endpoint to exploit

Depending on the Dynamics module you want to connect with, different integration techniques are provided as a SOAP, REST or OData-based service. The Open Data Protocol (OData) allows the creation and consumption of queryable and interoperable RESTful APIs in a simple and standard way. This offers a flexible way to create your own service.

Step 4 - Mapping in Mendix

Now, you need to map the import and export for all entities using XML or JSON. This will initiate the creation of placeholders for the entities. Afterwards you also need to map the child elements of the schema. The last step of the integration will include the calling of all necessary endpoint operations.


With the Mendix Platform you can build any extension on Dynamics 365. You need to understand how to set up Azure and Dynamics 365 integrations. With this high-level roadmap, and the example you can find in the Mendix App Store, we hope you can start building your first Mendix application complementary to Dynamics 365.

If you want to get started, please download our D365 Connector. If you are looking for help, feel free to contact .