create atmos tutorial-5

Author: v-missam

articles/active-directory/saas-apps/atmos-provisioning-tutorial.md

@@ -42,13 +42,13 @@ The scenario outlined in this tutorial assumes that you already have the followi
 
 ## Step 2. Configure Atmos to support provisioning with Azure AD
 
-* Log in to the [Management Console](https://auth.axissecurity.com/).
-* Navigate to **Settings**-> **Identity Providers** screen.
-* Hover over the **Azure Identity Provider** and select **edit**.
-* Navigate to **Advanced Settings**.
-* Navigate to **User Auto-Provisioning (SCIM)**. 
-* Click **Generate new token**.
-* Copy the **SCIM Service Provider Endpoint** and **SCIM Provisioning Token** and paste them into a text editor. You need them for Step 5.
+1. Log in to the [Management Console](https://auth.axissecurity.com/).
+1. Navigate to **Settings**-> **Identity Providers** screen.
+1. Hover over the **Azure Identity Provider** and select **edit**.
+1. Navigate to **Advanced Settings**.
+1. Navigate to **User Auto-Provisioning (SCIM)**. 
+1. Click **Generate new token**.
+1. Copy the **SCIM Service Provider Endpoint** and **SCIM Provisioning Token** and paste them into a text editor. You need them for Step 5.
 
 ## Step 3. Add Atmos from the Azure AD application gallery
 
@@ -71,27 +71,27 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
 
-	![Enterprise applications blade](common/enterprise-applications.png)
+	![Screenshot of enterprise applications blade.](common/enterprise-applications.png)
 
 1. In the applications list, select **Atmos**.
 
-	![The Atmos link in the Applications list](common/all-applications.png)
+	![Screenshot of the Atmos link in the Applications list.](common/all-applications.png)
 
 1. Select the **Provisioning** tab.
 
-	![Provisioning tab](common/provisioning.png)
+	![Screenshot of Provisioning tab.](common/provisioning.png)
 
 1. Set the **Provisioning Mode** to **Automatic**.
 
-	![Provisioning tab automatic](common/provisioning-automatic.png)
+	![Screenshot of Provisioning tab automatic.](common/provisioning-automatic.png)
 
 1. In the **Admin Credentials** section, paste the **SCIM Service Provider Endpoint** obtained from the Axis SCIM configuration (step 2) in Tenant URL, and paste the **SCIM Provisioning Token** obtained from the Axis SCIM configuration (step 2) in **Secret Token**. Click **Test Connection** to ensure Azure AD can connect to Atmos. If the connection fails, contact Axis to check your account setup.
 
- 	![Token](common/provisioning-testconnection-tenanturltoken.png)
+ 	![Screenshot of Token.](common/provisioning-testconnection-tenanturltoken.png)
 
 1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
 
-	![Notification Email](common/provisioning-notification-email.png)
+	![Screenshot of Notification Email.](common/provisioning-notification-email.png)
 
 1. Select **Save**.
 
@@ -125,15 +125,15 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 1. To enable the Azure AD provisioning service for Atmos, change the **Provisioning Status** to **On** in the **Settings** section.
 
-	![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
+	![Screenshot of Provisioning Status Toggled On.](common/provisioning-toggle-on.png)
 
 1. Define the users and groups that you would like to provision to Atmos by choosing the appropriate values in **Scope** in the **Settings** section.
 
-	![Provisioning Scope](common/provisioning-scope.png)
+	![Screenshot of Provisioning Scope.](common/provisioning-scope.png)
 
 1. When you're ready to provision, click **Save**.
 
-	![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
+	![Screenshot of Saving Provisioning Configuration.](common/provisioning-configuration-save.png)
 
 This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to execute than next cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.