Merge pull request #301998 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit e5ca4a1d3e19 · 2025-06-28T17:07:43.000Z
Merged by Learn.Build PR Management system
diff --git a/articles/app-service/quickstart-arm-template.md b/articles/app-service/quickstart-arm-template.md
@@ -25,8 +25,6 @@ To complete this quickstart, you need an Azure account with an active subscripti
 
 If you're familiar with using ARM templates, you can skip to the end by selecting this :::image type="content" source="~/reusable-content/ce-skilling/azure/media/template-deployments/deploy-to-azure-button.svg" alt-text="Button to deploy the Resource Manager template to Azure." border="false" link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.web%2Fapp-service-docs-windows%2Fazuredeploy.json"::: button. This button opens the ARM template in the Azure portal. 
 
-:::image type="content" source="media/quickstart-arm/create-windows-code.png" alt-text="Screenshot of the ARM Template in the Azure portal.":::
-
 In the Azure portal, select **Create new** to create a new Resource Group and then select the **Review + create** button to deploy the app.
 
 ::: zone-end
@@ -39,8 +37,6 @@ To complete this quickstart, you need an Azure account with an active subscripti
 
 If you're familiar with using ARM templates, you can skip to the end by selecting this :::image type="content" source="~/reusable-content/ce-skilling/azure/media/template-deployments/deploy-to-azure-button.svg" alt-text="Button to deploy the Resource Manager template to Azure." border="false" link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.web%2Fapp-service-docs-linux%2Fazuredeploy.json"::: button. This button opens the ARM template in the Azure portal. 
 
-:::image type="content" source="media/quickstart-arm/create-linux.png" alt-text="Screenshot of the ARM Template in the Azure portal.":::
-
 In the Azure portal, select **Create new** to create a new Resource Group and then select the **Review + create** button to deploy the app.
 ::: zone-end
 ::: zone pivot="platform-windows-container"
@@ -50,8 +46,6 @@ Get started with [Azure App Service](overview.md) by deploying an app to the clo
 
 If you're familiar with using ARM templates, you can skip to the end by selecting this :::image type="content" source="~/reusable-content/ce-skilling/azure/media/template-deployments/deploy-to-azure-button.svg" alt-text="Button to deploy the Resource Manager template to Azure." border="false" link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.web%2Fapp-service-docs-windows-container%2Fazuredeploy.json"::: button. This button opens the ARM template in the Azure portal. 
 
-:::image type="content" source="media/quickstart-arm/create-windows-container.png" alt-text="Screenshot of the ARM Template in the Azure portal.":::
-
 In the Azure portal, select **Create new** to create a new Resource Group and then select the **Review + create** button to deploy the app.
 ::: zone-end
 
