Dynamics 365 Finance and Operations
Connect Dynamics 365 Finance and Operations to Ploy to see every user in the environment, whether they are enabled, and which security roles they hold. Ploy can also create users, disable and re-enable them, and assign or remove security roles.
This integration is in beta
The Dynamics 365 integration is in beta. It was built from documentation and has not yet been checked against a live Finance and Operations environment, so some details may need adjusting once customers connect it. Beta does not limit what the integration can do.
The first step of setup is a consent checkbox. Ticking it lets Ploy capture redacted error data when a request to Dynamics 365 fails: the error response Dynamics 365 or Microsoft Entra sends back, with personal details, tokens and other secrets removed. Ploy uses it only to fix problems with this integration. You must tick the box to continue.
What Ploy reads
Every Finance and Operations user, including administrator, service and integration accounts, with their user ID, name, sign-in name, email address and whether they are enabled
Every security role, including roles nobody holds yet
Which users hold each security role
The environment itself, so a production and a sandbox environment stay separate in Ploy
Disabled users are shown as blocked and lose their access in Ploy straight away. A security role that is limited to some legal entities shows as the whole role.
Before you start
You need:
The address you sign in to Finance and Operations at, for example contoso.operations.dynamics.com
Permission to register an app in Microsoft Entra ID for your organization
A Finance and Operations administrator, to add the app inside Finance and Operations
Register an app in Microsoft Entra ID
In the Microsoft Entra admin center, go to App registrations and create a new registration, for example called Ploy. Leave the redirect URI empty.
Under API permissions, add a permission, search for the API called Microsoft Dynamics ERP, and add its permissions for accessing Dynamics AX data, the Dynamics AX custom service and Dynamics AX online as organization users. Grant admin consent.
Under Certificates and secrets, create a new client secret and copy its value. Entra shows it only once.
From the app's overview page, copy the Application (client) ID and the Directory (tenant) ID.
Add the app in Finance and Operations
In Finance and Operations, go to System administration, then Setup, then Microsoft Entra applications.
Add a new row with the Application (client) ID, a name such as Ploy, and a User ID.
Use a dedicated Finance and Operations user for this, not a person's own account, and give it the System administrator security role. Ploy reads and changes users and role assignments with exactly that user's access.
If the app is registered in Entra but not added here, Dynamics 365 refuses every request.
Connect Dynamics 365 in Ploy
In Ploy, go to Integrations and choose Dynamics 365 Finance and Operations.
Tick the beta consent checkbox.
Enter your environment address. You can paste the full address from your browser; Ploy keeps only the host.
Enter the Directory (tenant) ID, the Application (client) ID and the client secret.
Select Test connection. Ploy signs in as the app and reads one user to check everything works.
To connect a sandbox environment as well, add the integration again with the sandbox address.
What Ploy can change
Create a user: creates an enabled user who signs in with Microsoft Entra ID, using their email address. The user ID is taken from the part of the email before the @, up to 20 characters. The new user has no security roles until you grant them.
Disable or enable a user: disabling stops the person signing in to Finance and Operations; their security roles are kept, so enabling them again restores their access.
Security roles: assign or remove a security role from the role's resource page.
Ploy does not delete users. Disabling is how Finance and Operations removes access.
Troubleshooting
Dynamics 365 rejected that app: check the tenant ID, client ID and secret, and that the app is listed under Microsoft Entra applications in Finance and Operations.
Dynamics 365 refused to list users, or refused a change: give the Finance and Operations user the app is mapped to the System administrator security role.
Dynamics 365 did not recognise that environment: check the address. It ends in operations.dynamics.com.
A user with that ID may already exist: someone already has the user ID Ploy made from the email address. Create the user in Finance and Operations instead.
Your client secret expires: Entra client secrets have an expiry date. Create a new secret before it expires and update the connection in Ploy.