Does the integration need its own Dynamics licence?

An application user usually doesn't need a regular user licence, but it depends on your setup. I'll check that before we start.

Can you work with custom fields and tables we've made?

Yes. The Dataverse API sees custom tables and fields the same way as the built-in ones.

Do you use Power Automate?

Where it's enough, sure. When the logic grows or has to cope with failures, I'd rather build it in .NET, where it can be tested and monitored properly.

← All integrations

Integration

Dynamics 365 integration

Integrations with Dynamics 365 and Dataverse in .NET: customers, sales and orders kept in sync with the rest of your systems.

Dynamics 365 often becomes the heart of sales and customer follow-up, but the data is needed elsewhere too: in accounting, in a line-of-business system, on the website or in reports. I build the links between Dynamics and the rest, in .NET against the Dataverse Web API.

Typical jobs are getting enquiries from a form straight in as leads, syncing customers and orders with an ERP or accounting system, or pulling data out to a warehouse. Access is set up with an app registration in Entra ID, so the integration has its own identity with exactly the permissions it needs.

What can be connected to Dynamics 365

Leads and enquiries from web forms and other channels
Accounts, contacts and companies against ERP or accounting
Orders, quotes and products
Custom tables and fields you've added in Dataverse
Data out to a warehouse, Power BI or other reports

Access and setup

The integration gets its own app registration in Entra ID and an application user in Dynamics with a security role that grants only what it needs. It doesn't sign in as a person, and it doesn't break when someone changes their password or leaves.

.NET and integrations are what I've worked with the most, and the Microsoft stack is where I'm most at home.

Common questions

Does the integration need its own Dynamics licence?: An application user usually doesn't need a regular user licence, but it depends on your setup. I'll check that before we start.
Can you work with custom fields and tables we've made?: Yes. The Dataverse API sees custom tables and fields the same way as the built-in ones.
Do you use Power Automate?: Where it's enough, sure. When the logic grows or has to cope with failures, I'd rather build it in .NET, where it can be tested and monitored properly.