Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-pim-toc-mvc

Author: rolyon

articles/active-directory/active-directory-saas-app-provisioning.md

@@ -230,7 +230,7 @@ For scenario-based guidance on how to troubleshoot automatic user provisioning,
 
 > [!VIDEO https://www.youtube.com/embed/MAy8s5WSe3A]
 
-For an example step-by-step deployment plan for outbound user provisioning to an application, see the [Identity Deployment Guide for User Provisioning](https://aka.ms/userprovisioningdeploymentplan)/
+For an example step-by-step deployment plan for outbound user provisioning to an application, see the [Identity Deployment Guide for User Provisioning](https://aka.ms/userprovisioningdeploymentplan).
 
 
 ## Related articles

articles/active-directory/active-directory-tou.md

@@ -160,7 +160,7 @@ The following procedure describes how to add a Terms of use language.
 
 1. Select the Terms of use you want to edit.
 
-1. In the the details pane, click the **Languages** tab.
+1. In the details pane, click the **Languages** tab.
 
     ![Add TOU](media/active-directory-tou/languages-tou.png)
 

articles/active-directory/connect/active-directory-aadconnect-upgrade-previous-version.md

@@ -63,7 +63,7 @@ These steps also work to move from Azure AD Sync or a solution with FIM + Azure
 
 ### Use a swing migration to upgrade
 1. If you use Azure AD Connect on both servers and plan to only make a configuration change, make sure that your active server and staging server are both using the same version. That makes it easier to compare differences later. If you're upgrading from Azure AD Sync, then these servers have different versions. If you're upgrading from an older version of Azure AD Connect, it's a good idea to start with the two servers that are using the same version, but it's not required.
-2. If you've made a custom configuration and your staging server doesn't have it, follow the steps under [Move a custom configuration from the active server to the staging server](#move-custom-configuration-from-active-to-staging-server).
+2. If you've made a custom configuration and your staging server doesn't have it, follow the steps under [Move a custom configuration from the active server to the staging server](#move-a-custom-configuration-from-the-active-server-to-the-staging-server).
 3. If you're upgrading from an earlier release of Azure AD Connect, upgrade the staging server to the latest version. If you're moving from Azure AD Sync, then install Azure AD Connect on your staging server.
 4. Let the sync engine run full import and full synchronization on your staging server.
 5. Verify that the new configuration didn't cause any unexpected changes by using the steps under "Verify" in [Verify the configuration of a server](active-directory-aadconnectsync-operations.md#verify-the-configuration-of-a-server). If something isn't as expected, correct it, run the import and sync, and verify the data until it looks good, by following the steps.

articles/active-directory/managed-service-identity/qs-configure-template-windows-vm.md

@@ -353,7 +353,7 @@ If you have a VM that no longer needs a managed service identity:
 
 1. Whether you sign in to Azure locally or via the Azure portal, use an account that is associated with the Azure subscription that contains the VM.
 
-2. Load the template into an [editor](#azure-resource-manager-templates) and locate the `Microsoft.Compute/virtualMachines` resource of interest within the `resources` section. If you have a VM that only has user assigned identity, you can disable it by changing the the identity type to `None`.
+2. Load the template into an [editor](#azure-resource-manager-templates) and locate the `Microsoft.Compute/virtualMachines` resource of interest within the `resources` section. If you have a VM that only has user assigned identity, you can disable it by changing the identity type to `None`.
 
    The following example shows you how remove all user assigned identities from a VM with no system assigned identities:
 
@@ -376,7 +376,7 @@ If you have a VM that no longer needs a managed service identity:
 
    **Microsoft.Compute/virtualMachines API version 2017-12-01**
 
-   To remove a a single user assigned identity from a VM, remove it from the `identityIds` array.
+   To remove a single user assigned identity from a VM, remove it from the `identityIds` array.
 
    If you have a system assigned identity, keep it in the in the `type` value under the `identity` value.
 

articles/active-directory/managed-service-identity/qs-configure-template-windows-vmss.md

@@ -318,7 +318,7 @@ If you have a virtual machine scale set that no longer needs a managed service i
 
 1. Whether you sign in to Azure locally or via the Azure portal, use an account that is associated with the Azure subscription that contains the virtual machine scale set.
 
-2. Load the template into an [editor](#azure-resource-manager-templates) and locate the `Microsoft.Compute/virtualMachineScaleSets` resource of interest within the `resources` section. If you have a virtual machine scale set that only has user assigned identity, you can disable it by changing the the identity type to `None`.
+2. Load the template into an [editor](#azure-resource-manager-templates) and locate the `Microsoft.Compute/virtualMachineScaleSets` resource of interest within the `resources` section. If you have a virtual machine scale set that only has user assigned identity, you can disable it by changing the identity type to `None`.
 
    The following example shows you how remove all user assigned identities from a VM with no system assigned identities:
 
@@ -335,7 +335,7 @@ If you have a virtual machine scale set that no longer needs a managed service i
 
    **Microsoft.Compute/virtualMachineScaleSets API version 2018-06-01**
 
-   To remove a a single user assigned identity from a virtual machine scale set, remove it from the `userAssignedIdentities` dictionary.
+   To remove a single user assigned identity from a virtual machine scale set, remove it from the `userAssignedIdentities` dictionary.
 
    If you have a system assigned identity, keep it in the in the `type` value under the `identity` value.
 

articles/active-directory/saas-apps/klue-tutorial.md

@@ -13,7 +13,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 07/13/2017
+ms.date: 08/28/2018
 ms.author: jeedes
 
 ---
@@ -45,13 +45,15 @@ To test the steps in this tutorial, you should follow these recommendations:
 - If you don't have an Azure AD trial environment, you can get a one-month trial [here](https://azure.microsoft.com/pricing/free-trial/).
 
 ## Scenario description
+
 In this tutorial, you test Azure AD single sign-on in a test environment. 
 The scenario outlined in this tutorial consists of two main building blocks:
 
 1. Adding Klue from the gallery
-1. Configuring and testing Azure AD single sign-on
+2. Configuring and testing Azure AD single sign-on
 
 ## Adding Klue from the gallery
+
 To configure the integration of Klue into Azure AD, you need to add Klue from the gallery to your list of managed SaaS apps.
 
 **To add Klue from the gallery, perform the following steps:**
@@ -60,23 +62,24 @@ To configure the integration of Klue into Azure AD, you need to add Klue from th
 
 	![Active Directory][1]
 
-1. Navigate to **Enterprise applications**. Then go to **All applications**.
+2. Navigate to **Enterprise applications**. Then go to **All applications**.
 
 	![Applications][2]
-	
-1. To add new application, click **New application** button on the top of dialog.
+
+3. To add new application, click **New application** button on the top of dialog.
 
 	![Applications][3]
 
-1. In the search box, type **Klue**.
+4. In the search box, type **Klue**.
 
 	![Creating an Azure AD test user](./media/klue-tutorial/tutorial_klue_search.png)
 
-1. In the results panel, select **Klue**, and then click **Add** button to add the application.
+5. In the results panel, select **Klue**, and then click **Add** button to add the application.
 
 	![Creating an Azure AD test user](./media/klue-tutorial/tutorial_klue_addfromgallery.png)
 
 ##  Configuring and testing Azure AD single sign-on
+
 In this section, you configure and test Azure AD single sign-on with Klue based on a test user called "Britta Simon".
 
 For single sign-on to work, Azure AD needs to know what the counterpart user in Klue is to a user in Azure AD. In other words, a link relationship between an Azure AD user and the related user in Klue needs to be established.
@@ -86,10 +89,10 @@ In Klue, assign the value of the **user name** in Azure AD as the value of the *
 To configure and test Azure AD single sign-on with Klue, you need to complete the following building blocks:
 
 1. **[Configuring Azure AD Single Sign-On](#configuring-azure-ad-single-sign-on)** - to enable your users to use this feature.
-1. **[Creating an Azure AD test user](#creating-an-azure-ad-test-user)** - to test Azure AD single sign-on with Britta Simon.
-1. **[Creating a Klue test user](#creating-a-klue-test-user)** - to have a counterpart of Britta Simon in Klue that is linked to the Azure AD representation of user.
-1. **[Assigning the Azure AD test user](#assigning-the-azure-ad-test-user)** - to enable Britta Simon to use Azure AD single sign-on.
-1. **[Testing Single Sign-On](#testing-single-sign-on)** - to verify whether the configuration works.
+2. **[Creating an Azure AD test user](#creating-an-azure-ad-test-user)** - to test Azure AD single sign-on with Britta Simon.
+3. **[Creating a Klue test user](#creating-a-klue-test-user)** - to have a counterpart of Britta Simon in Klue that is linked to the Azure AD representation of user.
+4. **[Assigning the Azure AD test user](#assigning-the-azure-ad-test-user)** - to enable Britta Simon to use Azure AD single sign-on.
+5. **[Testing Single Sign-On](#testing-single-sign-on)** - to verify whether the configuration works.
 
 ### Configuring Azure AD single sign-on
 
@@ -101,39 +104,39 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
 
 	![Configure Single Sign-On][4]
 
-1. On the **Single sign-on** dialog, select **Mode** as	**SAML-based Sign-on** to enable single sign-on.
- 
+2. On the **Single sign-on** dialog, select **Mode** as	**SAML-based Sign-on** to enable single sign-on.
+
 	![Configure Single Sign-On](./media/klue-tutorial/tutorial_klue_samlbase.png)
 
-1. On the **Klue Domain and URLs** section, If you wish to configure the application in **IDP** initiated mode:
+3. On the **Klue Domain and URLs** section, If you wish to configure the application in **IDP** initiated mode:
 
 	![Configure Single Sign-On](./media/klue-tutorial/tutorial_klue_url1.png)
 
     a. In the **Identifier** textbox, type a URL using the following pattern: `urn:klue:<Customer ID>`
 
 	b. In the **Reply URL** textbox, type a URL using the following pattern: `https://app.klue.com/account/auth/saml/<Customer UUID>/callback`
 
-1. Check **Show advanced URL settings**. If you wish to configure the application in **SP** initiated mode:
+4. Check **Show advanced URL settings**. If you wish to configure the application in **SP** initiated mode:
 
 	![Configure Single Sign-On](./media/klue-tutorial/tutorial_klue_url2.png)
 
     In the **Sign-on URL** textbox, type a URL using the following pattern: `https://app.klue.com/account/auth/saml/<Customer UUID>/`
-	 
-	> [!NOTE] 
+
+	> [!NOTE]
 	> These values are not real. Update these values with the actual Reply URL, Identifier, and Sign-On URL. Contact [Klue Client support team](mailto:[email protected]) to get these values.
 
-1. The Klue application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. You can manage the values of these attributes from the "**User Attributes**" section on application integration page. 
+5. The Klue application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. You can manage the values of these attributes from the "**User Attributes**" section on application integration page.
 
 	![Configure Single Sign-On](./media/klue-tutorial/attribute.png)
 
-1. In the **User Attributes** section on the **Single sign-on** dialog, configure SAML token attribute as shown in the preceding image and perform the following steps:
-	
+6. In the **User Attributes** section on the **Single sign-on** dialog, configure SAML token attribute as shown in the preceding image and perform the following steps:
+
 	| Attribute Name      | Attribute Value      |
 	| ------------------- | -------------------- |
 	| first_name          | user.givenname |
 	| last_name 		  | user.surname |
 	| email               | user.userprincipalname|
-	
+
 	a. Click **Add attribute** to open the **Add Attribute** dialog.
 
 	![Configure Single Sign-On](./media/klue-tutorial/tutorial_attribute_04.png)
@@ -143,27 +146,28 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
 	b. In the **Name** textbox, type the attribute name shown for that row.
 
 	c. From the **Value** list, type the attribute value shown for that row.
-	
+
 	d. Click **Ok**.
 
-1. On the **SAML Signing Certificate** section, click **Certificate(Base64)** and then save the certificate file on your computer.
+	> [!NOTE]
+	> Please leave the **Namespace** value blank.
+
+7. On the **SAML Signing Certificate** section, click **Certificate(Base64)** and then save the certificate file on your computer.
 
 	![Configure Single Sign-On](./media/klue-tutorial/tutorial_klue_certificate.png) 
 
-1. Click **Save** button.
+8. Click **Save** button.
 
 	![Configure Single Sign-On](./media/klue-tutorial/tutorial_general_400.png)
-	
-1. On the **Klue Configuration** section, click **Configure Klue** to open **Configure sign-on** window. Copy the **SAML Entity ID and SAML Single Sign-On Service URL** from the **Quick Reference section.**
 
-	![Configure Single Sign-On](./media/klue-tutorial/tutorial_klue_configure.png) 
+9. On the **Klue Configuration** section, click **Configure Klue** to open **Configure sign-on** window. Copy the **SAML Entity ID and SAML Single Sign-On Service URL** from the **Quick Reference section.**
 
-1. To configure single sign-on on **Klue** side, you need to send the downloaded **Certificate(Base64), SAML Single Sign-On Service URL, and SAML Entity ID** to [Klue support team](mailto:support@klue.com).
+	![Configure Single Sign-On](./media/klue-tutorial/tutorial_klue_configure.png) 
 
-> [!TIP]
-> You can now read a concise version of these instructions inside the [Azure portal](https://portal.azure.com), while you are setting up the app!  After adding this app from the **Active Directory > Enterprise Applications** section, simply click the **Single Sign-On** tab and access the embedded documentation through the **Configuration** section at the bottom. You can read more about the embedded documentation feature here: [Azure AD embedded documentation]( https://go.microsoft.com/fwlink/?linkid=845985)
+10. To configure single sign-on on **Klue** side, you need to send the downloaded **Certificate(Base64), SAML Single Sign-On Service URL, and SAML Entity ID** to [Klue support team](mailto:[email protected]).
 
 ### Creating an Azure AD test user
+
 The objective of this section is to create a test user in the Azure portal called Britta Simon.
 
 ![Create Azure AD User][100]
@@ -172,18 +176,18 @@ The objective of this section is to create a test user in the Azure portal calle
 
 1. In the **Azure portal**, on the left navigation pane, click **Azure Active Directory** icon.
 
-	![Creating an Azure AD test user](./media/klue-tutorial/create_aaduser_01.png) 
+	![Creating an Azure AD test user](./media/klue-tutorial/create_aaduser_01.png)
+
+2. To display the list of users, go to **Users and groups** and click **All users**.
+
+	![Creating an Azure AD test user](./media/klue-tutorial/create_aaduser_02.png)
+
+3. To open the **User** dialog, click **Add** on the top of the dialog.
 
-1. To display the list of users, go to **Users and groups** and click **All users**.
-	
-	![Creating an Azure AD test user](./media/klue-tutorial/create_aaduser_02.png) 
+	![Creating an Azure AD test user](./media/klue-tutorial/create_aaduser_03.png)
 
-1. To open the **User** dialog, click **Add** on the top of the dialog.
- 
-	![Creating an Azure AD test user](./media/klue-tutorial/create_aaduser_03.png) 
+4. On the **User** dialog page, perform the following steps:
 
-1. On the **User** dialog page, perform the following steps:
- 
 	![Creating an Azure AD test user](./media/klue-tutorial/create_aaduser_04.png) 
 
     a. In the **Name** textbox, type **BrittaSimon**.
@@ -193,13 +197,13 @@ The objective of this section is to create a test user in the Azure portal calle
 	c. Select **Show Password** and write down the value of the **Password**.
 
     d. Click **Create**.
- 
+
 ### Creating a Klue test user
 
 The objective of this section is to create a user called Britta Simon in Klue. Klue supports just-in-time provisioning, which is by default enabled. There is no action item for you in this section. A new user is created during an attempt to access Klue if it doesn't exist yet.
 
->[!Note]
->If you need to create a user manually, Contact [Klue support team](mailto:[email protected]).
+> [!Note]
+> If you need to create a user manually, Contact [Klue support team](mailto:[email protected]).
 
 ### Assigning the Azure AD test user
 
@@ -213,24 +217,24 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 
 	![Assign User][201] 
 
-1. In the applications list, select **Klue**.
+2. In the applications list, select **Klue**.
 
 	![Configure Single Sign-On](./media/klue-tutorial/tutorial_klue_app.png) 
 
-1. In the menu on the left, click **Users and groups**.
+3. In the menu on the left, click **Users and groups**.
 
-	![Assign User][202] 
+	![Assign User][202]
 
-1. Click **Add** button. Then select **Users and groups** on **Add Assignment** dialog.
+4. Click **Add** button. Then select **Users and groups** on **Add Assignment** dialog.
 
 	![Assign User][203]
 
-1. On **Users and groups** dialog, select **Britta Simon** in the Users list.
+5. On **Users and groups** dialog, select **Britta Simon** in the Users list.
+
+6. Click **Select** button on **Users and groups** dialog.
 
-1. Click **Select** button on **Users and groups** dialog.
+7. Click **Assign** button on **Add Assignment** dialog.
 
-1. Click **Assign** button on **Add Assignment** dialog.
-	
 ### Testing single sign-on
 
 In this section, you test your Azure AD single sign-on configuration using the Access Panel.
@@ -243,8 +247,6 @@ For more information about the Access Panel, see [Introduction to the Access
 * [List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory](tutorial-list.md)
 * [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
 
-
-
 <!--Image references-->
 
 [1]: ./media/klue-tutorial/tutorial_general_01.png
@@ -257,5 +259,4 @@ For more information about the Access Panel, see [Introduction to the Access
 [200]: ./media/klue-tutorial/tutorial_general_200.png
 [201]: ./media/klue-tutorial/tutorial_general_201.png
 [202]: ./media/klue-tutorial/tutorial_general_202.png
-[203]: ./media/klue-tutorial/tutorial_general_203.png
-
+[203]: ./media/klue-tutorial/tutorial_general_203.png