Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-iga-licensing

Author: rolyon

.openpublishing.redirection.json

@@ -3930,6 +3930,61 @@
       "redirect_url": "/azure/architecture/cloud-adoption-guide/subscription-governance",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/azure-supportability/index.yml",
+      "redirect_url": "/azure/azure-portal/supportability/how-to-create-azure-support-request",
+      "redirect_document_id": false
+    },
+	    {
+      "source_path": "articles/azure-supportability/classic-deployment-model-quota-increase-requests.md",
+      "redirect_url": "/azure/azure-portal/supportability/classic-deployment-model-quota-increase-requests",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/azure-supportability/create-manage-support-requests-using-access-control.md",
+      "redirect_url": "/azure/azure-portal/supportability/how-to-create-azure-support-request#role-based-access-control",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/azure-supportability/how-to-create-azure-support-request.md",
+      "redirect_url": "/azure/azure-portal/supportability/how-to-create-azure-support-request",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/azure-supportability/how-to-use-file-uploader.md",
+      "redirect_url": "/azure/azure-portal/supportability/how-to-use-file-uploader",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/azure-supportability/low-priority-quota.md",
+      "redirect_url": "/azure/azure-portal/supportability/low-priority-quota",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/azure-supportability/networking-quota-requests.md",
+      "redirect_url": "/azure/azure-portal/supportability/networking-quota-requests",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/azure-supportability/per-vm-quota-requests.md",
+      "redirect_url": "/azure/azure-portal/supportability/per-vm-quota-requests",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/azure-supportability/regional-quota-requests.md",
+      "redirect_url": "/azure/azure-portal/supportability/regional-quota-requests",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/azure-supportability/resource-manager-core-quotas-request.md",
+      "redirect_url": "/azure/azure-portal/supportability/resource-manager-core-quotas-request",
+      "redirect_document_id": true
+    },
+	    {
+      "source_path": "articles/azure-supportability/sku-series-unavailable.md",
+      "redirect_url": "/azure/azure-portal/supportability/sku-series-unavailable",
+      "redirect_document_id": true
+    },
     {
       "source_path": "articles/azure-toolkit-for-eclipse-debugging-azure-applications.md",
       "redirect_url": "/java/azure/eclipse/azure-toolkit-for-eclipse",

articles/active-directory/authentication/howto-password-ban-bad-on-premises-deploy.md

@@ -31,7 +31,7 @@ During the audit stage, many organizations find out that:
 
 It is also possible for stronger password validation to affect your existing Active Directory domain controller deployment automation. We recommend that at least one DC promotion and one DC demotion happen during the audit period evaluation in order to help uncover such issues in advance.  For more information, see:
 
-* [Ntdsutil.exe is unable to set a weak Directory Services Repair Mode password](howto-password-ban-bad-on-premises-troubleshoot.md##ntdsutilexe-fails-to-set-a-weak-dsrm-password)
+* [Ntdsutil.exe is unable to set a weak Directory Services Repair Mode password](howto-password-ban-bad-on-premises-troubleshoot.md#ntdsutilexe-fails-to-set-a-weak-dsrm-password)
 * [Domain controller replica promotion fails because of a weak Directory Services Repair Mode password](howto-password-ban-bad-on-premises-troubleshoot.md#domain-controller-replica-promotion-fails-because-of-a-weak-dsrm-password)
 * [Domain controller demotion fails due to a weak local Administrator password](howto-password-ban-bad-on-premises-troubleshoot.md#domain-controller-demotion-fails-due-to-a-weak-local-administrator-password)
 

articles/active-directory/develop/howto-add-app-roles-in-azure-ad-apps.md

@@ -33,9 +33,9 @@ These application roles are defined in the [Azure portal](https://portal.azure.c
 ### Declare app roles using Azure portal
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-1. On the top bar, select your account, and then **Switch Directory**.
-1. Once the **Directory + subscription** pane opens, choose the Active Directory tenant where you wish to register your application, from the **Favorites** or **All Directories** list.
-1. Select **All services** in the left-hand nav, and choose **Azure Active Directory**.
+1. Select the **Directory + Subscription** icon in the portal toolbar.
+1. In the **Favorites** or **All Directories** list, choose the Active Directory tenant where you wish to register your application.
+1. In the Azure portal, search for and select **Azure Active Directory**.
 1. In the  **Azure Active Directory** pane, select **App registrations** to view a list of all your applications.
 1. Select the application you want to define app roles in. Then select **Manifest**.
 1. Edit the app manifest by locating the `appRoles` setting and adding all your Application Roles.

articles/active-directory/develop/reference-v2-libraries.md

@@ -104,7 +104,7 @@ For any standards-compliant library, you can use the Microsoft identity platform
 * For issues and new feature requests in library code, contact the library owner.
 * For issues and new feature requests in the service-side protocol implementation, contact Microsoft.
 * [File a feature request](https://feedback.azure.com/forums/169401-azure-active-directory) for additional features you want to see in the protocol.
-* [Create a support request](https://docs.microsoft.com/azure/azure-supportability/how-to-create-azure-support-request) if you find an issue where the Microsoft identity platform endpoint isn't compliant with OAuth 2.0 or OpenID Connect 1.0.
+* [Create a support request](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request) if you find an issue where the Microsoft identity platform endpoint isn't compliant with OAuth 2.0 or OpenID Connect 1.0.
 
 ## Related content
 

articles/active-directory/devices/troubleshoot-hybrid-join-windows-current.md

@@ -244,7 +244,7 @@ Applicable only for federated domain accounts.
 Reasons for failure:
 
 - Unable to get an Access token silently for DRS resource.
-   - Windows 10 devices acquire auth token from the federation service using Integrated Windows Authentication to an active WS-Trust endpoint. Details: [Federation Service Configuration](hybrid-azuread-join-manual.md##set-up-issuance-of-claims)
+   - Windows 10 devices acquire auth token from the federation service using Integrated Windows Authentication to an active WS-Trust endpoint. Details: [Federation Service Configuration](hybrid-azuread-join-manual.md#set-up-issuance-of-claims)
 
 **Common error codes:**
 

articles/active-directory/hybrid/how-to-connect-install-custom.md

@@ -77,7 +77,7 @@ After entering the forest name and clicking  **Add Directory**, a pop-up dialog
 | Option | Description |
 | --- | --- |
 | Create new account | Select this option if you want Azure AD Connect wizard to create the AD DS account required by Azure AD Connect for connecting to the AD forest during directory synchronization. When this option is selected, enter the username and password for an enterprise admin account. The enterprise admin account provided will be used by Azure AD Connect wizard to create the required AD DS account. You can enter the domain part in either NetBios or FQDN format, that is, FABRIKAM\administrator or fabrikam.com\administrator. |
-| Use existing account | Select this option if you want to provide an existing AD DS account to be used Azure AD Connect for connecting to the AD forest during directory synchronization. You can enter the domain part in either NetBios or FQDN format, that is, FABRIKAM\syncuser or fabrikam.com\syncuser. This account can be a regular user account because it only needs the default read permissions. However, depending on your scenario, you may need more permissions. For more information, see [Azure AD Connect Accounts and permissions](reference-connect-accounts-permissions.md##create-the-ad-ds-connector-account). |
+| Use existing account | Select this option if you want to provide an existing AD DS account to be used Azure AD Connect for connecting to the AD forest during directory synchronization. You can enter the domain part in either NetBios or FQDN format, that is, FABRIKAM\syncuser or fabrikam.com\syncuser. This account can be a regular user account because it only needs the default read permissions. However, depending on your scenario, you may need more permissions. For more information, see [Azure AD Connect Accounts and permissions](reference-connect-accounts-permissions.md#create-the-ad-ds-connector-account). |
 
 ![Connect Directory](./media/how-to-connect-install-custom/connectdir02.png)
 

articles/active-directory/hybrid/how-to-connect-sso-quick-start.md

@@ -208,7 +208,7 @@ To test the feature for a specific user, ensure that all the following condition
   - The user signs in on a corporate device.
   - The device is joined to your Active Directory domain. The device _doesn't_ need to be [Azure AD Joined](../active-directory-azureadjoin-overview.md).
   - The device has a direct connection to your domain controller (DC), either on the corporate wired or wireless network or via a remote access connection, such as a VPN connection.
-  - You have [rolled out the feature](##step-3-roll-out-the-feature) to this user through Group Policy.
+  - You have [rolled out the feature](#step-3-roll-out-the-feature) to this user through Group Policy.
 
 To test the scenario where the user enters only the username, but not the password:
    - Sign in to `https://myapps.microsoft.com/` in a new private browser session.

articles/active-directory/managed-identities-azure-resources/TOC.yml

@@ -20,8 +20,6 @@
       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 SQL
       href: tutorial-windows-vm-access-sql.md
     - name: Access Azure Key Vault

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

@@ -12,9 +12,8 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: tutorial
-ms.date: 09/10/2019
+ms.date: 01/10/2020
 ms.author: jeedes
 
 ms.collection: M365-identity-device-management
@@ -68,9 +67,8 @@ Configure and test Azure AD SSO with NetSuite by using a test user called **B.Si
 To configure and test Azure AD SSO with NetSuite, complete the following building blocks:
 
 1. [Configure Azure AD SSO](#configure-azure-ad-sso) to enable your users to use this feature.
-
-    a. [Create an Azure AD test user](#create-an-azure-ad-test-user) to test Azure AD single sign-on with user B.Simon.  
-    b. [Assign the Azure AD test user](#assign-the-azure-ad-test-user) to enable user B.Simon to use Azure AD single sign-on.
+    * [Create an Azure AD test user](#create-an-azure-ad-test-user) to test Azure AD single sign-on with user B.Simon.  
+    * [Assign the Azure AD test user](#assign-the-azure-ad-test-user) to enable user B.Simon to use Azure AD single sign-on.
 1. [Configure NetSuite SSO](#configure-netsuite-sso) to configure the single sign-on settings on the application side.
     * [Create the NetSuite test user](#create-the-netsuite-test-user) to have a counterpart of user B.Simon in NetSuite that's linked to the Azure AD representation of the user.
 1. [Test SSO](#test-sso) to verify that the configuration works.
@@ -87,52 +85,32 @@ To enable Azure AD SSO in the Azure portal, do the following:
 
 1. In the **Basic SAML Configuration** section, in the **Reply URL** text box, type a URL in one of the following formats:
 
-    ```
-    https://<tenant-name>.NetSuite.com/saml2/acs
-    https://<tenant-name>.na1.NetSuite.com/saml2/acs
-    https://<tenant-name>.na2.NetSuite.com/saml2/acs
-    https://<tenant-name>.sandbox.NetSuite.com/saml2/acs
-    https://<tenant-name>.na1.sandbox.NetSuite.com/saml2/acs
-    https://<tenant-name>.na2.sandbox.NetSuite.com/saml2/acs
-    ```
+    ||
+    |-|
+    | `https://<Account ID>.NetSuite.com/saml2/acs`|
+    | `https://<Account ID>.na1.NetSuite.com/saml2/acs`|
+    | `https://<Account ID>.na2.NetSuite.com/saml2/acs`|
+    | `https://<Account ID>.sandbox.NetSuite.com/saml2/acs`|
+    | `https://<Account ID>.na1.sandbox.NetSuite.com/saml2/acs`|
+    | `https://<Account ID>.na2.sandbox.NetSuite.com/saml2/acs`|
 
     > [!NOTE]
     > The values in the preceding URLs are not real. Update them with the actual Reply URL. To get the value, contact the [NetSuite Client support team](http://www.netsuite.com/portal/services/support-services/suitesupport.shtml). You can also refer to the formats shown in the **Basic SAML Configuration** section in the Azure portal.
 
-    The NetSuite application expects the SAML assertions to be displayed in a specific format. You'll need to add custom attribute mappings to your SAML token attributes configuration. 
-    
-1. To open the **User Attributes** pane, select the **Edit** ("pencil") icon. The pane displays a list of default attributes, as shown in the following image: 
-
-	![The User Attributes pane](common/edit-attribute.png)
+1. NetSuite application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
 
-    In addition to these attributes, the NetSuite application expects a few more attributes to be passed back in the SAML response. 
+	![image](common/default-attributes.png)
 
-1. In the **User Attributes** pane, under **User Claims**, perform the following steps to add the SAML token attribute that's shown in the following table:
+1. In addition to above, NetSuite application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements.
 
-	| Name | Source attribute | 
+	| Name | Source attribute |
 	| ---------------| --------------- |
 	| account  | `account id` |
 
-	a. Select **Add new claim** to open the **Manage user claims** pane.
-
-	b. In the **Name** box, type the attribute name that's shown for that row.
-
-	c. Leave the **Namespace** box blank.
-
-	d. In the **Source** drop-down list, select **Attribute**.
-
-	e. In the **Source attribute** list, enter the attribute value that's shown for that row.
+	> [!NOTE]
+	> The value of the account attribute is not real. You'll update this value, as explained later in this tutorial.
 
-	f. Select **OK**.
-
-	g. Select **Save**.
-
-	>[!NOTE]
-	>The value of the account attribute is not real. You'll update this value, as explained later in this tutorial.
-
-1. In the **Set up single sign-on with SAML** pane, in the **SAML Signing Certificate** section, look for **Federation Metadata XML**.
-
-1. Select **Download** to download the certificate and save it on your computer.
+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 certificate and save it on your computer.
 
 	![The certificate Download link](common/metadataxml.png)
 
@@ -272,7 +250,7 @@ In this section, you enable user B.Simon to use Azure single sign-on by granting
 
 In this section, a user called B.Simon is created in NetSuite. NetSuite supports just-in-time user provisioning, which is enabled by default. There's no action item for you in this section. If a user doesn't already exist in NetSuite, a new one is created after authentication.
 
-## Test SSO 
+## Test SSO
 
 In this section, you test your Azure AD single sign-on configuration by using the Access Panel.
 
@@ -284,4 +262,3 @@ When you select the NetSuite tile in the Access Panel, you should be automatical
 - [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)
 - [Try NetSuite with Azure AD](https://aad.portal.azure.com/)
-

articles/active-directory/users-groups-roles/directory-admin-roles-secure.md

@@ -371,7 +371,7 @@ Determine if you need to [transfer ownership of an Azure subscription to another
 
 3. Access your "break glass" account username/password combination to sign in to Azure AD. 
 
-4. Get help from Microsoft by [opening an Azure support request](../../azure-supportability/how-to-create-azure-support-request.md).
+4. Get help from Microsoft by [opening an Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md).
 
 5. Look at the [Azure AD sign-in reports](../reports-monitoring/overview-reports.md). There may be a lag between an event occurring and when it is included in the report.