Merge pull request #251650 from kenwith/admin-center-app-provisioning-steps-1

[SCOPED] Updates "Azure portal" to new branding.

Author: denrea

articles/active-directory/app-proxy/app-proxy-protect-ndes.md

@@ -50,14 +50,14 @@ Azure AD Application Proxy is built on Azure. It gives you a massive amount of n
    * If Internet Explorer Enhanced Security Configuration is turned on for the server where you install the connector, the registration screen might be blocked. To allow access, follow the instructions in the error message, or turn off Internet Explorer Enhanced Security during the install process.
    * If connector registration fails, see [Troubleshoot Application Proxy](application-proxy-troubleshoot.md).
 1. At the end of the setup, a note is shown for environments with an outbound proxy. To configure the Azure AD Application Proxy connector to work through the outbound proxy, run the provided script, such as `C:\Program Files\Microsoft AAD App Proxy connector\ConfigureOutBoundProxy.ps1`.
-1. On the Application proxy page in the Azure portal, the new connector is listed with a status of *Active*, as shown in the following example:
+1. On the Application proxy page in the Microsoft Entra admin center, the new connector is listed with a status of *Active*, as shown in the following example:
 
-    ![The new Azure AD Application Proxy connector shown as active in the Azure portal](./media/app-proxy-protect-ndes/connected-app-proxy.png)
+    ![The new Azure AD Application Proxy connector shown as active in the Microsoft Entra admin center](./media/app-proxy-protect-ndes/connected-app-proxy.png)
 
     > [!NOTE]
     > To provide high availability for applications authenticating through the Azure AD Application Proxy, you can install connectors on multiple VMs. Repeat the same steps listed in the previous section to install the connector on other servers joined to the Azure AD DS managed domain.
 
-1. After successful installation, go back to the Azure portal.
+1. After successful installation, go back to the Microsoft Entra admin center.
 
 1. Select **Enterprise applications**.
 

articles/active-directory/app-proxy/application-proxy-add-on-premises-application.md

@@ -1,6 +1,6 @@
 ---
 title: Tutorial - Add an on-premises app - Application Proxy in Azure Active Directory
-description:  Azure Active Directory (Azure AD) has an Application Proxy service that enables users to access on-premises applications by signing in with their Azure AD account. This tutorial shows you how to prepare your environment for use with Application Proxy. Then, it uses the Azure portal to add an on-premises application to your Azure AD tenant.
+description:  Azure Active Directory (Azure AD) has an Application Proxy service that enables users to access on-premises applications by signing in with their Azure AD account. This tutorial shows you how to prepare your environment for use with Application Proxy. Then, it uses the Microsoft Entra admin center to add an on-premises application to your Azure AD tenant.
 services: active-directory
 author: kenwith
 manager: amycolannino
@@ -180,9 +180,9 @@ For information about connectors, capacity planning, and how they stay up-to-dat
 
 ## Verify the connector installed and registered correctly
 
-You can use the Azure portal or your Windows server to confirm that a new connector installed correctly.
+You can use the Microsoft Entra admin center or your Windows server to confirm that a new connector installed correctly.
 
-### Verify the installation through Azure portal
+### Verify the installation through Microsoft Entra admin center
 
 To confirm the connector installed and registered correctly:
 
@@ -219,7 +219,7 @@ Now that you've prepared your environment and installed a connector, you're read
 
     | Field  | Description |
     | :--------------------- | :----------------------------------------------------------- |
-    | **Name** | The name of the application that appears on My Apps and in the Azure portal. |
+    | **Name** | The name of the application that appears on My Apps and in the Microsoft Entra admin center. |
     | **Maintenance Mode** | Select if you would like to enable maintenance mode and temporarily disable access for all users to the application. |
     | **Internal URL** | The URL for accessing the application from inside your private network. You can provide a specific path on the backend server to publish, while the rest of the server is unpublished. In this way, you can publish different sites on the same server as different apps, and give each one its own name and access rules.<br><br>If you publish a path, make sure that it includes all the necessary images, scripts, and style sheets for your application. For example, if your app is at `https://yourapp/app` and uses images located at `https://yourapp/media`, then you should publish `https://yourapp/` as the path. This internal URL doesn't have to be the landing page your users see. For more information, see [Set a custom home page for published apps](application-proxy-configure-custom-home-page.md). |
     | **External URL** | The address for users to access the app from outside your network. If you don't want to use the default Application Proxy domain, read about [custom domains in Azure AD Application Proxy](./application-proxy-configure-custom-domain.md). |

