Merge pull request #314645 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-13 17:04 UTC

Author: learn-build-service-prod[bot]

articles/app-service/includes/scenario-secure-app-clean-up-resources.md

@@ -32,15 +32,15 @@ This command might take several minutes to run.
 
 ### Delete the app registration
 
-In the [Microsoft Entra admin center](https://entra.microsoft.com), select **Applications** > **App registrations**. Then select the application you created.
+In the [Microsoft Entra admin center](https://entra.microsoft.com), select **App registrations**. Then select the application you created.
 :::image type="content" alt-text="Screenshot that shows selecting app registration." source="../media/scenario-secure-app-clean-up-resources/select-app-registration.png":::
 
 In the app registration overview, select **Delete**.
 :::image type="content" alt-text="Screenshot that shows deleting the app registration." source="../media/scenario-secure-app-clean-up-resources/delete-app-registration.png":::
 
 ### Delete the external tenant
 
-If you created a new external tenant, you can [delete it](/entra/external-id/customers/how-to-delete-external-tenant-portal).  In to the [Microsoft Entra admin center](https://entra.microsoft.com), browse to **Identity** > **Overview** > **Manage tenants**.
+If you created a new external tenant, you can [delete it](/entra/external-id/customers/how-to-delete-external-tenant-portal).  In to the [Microsoft Entra admin center](https://entra.microsoft.com), browse to **Entra ID** > **Overview** > **Manage tenants**.
 
 Select the tenant you want to delete, and then select **Delete**.
 

articles/app-service/includes/tutorial-set-up-app-service-authentication/after.md

@@ -150,7 +150,7 @@ When you enabled the App Service authentication/authorization module in the prev
 1. To check the settings, sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](/entra/identity/role-based-access-control/permissions-reference#application-developer).
 1. If you chose external configuration, use the **Settings** icon in the top menu to switch to the external tenant with your web app from the **Directories** + **subscriptions** menu. 
 
-1. Browse to **Identity** > **Applications** > **App registrations** and select **Applications** > **App registrations** from the menu. 
+1. Browse to **Entra ID** > **App registrations**, and select **App registrations** from the menu. 
 1. Select the app registration that was created. 
 1. In the overview, verify that **Supported account types** is set to **My organization only**.
 

articles/app-service/scenario-secure-app-authentication-app-service.md

@@ -5,7 +5,7 @@ author: cephalin
 ms.author: cephalin
 ms.service: azure-app-service
 ms.topic: tutorial
-ms.date: 05/16/2024
+ms.date: 03/17/2026
 ms.reviewer: mahender
 ms.custom: azureday1, AppServiceIdentity
 #Customer intent: As an application developer, enable authentication and authorization for a web app running on Azure App Service.

articles/app-service/tutorial-connect-msi-azure-database.md

@@ -6,7 +6,7 @@ description: Learn how to sign up, set up, and use Nutanix Cloud Clusters on Azu
 ms.topic: get-started
 ms.subservice: baremetal-nutanix
 ms.custom: engagement-fy23
-ms.date: 7/30/2025
+ms.date: 04/13/2026
 ms.service: azure-baremetal-infrastructure
 # Customer intent: As an IT administrator, I want to sign up for and configure Nutanix Cloud Clusters on Azure, so that I can efficiently manage my cloud infrastructure while ensuring connectivity and compliance with my organization’s requirements.
 ---
@@ -19,7 +19,7 @@ Learn how to get started with Nutanix Cloud Clusters (NC2) on Azure. You can als
 
 To deploy NC2 on Azure you must have the following:
 
-* An **active subscription** which will need to be allowlisted.
+* An **active subscription**. 
 * An **Azure account** associated with an active subscription and a **Microsoft Entra ID** with permissions to create an app registration in Microsoft Entra ID with access to the subscription.
 * A **My Nutanix** account.
 * In addition, there are **networking and Azure quota** requirements to consider.

articles/app-service/tutorial-dotnetcore-sqldb-app.md

@@ -77,11 +77,11 @@ Dynamic sessions are available in the following regions. Both code interpreter a
 | East US | North Europe | Japan East | |
 | East US 2 | Norway East | Japan West | |
 | North Central US | Poland Central | Jio India West | |
-| West Central US | Spain Central | Korea Central | |
-| West US | Sweden Central | South India | |
-| West US 2 | Switzerland North | Southeast Asia | |
-| West US 3 | Switzerland West | | |
-| | UK South | | |
+| South Central US | Spain Central | Korea Central | |
+| West Central US | Sweden Central | South India | |
+| West US | Switzerland North | Southeast Asia | |
+| West US 2 | Switzerland West | | |
+| West US 3 | UK South | | |
 | | UK West | | |
 | | West Europe | | |
 

articles/baremetal-infrastructure/workloads/nc2-on-azure/get-started.md

@@ -687,7 +687,7 @@ The sub path can refer to either a folder or a file in the volume.
 
 - If the sub path refers to a file, the mount path should refer to a file that doesn't already exist in the container.
 
-    For example, suppose the sub path is `my-volume-folder/my-volume-file.txt`, and the mount path is `/my-container-folder/my-container-file`. The folder `/my-container-folder` should already exist in the container but shouldn't yet contain the file `my-container-file.txt`.
+    For example, suppose the sub path is `my-volume-folder/my-volume-file.txt`, and the mount path is `/my-container-folder/my-container-file.txt`. The folder `/my-container-folder` should already exist in the container but shouldn't yet contain the file `my-container-file.txt`.
 
 The system ignores any sub path trailing slashes.
 

articles/container-apps/sessions.md

@@ -7,7 +7,7 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
-ms.date: 11/17/2025
+ms.date: 04/01/2026
 ms.author: jkinma
 ms.custom: sfi-image-nochange
 service.tree.id: 95459a4b-434c-4f83-879b-aa5f509fc7fa
@@ -212,13 +212,20 @@ You give others access to view, download, and pay invoices by assigning them the
 
 You might need to send your monthly invoice to your accounting team or to another one of your email addresses. You can do so without granting your accounting team or the secondary email access to your billing profile.
 
-1.  Sign in to the [Azure portal](https://portal.azure.com).
-1.  Search for **Cost Management + Billing**.  
-1.  Select **Invoices** from the left-hand side and then select **Invoice email preference** from the top of the page.  
-    :::image type="content" border="true" source="./media/download-azure-invoice/mca-billing-profile-select-email-invoice.png" lightbox="./media/download-azure-invoice/mca-billing-profile-select-email-invoice-zoomed.png" alt-text="Screenshot that shows the Email invoice option for invoices.":::
-1.  If you have multiple billing profiles, select a billing profile.
+1. Sign in to the [Azure portal](https://portal.azure.com).
+1. Search for **Cost Management + Billing**.  
+1. Select **Invoices** from the left-hand side and then select **Invoice email preference** from the top of the page.  
+1. If you have multiple billing profiles, select a billing profile.
 1. In the :::no-loc text="additional"::: recipients section, add the email addresses to receive invoices.
-1.  Select **Save**.
+1. Select **Save**.
+
+## Update the bill-to address or PO number on an invoice
+
+1. From the **Invoice list**, select the invoice you want to update.
+
+1. On the **Invoice details** page, select **Change bill-to + PO number** from the menu at the top of the page.
+
+1. Update the **bill-to address** and/or **PO number**, then regenerate the invoice to apply your changes.
 
 ## Azure Government support for invoices
 

articles/container-apps/storage-mounts.md

@@ -328,34 +328,78 @@ sections:
     - question: | 
         What actions should I take to avoid service disruption?
       answer: |
-        Microsoft will automatically migrate eligible profiles on a "best effort" basis to Azure Front Door Standard/Premium between April 10, 2026 and April 14, 2026, unless you notify us otherwise. Classic and Azure Front Door Standard/Premium SKUs are charged differently. Please refer to the [pricing page](https://azure.microsoft.com/en-us/pricing/details/frontdoor/?msockid=06fc59dfa84d6e0612124fafa9586f44) for details. 
+        Microsoft will automatically migrate eligible profiles on a "best effort" basis to Azure Front Door Standard/Premium between April 10 and April 14, 2026, unless you notify us otherwise. Classic and Azure Front Door Standard/Premium SKUs are charged differently. Please refer to the [pricing page](https://azure.microsoft.com/en-us/pricing/details/frontdoor/?msockid=06fc59dfa84d6e0612124fafa9586f44) for details. 
         
         If you plan to migrate to Azure Front Door Standard/Premium or switch to BYOC yourself, please notify Microsoft by April 9, 2026 by setting the required feature flag, see instructions below.
         
         You can check the auto-migration eligibility by following [the migration steps](https://learn.microsoft.com/en-us/azure/frontdoor/migrate-tier). If step 1 Validate compatibility succeeds, your profile is eligible. If you proceed with auto‑migration, monitor your email for final migration confirmation and status updates.
         
         **Required action**
            
-        Azure CDN from Microsoft (classic)
+        **Azure CDN from Microsoft (classic)**
         
         Before April 9, 2026: 
         - [Migrate to Azure Front Door Standard or Premium](https://learn.microsoft.com/en-us/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) or [move to Bring Your Own Certificate (BYOC)](https://learn.microsoft.com/en-us/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate).
         - If you plan to migrate to Azure Front Door or move to BYOC yourself before April 14, 2026 or  want to opt out of auto migration and willing to risk disruption to the HTTPS traffic, you will need to set a Feature Flag by following [instruction provided](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/preview-features?tabs=azure-portal), and selecting the Feature Flag "Microsoft.Cdn/DoNotAutoMigrateClassicManagedCertificatesProfiles") before April 9, 2026. Doing so will prevent Microsoft from migrating your eligible classic managed certificate profiles to Azure Front Door. 
        
-        Between April 10, 2026 and April 14, 2026: 
-        - Customers who didn't set the said Feature Flag before April 9, 2026, their profiles will be migrated to Azure Front Door Standard or Premium SKU on a "best effort" basis and should watch for an email related to their migration status.  
-        - Customers who set the said Feature Flag but are still consuming services with classic SKUs will have until April 14, 2026 to complete migration or move to BYOC. 
+        Between April 10 and April 14, 2026: 
+        - Customers who didn't set the said Feature Flag before April 9, 2026, their profiles will be migrated to Azure Front Door Standard or Premium SKU on a "best effort" basis and should watch for an email related to their migration status. You can also check migration status by following steps in the following question.
+        - Customers who set the said feature flag but are still consuming services with classic SKUs will have until April 14, 2026 to complete migration or move to BYOC. 
 
-        Azure Front Door (classic)
+        **Azure Front Door (classic)**
   
         Before April 9, 2026:
         - [Migrate to Azure Front Door Standard or Premium](https://learn.microsoft.com/en-us/azure/frontdoor/tier-migration) or [move to Bring Your Own Certificate (BYOC)](https://learn.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https?tabs=powershell).
 
         - If you plan to migrate to Azure Front Door or transition to Bring Your Own Certificate (BYOC) before April 14, 2026, or if you choose to opt out of auto migration and accept the risk of HTTPS traffic disruption, you will need to set a feature flag by following the [instruction provided](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/preview-features?tabs=azure-portal), and selecting the Feature Flag "Microsoft.Cdn/DoNotAutoMigrateClassicManagedCertificatesProfiles" before April 9, 2026. Doing so will prevent Microsoft from migrating your eligible classic managed certificate profiles to Azure Front Door.
 
-        Between April 10, 2026 and April 14, 2026:
+        Between April 10 and April 14, 2026:
+        - For customers who do not set the feature flag by April 9, 2026, Microsoft will migrate their profiles to Azure Front Door Standard or Premium SKU on a "best effort" basis. Customers are advised to monitor their email for updates on migration status. You can also check migration status by following steps in the following question.
+        - Customers who have set the said Feature Flag but are still consuming services with classic SKUs will have until April 14, 2026 to complete migration or move to BYOC.
 
-        - For customers who do not set the feature flag by April 9, 2026, Microsoft will migrate their profiles to Azure Front Door Standard or Premium SKU on a "best effort" basis. Customers are advised to monitor their email for updates on migration status. Customers who have set the said Feature Flag but are still consuming services with classic SKUs will have until April 14, 2026 to complete migration or move to BYOC.
+    - question: |
+         How to check the migration status? 
+      answer: |
+         Between April 10 and April 14, 2026, please check the status of your profile's migration.
+         
+         **Azure CDN from Microsoft (classic):**
+         Migration from Azure CDN (classic) is in-place tier upgrade to Azure Front Door Standard tier, using the same profile name. 
+            - After migration, the profile will appear as Azure Front Door Standard.
+            - The original CDN (classic) profile will no longer be visible.
+         Follow steps below to check the migration status.
+            - Go to the Azure portal and search for Front Doors.
+            - Identify the classic CDN profile names. For each profile: 
+                - If the profile is now on Azure Front Door Standard, the migration is successful. You can confirm by opening the profile and reviewing the configuration details.
+                - If the profile is still on Azure CDN (classic), open the profile, select Migration, and review the migration status:
+                      - No migration step initiated: This classic instance is not eligible for auto-migration.
+                      - Error at Step 1 Validate compatibility: Resolve the reported errors, then re-run validation and continue the migration. At this state no migration has not been done. You are responsible for completing the migration or moving to BYOC. 
+                      - Status at Step 2 Prepare for migration through Step 5 Migrate: Migration is in progress. Please wait until the migration completes. After step 2 Prepare for migration, the profile will be in a read-only state. Migration only affects control plan and there would not be any impact on traffic during the migration. 
+            - If migration is complete, the tier will change from CDN Classic to Standard and the profile name will remain the same.
+            - After migration, please monitor the domain state in the standard or premium profile and check if you need to revalidate domain ownership for managed certificate renewal. 
+            - If we are unable to migrate, profile will be rolled back to the original state. If you still wish to use managed certificates without any disruption to HTTPS traffic, you will be responsible for migrating to Azure Front Door or BYOC before 14 April 2026. 
+
+         **Azure Front Door (classic):**
+          To validate the migration status, please follow the steps below based on the migration documentation:
+            - Sign in to the Azure Portal -> Front Doors, and search for Front Door (Classic). 
+            - Select your Azure Front Door (Classic) instance and navigate to: Settings → Migration
+            - Review the migration status:
+                - No migration step initiated: This classic instance is not eligible for auto-migration. 
+                - Error at Step 1 Validate compatibility: Resolve the reported errors, then re-run validation and continue the migration. At this state no migration has not been done. You are responsible for completing the migration or moving to BYOC. 
+                - Status at Step 2 Prepare for migration through Step 5 Migrate: Migration is in progress. Please wait until the migration completes. After step 2 Prepare for migration, the profile will be in a read-only state. Migration only affects control plan and there would not be any impact on traffic during the migration. 
+            - If migration is complete, the tier will change from Azure Front Door Classic to Standard and the new profile name is in the format of [Endpointprefix]-migrated. Learn more in [Azure Front Door (Classic) To Standard/Premium Tier Migration Name convention](https://learn.microsoft.com/en-us/azure/frontdoor/tier-migration#naming-convention-used-for-migration).
+            - After migration, please monitor the domain state in the standard or premium profile and check if you need to revalidate domain ownership for managed certificate renewal. 
+            - If we are unable to migrate, profile will be rolled back to the original state. If you still wish to use managed certificates without any disruption to HTTPS traffic, you will be responsible for migrating to Azure Front Door or BYOC before 14 April 2026.
+    
+    - question: |
+        Do I need to take any action to renew my managed certificate after migration?
+      answer: |
+       In most cases, no action is required. After your profile is migrated, Azure Front Door automatically attempts to rotate your managed certificate if it is within 45 days of expiry. 
+       - If your domain is CNAME-mapped to Azure Front Door and meets CAA record and domain state requirements, the certificate is auto-rotated. Auto-rotation job runs every 6-8 hours and takes around 24-48 hours to complete. If the autorotation fails, the domain validation state goes to 'Pending validation' and you can revalidate domain ownership to manually trigger validation. 
+       - If autorotation does not meet the above-mentioned validation requirements, the certificate state changes to Pending revalidation, and you need to revalidate domain ownership. 
+
+       You can manually revalidate domain ownership for renewal by:
+         - Adding the required DNS validation record following step 3 for [domains pending validation]:(https://learn.microsoft.com/en-us/azure/frontdoor/standard-premium/how-to-add-custom-domain#add-a-new-custom-domain)
+         - Or triggering validation manually using PowerShell or Azure CLI (`RefreshValidation`).
     
   - name: Billing
     questions: