
This guide explains how to connect a Microsoft Entra tenant to Production Assist so users from a Microsoft Entra group can be synchronized into Production Assist.
The screenshots show older example views of the Microsoft Entra admin center and the Production Assist website, as well as an example account named GTG. Current portal and website views may use different menu names or layouts. Follow the settings and values described here.
Before you start, make sure you have:
Access to the Microsoft Entra admin center:
https://entra.microsoft.com
An administrator account with permission to grant Microsoft Graph application permissions. To grant consent for Microsoft Graph application permissions, you need at least the Privileged Role Administrator role. Depending on your tenant policy, Global Administrator may be required.
Access to the Production Assist organization settings where the Entra connection will be saved.
A Microsoft Entra group that contains the users who should get access to Production Assist. The group must be named exactly:
Azure_APP_Production-Assist
Use this display name for only one group in the tenant. If multiple groups have the same display name, Production Assist may select the wrong group.
Users in the group should have a usable email address or user principal name.
The setup has six parts:
Production-Assist app registration in Microsoft Entra.Production Assist uses two separate Entra functions:
Go to:
https://entra.microsoft.com
Sign in with an administrator account.
In the left sidebar, open:
Entra ID
Make sure you are in the correct tenant. In the tenant overview screen, confirm the tenant name and tenant ID.

The tenant overview confirms that you are working in the correct tenant and shows the tenant ID you need later.
If the app registration already exists, open it:
In the left sidebar, go to:
Entra ID > App registrations
Select:
All applications
Search for:
Production-Assist
Open the app registration.
If the app registration does not exist, create it:
Go to:
Entra ID > App registrations
Click:
New registration
Use this name:
Production-Assist
For supported account types, select:
Accounts in this organizational directory only
For the redirect URI, select the Web platform and enter this exact address:
https://www.production-assist.com/login/azure-redirect
Click:
Register
When signing in, Production Assist requests an OpenID Connect ID token through the hybrid flow. The app registration must therefore be configured as a web application and allowed to issue ID tokens.
In the app registration, open:
Authentication
Under Platform configurations, check whether a platform of type Web already exists. If not, select:
Add a platform > Web
Under Redirect URIs, enter this exact address:
https://www.production-assist.com/login/azure-redirect
Make sure to use https, include the full path, and not add a trailing slash.
Under Implicit grant and hybrid flows, enable:
ID tokens (used for implicit and hybrid flows)
The Access tokens option does not need to be enabled for Production Assist.
Click Save.
Alternatively, you can verify the setting in the app manifest. It should look like this:
"web": {
"redirectUris": [
"https://www.production-assist.com/login/azure-redirect"
],
"implicitGrantSettings": {
"enableIdTokenIssuance": true,
"enableAccessTokenIssuance": false
}
}
On the app registration overview page, copy these values:
You will enter both values in Production Assist later.

Use the Overview page to verify both IDs before you continue.
In the app registration, open:
Certificates & secrets
Open:
Client secrets
Click:
New client secret
Enter a description, for example:
Production Assist AD Sync
Choose an expiration period according to your company policy.
Click:
Add
Copy the secret Value immediately.
Important: copy the secret Value, not the secret ID. Microsoft only shows the secret value once.
You will enter this value in Production Assist as the client secret.

The Certificates & secrets area is where you create and later rotate client secrets.
In the app registration, open:
API permissions
Click:
Add a permission
Select:
Microsoft Graph
Select:
Application permissions
Do not select Delegated permissions. Production Assist runs the sync in the background without a signed-in Microsoft user.

Select Application permissions so the sync can run in the background without a signed-in Microsoft user.
Production Assist needs permission to find the access group and read its members.
Add these Microsoft Graph Application permissions:
User.Read.All
Group.Read.All
GroupMember.Read.All
In the permission search field, type:
group
Expand:
GroupMember
Select:
GroupMember.Read.All
Do not select:
GroupMember.ReadWrite.All

Make sure you select GroupMember.Read.All under GroupMember, not GroupMember.ReadWrite.All.
In the permission search field, type:
user
Expand:
User
Select:
User.Read.All
In the permission search field, type:
group
Expand:
Group
Select:
Group.Read.All
After selecting all three permissions, click:
Add permissions
After adding the permissions, they appear in the configured permissions table.
If your app registration already shows a default delegated permission such as User.Read, you can leave it in place. Production Assist uses User.Read.All, Group.Read.All, and GroupMember.Read.All as Application permissions for the background sync.
Adding permissions is not enough. An administrator must grant tenant-wide consent.
Stay on:
API permissions
Click:
Grant admin consent for <tenant name>
Confirm the consent dialog.
Check the Status column. The permissions should show admin consent granted for the tenant.
If the button is disabled, your account probably does not have enough administrative rights.