articles/active-directory/app-proxy/application-proxy-application-gateway-waf.md

@@ -22,13 +22,13 @@ Azure Web Application Firewall (WAF) on Azure Application Gateway provides centr
 
 ## Deployment steps
 
-This article guides you through the steps to securely expose a web application on the Internet, by integrating the Azure AD Application Proxy with Azure WAF on Application Gateway. In this guide we'll be using the Azure portal. The reference architecture for this deployment is represented below.   
+This article guides you through the steps to securely expose a web application on the Internet, by integrating the Azure AD Application Proxy with Azure WAF on Application Gateway. In this guide we'll be using the Microsoft Entra admin center. The reference architecture for this deployment is represented below.   
 
 ![Diagram of deployment described.](./media/application-proxy-waf/application-proxy-waf.png)
 
 ### Configure Azure Application Gateway to send traffic to your internal application.
 
-Some steps of the Application Gateway configuration will be omitted in this article. For a detailed guide on how to create and configure an Application Gateway, see [Quickstart: Direct web traffic with Azure Application Gateway - Azure portal][appgw_quick].
+Some steps of the Application Gateway configuration will be omitted in this article. For a detailed guide on how to create and configure an Application Gateway, see [Quickstart: Direct web traffic with Azure Application Gateway - Microsoft Entra admin center][appgw_quick].
 
 ##### 1. Create a private-facing HTTPS listener.
 

articles/active-directory/app-proxy/application-proxy-azure-front-door.md

@@ -22,7 +22,7 @@ Azure Front Door helps deliver low-latency, high-throughput content at scale fro
 
 ## Deployment steps
 
-This article guides you through the steps to securely expose a web application on the Internet, by integrating the Azure AD Application Proxy with Azure Front Door. In this guide we'll be using the Azure portal. The reference architecture for this deployment is represented below.   
+This article guides you through the steps to securely expose a web application on the Internet, by integrating the Azure AD Application Proxy with Azure Front Door. In this guide we'll be using the Microsoft Entra admin center. The reference architecture for this deployment is represented below.   
 
 :::image type="content" source="./media/application-proxy-azure-front-door/azure-front-door.png" alt-text="Diagram of deployment described." lightbox="./media/application-proxy-azure-front-door/azure-front-door.png":::
 

articles/active-directory/app-proxy/application-proxy-back-end-kerberos-constrained-delegation-how-to.md

@@ -131,7 +131,7 @@ The consumer of the Kerberos ticket provided by the connector. At this stage, ex
 
    - Check the SPN defined against the application’s settings in the portal. Make sure that the same SPN configured against the target Azure AD account is used by the application’s app pool.
 
-      ![SPN configuration in the Azure portal](./media/application-proxy-back-end-kerberos-constrained-delegation-how-to/graphic11.png)
+      ![SPN configuration in the Microsoft Entra admin center](./media/application-proxy-back-end-kerberos-constrained-delegation-how-to/graphic11.png)
 
    - Go into IIS and select the **Configuration Editor** option for the application. Navigate to **system.webServer/security/authentication/windowsAuthentication**. Make sure the value **UseAppPoolCredentials** is **True**.
 

articles/active-directory/app-proxy/application-proxy-config-how-to.md

@@ -21,7 +21,7 @@ This article helps you to understand how to configure an Application Proxy appli
 
 To learn about the initial configurations and creation of an Application Proxy application through the Admin Portal, follow the [Publish applications using Azure AD Application Proxy](application-proxy-add-on-premises-application.md).
 
