Last date modified: 2025-Nov-21

Purview Sync Application registration issues troubleshooting

In this topic, you can find solutions to common issues when registering the Purview Sync application with Microsoft.

Common issues

Click on any of the scenarios to see the cause of the issue and the resolution.

A Microsoft sign-in warning.

Cause

You have not configured the redirect URI. On the Authentication page, in the section Single-page application, the Redirect URIs does not have a configured URI.

Fix

To resolve this issue:

  1. Copy the redirect URI mentioned in the error message.
  2. Paste the redirect URI to Single-page application.
    You can also create a URI. For more information, see Authentication.
    The single-page application Redirect URIs in Microsoft.
    The single-page application redirect URL with the Relativity URI highlighted.

You can now sign into Microsoft.

Cause

User Client Secret is wrong or expired.

Fix 

Check that you provided Client Secret that is not expired.

To update the client secret:

  1. In RelativityOne, navigate to Purview Sync > Configuration.
  2. If secret is not expired, click Edit Purview Sync configuration.
  3. Update the Client Secret field.
  4. Click Save.

For more information, see Creating a client secret.

The Client Secret field in the Azure Active Directory Application Registration page.

Cause

Missing Global Admin assigned role.
The Grant admin content for Relativity button on the API permissions page.

Fix

To update the missing Global Admin role:

  1. In Azure, navigate to Users.
  2. Search for your user.
  3. Go to Assigned roles and click link next to the text.
    The Assigned Roles count.
  4. Check if you have Global Administrator role.

It might be that you will see information's about Eligible role assignment. In that case, please contact your Azure administrator.

The Global Administrator role on the Administrative Roles page.

Cause

There is an issue with wrong character in URI. Open Developer tools > Console. Repeat reproduction step to check what you logged in. The console window can look like the following image:
The Console in web developer tools.

Fix

To resolve this issue:

  1. Navigate to Purview Sync > Configuration.
  2. Verify if there is no white spaces at the beginning and end of the URI’s.
    The Azure Active Directory Application Registration fields.
  3. Then navigate to App Registration > Find your application > Authentication.
  4. Verify if Web Redirect URIs and Single-page application Redirect URIs contains correct URLs and verify if there are any spaces at the end or beginning of URI.
    • Web Redirect URIs should contain {Company URI}/purview-sync-services/api/v1/AppConfiguration/auth-response.
    • Single-page application Redirect URIs should contain {Company URI}/Relativity/CustomPages/f444a06a-617c-430b-90b2-a112e834b826/ms-auth-popup-redirect.html.

Considerations

Before using Purview Sync, consider the following:

  • Ensure pop-us are not blocked in your browser as this would prevent Microsoft Authentication Library (MSAL) modal from appearing. If your browser is blocking pop-up windows, you will not be able to authorize with Microsoft.
  • If you experience MSAL modal not appearing, or appearing for a short time, when logging in to start import of data in Purview Sync: clear your site data and then log out of Relativity and log in again. If you use Chrome, choose Delete browsing data.
Return to top of the page
Feedback