diff --git a/aspnetcore/host-and-deploy/scaling-aspnet-apps/scaling-aspnet-apps.md b/aspnetcore/host-and-deploy/scaling-aspnet-apps/scaling-aspnet-apps.md index 0685e74731ce..14cdd5598b47 100644 --- a/aspnetcore/host-and-deploy/scaling-aspnet-apps/scaling-aspnet-apps.md +++ b/aspnetcore/host-and-deploy/scaling-aspnet-apps/scaling-aspnet-apps.md @@ -5,7 +5,7 @@ description: Learn how to horizontally scale ASP.NET Core apps on Azure and addr ms.author: alexwolf ms.custom: mvc uid: host-and-deploy/scaling-aspnet-apps/scaling-aspnet-apps -ms.date: 8/31/2022 +ms.date: 7/25/2025 --- # Deploying and scaling an ASP.NET Core app on Azure Container Apps @@ -258,7 +258,7 @@ The necessary Azure resources have been created. In this section the app code is The preceding changes allow the app to manage data protection using a centralized, scalable architecture. `DefaultAzureCredential` discovers the managed identity configurations enabled earlier when the app is redeployed. > [!NOTE] -> The preceding example uses to simplify authentication while developing apps that deploy to Azure by combining credentials used in Azure hosting environments with credentials used in local development. When moving to production, an alternative is a better choice, such as . For more information, see [Authenticate Azure-hosted .NET apps to Azure resources using a system-assigned managed identity](/dotnet/azure/sdk/authentication/system-assigned-managed-identity). +> The preceding example uses to simplify authentication while developing apps that deploy to Azure by combining credentials used in Azure hosting environments with credentials used in local development. When moving to production, an alternative such as may be more appropriate. For more information, see [Authenticate Azure-hosted .NET apps to Azure resources using a system-assigned managed identity](/dotnet/azure/sdk/authentication/system-assigned-managed-identity). Update the placeholders in `AzureURIs` section of the `appsettings.json` file to include the following: