Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into pauljewell-obj-model

Author: pauljewellmsft

articles/active-directory/app-provisioning/configure-automatic-user-provisioning-portal.md

@@ -22,10 +22,11 @@ This article describes the general steps for managing automatic user account pro
 
 ## Finding your apps in the portal
 
-Use the Azure Active Directory portal to view and manage all applications that are configured for single sign-on in a directory. Enterprise apps are apps that are deployed and used within your organization. Follow these steps to view and manage your enterprise applications:
+Use the Azure portal to view and manage all applications that are configured for single sign-on in a directory. Enterprise apps are apps that are deployed and used within your organization. Follow these steps to view and manage your enterprise applications:
 
-1. Open the [Azure Active Directory portal](https://aad.portal.azure.com).
-1. Select **Enterprise applications** from the left pane. A list of all configured apps is shown, including apps that were added from the gallery.
+1. Open the [Azure portal](https://portal.azure.com).
+1. Browse to **Azure Active Directory** > **Enterprise applications**.
+1. A list of all configured apps is shown, including apps that were added from the gallery.
 1. Select any app to load its resource pane, where you can view reports and manage app settings.
 1. Select **Provisioning** to manage user account provisioning settings for the selected app.
 

articles/active-directory/app-provisioning/customize-application-attributes.md

@@ -29,8 +29,9 @@ You can customize the default attribute-mappings according to your business need
 
 Follow these steps to access the **Mappings** feature of user provisioning:
 
-1. Sign in to the [Azure Active Directory portal](https://aad.portal.azure.com).
-1. Select **Enterprise applications** from the left pane. A list of all configured apps is shown, including apps that were added from the gallery.
+1. Sign in to the [Azure portal](https://portal.azure.com).
+1. Browse to **Azure Active Directory** > **Enterprise applications**.
+1. A list of all configured apps is shown, including apps that were added from the gallery.
 1. Select any app to load its app management pane, where you can view reports and manage app settings.
 1. Select **Provisioning** to manage user account provisioning settings for the selected app.
 1. Expand **Mappings** to view and edit the user attributes that flow between Azure AD and the target application. If the target application supports it, this section lets you optionally configure provisioning of groups and user accounts.
@@ -142,7 +143,7 @@ When you are editing the list of supported attributes, the following properties
 
 #### Provisioning a custom extension attribute to a SCIM compliant application
 The SCIM RFC defines a core user and group schema, while also allowing for extensions to the schema to meet your application's needs. To add a custom attribute to a SCIM application:
-   1. Sign in to the [Azure Active Directory portal](https://aad.portal.azure.com), select **Enterprise Applications**, select your application, and then select **Provisioning**.
+   1. Sign in to the [Azure portal](https://portal.azure.com), select **Enterprise Applications**, select your application, and then select **Provisioning**.
    2. Under **Mappings**, select the object (user or group) for which you'd like to add a custom attribute.
    3. At the bottom of the page, select **Show advanced options**.
    4. Select **Edit attribute list for AppName**.

articles/active-directory/app-provisioning/on-premises-application-provisioning-architecture.md

@@ -79,7 +79,7 @@ Since ECMA Connector Host currently only supports the USER object type, the OBJE
 
 ### User creation workflow
 
-1.  The Azure AD provisioning service queries the ECMA Connector Host to see if the user exists.  It uses the **matching attribute** as the filter.  This attribute is defined in the Azure AD portal under Enterprise applications -> On-premises provisioning -> provisioning -> attribute matching.  It is denoted by the 1 for matching precedence.
+1.  The Azure AD provisioning service queries the ECMA Connector Host to see if the user exists.  It uses the **matching attribute** as the filter.  This attribute is defined in the Azure portal under Enterprise applications -> On-premises provisioning -> provisioning -> attribute matching.  It is denoted by the 1 for matching precedence.
 You can define one or more matching attribute(s) and prioritize them based on the precedence.  Should you want to change the matching attribute you can also do so.
  [![Matching attribute](.\media\on-premises-application-provisioning-architecture\match-1.png)](.\media\on-premises-application-provisioning-architecture\match-1.png#lightbox)
 

articles/active-directory/app-provisioning/plan-auto-user-provisioning.md

@@ -144,7 +144,7 @@ Widen the rollout to larger groups of users by increasing the scope of the group
 
 ## Plan application connections and administration
 
-Use the Azure AD portal to view and manage all the applications that support provisioning. See [Finding your apps in the portal](../app-provisioning/configure-automatic-user-provisioning-portal.md).
+Use the Azure portal to view and manage all the applications that support provisioning. See [Finding your apps in the portal](../app-provisioning/configure-automatic-user-provisioning-portal.md).
 
 ### Determine the type of connector to use
 

articles/active-directory/app-provisioning/plan-cloud-hr-provision.md

@@ -150,7 +150,7 @@ To facilitate Azure AD provisioning workflows between the cloud HR app and Activ
 
 For example, the following image lists the Workday connector apps that are available in the Azure AD app gallery.
 
-![Azure Active Directory portal app gallery](media/plan-cloud-hr-provision/plan-cloudhr-provisioning-img2.png)
+![Azure portal app gallery](media/plan-cloud-hr-provision/plan-cloudhr-provisioning-img2.png)
 
 ### Decision flow chart
 

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

@@ -1308,8 +1308,9 @@ Applications that support the SCIM profile described in this article can be conn
 
 **To connect an application that supports SCIM:**
 
-1. Sign in to the [Azure AD portal](https://aad.portal.azure.com). You can get access a free trial for Azure AD with P2 licenses by signing up for the [developer program](https://developer.microsoft.com/microsoft-365/dev-program))
-1. Select **Enterprise applications** from the left pane. A list of all configured apps is shown, including apps that were added from the gallery.
+1. Sign in to the [Azure portal](https://portal.azure.com). You can get access a free trial for Azure AD with P2 licenses by signing up for the [developer program](https://developer.microsoft.com/microsoft-365/dev-program))
+1. Browse to **Azure Active Directory** > **Enterprise applications**.
+1. A list of all configured apps is shown, including apps that were added from the gallery.
 1. Select **+ New application** > **+ Create your own application**.
 1. Enter a name for your application, choose the option "*integrate any other application you don't find in the gallery*" and select **Add** to create an app object. The new app is added to the list of enterprise applications and opens to its app management screen.
 
@@ -1397,9 +1398,7 @@ The provisioning service supports the [authorization code grant](https://tools.i
 > [!NOTE]
 > OAuth v1 is not supported due to exposure of the client secret. OAuth v2 is supported.  
 
-Best practices (recommended, but not required):
-* Support multiple redirect URLs. Administrators can configure provisioning from both "portal.azure.com" and "aad.portal.azure.com". Supporting multiple redirect URLs will ensure that users can authorize access from either portal.
-* Support multiple secrets for easy renewal, without downtime. 
+Supportting multiple secrets for easy renewal, without downtime is recommended, but not required.
 
 #### How to set up OAuth code grant flow
 

articles/active-directory/app-proxy/application-proxy-config-problem.md

@@ -1,6 +1,6 @@
 ---
 title: Problem creating an Azure Active Directory Application Proxy application
-description: How to troubleshoot issues creating Application Proxy applications in the Azure Active Directory Admin portal
+description: How to troubleshoot issues creating Application Proxy applications in the Azure portal
 services: active-directory
 author: kenwith
 manager: amycolannino

articles/active-directory/app-proxy/application-proxy-configure-custom-domain.md

@@ -66,7 +66,7 @@ To create and verify a custom domain:
 1. Go to your domain registrar and create a new TXT record for your domain, based on your copied DNS information.
 1. After you register the domain, on the domain's page in Azure Active Directory, select **Verify**. Once the domain status is **Verified**, you can use the domain across all your Azure AD configurations, including Application Proxy. 
 
-For more detailed instructions, see [Add your custom domain name using the Azure Active Directory portal](../fundamentals/add-custom-domain.md).
+For more detailed instructions, see [Add your custom domain name using the Azure portal](../fundamentals/add-custom-domain.md).
 
 ### Configure an app to use a custom domain
 

articles/active-directory/app-proxy/application-proxy-configure-custom-home-page.md

@@ -42,7 +42,7 @@ You can set the home page URL either through the Azure portal or by using PowerS
 
 ## Change the home page in the Azure portal
 
-To change the home page URL of your app through the Azure AD portal, follow these steps:
+To change the home page URL of your app through the Azure portal, follow these steps:
 
 1. Sign in to the [Azure portal](https://portal.azure.com/) as an administrator.
 1. Select **Azure Active Directory**, and then **App registrations**. The list of registered apps appears.

articles/active-directory/app-proxy/application-proxy-configure-native-client-application.md

@@ -33,9 +33,8 @@ Publish your proxy application as you would any other application and assign use
 
 You now need to register your application in Azure AD, as follows:
 
-1. Sign in to the [Azure Active Directory portal](https://aad.portal.azure.com/). The **Dashboard** for the **Azure Active Directory admin center** appears.
-1. In the sidebar, select **Azure Active Directory**. The **Azure Active Directory** overview page appears.
-1. In the Azure AD overview sidebar, select **App registrations**. The list of all app registrations appears.
+1. Sign in to the [Azure portal](https://portal.azure.com).
+1. Browse to **Azure Active Directory** > **App registrations**. The list of all app registrations appears.
 1. Select **New registration**. The **Register an application** page appears.
 
    ![Create a new app registration in the Azure portal](./media/application-proxy-configure-native-client-application/create.png)
@@ -99,9 +98,9 @@ if (authResult != null)
  }
 ```
 
-The required info in the sample code can be found in the Azure AD portal, as follows:
+The required info in the sample code can be found in the Azure portal, as follows:
 
-| Info required | How to find it in the Azure AD portal |
+| Info required | How to find it in the Azure portal |
 | --- | --- |
 | \<Tenant ID> | **Azure Active Directory** > **Properties** > **Directory ID** |
 | \<App ID of the Native app> | **Application registration** > *your native application* > **Overview** > **Application ID** |