Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into apimmcp

Author: gitName

articles/app-service/configure-basic-auth-disable.md

@@ -68,7 +68,7 @@ The following table shows how various deployment methods behave when basic authe
 
 | Deployment method | When basic authentication is disabled |
 |-|-|
-| Visual Studio deployment | Doesn't work. |
+| Visual Studio deployment | Deployment with Microsoft Entra authentication requires Visual Studio 2022 version 17.12 or later. |
 | [FTP](deploy-ftp.md) | Doesn't work. |
 | [Local Git](deploy-local-git.md) | Doesn't work. |
 | Azure CLI | In the Azure CLI 2.48.1 or higher, the following commands fall back to Microsoft Entra authentication:<br/>[`az webapp up`](/cli/azure/webapp#az-webapp-up).<br/>[`az webapp deploy`](/cli/azure/webapp#az-webapp-deploy).<br/>[`az webapp log deployment show`](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-show).<br/>[`az webapp log deployment list`](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-list).<br/>[`az webapp log download`](/cli/azure/webapp/log#az-webapp-log-download).<br/>[`az webapp log tail`](/cli/azure/webapp/log#az-webapp-log-tail).<br/>[`az webapp browse`](/cli/azure/webapp#az-webapp-browse).<br/>[`az webapp create-remote-connection`](/cli/azure/webapp#az-webapp-create-remote-connection).<br/>[`az webapp ssh`](/cli/azure/webapp#az-webapp-ssh).<br/>[`az functionapp deploy`](/cli/azure/functionapp#az-functionapp-deploy).<br/>[`az functionapp log deployment list`](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-list).<br/>[`az functionapp log deployment show`](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-show).<br/>[`az functionapp deployment source config-zip`](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip). |

articles/application-gateway/media/rewrite-http-headers-url/url-rewrite-overview.png

@@ -484,12 +484,23 @@
             - name: Core Tools development
               href: functions-run-local.md
               displayName: local, runtime
+        - name: Create a function app
+          items:
+            - name: Infrastructure as code
+              href: functions-infrastructure-as-code.md
+              displayName: bicep, ARM template, create function app 
+            - name: Azure portal 
+              href: functions-create-function-app-portal.md
+              displayName: create function app
+            - name: Azure CLI  
+              href: ./scripts/functions-cli-create-serverless.md
+              displayName: create function app
         - name: Create functions
           items:
             - name: HTTP trigger
               items:
                 - name: Azure portal
-                  href: functions-create-function-app-portal.md
+                  href: functions-create-http-endpoint.md
                 - name: Kotlin using IntelliJ
                   href: functions-create-maven-kotlin-intellij.md
                 - name: Consumption plan
@@ -545,7 +556,7 @@
           href: bring-dependency-to-functions.md
         - name: Develop Python worker extensions
           href: develop-python-worker-extensions.md
-    - name: Deploy
+    - name: Deploy 
       items:
         - name: Continuous deployment
           href: functions-continuous-deployment.md
@@ -568,9 +579,6 @@
           href: deployment-zip-push.md
         - name: Run from package
           href: run-functions-from-deployment-package.md
-        - name: Automate resource deployment
-          href: functions-infrastructure-as-code.md
-          displayName: bicep, ARM template
         - name: Deploy using the Jenkins plugin
           href: /azure/developer/jenkins/deploy-to-azure-functions?toc=/azure/azure-functions/toc.json
     - name: Configure
@@ -741,6 +749,9 @@
   items:
     - name: Migrate from AWS Lambda
       items:
+        - name: Migrate from AWS Lambda
+          href: migration/migrate-aws-lambda-to-azure-functions.md
+          displayName: AWS Lambda, migration
         - name: Overview
           href: migration/migrate-lambda-workloads-overview.md
           displayName: AWS Lambda, migration

articles/azure-functions/TOC.yml

@@ -66,7 +66,7 @@ Set up a secured storage account for your function app:
 
 1. Secure the new storage account in one of the following ways:
 
-    * [Create a private endpoint](../storage/common/storage-private-endpoints.md#creating-a-private-endpoint). As you set up your private endpoint connection, create private endpoints for the `file` and `blob` subresources. For Durable Functions, you must also make `queue` and `table` subresources accessible through private endpoints. If you're using a custom or on-premises Domain Name System (DNS) server, [configure your DNS server](../storage/common/storage-private-endpoints.md#dns-changes-for-private-endpoints) to resolve to the new private endpoints.
+    * [Create a private endpoint](../storage/common/storage-private-endpoints.md#creating-a-private-endpoint). As you set up your private endpoint connection, create private endpoints for the `file`, `blob` and `table` subresources. For Durable Functions, you must also make `queue` subresources accessible through private endpoints. If you're using a custom or on-premises Domain Name System (DNS) server, [configure your DNS server](../storage/common/storage-private-endpoints.md#dns-changes-for-private-endpoints) to resolve to the new private endpoints.
 
     * [Restrict traffic to specific subnets](../storage/common/storage-network-security.md#grant-access-from-a-virtual-network). Ensure your function app is network integrated with an allowed subnet and that the subnet has only one of these service endpoints defined: 
         * `Microsoft.Storage`: use when your app is in the same region as your virtual network.

articles/azure-functions/configure-networking-how-to.md

@@ -1,7 +1,7 @@
 ---
 title: Azure Functions Consumption plan hosting
-description: Learn about how Azure Functions Consumption plan hosting lets you run your code in an environment that scales dynamically, but you only pay for resources used during execution.
-ms.date: 07/10/2023
+description: Learn about how Azure Functions Consumption plan hosting lets you run your code in an environment that scales dynamically.
+ms.date: 05/06/2025
 ms.topic: conceptual
 ms.custom:
   - build-2024
@@ -10,7 +10,7 @@ ms.custom:
 
 # Azure Functions Consumption plan hosting
 
-When you're using the Consumption plan, instances of the Azure Functions host are dynamically added and removed based on the number of incoming events. The Consumption plan, along with the [Flex Consumption plan](./flex-consumption-plan.md), is a fully <em>serverless</em> hosting option for Azure Functions.
+When you're using the Consumption plan, instances of the Azure Functions host are dynamically added and removed based on the number of incoming events. The Consumption plan, along with the [Flex Consumption plan](./flex-consumption-plan.md), is a fully *serverless* hosting option for Azure Functions.
 
 ## Benefits
 
@@ -23,29 +23,29 @@ For a comparison of the Consumption plan against the other plan and hosting type
 
 ## Billing
 
-Billing is based on number of executions, execution time, and memory used. Usage is aggregated across all functions within a function app. For more information, see the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/).
+Billing is based on number of executions, execution time, and memory used. Usage is aggregated across all functions within a function app. For more information, see [Azure Functions pricing](https://azure.microsoft.com/pricing/details/functions/).
 
 To learn more about how to estimate costs when running in a Consumption plan, see [Understanding Consumption plan costs](functions-consumption-costs.md).
 
 ## Create a Consumption plan function app
 
 When you create a function app in the Azure portal, the Consumption plan is the default. When using APIs to create your function app, you don't have to first create an App Service plan as you do with Premium and Dedicated plans.
 
-In Consumption plan hosting, each function app typically runs in its own plan. In the Azure portal or in code, you may also see the Consumption plan referred to as `Dynamic` or `Y1`. 
+In Consumption plan hosting, each function app typically runs in its own plan. In the Azure portal or in code, you might also see the Consumption plan referred to as `Dynamic` or `Y1`.
 
 Use the following links to learn how to create a serverless function app in a Consumption plan, either programmatically or in the Azure portal:
 
-+ [Azure CLI](./scripts/functions-cli-create-serverless.md)
-+ [Azure portal](./functions-get-started.md)
-+ [Azure Resource Manager template](functions-create-first-function-resource-manager.md)
+- [Azure CLI](./scripts/functions-cli-create-serverless.md)
+- [Azure portal](./functions-get-started.md)
+- [Azure Resource Manager template](functions-create-first-function-resource-manager.md)
 
 You can also create function apps in a Consumption plan when you publish a Functions project from [Visual Studio Code](./create-first-function-vs-code-csharp.md#publish-the-project-to-azure) or [Visual Studio](functions-create-your-first-function-visual-studio.md#publish-the-project-to-azure).
 
 ## Multiple apps in the same plan
 
-The general recommendation is for each function app to have its own Consumption plan. However, if needed, function apps in the same region can be assigned to the same Consumption plan. Keep in mind that there is a [limit to the number of function apps that can run in a Consumption plan](functions-scale.md#service-limits). Function apps in the same plan still scale independently of each other.
+The general recommendation is for each function app to have its own Consumption plan. However, if needed, function apps in the same region can be assigned to the same Consumption plan. Keep in mind that there's a [limit to the number of function apps that can run in a Consumption plan](functions-scale.md#service-limits). Function apps in the same plan still scale independently of each other.
 
 ## Next steps
 
-+ [Azure Functions hosting options](functions-scale.md)
-+ [Event-driven scaling in Azure Functions](event-driven-scaling.md)
+- [Azure Functions hosting options](functions-scale.md)
+- [Event-driven scaling in Azure Functions](event-driven-scaling.md)

articles/azure-functions/consumption-plan.md

@@ -4,23 +4,23 @@ description: Use the .zip file deployment facilities of the Kudu deployment serv
 
 ms.topic: conceptual
 ms.custom: devx-track-azurecli, devx-track-arm-template
-ms.date: 08/12/2018
+ms.date: 05/06/2025
 ---
 
 # Zip deployment for Azure Functions
 
-This article describes how to deploy your function app project files to Azure from a .zip (compressed) file. You learn how to do a push deployment, both by using Azure CLI and by using the REST APIs. [Azure Functions Core Tools](functions-run-local.md) also uses these deployment APIs when publishing a local project to Azure. 
+This article describes how to deploy your function app project files to Azure from a .zip (compressed) file. You learn how to do a push deployment, both by using Azure CLI and by using the REST APIs. [Azure Functions Core Tools](functions-run-local.md) also uses these deployment APIs when publishing a local project to Azure.
 
-Zip deployment is also an easy way to [run your functions from a package file in Azure](run-functions-from-deployment-package.md). It is the default deployment technology in the [Consumption](./consumption-plan.md), [Elastic Premium](./functions-premium-plan.md), and [Dedicated (App Service)](./dedicated-plan.md) hosting plans. The [Flex Consumption](./flex-consumption-plan.md) plan does not support zip deployment.
+Zip deployment is also an easy way to [run your functions from a package file in Azure](run-functions-from-deployment-package.md). It's the default deployment technology in the [Consumption](./consumption-plan.md), [Elastic Premium](./functions-premium-plan.md), and [Dedicated (App Service)](./dedicated-plan.md) hosting plans. The [Flex Consumption](./flex-consumption-plan.md) plan doesn't support zip deployment.
 
 Azure Functions has the full range of continuous deployment and integration options that are provided by Azure App Service. For more information, see [Continuous deployment for Azure Functions](functions-continuous-deployment.md).
 
 To speed up development, you might find it easier to deploy your function app project files directly from a .zip file. The .zip deployment API takes the contents of a .zip file and extracts the contents into the `wwwroot` folder of your function app. This .zip file deployment uses the same Kudu service that powers continuous integration-based deployments, including:
 
-+ Deletion of files that were left over from earlier deployments.
-+ Deployment customization, including running deployment scripts.
-+ Deployment logs.
-+ Syncing function triggers in a [Consumption plan](functions-scale.md) function app.
+- Deletion of files that were left over from earlier deployments.
+- Deployment customization, including running deployment scripts.
+- Deployment logs.
+- Syncing function triggers in a [Consumption plan](functions-scale.md) function app.
 
 For more information, see the [.zip deployment reference](https://github.com/projectkudu/kudu/wiki/Deploying-from-a-zip-file).
 
@@ -31,11 +31,11 @@ For more information, see the [.zip deployment reference](https://github.com/pro
 
 [!INCLUDE [functions-deployment-zip-structure](../../includes/functions-deployment-zip-structure.md)]
 
-A zip deployment process extracts the zip archive's files and folders in the `wwwroot` directory. If you include the parent directory when creating the archive, the system will not find the files it expects to see in `wwwroot`.
+A zip deployment process extracts the zip archive's files and folders in the `wwwroot` directory. If you include the parent directory when creating the archive, the system won't find the files it expects to see in `wwwroot`.
 
 ## <a name="cli"></a>Deploy by using Azure CLI
 
-You can use Azure CLI to trigger a push deployment. Push deploy a .zip file to your function app by using the [az functionapp deployment source config-zip](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) command. To use this command, you must use Azure CLI version 2.0.21 or later. To see what Azure CLI version you are using, use the `az --version` command.
+You can use Azure CLI to trigger a push deployment. Push deploy a .zip file to your function app by using the [az functionapp deployment source config-zip](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) command. To use this command, you must use Azure CLI version 2.0.21 or later. To see what Azure CLI version you're using, use the `az --version` command.
 
 In the following command, replace the `<zip_file_path>` placeholder with the path to the location of your .zip file. Also, replace `<app_name>` with the unique name of your function app and replace `<resource_group>` with the name of your resource group.
 
@@ -107,7 +107,7 @@ For the initial deployment, you would deploy directly to the production slot. Fo
 
 ## Run functions from the deployment package
 
-You can also choose to run your functions directly from the deployment package file. This method skips the deployment step of copying files from the package to the `wwwroot` directory of your function app. Instead, the package file is mounted by the Functions runtime, and the contents of the `wwwroot` directory become read-only.  
+You can also choose to run your functions directly from the deployment package file. This method skips the deployment step of copying files from the package to the `wwwroot` directory of your function app. Instead, the Functions runtime mounts the package file, and the contents of the `wwwroot` directory become read-only.  
 
 Zip deployment integrates with this feature, which you can enable by setting the function app setting `WEBSITE_RUN_FROM_PACKAGE` to a value of `1`. For more information, see [Run your functions from a deployment package file](run-functions-from-deployment-package.md).
 
@@ -117,25 +117,25 @@ Zip deployment integrates with this feature, which you can enable by setting the
 
 If you created your functions by using the editor in the Azure portal, you can download your existing function app project as a .zip file in one of these ways:
 
-+ **From the Azure portal:**
+- **From the Azure portal:**
 
   1. Sign in to the [Azure portal](https://portal.azure.com), and then go to your function app.
 
   2. On the **Overview** tab, select **Download app content**. Select your download options, and then select **Download**.
 
-      ![Download the function app project](./media/deployment-zip-push/download-project.png)
+    :::image type="content" source="./media/deployment-zip-push/download-project.png" alt-text="Screenshot shows the Azure portal page to download the function app project.":::
 
      The downloaded .zip file is in the correct format to be republished to your function app by using .zip push deployment. The portal download can also add the files needed to open your function app directly in Visual Studio.
 
-+ **Using REST APIs:**
+- **Using REST APIs:**
 
     Use the following deployment GET API to download the files from your `<function_app>` project: 
 
     ```http
     https://<function_app>.scm.azurewebsites.net/api/zip/site/wwwroot/
     ```
 
-    Including `/site/wwwroot/` makes sure your zip file includes only the function app project files and not the entire site. If you are not already signed in to Azure, you will be asked to do so.  
+    Including `/site/wwwroot/` makes sure your zip file includes only the function app project files and not the entire site. If you aren't already signed in to Azure, you are asked to do so.  
 
 You can also download a .zip file from a GitHub repository. When you download a GitHub repository as a .zip file, GitHub adds an extra folder level for the branch. This extra folder level means that you can't deploy the .zip file directly as you downloaded it from GitHub. If you're using a GitHub repository to maintain your function app, you should use [continuous integration](functions-continuous-deployment.md) to deploy your app.