Prerequisites
- Login credentials to the Quality Clouds portal – https://portal.qualityclouds.com/
- The Tenant ID, Client ID, and Client Secret from Setting up Office 365 instance
- (Dynamics 365 only) The Application User already created in your environment — see Step 1a in Setting up Office 365 instance
Setting up your instances #
In order to be able to scan your instances, you need to point Quality Clouds to them.
→ To create an instance in Quality Clouds #
- Log in to the Quality Clouds portal at https://portal.qualityclouds.com/.
- Go to Account → Instances.
- Select the Office 365 tab (if you use several SaaS platforms with Quality Clouds), and click the Add button.
- Select the Project this instance belongs to (or create a new one).
- Select Microsoft Dynamics Cloud, and fill in the following information:
- Description — short and meaningful description of the instance. For example:
MyCompany UAT - Environment — environment type of the instance, used to add descriptive context
- URL — URL of your Dynamics 365 environment (e.g.
https://yourorg.crm11.dynamics.com, without a trailing slash). - Tenant ID — identifier for the org in Azure (Directory tenant ID)
- Client ID — the application identifier for the authenticator you registered, used to access the instance
- Client Secret — the secret’s Value (not Secret ID) generated for that authenticator application, similar to a password
- Go-live Date — date on which the instance first went live; serves as a baseline for org changes
- Tags — use tags to add specific information for better instance recognition
- Persist APP API Key Emails — leave enabled unless you have a specific reason to disable it
- Description — short and meaningful description of the instance. For example:
- Click Save.

→ To test connectivity and launch your first scan #
- From the Instances list, click the connectivity icon (the plug 🔌) on your instance’s row.
- If the check fails, double-check that you copied the Client Secret’s Value, not its Secret ID, and that admin consent for the API permissions was granted in Azure (it can take a few minutes to propagate after granting it).
- Once connectivity succeeds, go to Launch Scan → Office 365 tab.
- Find your instance (filter by Description if needed), and it should show as Scanning with a Full scan running.

#
→ Configure the Quality Gates #
- When setting or editing an instance, click on the ‘Quality Gates’ tab.
- Enable the Quality Gates toggle.
- Add the Activation Date.
- Configure the Blocking rules table and smart tagging.
- Click ‘Save’.
Click here to learn how Quality Gates work.
#
→ Configure the Peer Review #
- When setting or editing an instance, click on the ‘Peer Review’ tab.
- Enable the Peer Review toggle.
- Select when to get notified when Peer Reviews are pending: None, Daily, Weekly, or Monthly.
- In the Peer Review Workflow section, select ‘Write Off assignation’:
- Manual Assign
- Auto Assign
- Developer Assign
- Select the Default assignee email on the dropdown menu. Enable it if you want the default assignee to be notified when a write-off is assigned.
- Enable or disable the Source Code toggle.
- Click ‘Save’.
