Dynamics 365 Finance
Dynamics 365 Finance should start in a customer-owned sandbox with one AP, journal, or worker workflow and a tightly scoped allowlist.
Sandbox availability
Keep the first connector setup constrained to one environment, one identity, and one clearly reviewable workflow.
Choose the customer-owned sandbox
Use a customer-owned non-production environment for Dynamics 365 Finance. This connector should be validated only where the reference data, approvals, and permissions resemble production.
Create the least-privilege integration identity
Save the Dynamics 365 Finance environment URL, Microsoft Entra app credentials, and the vendor, vendor invoice, ledger journal, and ledger-dimension allowlists for the initial workflows.
Enter the connector settings and narrow allowlists in ActionPlane
Open the connector page in ActionPlane, save the environment URL and credentials, and keep the first workflow scoped to one transaction family with a small field allowlist.
Validate auth and sync metadata for the exact transaction path
Run metadata sync so ActionPlane can validate Dynamics 365 Finance entities plus AP and journal field allowlists before live writes.
Run one realistic sandbox transaction before any broader rollout
Submit the Dynamics vendor invoice or journal-entry preset as a dry run from the dashboard and confirm that the preview, governance decision, and artifacts look correct. After that, run one live sandbox transaction and confirm the rollback or compensation evidence before going further.
Business context
Finance wants one AP or journal workflow that buyers and operators can review without needing founder narration.
Starting record state
A single invoice, vendor bill, journal, or worker update is isolated in a customer-owned sandbox with supporting references attached.
Requested change
Approve or post one narrowly scoped transaction with clear supplier, amount, coding, and reversal context.
Why it routes
ERP and finance actions need a customer-owned sandbox because the proof only matters when the control points match the production environment.
Expected artifacts
Request evidence, approval route, posting output, rollback or compensation context, and audit events should all remain bound to the same run.
Reset behavior
Reset depends on the customer sandbox and should restore the selected transaction or refresh the non-production fixture data.
Onboarding metering tracks activation progress for the connector. It is not a separate billable unit; workspace billing remains governed-run based.
Save the connector, validate it immediately, and sync metadata in one authenticated call.
{
"loginUrl": "https://contoso.operations.dynamics.com",
"instanceUrl": "https://contoso.operations.dynamics.com",
"clientId": "\u003Cclient-id\u003E",
"clientSecret": "\u003Cclient-secret\u003E",
"refreshToken": "\u003Crefresh-token-or-empty\u003E",
"apiVersion": "10.0",
"isSandbox": true,
"isEnabled": true,
"validateAfterSave": true,
"syncMetadataAfterSave": true,
"managedObjects": [
{
"objectApiName": "vendor",
"displayName": "Vendors",
"allowedFields": [
"vendorAccount",
"vendorGroup",
"paymentTerms",
"currencyCode",
"bankAccountMask"
]
},
{
"objectApiName": "vendorinvoice",
"displayName": "Vendor invoices",
"allowedFields": [
"invoiceNumber",
"invoiceAmount",
"dueDate",
"approvalStatus",
"matchStatus"
]
},
{
"objectApiName": "ledgerjournal",
"displayName": "Ledger journals",
"allowedFields": [
"externalId",
"journalName",
"postingPeriod",
"currencyCode",
"postingLayer"
]
},
{
"objectApiName": "ledgerdimension",
"displayName": "Ledger dimensions",
"allowedFields": [
"mainAccount",
"costCenter",
"department",
"legalEntity",
"postingProfile"
]
}
]
}
curl -X POST \ "$ACTIONPLANE_BASE_URL/api/connectors/onboarding/dynamics365-finance/connect" \ -H "Authorization: Bearer <session-token>" \ -H "Content-Type: application/json" \ --data @"connect-dynamics365-finance.json"
Re-run auth and instance validation without resubmitting the connector payload.
curl -X POST \ "$ACTIONPLANE_BASE_URL/api/connectors/onboarding/dynamics365-finance/validate" \ -H "Authorization: Bearer <session-token>" \ -H "Content-Type: application/json"
Refresh the writable object and field catalog after credentials or allowlists change.
curl -X POST \ "$ACTIONPLANE_BASE_URL/api/connectors/onboarding/dynamics365-finance/sync-metadata" \ -H "Authorization: Bearer <session-token>" \ -H "Content-Type: application/json"
Narrow AP, journal, or worker workflow rollout with explicit approval posture
Supporting artifacts and audit evidence on the same run
Go-live path centered on customer-owned sandbox validation, not generic demos
First-class onboarding API can save, validate, and sync the connector in one authenticated flow
Pick one customer-owned sandbox and one transaction family before any live integration is enabled.
Validate supporting artifacts, approval routing, and the compensation story with realistic fixture data.
Only widen to production after a buyer and an operator can both explain the same proof chain.
ERP, finance, and HCM connectors require a customer-owned sandbox today.
Proof quality depends on realistic reference data, approval paths, and compensating controls in that sandbox.
We intentionally do not promise broad coverage until one narrow workflow has been validated end to end.