@@ -97,7 +91,7 @@ This template contains several parameters that are predefined for your convenien
 | appServicePlanName | string  | `webAppPlan-<uniqueString>` | App Service Plan name based on a [unique string value](../azure-resource-manager/templates/template-functions-string.md#uniquestring) |
 | location   | string  | `[resourceGroup().location]` | [App region](../azure-resource-manager/templates/template-functions-resource.md#resourcegroup)
 | sku        | string  | `F1`                         | Instance size (F1 = Free Tier) |
-| linuxFxVersion   | string  | `DOTNETCORE|3.0`        | "Programming language stack &#124; Version" |
+| linuxFxVersion   | string  | `DOTNETCORE|9.0`        | "Programming language stack &#124; Version" |
 | repoUrl    | string  | ` `                          | External Git repo (optional) |
 
 ---
@@ -162,11 +156,11 @@ az webapp config show --resource-group myResourceGroup --name <app-name> --query
 
 | Language    | Example                                                                            |
 |-------------|------------------------------------------------------------------------------------|
-| **.NET**    | linuxFxVersion="DOTNETCORE&#124;3.0"                                               |
-| **Java**    | linuxFxVersion="JAVA&#124;21-java21 TOMCAT&#124;10.1-java21 JBOSSEAP&#124;8-java17"|
-| **Node.js** | linuxFxVersion="NODE&#124;10.15"                                                   |
-| **Python**  | linuxFxVersion="PYTHON&#124;3.7"                                                   |
-| **PHP**     | linuxFxVersion="PHP&#124;7.4"                                                      |
+| **.NET**    | linuxFxVersion="DOTNETCORE&#124;9.0"                                               |
+| **Java**    | linuxFxVersion="JAVA&#124;21-java21 TOMCAT&#124;11.0-java21 JBOSSEAP&#124;8-java17"|
+| **Node.js** | linuxFxVersion="NODE&#124;22-lts                                                   |
+| **Python**  | linuxFxVersion="PYTHON&#124;3.13"                                                   |
+| **PHP**     | linuxFxVersion="PHP&#124;8.4"                                                      |
 
 ---
 ::: zone-end
@@ -220,3 +214,4 @@ When no longer needed, [delete the resource group](../azure-resource-manager/man
 
 > [!div class="nextstepaction"]
 > [Secure with custom domain and certificate](tutorial-secure-domain-certificate.md)
+
diff --git a/articles/app-service/tutorial-php-mysql-app.md b/articles/app-service/tutorial-php-mysql-app.md
@@ -239,7 +239,7 @@ The creation wizard generated the connectivity variables for you already as [app
         A **Create connection** dialog is opened on top of the edit dialog.
     :::column-end:::
     :::column:::
-        :::image type="content" source="./media/tutorial-php-mysql-app/azure-portal-secure-connection-secrets-5.png" alt-text="A screenshot showing how to edit a service connector with a key vault connection." lightbox="./media/tutorial-php-mysql-app/azure-portal-secure-connection-secrets-5.png":::
+        :::image type="content" source="./media/tutorial-php-mysql-app/azure-portal-secure-connection-secrets-5.png" alt-text="A screenshot that shows how to edit a service connector with a key vault connection." lightbox="./media/tutorial-php-mysql-app/azure-portal-secure-connection-secrets-5.png":::
     :::column-end:::
 :::row-end:::
 :::row:::
diff --git a/articles/azure-resource-manager/managed-applications/publish-bicep-definition.md b/articles/azure-resource-manager/managed-applications/publish-bicep-definition.md
@@ -33,7 +33,7 @@ To complete the tasks in this article, you need the following items:
 ## Create a Bicep file
 
 > [!Note]
-> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](https://learn.microsoft.com/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
+> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
 
 Every managed application definition includes a file named _mainTemplate.json_. The template defines the Azure resources to deploy and is no different than a regular ARM template. You can develop the template using Bicep and then convert the Bicep file to JSON.
 
diff --git a/articles/azure-resource-manager/managed-applications/publish-service-catalog-app.md b/articles/azure-resource-manager/managed-applications/publish-service-catalog-app.md
@@ -34,7 +34,7 @@ To complete this quickstart, you need the following items:
 ## Create the ARM template
 
 > [!Note]
-> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](https://learn.microsoft.com/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
+> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
 
 Every managed application definition includes a file named _mainTemplate.json_. The template defines the Azure resources to deploy and is no different than a regular ARM template.
 
diff --git a/articles/azure-resource-manager/managed-applications/publish-service-catalog-bring-your-own-storage.md b/articles/azure-resource-manager/managed-applications/publish-service-catalog-bring-your-own-storage.md
@@ -35,7 +35,7 @@ To complete this quickstart, you need the following items:
 ## Create the ARM template
 
 > [!Note]
-> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](https://learn.microsoft.com/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
+> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
 
 Every managed application definition includes a file named _mainTemplate.json_. The template defines the Azure resources to deploy and is no different than a regular ARM template.
 
diff --git a/articles/azure-resource-manager/managed-applications/reference-main-template-artifact.md b/articles/azure-resource-manager/managed-applications/reference-main-template-artifact.md
@@ -12,7 +12,7 @@ This article is a reference for a _mainTemplate.json_ artifact in Azure Managed
 ## Deployment template
 
 > [!Note]
-> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](https://learn.microsoft.com/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
+> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
 
 The following JSON shows an example of _mainTemplate.json_ file for Azure Managed Applications:
 
diff --git a/articles/confidential-computing/confidential-vm-overview.md b/articles/confidential-computing/confidential-vm-overview.md
@@ -122,14 +122,14 @@ Pricing depends on your confidential VM size. For more information, see the [Pri
 
 Confidential VMs *don't support*:
 
-- [Azure Backup](https://learn.microsoft.com/azure/backup/backup-overview)
+- [Azure Backup](/azure/backup/backup-overview)
 - [Azure Site Recovery](https://azure.microsoft.com/products/site-recovery/)
-- Limited [Azure Compute Gallery](https://learn.microsoft.com/azure/virtual-machines/azure-compute-gallery) support
-- [Shared disks](https://learn.microsoft.com/azure/virtual-machines/disks-shared)
-- [Accelerated Networking](https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview)
-- [Live migration](https://learn.microsoft.com/windows-server/virtualization/hyper-v/manage/live-migration-overview)
-- [Screenshots under boot diagnostics](https://learn.microsoft.com/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view)
-- [Dynamic memory](https://learn.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831766(v=ws.11))
+- Limited [Azure Compute Gallery](/azure/virtual-machines/azure-compute-gallery) support
+- [Shared disks](/azure/virtual-machines/disks-shared)
+- [Accelerated Networking](/azure/virtual-network/accelerated-networking-overview)
+- [Live migration](/windows-server/virtualization/hyper-v/manage/live-migration-overview)
+- [Screenshots under boot diagnostics](/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view)
+- [Dynamic memory](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831766(v=ws.11))
 
 ## Next steps
 
diff --git a/articles/healthcare-apis/deidentification/quickstart-asynchronous-python.md b/articles/healthcare-apis/deidentification/quickstart-asynchronous-python.md
@@ -89,7 +89,7 @@ az storage account update --name $StorageAccountName --public-network-access Dis
 ```
 
 ## Use the python SDK
-The code below contains a sample from the [Azure Health Deidentification SDK for Python](https://learn.microsoft.com/python/api/overview/azure/health-deidentification?view=azure-python). 
+The code below contains a sample from the [Azure Health Deidentification SDK for Python](/python/api/overview/azure/health-deidentification). 
 
 ```Bash
 
diff --git a/articles/healthcare-apis/register-application-cli-rest.md b/articles/healthcare-apis/register-application-cli-rest.md
@@ -95,7 +95,7 @@ echo $clientsecret
 
 ## Change the flag for public client applications
 
-For public client applications that use the OAuth authorization protocol or features as described in [Public client and confidential client applications](https://learn.microsoft.com/entra/identity-platform/msal-client-applications#when-should-you-enable-a-public-client-flow-in-your-app-registration), change the **Allow public client flows** flag to **Yes**. For confidential client applications, skip this step.
+For public client applications that use the OAuth authorization protocol or features as described in [Public client and confidential client applications](/entra/identity-platform/msal-client-applications#when-should-you-enable-a-public-client-flow-in-your-app-registration), change the **Allow public client flows** flag to **Yes**. For confidential client applications, skip this step.
 
 [![Allow public client flows](media/app-registration-public-client.png)](media/app-registration-public-client.png#lightbox)
 
diff --git a/articles/healthcare-apis/register-application.md b/articles/healthcare-apis/register-application.md
@@ -39,7 +39,7 @@ If you keep this default value, the application registration is a **confidential
 
 [ ![Screenshot of confidential client application.](media/register-application-five.png) ](media/register-application-five.png#lightbox)
 
-If you change the default value to "Yes" for the "Allow public client flows" option in the advanced setting, the application registration is a **public client application** and a certificate or secret isn't required. The "Yes" value is useful when you want to build a public client application using the OAuth authorization protocol or features as described in [Public client and confidential client applications](https://learn.microsoft.com/entra/identity-platform/msal-client-applications#when-should-you-enable-a-public-client-flow-in-your-app-registration).
+If you change the default value to "Yes" for the "Allow public client flows" option in the advanced setting, the application registration is a **public client application** and a certificate or secret isn't required. The "Yes" value is useful when you want to build a public client application using the OAuth authorization protocol or features as described in [Public client and confidential client applications](/entra/identity-platform/msal-client-applications#when-should-you-enable-a-public-client-flow-in-your-app-registration).
 
 For tools that require a redirect URL, select **Add a platform** to configure the platform.
 
