Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-limits-deny-assignments

Author: rolyon

articles/app-service/includes/quickstart-python/create-app-cli.md

@@ -17,10 +17,10 @@ az login
 Create the webapp and other resources, then deploy your code to Azure using [az webapp up](/cli/azure/webapp#az-webapp-up).
 
 ```azurecli
-az webapp up --runtime PYTHON:3.9 --sku B1 --logs
+az webapp up --runtime PYTHON:3.13 --sku B1 --logs
 ```
 
-* The `--runtime` parameter specifies what version of Python your app is running. This example uses Python 3.9. To list all available runtimes, use the command `az webapp list-runtimes --os linux --output table`.
+* The `--runtime` parameter specifies what version of Python your app is running. This example uses Python 3.13. To list all available runtimes, use the command `az webapp list-runtimes --os linux --output table`.
 * The `--sku` parameter defines the size (CPU, memory) and cost of the app service plan. This example uses the B1 (Basic) service plan, which will incur a small cost in your Azure subscription. For a full list of App Service plans, view the [App Service pricing](https://azure.microsoft.com/pricing/details/app-service/linux/) page.
 * The `--logs` flag configures default logging required to enable viewing the log stream immediately after launching the webapp.
 * You can optionally specify a name with the argument `--name <app-name>`. If you don't provide one, then a name will be automatically generated.
@@ -47,7 +47,7 @@ You can launch the app at http://&lt;app-name>.azurewebsites.net
   "name": "&lt;app-name>",
   "os": "&lt;os-type>",
   "resourcegroup": "&lt;group-name>",
-  "runtime_version": "python|3.9",
+  "runtime_version": "python|3.13",
   "runtime_version_detected": "0.0",
   "sku": "FREE",
   "src_path": "&lt;your-folder-location>"

articles/app-service/includes/quickstart-python/create-app-service-azure-portal-3.md

@@ -8,6 +8,6 @@ On the **Create Web App** page, fill out the form as follows.
 
 1. **Resource Group** → Select **Create new** and use a name of *msdocs-python-webapp-quickstart*.
 1. **Name** → *msdocs-python-webapp-quickstart-XYZ* where XYZ is any three random characters. This name must be unique across Azure.
-1. **Runtime stack** → **Python 3.9**.
+1. **Runtime stack** → **Python 3.13**.
 1. **Region** → Any Azure region near you.
 1. **App Service Plan** → Under **Pricing plan**, select **Explore pricing plans** to select a different App Service plan.

articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-5.md

@@ -4,4 +4,4 @@ ms.author: daberry
 ms.topic: include
 ms.date: 04/30/2022
 ---
-Select the runtime stack for the application. In this example, select **Python 3.9**.
+Select the runtime stack for the application. In this example, select **Python 3.13**.

articles/app-service/quickstart-dotnetcore.md

@@ -36,18 +36,13 @@ target cross-platform with .NET 8.0.
 
 # Quickstart: Deploy an ASP.NET web app
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 In this quickstart, you learn how to create and deploy your first ASP.NET web app to [Azure App Service](overview.md). App Service supports various versions of .NET apps. It provides a highly scalable, self-patching web hosting service. ASP.NET web apps are cross-platform and can be hosted on Linux or Windows. When you're finished, you have an Azure resource group that includes an App Service hosting plan and an App Service with a deployed web application.
 
 Alternatively, you can deploy an ASP.NET web app as part of a [Windows or Linux container in App Service](quickstart-custom-container.md).
 
 > [!TIP]
 > Find GitHub Copilot tips in the Visual Studio, Visual Studio Code, and Azure portal steps.
 
-> [!NOTE]
-> Building .NET 9 (STS) apps with Windows App Service using MSBuild or SCM_DO_BUILD isn't yet supported. Support for these build scenarios is planned after the initial general availability date and by December 4, 2024. Deployments that build outside of App Service through Visual Studio, Visual Studio Code, GitHub Actions, and Azure DevOps are fully supported.
-
 ## Prerequisites
 
 :::zone target="docs" pivot="development-environment-vs"
@@ -111,23 +106,26 @@ If you already installed Visual Studio 2022:
 
 :::zone-end
 
-:::zone target="docs" pivot="development-environment-azd"
-
-- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/dotnet).
-- The [Azure Developer CLI](/azure/developer/azure-developer-cli/install-azd).
-- [The latest .NET 8.0 SDK](https://dotnet.microsoft.com/download/dotnet/8.0).
+:::zone target="docs" pivot="development-environment-vs, development-environment-azure-portal, development-environment-ps, development-environment-vscode, development-environment-cli"
 
-:::zone-end
+## Skip to the end
 
-:::zone target="docs" pivot="development-environment-vs, development-environment-azure-portal, development-environment-ps, development-environment-vscode, development-environment-cli"
+You can quickly deploy the ASP.NET Core sample app in this tutorial using Azure Developer CLI and see it running in Azure. Just run the following commands in the [Azure Cloud Shell](https://shell.azure.com), and follow the prompt:
 
-## Create an ASP.NET web app
+```bash
+mkdir dotnetcore-quickstart
+cd dotnetcore-quickstart
+azd init --template https://github.com/Azure-Samples/quickstart-deploy-aspnet-core-app-service.git
+azd up
+```
 
-:::zone-end
+And, to delete the resources:
 
-:::zone target="docs" pivot="development-environment-azd"
+```bash
+azd down
+```
 
-## Initialize the ASP.NET web app template
+## Create an ASP.NET web app
 
 :::zone-end
 
@@ -223,32 +221,6 @@ In this step, you fork a demo project to deploy.
 
 :::zone-end
 
-:::zone target="docs" pivot="development-environment-azd"
-
-This quickstart uses the [Azure Developer CLI](/azure/developer/azure-developer-cli/overview) (`azd`) both to create Azure resources and deploy code to it. For more information, see [Install the Azure Developer CLI](/azure/developer/azure-developer-cli/install-azd?tabs=winget-windows%2Cbrew-mac%2Cscript-linux&pivots=os-windows) and [Build and deploy applications with the Azure Developer CLI](/training/paths/azure-developer-cli/).
-
-To get and initialize [the ASP.NET Core web app template](https://github.com/Azure-Samples/quickstart-deploy-aspnet-core-app-service), use the following steps:
-
-1. Open a terminal window on your computer to an empty working directory. Run the following command:
-
-   ```bash
-   azd init --template https://github.com/Azure-Samples/quickstart-deploy-aspnet-core-app-service.git
-   ```
-
-   When prompted for an environment name, enter `dev`.
-
-1. From the same terminal session, run the application locally using the `dotnet run` command. Use the `--project` parameter to specify the `src` directory of the `azd` template, which is where the application code lives.
-
-   ```bash
-   dotnet run --project src --urls=https://localhost:5001/
-   ```
-
-1. Open a web browser and navigate to the app at `https://localhost:5001`. The ASP.NET Core 8.0 web app template is displayed on the page.
-
-   :::image type="content" source="media/quickstart-dotnetcore/local-web-app-net.png" alt-text="Screenshot of Visual Studio Code - ASP.NET Core 8.0 in local browser." lightbox="media/quickstart-dotnetcore/local-web-app-net.png" border="true":::
-
-:::zone-end
-
 ## Publish your web app
 
 Follow these steps to create your App Service resources and publish your project:
@@ -284,7 +256,7 @@ Follow these steps to create your App Service resources and publish your project
    | **Location**     | *West Europe*            | The datacenter where the web app is hosted.                           |
    | **Size**         | Choose the lowest tier.                   | [Pricing tiers][app-service-pricing-tier] define hosting features. |
 
-1. In **Name**, enter a unique app name. Include only characters `a-z`, `A-Z`, `0-9`, and `-`. You can accept the automatically generated unique name. The URL of the web app is `http://<app-name>.azurewebsites.net`, where `<app-name>` is your app name.
+1. In **Name**, enter a unique app name. Include only characters `a-z`, `A-Z`, `0-9`, and `-`. You can accept the automatically generated unique name. 
 1. Select **Create** to create the Azure resources.
 
    :::image type="content" source="media/quickstart-dotnetcore/web-app-name.png" border="true" alt-text="Screenshot of Visual Studio - Create app resources dialog." lightbox="media/quickstart-dotnetcore/web-app-name.png" :::
@@ -531,7 +503,7 @@ Follow these steps to create your App Service resources and publish your project
 
    :::image type="content" source="./media/quickstart-dotnet/next-steps.png" alt-text="Screenshot of the next step of going to the resource.":::
 
-1. Browse to the deployed application in your web browser at the URL `http://<app-name>.azurewebsites.net`. If you see the message *Your web app is running and waiting for your content*, GitHub deployment is still running. Wait a couple of minutes and refresh the page.
+1. To browse to the created app, select the **default domain** in the **Overview** page. If you see the message *Your web app is running and waiting for your content*, GitHub deployment is still running. Wait a couple of minutes and refresh the page.
 
    ### [.NET 8.0](#tab/net80)
 
@@ -544,34 +516,6 @@ Follow these steps to create your App Service resources and publish your project
 
 :::zone-end
 
-:::zone target="docs" pivot="development-environment-azd"
-
-The AZD template contains files that generate the following required resources for your application to run in App service:
-
-- A new [resource group](../azure-resource-manager/management/overview.md#terminology) to contain all of the Azure resources for the service.
-- A new [App Service plan](overview-hosting-plans.md) that specifies the location, size, and features of the web server farm that hosts your app.
-- A new [App Service app](overview-hosting-plans.md) instance to run the deployed application.
-
-1. Sign into your Azure account by using the `azd auth login` command and following the prompt:
-
-   ```bash
-   azd auth login
-   ```
-
-1. Create the Azure resources and deploy your app using the `azd up` command:
-
-   ```bash
-   azd up
-   ```
-
-   The `azd up` command might take a few minutes to complete. `azd up` uses the Bicep files in your projects to create the resource group, App Service Plan, and hosting app. It also performs certain configurations such as enabling logging and deploys your compiled app code. While it runs, the command provides messages about the provisioning and deployment process, including a link to the deployment in Azure. When it finishes, the command also displays a link to the deploy application.
-
-1. Open a web browser and navigate to the URL. You see the ASP.NET Core 8.0 web app displayed in the page.
-
-   :::image type="content" source="media/quickstart-dotnetcore/browse-dotnet-70.png" lightbox="media/quickstart-dotnetcore/browse-dotnet-70.png" border="true" alt-text="Screenshot of the deployed .NET Framework 4.8 sample app.":::
-
-:::zone-end
-
 ## Update the app and redeploy
 
 Make a change to *Index.cshtml* and redeploy to see the changes. In the .NET 8.0 template, it's in the *Pages* folder. In the .NET Framework 4.8 template, it's in the *Views/Home* folder. Follow these steps to update and redeploy your web app:
@@ -649,7 +593,7 @@ Make a change to *Index.cshtml* and redeploy to see the changes. In the .NET 8.0
 :::zone-end
 
 <!-- markdownlint-disable MD044 -->
-:::zone target="docs" pivot="development-environment-cli,development-environment-ps,development-environment-azd"
+:::zone target="docs" pivot="development-environment-cli,development-environment-ps"
 > [!TIP]
 > To see how Visual Studio Code with GitHub Copilot helps improve your web development experience, see the Visual Studio Code steps.
 <!-- markdownlint-enable MD044 -->
@@ -813,33 +757,6 @@ You see the updated ASP.NET Core 8.0 web app displayed in the page.
 
 :::zone-end
 
-<!-- markdownlint-disable MD044 -->
-:::zone target="docs" pivot="development-environment-azd"
-<!-- markdownlint-enable MD044 -->
-
-In the local directory, open the *src/Pages/Index.cshtml* file. Replace the first `<div>` element:
-
-```html
-<div class="jumbotron">
-    <h1>.NET 💜 Azure</h1>
-    <p class="lead">Example .NET app to Azure App Service.</p>
-</div>
-```
-
-Save your changes, then redeploy the app using the `azd up` command again:
-
-```azurecli
-azd up
-```
-
-`azd up` skips the provisioning resources step this time and only redeploys your code, since there are no changes to the Bicep files.
-
-After deployment completes, the browser opens to the updated ASP.NET Core 8.0 web app.
-
-:::image type="content" source="media/quickstart-dotnetcore/updated-azure-web-app-net.png" lightbox="media/quickstart-dotnetcore/updated-azure-web-app-net.png" border="true" alt-text="Screenshot of the CLI - Updated ASP.NET Core 8.0 web app in Azure.":::
-
-:::zone-end
-
 ## Manage the Azure app
 
 To manage your web app, go to the [Azure portal](https://portal.azure.com), and search for and select **App Services**.
@@ -890,12 +807,6 @@ For your convenience, the [az webapp up](/cli/azure/webapp#az-webapp-up) command
 :::zone-end
 <!-- markdownlint-enable MD044 -->
 
-:::zone target="docs" pivot="development-environment-azd"
-<!-- markdownlint-enable MD044 -->
-[!INCLUDE [Clean-up Azure Developer CLI web app resources](../../includes/clean-up-section-azure-developer-cli.md)]
-:::zone-end
-<!-- markdownlint-enable MD044 -->
-
 ## Next steps
 
 ### [.NET 8.0](#tab/net80)
@@ -911,11 +822,6 @@ Advance to the next article to learn how to create a .NET Core app and connect i
 > [!div class="nextstepaction"]
 > [Configure ASP.NET Core app](configure-language-dotnetcore.md)
 
-:::zone target="docs" pivot="development-environment-azd"
-> [!div class="nextstepaction"]
-> [Learn more about the Azure Developer CLI](/azure/developer/azure-developer-cli/overview)
-:::zone-end
-
 ### [.NET Framework 4.8](#tab/netframework48)
 
 Advance to the next article to learn how to create a .NET Framework app and connect it to a SQL Database:

articles/app-service/quickstart-python.md

@@ -2,7 +2,7 @@
 title: 'Quickstart: Deploy a Python (Django, Flask, or FastAPI) web app to Azure'
 description: Get started with Azure App Service by deploying your first Python app to Azure App Service.
 ms.topic: quickstart
-ms.date: 09/13/2024
+ms.date: 04/24/2025
 ms.author: msangapu
 author: msangapu-msft
 ms.devlang: python
@@ -23,6 +23,45 @@ To complete this quickstart, you need:
 > [!NOTE]
 > This article contains current instructions on deploying a Python web app using Azure App Service. Python on Windows is no longer supported.
 
+## Skip to the end
+
+You can quickly deploy the sample app in this tutorial using Azure Developer CLI and see it running in Azure. Just run the following commands in the [Azure Cloud Shell](https://shell.azure.com)want, and follow the prompt:
+
+### [Flask](#tab/flask)
+
+```bash
+mkdir flask-quickstart
+cd flask-quickstart
+azd init --template https://github.com/Azure-Samples/msdocs-python-flask-webapp-quickstart
+azd up
+```
+
+### [Django](#tab/django)
+
+```bash
+mkdir django-quickstart
+cd django-quickstart
+azd init --template https://github.com/Azure-Samples/msdocs-python-django-webapp-quickstart
+azd up
+```
+
+### [FastAPI](#tab/fastapi)
+
+```bash
+mkdir fastapi-quickstart
+cd fastapi-quickstart
+azd init --template https://github.com/Azure-Samples/msdocs-python-fastapi-webapp-quickstart
+azd up
+```
+
+---
+
+And, to delete the resources:
+
+```bash
+azd down
+```
+
 ## Sample application
 
 This quickstart can be completed using either Flask, Django, or FastAPI. A sample application in each framework is provided to help you follow along with this quickstart. Download or clone the sample application to your local workstation.

articles/azure-resource-manager/management/tag-support.md

@@ -2,7 +2,7 @@
 title: Tag support for resources
 description: Shows which Azure resource types support tags. Provides details for all Azure services.
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 04/24/2025
 ---
 
 # Tag support for Azure resources
@@ -1700,6 +1700,7 @@ To get the same data as a file of comma-separated values, download [tag-support.
 > | machines / assessPatches | No | No |
 > | machines / extensions | Yes | Yes |
 > | machines / installPatches | No | No |
+> | machines / licenseProfiles | Yes |  |
 > | machines / privateLinkScopes | No | No |
 > | privateLinkScopes | Yes | Yes |
 > | privateLinkScopes / privateEndpointConnectionProxies | No | No |

articles/azure-vmware/architecture-private-clouds.md

@@ -120,6 +120,9 @@ AV64 host types are available per availability zone. The following table lists t
 
 [!INCLUDE [hosts-minimum-initial-deployment-statement](includes/hosts-minimum-initial-deployment-statement.md)]
 
+> [!CAUTION]
+> Deleting a cluster terminates all running workloads and components and is an irreversible operation. Once you delete a cluster, you cannot recover the data.
+
 [!INCLUDE [azure-vmware-solutions-limits](includes/azure-vmware-solutions-limits.md)]
 
 ## VMware software versions

articles/azure-vmware/disaster-recovery-using-vmware-site-recovery-manager.md

@@ -7,7 +7,7 @@ ms.date: 01/13/2025
 ms.custom: engagement-fy23
 ---
 
-# Deploy disaster recovery with VMware Site Recovery Manager (SRM)
+# Deploy disaster recovery with VMware Live Site Recovery
 
 This article explains how to implement disaster recovery for on-premises VMware vSphere virtual machines (VMs) or Azure VMware Solution-based VMs. The solution in this article uses [VMware Site Recovery Manager (SRM)](https://techdocs.broadcom.com/us/en/vmware-cis/live-recovery/site-recovery-manager/8-8.html) and vSphere Replication with Azure VMware Solution. Instances of VMware SRM and replication servers are deployed at both the protected and the recovery sites.       
 
@@ -17,7 +17,7 @@ VMware vSphere Replication is VMware's hypervisor-based replication technology f
 
 
 > [!NOTE]
-> The current version of VMware Site Recovery Manager (SRM) in Azure VMware Solution is 8.7.0.3.
+> The current version of VMware Site Recovery Manager (SRM) in Azure VMware Solution is 8.8.0.3.
 
 ## Supported scenarios
 
@@ -281,11 +281,9 @@ If you no longer require VMware SRM, you must uninstall it in a clean manner. Be
 
 ## Support 
 
-VMware Site Recovery Manager (SRM) is a Disaster Recovery solution from VMware.  
-
-Microsoft only supports install/uninstall of VMware SRM and vSphere Replication Manager and scale up/down of vSphere Replication appliances within Azure VMware Solution. 
+VMware Live Site Recovery is a Disaster Recovery solution from VMware by Broadcom. Microsoft supports the installation and uninstallation of VMware Live Site Recovery and vSphere Replication Manager, as well as the scaling up or down of vSphere Replication appliances within Azure VMware Solution.
 
-For all other issues, such as configuration and replication, contact VMware for support.
+For any other issues, customers are requested to contact Broadcom for support regarding site configurations, licensing issues, replication, pairing failures, and DNS-related problems.
 
 VMware and Microsoft support teams engage each other as needed to troubleshoot VMware SRM issues on Azure VMware Solution.