The configured permissions view should show User.Read.All, Group.Read.All, and GroupMember.Read.All under Microsoft Graph and let an administrator grant tenant-wide consent.
Production Assist looks for a group with this exact display name:
Azure_APP_Production-Assist
To create or verify the group:
In Microsoft Entra, go to:
Entra ID > Groups
Select:
All groups
Search for:
Azure_APP_Production-Assist
If the group does not exist, click:
New group
Use:
Group type: Security
Group name: Azure_APP_Production-Assist
Add all users who should get access to Production Assist.
Save the group.
Important: Production Assist reads direct group members. Avoid relying on nested groups unless the sync implementation has been changed to support them.
In Production Assist, open User Settings for the organization or tenant, then select Account & Billing. Under Configure an AD Server for authentication, enter these values:
| Production Assist field | Value from Microsoft Entra |
|---|---|
| AD Master Tenant Id | Directory (tenant) ID |
| AD Master Client Id | Application (client) ID |
| AD Master Client Secret | Client secret Value |

When setting up the connection or changing any of its fields, select Save configuration. Production Assist first checks the connection and group preview. If the check succeeds, it saves the configuration and displays the preview. The client secret field is then cleared.
Refresh AD preview retrieves the already saved configuration. Do not use it to check unsaved changes in the fields.
In the preview, verify that the listed users match the direct members of this group:
Azure_APP_Production-Assist
The preview consolidates duplicate email addresses and warns about members without a usable email address. Those members are skipped during synchronization.
After you save the configuration, synchronization starts the next time the server starts and then runs every 20 minutes. There is no manual sync command in the configuration area.
The expected result is:
The group controls automatic enrollment, but removing a user from the Entra group later does not revoke an existing collaborator or license grant. If needed, also remove access in Production Assist under Collaborators or Shared Licence Users. See Share a Pro Teams license and grant project access for the steps.
In the server logs, a successful sync should look similar to:
Fetched <number> users from tenant <tenant-id>
Processed <number> users for tenant <tenant-id>
Updated tenant <production-assist-tenant-id> with <number> users
Other diagnostic log lines may contain names, email addresses, and Entra user IDs. Share server logs only according to your organization's privacy rules, and redact personal data when it is not needed for troubleshooting.
Azure_APP_Production-Assist group.Keep the desktop app open while you complete Microsoft sign-in and any required multi-factor authentication. The desktop app waits for up to five minutes and automatically completes the successful sign-in.
Azure sign-in requires Production Assist to have linked the synchronized Entra account to this Production Assist account. A matching email address alone is not enough if the Entra account does not match the synchronized identity. If sign-in does not start, first check the account and synchronization. See Troubleshooting for other issues.
During Microsoft sign-in, the desktop app automatically checks whether it has finished. A sign-in that is still pending or a temporary limit on polling does not produce repeated network error messages. Complete sign-in in the open browser and keep the desktop app open.
If the attempt has not completed after at most five minutes, start Login with Azure again. Use the newly opened sign-in flow and do not reload an old Microsoft callback page. If a permanent error occurs, the desktop app ends the attempt and displays the error.
The app registration is not yet allowed to issue ID tokens for the hybrid flow used by Production Assist.
Check the following:
Entra ID > App registrations > Production-Assist > Authentication.https://www.production-assist.com/login/azure-redirect
The redirect URI sent by Production Assist does not exactly match the one in the app registration.
Pay particular attention to the scheme, host, path, and any trailing slash. For the production environment, the URI must be exactly:
https://www.production-assist.com/login/azure-redirect
The app does not have the required Microsoft Graph application permissions, or admin consent has not been granted.
Check:
User.Read.All and Group.Read.All are added as Application permissions.GroupMember.Read.All is added as an Application permission.For groups with hidden membership, this configuration is not sufficient: Production Assist does not request the additional Microsoft Graph permission Member.Read.Hidden. Use a group with visible membership for this integration.
Production Assist could not find:
Azure_APP_Production-Assist
Check:
Check:
Azure_APP_Production-Assist.Fetched users and Processed users.If the logs show users fetched but zero users processed, the Microsoft Graph response may not contain usable email information for those users.
Check:
Use at least the Privileged Role Administrator role. Depending on your tenant policy, Global Administrator may be required.
Then reload the app registration and try again.
Client secrets expire. Before the secret expires: