Purpose
Microsoft cloud ERP/CRM: Business Central, Finance and Operations or Dataverse (Sales, Customer Service). Access uses a Microsoft Entra ID application with permissions for the required entities.
Connection fields
| Field | Rule and default value | Explanation |
|---|---|---|
Productproduct | As configured Default: dataverse | business_central — Dynamics 365 Business Centralfinance — Dynamics 365 Finance and Operationsdataverse — Dataverse (Sales, Customer Service, Field Service) |
OData service addressservice_url | Required | Business Central: https://api.businesscentral.dynamics.com/v2.0/{tenant}/{environment}/api/v2.0/companies({company ID}); Finance and Operations: https://{organization}.operations.dynamics.com/data; Dataverse: https://{organization}.crm.dynamics.com/api/data/v9.2. |
Tenant ID (Microsoft Entra ID directory)tenant_id | Required | Set the value according to your service configuration. |
Application Client IDclient_id | Required | Set the value according to your service configuration. |
Application client secretsecret | Separate protected field | The secret is not displayed after saving. An empty field in an existing connection preserves its current secret. |
Setup and validation
- Create a connection and give it a clear name.
- Complete required fields and the separate secret field.
- Run “Test” and read the diagnostics.
- Save the connection and select it in the appropriate flow block.
A successful test does not replace checking access to the required object and specific write mode.
Use in a flow
Server and account settings are stored in the connection. The specific object, fields and flow behavior are defined in the block. Go to data-handling rules →