ERP Integrations
Dynamics 365 / Business Central
Connect Microsoft ERP systems and choose the company scope Atlas should operate against.
Prerequisites
| Tenant consent | Microsoft admin consent for the ERP application |
|---|---|
| Company | Selected Business Central company or D365 environment |
| Access mode | OData/API access for entities used by workflows |
Connect in Atlas
Atlas -> Connectors -> Native Integrations -> Dynamics 365 Business Central
Atlas supports the managed install path and a customer-managed Entra app form.
- Managed install
- Click Install Atlas ERP Connector. Atlas opens Microsoft admin consent, polls for completion, then asks for a Business Central company when multiple companies exist.
- Tenant ID example
- 00000000-1111-2222-3333-444444444444 from Microsoft Entra app Overview.
- Client ID example
- aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee from the Atlas app registration.
- Client Secret example
- Paste the secret Value, not the Secret ID, from Certificates & secrets.
- Environment example
- Production, Sandbox, or a custom name such as Sandbox-UAT from the Business Central URL/admin center.
- BC Company ID example
- Leave blank for one company, or paste a company GUID from Business Central Companies or the companies API.
- Connected modal
- Use Test Connection, Disconnect, and the Business Central catalog fidelity card after setup.
- Per-user consent
- If delegated user access is required, click Sign in to Business Central on the connector surface.
- 1
Open the Business Central card
In Atlas, go to Connectors, find Dynamics 365 Business Central under Native Integrations, and click the card.
- 2
Use the managed install when available
Click Install Atlas ERP Connector. Microsoft opens an admin consent flow; approve it with a tenant admin account.
- 3
Select a company if prompted
If Atlas finds multiple Business Central companies, choose the BC Company in the modal before continuing.
- 4
Complete user consent if requested
Some workflows need delegated Business Central access. Use the Sign in to Business Central button and confirm the signed-in identity is the intended operator.
- 5
Verify the connector
After the modal shows Connected, use Test Connection and then run catalog ingestion before enabling workflows.
Atlas must know which tenant, environment, and company to use before catalog ingestion and workflow routing begin.
After connection
Run a catalog sync and verify core entities before enabling live workflow dispatch.
Business Central setup references
- Business Central service-to-service authentication
Use this when registering the Entra application, granting app_access, and assigning the application inside Business Central.
- Business Central API companies endpoint
Use this to find the company IDs available to the authenticated Business Central tenant and environment.
API access
Dynamics 365 and Business Central access typically uses Microsoft Entra identity with OAuth tokens. Atlas must know which tenant, environment, and company it is operating against before it can ingest the catalog or route workflows.
| Tenant | Microsoft Entra tenant that owns the ERP environment |
|---|---|
| Environment | Dynamics environment or Business Central environment name |
| Company | Business Central company ID or name when using company-scoped APIs |
| Permissions | API permissions and ERP roles for the entities Atlas reads or writes |
Customer-managed app setup
- 1
Create the app registration
In Microsoft Entra admin center, create a single-tenant app registration named Atlas and capture the Directory tenant ID and Application client ID.
- 2
Create a client secret
In Certificates & secrets, create a new client secret and copy the Value immediately. Paste it into the Atlas Client Secret field.
- 3
Grant Business Central app_access
In API permissions, add Dynamics 365 Business Central application permission app_access, then grant admin consent for the tenant.
- 4
Register the app inside Business Central
In Business Central, open Azure Active Directory Applications or Microsoft Entra Applications, add the same Client ID, assign the needed permission set, enable the app, and grant consent.
- 5
Select the environment
In Atlas, choose Production, Sandbox, or Custom and enter the exact Business Central environment name.
- 6
Select the company
Leave BC Company ID blank when there is one company. If there are multiple, use the Atlas picker or paste the company GUID from Business Central or the companies API.
- 7
Run catalog ingestion
Let Atlas read available entities, fields, and enum values so workflow tools use tenant-specific schema.
Verify
- 1
Read companies
Confirm Atlas can list or resolve the company scope for the selected environment.
- 2
Read core entities
Verify reads for customers, vendors, items, sales orders, purchase orders, and invoices as applicable.
- 3
Check extension fidelity
If Atlas depends on custom fields or an extension, confirm those fields appear in the catalog before enabling workflows.
- 4
Validate approval policy
Writes to ERP records should remain approval-gated until operators have reviewed successful read evidence.
Common errors
- Unauthorized: OAuth consent exists but the service principal or user lacks ERP application roles.
- Company not selected: Business Central APIs require a concrete company scope for most business data.
- Entity not found: the API page, table, extension, or Dataverse entity is not exposed in that environment.
- Partial catalog: standard entities are visible but custom fields require an extension or additional API exposure.
- Reconnect required: tenant consent, company selection, or ERP roles changed after the connector was authorized. Disable the connector, remove stale Microsoft consent if needed, reconnect, and verify with a fresh ERP read.