Update Azure AI Foundry and Azure AI services references (#36799)

Author: JKirsch1

aspnetcore/blazor/host-and-deploy/server/index.md

@@ -151,7 +151,7 @@ For a deeper exploration of scaling server-side Blazor apps on the Azure Contain
 
 1. To create the container app managed identity and grant it access to blob storage and a key vault, complete the following steps:
 
-   1. In the Azure Portal, navigate to the overview page of the container app.
+   1. In the Azure portal, navigate to the overview page of the container app.
    1. Select **Service Connector** from the left navigation.
    1. Select **+ Create** from the top navigation.
    1. In the **Create connection** flyout menu, enter the following values:

aspnetcore/blazor/security/webassembly/hosted-with-azure-active-directory-b2c.md

@@ -328,7 +328,7 @@ builder.Services.AddMsalAuthentication(options =>
 
 The `{SCOPE URI}` is the default access token scope (for example, `https://contoso.onmicrosoft.com/00001111-aaaa-2222-bbbb-3333cccc4444/API.Access` or the custom URI that you configured in the Azure portal).
 
-The <xref:Microsoft.Extensions.DependencyInjection.MsalWebAssemblyServiceCollectionExtensions.AddMsalAuthentication%2A> method accepts a callback to configure the parameters required to authenticate an app. The values required for configuring the app can be obtained from the Azure Portal AAD configuration when you register the app.
+The <xref:Microsoft.Extensions.DependencyInjection.MsalWebAssemblyServiceCollectionExtensions.AddMsalAuthentication%2A> method accepts a callback to configure the parameters required to authenticate an app. The values required for configuring the app can be obtained from the Azure portal AAD configuration when you register the app.
 
 ### Access token scopes
 

aspnetcore/blazor/security/webassembly/hosted-with-microsoft-entra-id.md

@@ -334,7 +334,7 @@ builder.Services.AddMsalAuthentication(options =>
 });
 ```
 
-The <xref:Microsoft.Extensions.DependencyInjection.MsalWebAssemblyServiceCollectionExtensions.AddMsalAuthentication%2A> method accepts a callback to configure the parameters required to authenticate an app. The values required for configuring the app can be obtained from the Azure Portal ME-ID configuration when you register the app.
+The <xref:Microsoft.Extensions.DependencyInjection.MsalWebAssemblyServiceCollectionExtensions.AddMsalAuthentication%2A> method accepts a callback to configure the parameters required to authenticate an app. The values required for configuring the app can be obtained from the Azure portal ME-ID configuration when you register the app.
 
 ### Access token scopes
 

aspnetcore/blazor/security/webassembly/microsoft-entra-id-groups-and-roles-net-5-to-7.md

@@ -532,7 +532,7 @@ The following example assumes that the **CLIENT** and **SERVER** apps are config
 > [!NOTE]
 > When developing a hosted Blazor WebAssembly app or a client-server pair of standalone apps (a standalone Blazor WebAssembly app and an ASP.NET Core server API/web API app), the `appRoles` manifest property of both the client and the server Azure portal app registrations must include the same configured roles. After establishing the roles in the client app's manifest, copy them in their entirety to the server app's manifest. If you don't mirror the manifest `appRoles` between the client and server app registrations, role claims aren't established for authenticated users of the server API/web API, even if their access token has the correct entries in the role claims.
 
-Although you can't [assign roles to groups](/entra/identity/role-based-access-control/groups-concept) without an Microsoft Entra ID Premium account, you can assign roles to users and receive role claims for users with a standard Azure account. The guidance in this section doesn't require an ME-ID Premium account.
+Although you can't [assign roles to groups](/entra/identity/role-based-access-control/groups-concept) without a Microsoft Entra ID Premium account, you can assign roles to users and receive role claims for users with a standard Azure account. The guidance in this section doesn't require an ME-ID Premium account.
 
 When working with the default directory, follow the guidance in [Add app roles to your application and receive them in the token](/entra/identity-platform/howto-add-app-roles-in-apps) to configure and assign roles. If you aren't working with the default directory, edit the app's manifest in the Azure portal to establish the app's roles manually in the `appRoles` entry of the manifest file. The following is an example `appRoles` entry that creates `Admin` and `Developer` roles. These example roles are used later in this section's example at the component level to implement access restrictions:
 

aspnetcore/blazor/security/webassembly/standalone-with-azure-active-directory-b2c.md

@@ -90,7 +90,7 @@ The output location specified with the `-o|--output` option creates a project fo
 
 After creating the app, you should be able to:
 
-* Log into the app using an Microsoft Entra ID user account.
+* Log into the app using a Microsoft Entra ID user account.
 * Request access tokens for Microsoft APIs. For more information, see:
   * [Access token scopes](#access-token-scopes)
   * [Quickstart: Configure an application to expose web APIs](/entra/identity-platform/quickstart-configure-app-expose-web-apis).

aspnetcore/host-and-deploy/azure-apps/index.md

@@ -46,7 +46,7 @@ Understand and troubleshoot warnings and errors with ASP.NET Core projects.
 
 ### Platform
 
-The platform architecture (x86/x64) of an App Services app is set in the app's settings in the Azure Portal for apps that are hosted on an A-series compute (Basic) or higher hosting tier. Confirm that the app's publish settings (for example, in the Visual Studio [publish profile (.pubxml)](xref:host-and-deploy/visual-studio-publish-profiles)) match the setting in the app's service configuration in the Azure Portal.
+The platform architecture (x86/x64) of an App Services app is set in the app's settings in the Azure portal for apps that are hosted on an A-series compute (Basic) or higher hosting tier. Confirm that the app's publish settings (for example, in the Visual Studio [publish profile (.pubxml)](xref:host-and-deploy/visual-studio-publish-profiles)) match the setting in the app's service configuration in the Azure portal.
 
 :::moniker range=">= aspnetcore-2.2"
 
@@ -72,9 +72,9 @@ Include the following NuGet packages to provide automatic logging features for a
 
 The preceding packages must be explicitly referenced in the app's project file.
 
-## Override app configuration using the Azure Portal
+## Override app configuration using the Azure portal
 
-App settings in the Azure Portal permit you to set environment variables for the app. For more information, see the following resources:
+App settings in the Azure portal permit you to set environment variables for the app. For more information, see the following resources:
 
 * [Configure an App Service app (Azure documentation)](/azure/app-service/configure-common)
 * <xref:fundamentals/configuration/index#environment-variables-configuration-provider>
@@ -186,7 +186,7 @@ The Docker Hub at `https://hub.docker.com/_/microsoft-dotnet` contains the lates
 
 If a problem occurs using the preview site extension, open an [dotnet/AspNetCore issue](https://github.com/dotnet/AspNetCore/issues).
 
-1. From the Azure Portal, navigate to the App Service.
+1. From the Azure portal, navigate to the App Service.
 1. Select the web app.
 1. Type "ex" in the search box to filter for "Extensions" or scroll down the list of management tools.
 1. Select **Extensions**.
@@ -209,9 +209,9 @@ When the operation completes, the latest .NET Core preview is installed. Verify
    The command returns `True` when the x64 preview runtime is installed.
 
 > [!NOTE]
-> The platform architecture (x86/x64) of an App Services app is set in the app's settings in the Azure Portal for apps that are hosted on an A-series compute (Basic) or higher hosting tier. Confirm that the app's publish settings (for example, in the Visual Studio [publish profile (.pubxml)](xref:host-and-deploy/visual-studio-publish-profiles)) match the setting in the app's service configuration in the Azure portal.
+> The platform architecture (x86/x64) of an App Services app is set in the app's settings in the Azure portal for apps that are hosted on an A-series compute (Basic) or higher hosting tier. Confirm that the app's publish settings (for example, in the Visual Studio [publish profile (.pubxml)](xref:host-and-deploy/visual-studio-publish-profiles)) match the setting in the app's service configuration in the Azure portal.
 >
-> If the app is run in in-process mode and the platform architecture is configured for 64-bit (x64), the ASP.NET Core Module uses the 64-bit preview runtime, if present. Install the **ASP.NET Core {X.Y} (x64) Runtime** extension using the Azure Portal.
+> If the app is run in in-process mode and the platform architecture is configured for 64-bit (x64), the ASP.NET Core Module uses the 64-bit preview runtime, if present. Install the **ASP.NET Core {X.Y} (x64) Runtime** extension using the Azure portal.
 >
 > After installing the x64 preview runtime, run the following command in the Azure Kudu PowerShell command window to verify the installation. Substitute the ASP.NET Core runtime version for `{X.Y}` in the following command:
 >

aspnetcore/host-and-deploy/visual-studio-publish-profiles.md

@@ -214,7 +214,7 @@ In the preceding example:
 See [Microsoft.NET.Sdk.Publish](https://github.com/dotnet/sdk/tree/main/src/WebSdk#microsoftnetsdkpublish).
 
 <!-- As of Nov 2024 
-On the Azure Portal, settings/configuration, enable SCM and FTB basic auth publishing.
+On the Azure portal, settings/configuration, enable SCM and FTB basic auth publishing.
 Download the publish profile and get the username and password.
 
 Using the default publish profile, the following command publishes to an MSDeploy endpoint:

aspnetcore/security/key-vault-configuration.md

@@ -104,7 +104,7 @@ Complete the following steps to create an Azure Key Vault and store the sample a
 
 ## Use Application ID and X.509 certificate for non-Azure-hosted apps
 
-Configure Azure Key Vault and the app to use an Microsoft Entra ID Application ID and X.509 certificate to authenticate to a vault **when the app is hosted outside of Azure**. For more information, see [About keys, secrets, and certificates](/azure/key-vault/about-keys-secrets-and-certificates).
+Configure Azure Key Vault and the app to use a Microsoft Entra ID Application ID and X.509 certificate to authenticate to a vault **when the app is hosted outside of Azure**. For more information, see [About keys, secrets, and certificates](/azure/key-vault/about-keys-secrets-and-certificates).
 
 > [!NOTE]
 > Although using an Application ID and X.509 certificate is supported for apps hosted in Azure, it's not recommended. Instead, use [Managed identities for Azure resources](#use-managed-identities-for-azure-resources) when hosting an app in Azure. Managed identities don't require storing a certificate in the app or in the `Development` environment.
@@ -483,7 +483,7 @@ Complete the following steps to create an Azure Key Vault and store the sample a
 
 ## Use Application ID and X.509 certificate for non-Azure-hosted apps
 
-Configure Azure Key Vault and the app to use an Microsoft Entra ID Application ID and X.509 certificate to authenticate to a vault **when the app is hosted outside of Azure**. For more information, see [About keys, secrets, and certificates](/azure/key-vault/about-keys-secrets-and-certificates).
+Configure Azure Key Vault and the app to use a Microsoft Entra ID Application ID and X.509 certificate to authenticate to a vault **when the app is hosted outside of Azure**. For more information, see [About keys, secrets, and certificates](/azure/key-vault/about-keys-secrets-and-certificates).
 
 > [!NOTE]
 > Although using an Application ID and X.509 certificate is supported for apps hosted in Azure, it's not recommended. Instead, use [Managed identities for Azure resources](#use-managed-identities-for-azure-resources) when hosting an app in Azure. Managed identities don't require storing a certificate in the app or in the `Development` environment.

aspnetcore/test/troubleshoot-azure-iis.md

@@ -328,7 +328,7 @@ The console output from the app, showing any errors, is piped to the Kudu consol
 
 The ASP.NET Core Module stdout log often records useful error messages not found in the Application Event Log. To enable and view stdout logs:
 
-1. In the Azure Portal, navigate to the web app.
+1. In the Azure portal, navigate to the web app.
 1. In the **App Service** blade, enter **kudu** in the search box.
 1. Select **Advanced Tools** > **Go**.
 1. Select  **Debug console > CMD**.

aspnetcore/test/troubleshoot-azure-iis/includes/troubleshoot-azure-iis7.md

@@ -316,7 +316,7 @@ The console output from the app, showing any errors, is piped to the Kudu consol
 
 The ASP.NET Core Module stdout log often records useful error messages not found in the Application Event Log. To enable and view stdout logs:
 
-1. In the Azure Portal, navigate to the web app.
+1. In the Azure portal, navigate to the web app.
 1. In the **App Service** blade, enter **kudu** in the search box.
 1. Select **Advanced Tools** > **Go**.
 1. Select  **Debug console > CMD**.