Configure your Office 365 instance so that it can be scanned by Quality Clouds. This step ensures you stay in control of the data Quality Clouds accesses in your instance.

You can use this same procedure to connect Dynamics 365 (Dataverse) environments. Follow the extra steps outlined below for Dynamics.

Before you start, make sure you have:

• An account with permission to create App Registrations in Azure AD.
• An account with permission to grant admin consent on API permissions in Azure AD. In many organizations, these are different people. Confirm that you have access to both, or a contact who can grant consent for you.
• (Dynamics 365 only) Access to the Power Platform admin center for the target environment.

 

 

Step 1: Create a new App registration #

Quality Clouds connects to Office 365 instances through an app registration, which needs to be defined in your Azure Active Directory.

 

→ To create a new App Registration #

1. Log into the Microsoft Azure administration console at https://portal.azure.com.
2. Go to Azure Active Directory → App registrations → New registration.
3. Fill in the Register an application form, and choose “Accounts in this organizational directory only (Single tenant)” for Supported Account Types. Leave the Redirect URI empty.
4. Click Register.

 

 

1. Go to API permissions → Add a permission, and assign the following API permissions (of type Application permissions):
   • Microsoft Graph
     • AuditLog.Read.All
     • Directory.Read.All
     • Files.Read.All
     • Group.Read.All
     • Reports.Read.All
     • Sites.Read.All
     • User.Read.All
2. (Only if you’re setting up Dynamics CRM) Add the following API permission:
   • Dynamics CRM: user_impersonation. Note that Azure only offers this permission as Delegated, not Application. This is expected.

 

All of these are read-only permissions; Quality Clouds will not modify data in your Office 365 or Dynamics 365 instance.

7. Click Grant admin consent for [your tenant], and confirm. If the button is greyed out or you get a permissions error, you don’t have the required Azure AD role (Global Administrator or Cloud Application Administrator)
8. Confirm every permission’s Status shows a green checkmark before continuing.

 

 

Step 1a (only for Dynamics CRM): Create an application user in Dynamics #

The classic “Application Users” view under Settings → Security → Users in the legacy Dynamics 365 web client is being deprecated by Microsoft and may already be unavailable in your environment. Use the Power Platform admin center instead:

 

→ To create an application user in Dynamics #

1. Log in to the Power Platform admin center at https://admin.powerplatform.microsoft.com/.
2. Go to Environments and select the Dynamics environment you want to create the user for.
3. Go to Settings → Users + permissions → Application users. (If you land on the general Users list instead, look for the link “Looking for application users? Click here to go to the app users list.”)

 

 

1. Click + New app user.
2. Click + Add an app, and search for the app you registered in Step 1 by name.
3. Set the Business unit (your root business unit if unsure).
4. Assign a Security role — System Administrator for testing; for production, use the least-privileged role that covers what needs to be scanned.
5. Click Save. Note down the app’s Client ID (already known from Step 2 below) — this confirms the Application User is linked correctly.

 

Step 2: Generate and note down the client secret #

In order to configure the O365 environment in Quality Clouds, you need an authentication token (API secret) with the following attributes of the newly registered app:

• Application (client) ID
• Directory (tenant) ID

 

→ To obtain the authentication token (API secret) #

1. In the Microsoft Azure administration console at https://portal.azure.com, go to Azure Active Directory → App registrations → (choose your newly registered Quality Clouds app).
2. Go to Certificates & secrets → New Client Secret. Give it a description and expiration, then click Add.
3. Copy the value in the “Value” column immediately — not the “Secret ID” column. The Value is the actual credential Quality Clouds needs, and it’s shown only once; if you navigate away without copying it, you’ll need to generate a new one. Copying the Secret ID by mistake is the most common cause of failed connectivity tests later on.
4. Note down the generated Application (client) ID and Directory (tenant) ID, both visible on the app’s Overview page, to use in the setup of your O365 environment in Quality Clouds.

 

You can now move to Setting up Quality Clouds environment for Office 365.