Merge pull request #78624 from MicrosoftDocs/master

6/3 PM Publish

Author: huypub

.openpublishing.redirection.json

@@ -20,6 +20,26 @@
       "redirect_url": "https://docs.microsoft.com/previous-versions/azure/batch-ai/how-to-migrate",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/best-practices-network-security.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/virtual-network/virtual-networks-dmz-nsg-asm.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/virtual-network/virtual-networks-dmz-nsg-fw-asm.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/virtual-network/virtual-networks-dmz-nsg-fw-udr-asm.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter",
+      "redirect_document_id": true
+    },
     {
       "source_path": "articles/batch-ai/migrate-to-new-api.md",
       "redirect_url": "https://docs.microsoft.com/previous-versions/azure/batch-ai/how-to-migrate",
@@ -16409,6 +16429,21 @@
       "redirect_url": "/azure/service-fabric/service-fabric-tutorial-deploy-app-to-party-cluster",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/migrate/migrate-best-practices-costs.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/cloud-adoption/migrate/azure-best-practices/migrate-best-practices-costs",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/migrate/migrate-best-practices-networking.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/cloud-adoption/migrate/azure-best-practices/migrate-best-practices-networking",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/migrate/migrate-best-practices-security-management.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/cloud-adoption/migrate/azure-best-practices/migrate-best-practices-security-management",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/migrate/how-to-tag-v-center.md",
       "redirect_url": "how-to-create-a-group",
@@ -32409,6 +32444,31 @@
       "redirect_url": "/azure/cloud-shell/persisting-shell-storage",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/cdn/cdn-rules-engine-reference-conditional-expressions.md",
+      "redirect_url": "/azure/cdn/cdn-verizon-premium-rules-engine-reference-conditional-expressions",
+      "redirect_document_id": true 
+    },
+    {
+      "source_path": "articles/cdn/cdn-rules-engine-reference-features.md",
+      "redirect_url": "/azure/cdn/cdn-verizon-premium-rules-engine-reference-features",
+      "redirect_document_id": true 
+    }, 
+    {
+      "source_path": "articles/cdn/cdn-rules-engine-reference-match-conditions.md",
+      "redirect_url": "/azure/cdn/cdn-verizon-premium-rules-engine-reference-match-conditions",
+      "redirect_document_id": true 
+    }, 
+    {
+      "source_path": "articles/cdn/cdn-rules-engine-reference.md",
+      "redirect_url": "/azure/cdn/cdn-verizon-premium-rules-engine-reference",
+      "redirect_document_id": true 
+    }, 
+    {
+      "source_path": "articles/cdn/cdn-rules-engine.md",
+      "redirect_url": "/azure/cdn/cdn-verizon-premium-rules-engine",
+      "redirect_document_id": true 
+    },  
     {
       "source_path": "articles/cognitive-services/LUIS/luis-tutorial-interchangeable-phrase-list.md",
       "redirect_url": "/azure/cognitive-services/LUIS/luis-quickstart-primary-and-secondary-data",

articles/active-directory/hybrid/plan-hybrid-identity-design-considerations-hybrid-id-management-tasks.md

@@ -42,24 +42,24 @@ While defining those requirements, ensure that at least the following questions
 
   * Does the hybrid identity solution handles license management?
     * If yes, what capabilities are available?
-* Does the solution handle group-based license management? 
+  * Does the solution handle group-based license management? 
 
-      - If yes, is it possible to assign a security group to it? 
-       - If yes, will the cloud directory automatically assign licenses to all the members of the group? 
-        - What happens if a user is subsequently added to, or removed from the group, will a license be automatically assigned or removed as appropriate? 
+    * If yes, is it possible to assign a security group to it? 
+    * If yes, will the cloud directory automatically assign licenses to all the members of the group? 
+    * What happens if a user is subsequently added to, or removed from the group, will a license be automatically assigned or removed as appropriate? 
 * Integration with other third-party identity providers:
-* Can this hybrid solution be integrated with third-party identity providers to implement single sign-on?
-* Is it possible to unify all the different identity providers into a cohesive identity system?
-* If yes, how and which are they and what capabilities are available?
+  * Can this hybrid solution be integrated with third-party identity providers to implement single sign-on?
+  * Is it possible to unify all the different identity providers into a cohesive identity system?
+  * If yes, how and which are they and what capabilities are available?
 
 ## Synchronization Management
 One of the goals of an identity manager, to be able to bring all the identity providers and keep them synchronized. You keep the data synchronized based on an authoritative master identity provider. In a hybrid identity scenario, with a synchronized management model, you manage all user and device identities in an on-premises server and synchronize the accounts and, optionally, passwords to the cloud. The user enters the same password on-premises as they do in the cloud, and at sign-in, the password is verified by the identity solution. This model uses a directory synchronization tool.
 
 ![directory sync](./media/plan-hybrid-identity-design-considerations/Directory_synchronization.png)
 To proper design the synchronization of your hybrid identity solution ensure that the following questions are answered:
-•    What are the sync solutions available for the hybrid identity solution?
-•    What are the single sign on capabilities available?
-•    What are the options for identity federation between B2B and B2C?
+*    What are the sync solutions available for the hybrid identity solution?
+*    What are the single sign on capabilities available?
+*    What are the options for identity federation between B2B and B2C?
 
 ## Next steps
 [Determine hybrid identity management adoption strategy](plan-hybrid-identity-design-considerations-lifecycle-adoption-strategy.md)

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

@@ -0,0 +1,150 @@
+---
+title: 'Tutorial: Azure Active Directory integration with ANAQUA | Microsoft Docs'
+description: Learn how to configure single sign-on between Azure Active Directory and ANAQUA.
+services: active-directory
+documentationCenter: na
+author: jeevansd
+manager: mtillman
+ms.reviewer: celested
+
+ms.assetid: ab13b73e-ca4f-460c-8f79-fabf81b778c0
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.tgt_pltfrm: na
+ms.devlang: na
+ms.topic: tutorial
+ms.date: 05/31/2019
+ms.author: jeedes
+
+ms.collection: M365-identity-device-management
+---
+
+# Tutorial: Integrate ANAQUA with Azure Active Directory
+
+In this tutorial, you'll learn how to integrate ANAQUA with Azure Active Directory (Azure AD). When you integrate ANAQUA with Azure AD, you can:
+
+* Control in Azure AD who has access to ANAQUA.
+* Enable your users to be automatically signed-in to ANAQUA with their Azure AD accounts.
+* Manage your accounts in one central location - the Azure portal.
+
+To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis).
+
+## Prerequisites
+
+To get started, you need the following items:
+
+* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
+* ANAQUA single sign-on (SSO) enabled subscription.
+
+## Scenario description
+
+In this tutorial, you configure and test Azure AD SSO in a test environment. ANAQUA supports **SP and IDP** initiated SSO and supports **Just In Time** user provisioning.
+
+## Adding ANAQUA from the gallery
+
+To configure the integration of ANAQUA into Azure AD, you need to add ANAQUA from the gallery to your list of managed SaaS apps.
+
+1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account.
+1. On the left navigation pane, select the **Azure Active Directory** service.
+1. Navigate to **Enterprise Applications** and then select **All Applications**.
+1. To add new application, select **New application**.
+1. In the **Add from the gallery** section, type **ANAQUA** in the search box.
+1. Select **ANAQUA** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
+
+## Configure and test Azure AD single sign-on
+
+Configure and test Azure AD SSO with ANAQUA using a test user called **B. Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in ANAQUA.
+
+To configure and test Azure AD SSO with ANAQUA, complete the following building blocks:
+
+1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** to enable your users to use this feature.
+2. **[Configure ANAQUA](#configure-anaqua)** to configure the SSO settings on application side.
+3. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** to test Azure AD single sign-on with B. Simon.
+4. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** to enable B. Simon to use Azure AD single sign-on.
+5. **[Create ANAQUA test user](#create-anaqua-test-user)** to have a counterpart of B. Simon in ANAQUA that is linked to the Azure AD representation of user.
+6. **[Test SSO](#test-sso)** to verify whether the configuration works.
+
+### Configure Azure AD SSO
+
+Follow these steps to enable Azure AD SSO in the Azure portal.
+
+1. In the [Azure portal](https://portal.azure.com/), on the **ANAQUA** application integration page, find the **Manage** section and select **Single sign-on**.
+1. On the **Select a Single sign-on method** page, select **SAML**.
+1. On the **Set up Single Sign-On with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings.
+
+   ![Edit Basic SAML Configuration](common/edit-urls.png)
+
+1. On the **Basic SAML Configuration** section, if you wish to configure the application in **IDP** initiated mode, perform the following steps:
+
+    a. In the **Identifier** text box, type a URL using the following pattern:
+    `https://<SUBDOMAIN>.anaqua.com`
+
+    b. In the **Reply URL** text box, type a URL using the following pattern:
+    `https://<SUBDOMAIN>.anaqua.com/anaqua/Public/login.aspx`
+
+1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
+
+    In the **Sign-on URL** text box, type a URL using the following pattern:
+    `https://<SUBDOMAIN>.anaqua.com/anaqua/Public/login.aspx`
+
+	> [!NOTE]
+	> These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [ANAQUA Client support team](https://go.anaqua.com/contact-us) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+
+1. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the metadata file and save it on your computer.
+
+   ![The Certificate download link](common/metadataxml.png)
+
+1. On the **Set up ANAQUA** section, copy the appropriate URL(s) based on your requirement.
+
+   ![Copy configuration URLs](common/copy-configuration-urls.png)
+
+### Configure ANAQUA
+
+To configure single sign-on on **ANAQUA** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [ANAQUA support team](https://go.anaqua.com/contact-us). They set this setting to have the SAML SSO connection set properly on both sides.
+
+### Create an Azure AD test user
+
+In this section, you'll create a test user in the Azure portal called B. Simon.
+
+1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
+1. Select **New user** at the top of the screen.
+1. In the **User** properties, follow these steps:
+   1. In the **Name** field, enter `B. Simon`.  
+   1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
+   1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
+   1. Click **Create**.
+
+### Assign the Azure AD test user
+
+In this section, you'll enable B. Simon to use Azure single sign-on by granting access to ANAQUA.
+
+1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
+1. In the applications list, select **ANAQUA**.
+1. In the app's overview page, find the **Manage** section and select **Users and groups**.
+
+   ![The "Users and groups" link](common/users-groups-blade.png)
+
+1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
+
+	![The Add User link](common/add-assign-user.png)
+
+1. In the **Users and groups** dialog, select **B. Simon** from the Users list, then click the **Select** button at the bottom of the screen.
+1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen.
+1. In the **Add Assignment** dialog, click the **Assign** button.
+
+### Create ANAQUA test user
+
+In this section, a user called Britta Simon is created in ANAQUA. ANAQUA supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in ANAQUA, a new one is created after authentication.
+
+### Test SSO
+
+When you select the ANAQUA tile in the Access Panel, you should be automatically signed in to the ANAQUA for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
+
+## Additional Resources
+
+- [List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
+
+- [What is application access and single sign-on with Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
+
+- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)

articles/active-directory/saas-apps/toc.yml

@@ -77,6 +77,8 @@
         href: amplitude-tutorial.md
       - name: Anaplan
         href: anaplan-tutorial.md
+      - name: ANAQUA
+        href: anaqua-tutorial.md
       - name: Andfrankly
         href: andfrankly-tutorial.md
       - name: Andromeda