Merge pull request #9163 from MicrosoftDocs/FromPrivateRepo

From private repo

Author: huypub

.openpublishing.redirection.json

@@ -660,16 +660,6 @@
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-nonaad",
             "redirect_document_id": true
         },
-        {
-            "source_path": "articles/active-directory/managed-service-identity/tutorial-vm-windows-access-storage.md",
-            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-storage",
-            "redirect_document_id": false
-        },
-        {
-            "source_path": "articles/active-directory/managed-service-identity/tutorial-linux-vm-access-storage.md",
-            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-storage-sas",
-            "redirect_document_id": true
-        },
         {
             "source_path": "articles/active-directory/msi-tutorial-linux-vm-access-storage-sas.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-storage-sas",
@@ -4405,6 +4395,21 @@
             "redirect_url": "/azure/data-lake-analytics/data-lake-analytics-u-sql-get-started",
             "redirect_document_id": false
         },
+        {
+            "source_path": "articles/data-lake-analytics/data-lake-analytics-u-sql-develop-assemblies.md",
+            "redirect_url": "/azure/data-lake-analytics/data-lake-analytics-data-lake-tools-for-vscode",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/data-lake-analytics/data-lake-analytics-get-started-rest-api.md",
+            "redirect_url": "/rest/api/datalakeanalytics/",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/data-lake-analytics/data-lake-analytics-get-started-java-sdk.md",
+            "redirect_url": "/azure/data-lake-analytics/data-lake-analytics-manage-use-java-sdk",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/dotnet/index.md",
             "redirect_url": "/dotnet/azure/",
@@ -21866,11 +21871,19 @@
             "redirect_document_id": true
         },
         {
-            "source_path": "articles/application-gateway/application-gateway-ilb.md",
+            "source_path": "articles/cosmos-db/table-storage-how-to-use-powershell.md",
+            "redirect_url": "/azure/storage/tables/table-storage-how-to-use-powershell",
+            "redirect_document_id": true
+        },
+        {   "source_path": "articles/application-gateway/application-gateway-ilb.md",
             "redirect_url": "/azure/application-gateway/application-gateway-ilb-arm",
             "redirect_document_id": false
-        }
-        ,
+        },
+        {
+            "source_path": "articles/application-gateway/create-waf-portal.md",
+            "redirect_url": "/azure/application-gateway/application-gateway-web-application-firewall-portal",
+            "redirect_document_id": false
+        },
 	    {
             "source_path": "articles/active-directory/active-directory-conditional-access-vpn-connectivity-windows10.md",
             "redirect_url": "https://docs.microsoft.com/en-us/windows-server/remote/remote-access/vpn/always-on-vpn/deploy/always-on-vpn-deploy",
@@ -21889,4 +21902,4 @@
             "redirect_document_id": true
         }
     ]
-}
+}

articles/active-directory/active-directory-saas-foreseecxsuite-tutorial.md

