Defining Dynamics Cloud Office 365 instances

Prerequisites

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 #

  1. Log in to the Quality Clouds portal at https://portal.qualityclouds.com/.
  2. Go to Account → Instances.
  3. Select the Office 365 tab (if you use several SaaS platforms with Quality Clouds), and click the Add button.
  4. Select the Project this instance belongs to (or create a new one).
  5. 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
  6. Click Save.

→ To test connectivity and launch your first scan #

  1. From the Instances list, click the connectivity icon (the plug 🔌) on your instance’s row.
  2. 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).
  3. Once connectivity succeeds, go to Launch Scan → Office 365 tab.
  4. Find your instance (filter by Description if needed), and it should show as Scanning with a Full scan running.

  #

→ Configure the Quality Gates #

  1. When setting or editing an instance, click on the ‘Quality Gates’ tab.
  2. Enable the Quality Gates toggle.
  3. Add the Activation Date.
  4. Configure the Blocking rules table and smart tagging.
  5. Click ‘Save’.

 

Click here to learn how Quality Gates work.

#

→ Configure the Peer Review #

  1. When setting or editing an instance, click on the ‘Peer Review’ tab.
  2. Enable the Peer Review toggle.
  3. Select when to get notified when Peer Reviews are pending: None, Daily, Weekly, or Monthly.
  4. In the Peer Review Workflow section, select ‘Write Off assignation’:
    • Manual Assign
    • Auto Assign
    • Developer Assign
  5. 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.
  6. Enable or disable the Source Code toggle.
  7. Click ‘Save’.

    Was it helpful ?