warning related changes

jainsabal · jainsabal · commit 1b6e5b7c5100 · 2025-08-06T19:28:39.000+05:30
diff --git a/articles/frontdoor/TOC.yml b/articles/frontdoor/TOC.yml
@@ -178,7 +178,7 @@
       - name: Custom domain
         href: migrate-cdn-to-front-door.md
     - name: AFD/CDN Classic migration FAQ
-      href: afd-cdn-classic-migration-faq.md
+      href: migration-faq.md
     - name: Post migration Dev-Ops experience
       href: post-migration-dev-ops-experience.md
   - name: Upgrades
diff --git a/articles/frontdoor/post-migration-dev-ops-experience.md b/articles/frontdoor/post-migration-dev-ops-experience.md
@@ -36,40 +36,40 @@ After migration, all classic AFD resources are migrated to AFD Standard and Prem
 After migration, all classic AFD resources are migrated to AFD Standard and Premium.
 
 - **Export ARM templates for Front Door Standard/Premium** using any of the following:
-  - **Azure portal**: [Export template in Azure portal](https://learn.microsoft.com/azure/azure-resource-manager/templates/export-template-portal).
-  - **Azure CLI**: [Export template in Azure CLI](https://learn.microsoft.com/azure/azure-resource-manager/templates/export-template-cli).
-  - **Azure PowerShell**: [Export template in Azure PowerShell](https://learn.microsoft.com/azure/azure-resource-manager/templates/export-template-powershell).
+  - **Azure portal**: [Export template in Azure portal](../azure-resource-manager/templates/export-template-portal.md).
+  - **Azure CLI**: [Export template in Azure CLI](../azure-resource-manager/templates/export-template-cli.md).
+  - **Azure PowerShell**: [Export template in Azure PowerShell](../azure-resource-manager/templates/export-template-powershell.md).
 - **Update ARM templates in your pipeline** to use the new Front Door Standard/Premium template instead of the Front Door (Classic) template. In Azure DevOps or GitHub Actions, update the template path and parameters in your deployment step, then deploy the new template.
 - **Validate**: Remove or archive references to the classic Front Door template to avoid confusion.
 
 ## Bicep
 
 ### Prerequisites
 
-- Install the Bicep CLI and tools. See [Set up Bicep development and deployment environments](https://learn.microsoft.com/azure/azure-resource-manager/bicep/install).
+- Install the Bicep CLI and tools. See [Set up Bicep development and deployment environments](../azure-resource-manager/bicep/install.md).
 
 ### Steps
 
 After migration, all classic AFD resources are migrated to AFD Standard and Premium.
 
-- **Generate a Bicep template for Front Door Standard/Premium** by decompiling an exported ARM template. See [Decompile ARM template JSON to Bicep](https://learn.microsoft.com/azure/azure-resource-manager/bicep/decompile?tabs=azure-cli).
+- **Generate a Bicep template for Front Door Standard/Premium** by decompiling an exported ARM template. See [Decompile ARM template JSON to Bicep](../azure-resource-manager/bicep/decompile.md?tabs=azure-cli).
 - **Update Bicep files in your pipeline**: Replace Front Door Classic definitions with Standard/Premium. This may include updating resource types such as [`Microsoft.Cdn/profiles`](https://learn.microsoft.com/azure/templates/microsoft.cdn/profiles?pivots=deployment-language-bicep) and child resources (endpoints, routes, etc.).
 - **Test** a deployment (for example, `az deployment group create`) to verify provisioning of AFD Standard/Premium.
 
 ## PowerShell
 
 ### Prerequisites
 
-Make sure you have the latest Azure PowerShell Az modules installed (Az.Cdn module version that supports AFD Standard/Premium). See [Install Azure PowerShell](https://learn.microsoft.com/powershell/azure/install-azps-windows?view=azps-14.2.0&tabs=powershell&pivots=windows-psgallery).
+Make sure you have the latest Azure PowerShell Az modules installed (Az.Cdn module version that supports AFD Standard/Premium). See [Install Azure PowerShell](https://learn.microsoft.com/powershell/azure/install-azps-windows).
 
 ### Steps
 
 - **Update PowerShell deployment scripts**: Replace any Front Door (Classic) cmdlets with AFD Standard/Premium cmdlets. For examples, see the [Azure Front Door PowerShell quickstart](create-front-door-powershell.md).
 - **Incorporate new configuration and remove old references**: Ensure scripts configure required components (origins, origin groups, routes, rules, etc.). Remove or comment commands that manage Classic Front Door.
 - Command group mapping:
-  - AzFrontDoorCdn commands under the [Az.Cdn module](https://learn.microsoft.com/powershell/module/az.cdn/?view=azps-14.2.0) are for AFD Standard/Premium.
-  - AzCdn commands under the [Az.Cdn module](https://learn.microsoft.com/powershell/module/az.cdn/?view=azps-14.2.0) are for CDN Classic.
-  - The [Az.FrontDoor module](https://learn.microsoft.com/powershell/module/az.frontdoor/?view=azps-14.2.0) is for AFD Classic.
+  - AzFrontDoorCdn commands under the [Az.Cdn module](https://learn.microsoft.com/powershell/module/az.cdn/) are for AFD Standard/Premium.
+  - AzCdn commands under the [Az.Cdn module](https://learn.microsoft.com/powershell/module/az.cdn/) are for CDN Classic.
+  - The [Az.FrontDoor module](https://learn.microsoft.com/powershell/module/az.frontdoor/) is for AFD Classic.
 - **Test** your script (locally or in a test pipeline) to verify creation or updates to AFD Standard/Premium, then commit changes to your pipeline.
 
 ## CLI
@@ -81,14 +81,14 @@ Make sure you have the latest Azure PowerShell Az modules installed (Az.Cdn modu
 
 ### Steps
 
-- **Update CLI commands in scripts**: Use the Azure Front Door Standard/Premium command group: [`az afd`](https://learn.microsoft.com/cli/azure/afd?view=azure-cli-latest).
+- **Update CLI commands in scripts**: Use the Azure Front Door Standard/Premium command group: [`az afd`](https://learn.microsoft.com/cli/azure/afd).
 - **Replace or remove Front Door Classic CLI usage**:
-  - CDN Classic commands: [`az cdn`](https://learn.microsoft.com/cli/azure/cdn?view=azure-cli-latest)
-  - AFD Classic commands: [`az network front-door`](https://learn.microsoft.com/cli/azure/network/front-door?view=azure-cli-latest)
+  - CDN Classic commands: [`az cdn`](https://learn.microsoft.com/cli/azure/cdn)
+  - AFD Classic commands: [`az network front-door`](https://learn.microsoft.com/cli/azure/network/front-door)
 - **Validate** the updated CLI script manually or in a staging pipeline to ensure successful configuration of Front Door Standard/Premium.
 
 ## Next step
 
-* For more questions, refer to the [AFD/CDN Classic Migration FAQ](afd-cdn-classic-migration-faq.md).
+* For more questions, refer to the [AFD/CDN Classic Migration FAQ](migration-faq.md).
 * Understand the [settings mapping between Azure Front Door tiers](tier-mapping.md).
 
diff --git a/articles/frontdoor/standard-premium/how-to-enable-private-link-web-app-powershell.md b/articles/frontdoor/standard-premium/how-to-enable-private-link-web-app-powershell.md
@@ -19,7 +19,7 @@ This article guides you through how to configure Azure Front Door Premium tier t
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - Azure PowerShell installed locally or Azure Cloud Shell
 - Azure FrontDoor Premium profile, endpoint, and origin group. For more information on how to create an Azure Front Door profile, see [Create a Front Door - PowerShell](../create-front-door-powershell.md).
-- Azure App Service (WebApp) instance. For more information on how to create an Azure App Service, see [Create an App Service - PowerShell](../create-app-service-plan-powershell.md).
+- Azure App Service (WebApp) instance. For more information on how to create an Azure App Service, see [Create an App Service - PowerShell](../../app-service/quickstart-dotnetcore.md?tabs=net80&pivots=development-environment-ps).
 
 > [!NOTE]
 > Private endpoints requires your App Service plan to meet some requirements. For more information, see [Using Private Endpoints for Azure Web App](../../app-service/networking/private-endpoint.md).