@@ -0,0 +1,229 @@
+---
+title: 'Tutorial: Azure Active Directory integration with ForeSee CX Suite | Microsoft Docs'
+description: Learn how to configure single sign-on between Azure Active Directory and ForeSee CX Suite.
+services: active-directory
+documentationCenter: na
+author: jeevansd
+manager: femila
+ms.reviewer: joflore
+
+ms.assetid: 5f4b7830-6186-4d17-b77b-504d4192bfde
+ms.service: active-directory
+ms.workload: identity
+ms.tgt_pltfrm: na
+ms.devlang: na
+ms.topic: article
+ms.date: 05/24/2018
+ms.author: jeedes
+
+---
+# Tutorial: Azure Active Directory integration with ForeSee CX Suite
+
+In this tutorial, you learn how to integrate ForeSee CX Suite with Azure Active Directory (Azure AD).
+
+Integrating ForeSee CX Suite with Azure AD provides you with the following benefits:
+
+- You can control in Azure AD who has access to ForeSee CX Suite.
+- You can enable your users to automatically get signed-on to ForeSee CX Suite (Single Sign-On) with their Azure AD accounts.
+- You can manage your accounts in one central location - the Azure portal.
+
+If you want to know more details about SaaS app integration with Azure AD, see [what is application access and single sign-on with Azure Active Directory](active-directory-appssoaccess-whatis.md).
+
+## Prerequisites
+
+To configure Azure AD integration with ForeSee CX Suite, you need the following items:
+
+- An Azure AD subscription
+- A ForeSee CX Suite single sign-on enabled subscription
+
+> [!NOTE]
+> To test the steps in this tutorial, we do not recommend using a production environment.
+
+To test the steps in this tutorial, you should follow these recommendations:
+
+- Do not use your production environment, unless it is necessary.
+- If you don't have an Azure AD trial environment, you can [get a one-month trial](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 ForeSee CX Suite from the gallery
+2. Configuring and testing Azure AD single sign-on
+
+## Adding ForeSee CX Suite from the gallery
+To configure the integration of ForeSee CX Suite into Azure AD, you need to add ForeSee CX Suite from the gallery to your list of managed SaaS apps.
+
+**To add ForeSee CX Suite from the gallery, perform the following steps:**
+
+1. In the **[Azure portal](https://portal.azure.com)**, on the left navigation panel, click **Azure Active Directory** icon.
+
+	![The Azure Active Directory button][1]
+
+2. Navigate to **Enterprise applications**. Then go to **All applications**.
+
+	![The Enterprise applications blade][2]
+
+3. To add new application, click **New application** button on the top of dialog.
+
+	![The New application button][3]
+
+4. In the search box, type **ForeSee CX Suite**, select **ForeSee CX Suite** from result panel then click **Add** button to add the application.
+
+	![ForeSee CX Suite in the results list](./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_foreseecxsuite_addfromgallery.png)
+
+## Configure and test Azure AD single sign-on
+
+In this section, you configure and test Azure AD single sign-on with ForeSee CX Suite based on a test user called "Britta Simon".
+
+For single sign-on to work, Azure AD needs to know what the counterpart user in ForeSee CX Suite is to a user in Azure AD. In other words, a link relationship between an Azure AD user and the related user in ForeSee CX Suite needs to be established.
+
+To configure and test Azure AD single sign-on with ForeSee CX Suite, you need to complete the following building blocks:
+
+1. **[Configure Azure AD Single Sign-On](#configure-azure-ad-single-sign-on)** - to enable your users to use this feature.
+2. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with Britta Simon.
+3. **[Create a ForeSee CX Suite test user](#create-a-foresee-cx-suite-test-user)** - to have a counterpart of Britta Simon in ForeSee CX Suite that is linked to the Azure AD representation of user.
+4. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable Britta Simon to use Azure AD single sign-on.
+5. **[Test single sign-on](#test-single-sign-on)** - to verify whether the configuration works.
+
+### Configure Azure AD single sign-on
+
+In this section, you enable Azure AD single sign-on in the Azure portal and configure single sign-on in your ForeSee CX Suite application.
+
+**To configure Azure AD single sign-on with ForeSee CX Suite, perform the following steps:**
+
+1. In the Azure portal, on the **ForeSee CX Suite** application integration page, click **Single sign-on**.
+
+	![Configure single sign-on link][4]
+
+2. On the **Single sign-on** dialog, select **Mode** as **SAML-based Sign-on** to enable single sign-on.
+
+	![Single sign-on dialog box](./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_foreseecxsuite_samlbase.png)
+
+3. On the **ForeSee CX Suite Domain and URLs** section, if you have **Service Provider metadata file**, perform the following steps:
+
+	![ForeSee CX Suite Domain and URLs single sign-on information](./media/active-directory-saas-foreseecxsuite-tutorial/upload.png)
+
+	a. Click **Upload metadata file**.
+
+	![ForeSee CX Suite Domain and URLs single sign-on information](./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_foreseen_uploadconfig.png)
+
+	b. Click on **folder logo** to select the metadata file and click **Upload**.
+
+	c. After successfull completion of uploading **Service Provider metadata file** the **Identifier** value get auto populated in **ForeSee CX Suite Domain and URLs** section textbox as shown below:
+
+	![ForeSee CX Suite Domain and URLs single sign-on information](./media/active-directory-saas-foreseecxsuite-tutorial/urlupload.png)
+
+4. If you dont have **Service Provider metadata file**, perform the following steps:
+
+	![ForeSee CX Suite Domain and URLs single sign-on information](./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_foreseecxsuite_url.png)
+
+    a. In the **Sign-on URL** textbox, type the URL: `https://cxsuite.foresee.com/`
+
+	b. In the **Identifier** textbox, type a URL using the following pattern: `https://www.okta.com/saml2/service-provider/<UniqueID>`
+
+	> [!NOTE]
+	> The Identifier value is not real. Update this value with the actual Identifier. Contact [ForeSee CX Suite Client support team](mailto:[email protected]) to get this value.
+
+5. On the **SAML Signing Certificate** section, click **Metadata XML** and then save the metadata file on your computer.
+
+	![The Certificate download link](./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_foreseecxsuite_certificate.png)
+
+6. Click **Save** button.
+
+	![Configure Single Sign-On Save button](./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_400.png)
+
+7. To configure single sign-on on **ForeSee CX Suite** side, you need to send the downloaded **Metadata XML** to [ForeSee CX Suite support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
+
+### Create an Azure AD test user
+
+The objective of this section is to create a test user in the Azure portal called Britta Simon.
+
+   ![Create an Azure AD test user][100]
+
+**To create a test user in Azure AD, perform the following steps:**
+
+1. In the Azure portal, in the left pane, click the **Azure Active Directory** button.
+
+    ![The Azure Active Directory button](./media/active-directory-saas-foreseecxsuite-tutorial/create_aaduser_01.png)
+
+2. To display the list of users, go to **Users and groups**, and then click **All users**.
+
+    ![The "Users and groups" and "All users" links](./media/active-directory-saas-foreseecxsuite-tutorial/create_aaduser_02.png)
+
+3. To open the **User** dialog box, click **Add** at the top of the **All Users** dialog box.
+
+    ![The Add button](./media/active-directory-saas-foreseecxsuite-tutorial/create_aaduser_03.png)
+
+4. In the **User** dialog box, perform the following steps:
+
+    ![The User dialog box](./media/active-directory-saas-foreseecxsuite-tutorial/create_aaduser_04.png)
+
+    a. In the **Name** box, type **BrittaSimon**.
+
+    b. In the **User name** box, type the email address of user Britta Simon.
+
+    c. Select the **Show Password** check box, and then write down the value that's displayed in the **Password** box.
+
+    d. Click **Create**.
+
+### Create a ForeSee CX Suite test user
+
+In this section, you create a user called Britta Simon in ForeSee CX Suite. Work with [ForeSee CX Suite support team](mailto:[email protected]) to add the users or the domain which is needed to be whitelisted in the ForeSee CX Suite platform. If the domain is added by the team, users will get automatically provisioned to the ForeSee CX Suite platform. Users must be created and activated before you use single sign-on.
+
+### Assign the Azure AD test user
+
+In this section, you enable Britta Simon to use Azure single sign-on by granting access to ForeSee CX Suite.
+
+![Assign the user role][200]
+
+**To assign Britta Simon to ForeSee CX Suite, perform the following steps:**
+
+1. In the Azure portal, open the applications view, and then navigate to the directory view and go to **Enterprise applications** then click **All applications**.
+
+	![Assign User][201]
+
+2. In the applications list, select **ForeSee CX Suite**.
+
+	![The ForeSee CX Suite link in the Applications list](./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_foreseecxsuite_app.png)
+
+3. In the menu on the left, click **Users and groups**.
+
+	![The "Users and groups" link][202]
+
+4. Click **Add** button. Then select **Users and groups** on **Add Assignment** dialog.
+
+	![The Add Assignment pane][203]
+
+5. On **Users and groups** dialog, select **Britta Simon** in the Users list.
+
+6. Click **Select** button on **Users and groups** dialog.
+
+7. Click **Assign** button on **Add Assignment** dialog.
+
+### Test single sign-on
+
+In this section, you test your Azure AD single sign-on configuration using the Access Panel.
+
+When you click the ForeSee CX Suite tile in the Access Panel, you should get automatically signed-on to your ForeSee CX Suite application.
+For more information about the Access Panel, see [Introduction to the Access Panel](active-directory-saas-access-panel-introduction.md).
+
+## Additional resources
+
+* [List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory](active-directory-saas-tutorial-list.md)
+* [What is application access and single sign-on with Azure Active Directory?](active-directory-appssoaccess-whatis.md)
+
+<!--Image references-->
+
+[1]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_01.png
+[2]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_02.png
+[3]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_03.png
+[4]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_04.png
+
+[100]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_100.png
+
+[200]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_200.png
+[201]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_201.png
+[202]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_202.png
+[203]: ./media/active-directory-saas-foreseecxsuite-tutorial/tutorial_general_203.png
+

articles/active-directory/develop/active-directory-token-and-claims.md

@@ -52,7 +52,7 @@ eyJ0eXAiOiJKV1QiLCJhbGciOiJub25lIn0.eyJhdWQiOiIyZDRkMTFhMi1mODE0LTQ2YTctODkwYS0y
 | JWT Claim | Name | Description |
 | --- | --- | --- |
 | `aud` |Audience |The intended recipient of the token. The application that receives the token must verify that the audience value is correct and reject any tokens intended for a different audience. <br><br> **Example SAML Value**: <br> `<AudienceRestriction>`<br>`<Audience>`<br>`https://contoso.com`<br>`</Audience>`<br>`</AudienceRestriction>` <br><br> **Example JWT Value**: <br> `"aud":"https://contoso.com"` |
-| `appidacr` |Application Authentication Context Class Reference |Indicates how the client was authenticated. For a public client, the value is 0. If client ID and client secret are used, the value is 1. <br><br> **Example JWT Value**: <br> `"appidacr": "0"` |
+| `appidacr` |Application Authentication Context Class Reference |Indicates how the client was authenticated. For a public client, the value is 0. If client ID and client secret are used, the value is 1. If a client certificate was used for authentication, the value is 2. <br><br> **Example JWT Value**: <br> `"appidacr": "0"` |
 | `acr` |Authentication Context Class Reference |Indicates how the subject was authenticated, as opposed to the client in the Application Authentication Context Class Reference claim. A value of "0" indicates the end-user authentication did not meet the requirements of ISO/IEC 29115. <br><br> **Example JWT Value**: <br> `"acr": "0"` |
 | Authentication Instant |Records the date and time when authentication occurred. <br><br> **Example SAML Value**: <br> `<AuthnStatement AuthnInstant="2011-12-29T05:35:22.000Z">` | |
 | `amr` |Authentication Method |Identifies how the subject of the token was authenticated. <br><br> **Example SAML Value**: <br> `<AuthnContextClassRef>`<br>`http://schemas.microsoft.com/ws/2008/06/identity/claims/authenticationmethod/password`<br>`</AuthnContextClassRef>` <br><br> **Example JWT Value**: `“amr”: ["pwd"]` |

articles/active-directory/managed-service-identity/TOC.yml

@@ -18,6 +18,8 @@
     items:
     - name: Access Azure Data Lake Store
       href: tutorial-windows-vm-access-datalake.md
+    - name: Access Azure Storage
+      href: tutorial-vm-windows-access-storage.md
     - name: Access Azure Storage using an access key
       href: tutorial-windows-vm-access-storage.md
     - name: Access Azure Storage using SAS
@@ -34,6 +36,8 @@
     items:
     - name: Access Azure Data Lake Store
       href: tutorial-linux-vm-access-datalake.md
+    - name: Access Azure Storage
+      href: tutorial-linux-vm-access-storage.md
     - name: Access Azure Storage using an access key
       href: tutorial-linux-vm-access-storage-access-key.md
     - name: Access Azure Storage using SAS