-For details on configuring Connectors, see [Enable Application Proxy in the Azure portal](application-proxy-add-on-premises-application.md).
+For details on configuring Connectors, see [Enable Application Proxy in the Microsoft Entra admin center](application-proxy-add-on-premises-application.md).
 
 For information on uploading certificates and using custom domains, see [Working with custom domains in Azure AD Application Proxy](application-proxy-configure-custom-domain.md).
 
@@ -37,7 +37,7 @@ If you are following the steps in the [Publish applications using Azure AD Appli
 
 The error message should display in the top-right corner when you create the application. You can also select the notification icon to see the error messages.
 
-![Shows where to find the Notification prompt in the Azure portal](./media/application-proxy-config-how-to/error-message.png)
+![Shows where to find the Notification prompt in the Microsoft Entra admin center](./media/application-proxy-config-how-to/error-message.png)
 
 ## Configure connectors/connector groups
 

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 portal
+description: How to troubleshoot issues creating Application Proxy applications in the Microsoft Entra admin center
 services: active-directory
 author: kenwith
 manager: amycolannino
@@ -42,4 +42,4 @@ The error message should display in the top right corner when you create the app
    ![Notification prompt](./media/application-proxy-config-problem/error-message.png)
 
 ## Next steps
-[Enable Application Proxy in the Azure portal](application-proxy-add-on-premises-application.md)
+[Enable Application Proxy in the Microsoft Entra admin center](application-proxy-add-on-premises-application.md)

articles/active-directory/app-proxy/application-proxy-config-sso-how-to.md

@@ -28,7 +28,7 @@ To configure SSO, first make sure that your application is configured for Pre-Au
 
 For more information on the Pre-Authentication methods, see step 4 of the [app publishing document](application-proxy-add-on-premises-application.md).
 
-   ![Pre-authentication method in Azure portal](./media/application-proxy-config-sso-how-to/app-proxy.png)
+   ![Pre-authentication method in Microsoft Entra admin center](./media/application-proxy-config-sso-how-to/app-proxy.png)
 
 ## Configuring single sign-on modes for Application Proxy Applications
 Configure the specific type of single sign-on. The sign-on methods are classified based on what type of authentication the backend application uses. App Proxy applications support three types of sign-on:

articles/active-directory/app-proxy/application-proxy-configure-cookie-settings.md

@@ -40,11 +40,11 @@ Additionally, if your back-end application has cookies that need to be available
 
 
 
-## Set the cookie settings - Azure portal
+## Set the cookie settings - Microsoft Entra admin center
 
 [!INCLUDE [portal updates](~/articles/active-directory/includes/portal-update.md)]
 
-To set the cookie settings using the Azure portal:
+To set the cookie settings using the Microsoft Entra admin center:
 
 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Application Administrator](../roles/permissions-reference.md#application-administrator).
 1. Browse to **Identity** > **Applications** > **Enterprise applications** > **Application proxy**.

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

@@ -67,7 +67,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 portal](../fundamentals/add-custom-domain.md).
+For more detailed instructions, see [Add your custom domain name using the Microsoft Entra admin center](../fundamentals/add-custom-domain.md).
 
 ### Configure an app to use a custom domain
 
@@ -105,7 +105,7 @@ To publish your app through Application Proxy with a custom domain:
 
    ![Add CNAME DNS entry](./media/application-proxy-configure-custom-domain/dns-info.png)
 
-10. Follow the instructions at [Manage DNS records and record sets by using the Azure portal](../../dns/dns-operations-recordsets-portal.md) to add a DNS record that redirects the new external URL to the *msappproxy.net* domain in Azure DNS. If a different DNS provider is used, please contact the vendor for the instructions.
+10. Follow the instructions at [Manage DNS records and record sets by using the Microsoft Entra admin center](../../dns/dns-operations-recordsets-portal.md) to add a DNS record that redirects the new external URL to the *msappproxy.net* domain in Azure DNS. If a different DNS provider is used, please contact the vendor for the instructions.
 
    > [!IMPORTANT] 
    > Ensure that you are properly using a CNAME record that points to the *msappproxy.net* domain. Do not point records to IP addresses or server DNS names since these are not static and may impact the resiliency of the service.