Merge pull request #289513 from MicrosoftDocs/main

OOB Publish 10/30 - 12:15 PM PST

Author: Albertyang0

articles/api-management/v2-service-tiers-overview.md

@@ -45,6 +45,7 @@ The v2 tiers are supported in API Management API version **2023-05-01-preview**
 
 ### Supported regions
 The v2 tiers are available in the following regions:
+* East US
 * East US 2
 * South Central US
 * North Central US

articles/app-service/overview-vnet-integration.md

@@ -76,12 +76,6 @@ Because subnet size can't be changed after assignment, use a subnet that's large
 
 With multi plan subnet join (MPSJ), you can join multiple App Service plans in to the same subnet. All App Service plans must be in the same subscription but the virtual network/subnet can be in a different subscription. Each instance from each App Service plan requires an IP address from the subnet and to use MPSJ a minimum size of `/26` subnet is required. If you plan to join many and/or large scale plans, you should plan for larger subnet ranges.
 
->[!NOTE]
-> Multi plan subnet join is currently in public preview. During preview the following known limitations should be observed:
-> 
-> * The minimum requirement for subnet size of `/26` is currently not enforced, but will be enforced at GA. If you have joined multiple plans to a smaller subnet during preview they will still work, but you cannot connect additional plans and if you disconnect you will not be able to connect again.
-> * There is currently no validation if the subnet has available IPs, so you might be able to join N+1 plan, but the instances will not get an IP. You can view available IPs in the Virtual network integration page in Azure portal in apps that are already connected to the subnet.
-
 ### Windows Containers specific limits
 
 Windows Containers uses an extra IP address per app for each App Service plan instance, and you need to size the subnet accordingly. If you have, for example, 10 Windows Container App Service plan instances with four apps running, you need 50 IP addresses and extra addresses to support horizontal (in/out) scale.

articles/azure-functions/functions-container-apps-hosting.md

@@ -110,3 +110,4 @@ Keep in mind the following considerations when deploying your function app conta
 ## Next steps
 
 + [Hosting and scale](./functions-scale.md)
++ [Create your first containerized functions on Container Apps](./functions-deploy-container-apps.md)

articles/azure-functions/functions-deployment-slots.md

@@ -6,7 +6,18 @@ ms.date: 02/27/2024
 ---
 # Azure Functions deployment slots
 
-Azure Functions deployment slots allow your function app to run different instances called _slots_. Slots are different environments exposed via a publicly available endpoint. One app instance is always mapped to the production slot, and you can swap instances assigned to a slot on demand. Function apps running in a [Consumption plan](./consumption-plan.md) have a single extra slot for staging. You can obtain more staging slots by running your app in a [Premium plan](./functions-premium-plan.md) or [Dedicated (App Service) plan](./dedicated-plan.md). For more information, see [Service limits](./functions-scale.md#service-limits). 
+Azure Functions deployment slots allow your function app to run different instances called _slots_. Slots are different environments exposed via a publicly available endpoint. One app instance is always mapped to the production slot, and you can swap instances assigned to a slot on demand. 
+
+The number of available slots depends on your specific hosting option:
+
+| Hosting option | Slots (including production) |
+| ---- | ---- | 
+| [Consumption plan](consumption-plan.md) | 2 |
+| [Flex Consumption plan](flex-consumption-plan.md) | Not currently supported |
+| [Premium plan](functions-premium-plan.md) | 3 |
+| [Dedicated (App Service) plan](dedicated-plan.md) | [1-20](../azure-resource-manager/management/azure-subscription-service-limits.md#app-service-limits) |
+| [Container Apps](functions-container-apps-hosting.md) | Uses [Revisions](../container-apps/revisions.md) |
+  
 
 The following reflect how functions are affected by swapping slots:
 

articles/azure-functions/functions-deployment-technologies.md

@@ -3,7 +3,7 @@ title: Continuously update function app code using Azure Pipelines
 description: Learn how to use Azure Pipelines to set up a pipeline that builds and deploys apps to Azure Functions.
 author: juliakm
 ms.topic: conceptual
-ms.date: 04/03/2024
+ms.date: 09/27/2024
 ms.author: jukullam
 ms.custom: devx-track-csharp, devx-track-azurecli, devops-pipelines-deploy
 ms.devlang: azurecli
@@ -186,7 +186,7 @@ steps:
 
 You'll deploy with the [Azure Function App Deploy](/azure/devops/pipelines/tasks/deploy/azure-function-app) task. This task requires an [Azure service connection](/azure/devops/pipelines/library/service-endpoints) as an input. An Azure service connection stores the credentials to connect from Azure Pipelines to Azure.
 
-To deploy to Azure Functions, add the following snippet at the end of your `azure-pipelines.yml` file. The default `appType` is Windows. You can specify Linux by setting the `appType` to `functionAppLinux`.
+To deploy to Azure Functions, add the following snippet at the end of your `azure-pipelines.yml` file. The default `appType` is Windows. You can specify Linux by setting the `appType` to `functionAppLinux`. Deploying to a Flex Consumption app is not supported with @v1 of the AzureFunctionApp task.
 
 ```yaml
 trigger:
@@ -435,35 +435,74 @@ You'll deploy with the [Azure Function App Deploy v2](/azure/devops/pipelines/ta
 
 The v2 version of the task includes support for newer applications stacks for .NET, Python, and Node. The task includes networking predeployment checks. When there are predeployment issues, deployment stops. 
 
-To deploy to Azure Functions, add the following snippet at the end of your `azure-pipelines.yml` file. The default `appType` is Windows. You can specify Linux by setting the `appType` to `functionAppLinux`.
+To deploy to Azure Functions, add the following snippet at the end of your `azure-pipelines.yml` file. The default `appType` is Windows. You can specify Linux by setting the `appType` to `functionAppLinux`. Deploying to a Flex Consumption app requires you to set both `appType: functionAppLinux` and `isFlexConsumption: true`.
 
+### [Windows App](#tab/windows)
 ```yaml
 trigger:
 - main
 
 variables:
   # Azure service connection established during pipeline creation
-  azureSubscription: <Name of your Azure subscription>
-  appName: <Name of the function app>
+  azureSubscription: <SUBSCRIPTION_NAME>
+  appName: <APP_NAME>
+  # Agent VM image name
+  vmImageName: 'windows-latest'
+
+- task: AzureFunctionApp@2 # Add this at the end of your file
+  inputs:
+    azureSubscription: <AZURE_SERVICE_CONNECTION>
+    appType: functionApp # this specifies a Windows-based function app
+    appName: $(appName)
+    package: $(System.ArtifactsDirectory)/**/*.zip
+    deploymentMethod: 'auto' # 'auto' | 'zipDeploy' | 'runFromPackage'. Required. Deployment method. Default: auto.
+    #Uncomment the next lines to deploy to a deployment slot
+    #Note that deployment slots is not supported for Linux Dynamic SKU
+    #deployToSlotOrASE: true
+    #resourceGroupName: '<RESOURCE_GROUP>'
+    #slotName: '<SLOT_NAME>'
+```
+
+### [Linux App](#tab/linux)
+```yaml
+trigger:
+- main
+
+variables:
+  # Azure service connection established during pipeline creation
+  azureSubscription: <SUBSCRIPTION_NAME>
+  appName: <APP_NAME>
   # Agent VM image name
   vmImageName: 'ubuntu-latest'
 
 - task: AzureFunctionApp@2 # Add this at the end of your file
   inputs:
-    azureSubscription: <Azure service connection>
-    appType: functionAppLinux # default is functionApp
+    azureSubscription: <AZURE_SERVICE_CONNECTION>
+    appType: functionAppLinux # This specifies a Linux-based function app
+    #isFlexConsumption: true # Uncomment this line if you are deploying to a Flex Consumption app
     appName: $(appName)
     package: $(System.ArtifactsDirectory)/**/*.zip
     deploymentMethod: 'auto' # 'auto' | 'zipDeploy' | 'runFromPackage'. Required. Deployment method. Default: auto.
     #Uncomment the next lines to deploy to a deployment slot
     #Note that deployment slots is not supported for Linux Dynamic SKU
     #deployToSlotOrASE: true
-    #resourceGroupName: '<Resource Group Name>'
-    #slotName: '<Slot name>'
+    #resourceGroupName: '<RESOURCE_GROUP>'
+    #slotName: '<SLOT_NAME>'
 ```
 
 The snippet assumes that the build steps in your YAML file produce the zip archive in the `$(System.ArtifactsDirectory)` folder on your agent.
 
+If you opted to deploy to a [deployment slot](functions-deployment-slots.md), you can add the following step to perform a slot swap. Deployment slots are not yet available for the Flex Consumption SKU.
+```yaml
+- task: AzureAppServiceManage@0
+  inputs:
+    azureSubscription: <AZURE_SERVICE_CONNECTION>
+    WebAppName: <APP_NAME>
+    ResourceGroupName: <RESOURCE_GROUP>
+    SourceSlot: <SLOT_NAME>
+    SwapWithProduction: true
+```
+
 ## Deploy a container
 
 You can automatically deploy your code to Azure Functions as a custom container after every successful build. To learn more about containers, see [Working with containers and Azure Functions](./functions-how-to-custom-container.md) . 
@@ -480,9 +519,9 @@ trigger:
 
 variables:
   # Container registry service connection established during pipeline creation
-  dockerRegistryServiceConnection: <Docker registry service connection>
-  imageRepository: <Name of your image repository>
-  containerRegistry: <Name of the Azure container registry>
+  dockerRegistryServiceConnection: <DOCKER_REGISTRY_SERVICE_CONNECTION>
+  imageRepository: <IMAGE_REPOSITORY_NAME>
+  containerRegistry: <AZURE_CONTAINER_REGISTRY_NAME>
   dockerfilePath: '$(Build.SourcesDirectory)/Dockerfile'
   tag: '$(Build.BuildId)'
   
@@ -491,40 +530,13 @@ variables:
 
 - task: AzureFunctionAppContainer@1 # Add this at the end of your file
   inputs:
-    azureSubscription: '<Azure service connection>'
-    appName: '<Name of the function app>'
+    azureSubscription: '<AZURE_SERVICE_CONNECTION>'
+    appName: '<APP_NAME>'
     imageName: $(containerRegistry)/$(imageRepository):$(tag)
 ```
 
 The snippet pushes the Docker image to your Azure Container Registry. The **Azure Function App on Container Deploy** task pulls the appropriate Docker image corresponding to the `BuildId` from the repository specified, and then deploys the image.
 
-## Deploy to a slot
-
-You can configure your function app to have multiple slots. Slots allow you to safely deploy your app and test it before making it available to your customers.
-
-The following YAML snippet shows how to deploy to a staging slot, and then swap to a production slot:
-
-```yaml
-- task: AzureFunctionApp@2
-  inputs:
-    azureSubscription: <Azure service connection>
-    appType: functionAppLinux
-    appName: <Name of the Function app>
-    package: $(System.ArtifactsDirectory)/**/*.zip
-    deploymentMethod: 'auto'
-    deployToSlotOrASE: true
-    resourceGroupName: <Name of the resource group>
-    slotName: staging
-
-- task: AzureAppServiceManage@0
-  inputs:
-    azureSubscription: <Azure service connection>
-    WebAppName: <name of the Function app>
-    ResourceGroupName: <name of resource group>
-    SourceSlot: staging
-    SwapWithProduction: true
-```
-
 ## Create a pipeline with Azure CLI
 
 To create a build pipeline in Azure, use the `az functionapp devops-pipeline create` [command](/cli/azure/functionapp/devops-pipeline#az-functionapp-devops-pipeline-create). The build pipeline is created to build and release any code changes that are made in your repo. The command generates a new YAML file that defines the build and release pipeline and then commits it to your repo. The prerequisites for this command depend on the location of your code.

articles/azure-functions/functions-how-to-azure-devops.md

@@ -2,7 +2,7 @@
 title: Use GitHub Actions to make code updates in Azure Functions
 description: Learn how to use GitHub Actions to define a workflow to build and deploy Azure Functions projects in GitHub.
 ms.topic: conceptual
-ms.date: 03/16/2024
+ms.date: 09/27/2024
 ms.custom: devx-track-csharp, github-actions-azure
 zone_pivot_groups: github-actions-deployment-options
 ---
@@ -281,23 +281,35 @@ The Azure Functions action (`Azure/azure-functions`) defines how your code is pu
 
 ### Parameters
 
-The following parameters are most commonly used with this action:
+The following parameters are required for all function app plans:
 
 |Parameter |Explanation  |
 |---------|---------|
-|_**app-name**_ | (Mandatory) The name of your function app. |
-|_**slot-name**_ | (Optional) The name of a specific [deployment slot](functions-deployment-slots.md) you want to deploy to. The slot must already exist in your function app. When not specified, the code is deployed to the active slot. |
-|_**publish-profile**_ | (Optional) The name of the GitHub secret that contains your publish profile. |
+|_**app-name**_ | The name of your function app. |
+|***package*** | This is the location in your project to be published. By default, this value is set to `.`, which means all files and folders in the GitHub repository will be deployed.|
 
-The following parameters are also supported, but are used only in specific cases:
+The following parameters are required for the Flex Consumption plan:
 
 |Parameter |Explanation  |
 |---------|---------|
-| _**package**_ | (Optional) Sets a subpath in your repository from which to publish. By default, this value is set to `.`, which means all files and folders in the GitHub repository are deployed. |
-| _**respect-pom-xml**_ | (Optional) Used only for Java functions. Whether it's required for your app's deployment artifact to be derived from the pom.xml file. When deploying Java function apps, you should set this parameter to `true` and set `package` to `.`. By default, this parameter is set to `false`, which means that the `package` parameter must point to your app's artifact location, such as `./target/azure-functions/` |
-| _**respect-funcignore**_ | (Optional) Whether GitHub Actions honors your .funcignore file to exclude files and folders defined in it. Set this value to `true` when your repository has a .funcignore file and you want to use it exclude paths and files, such as text editor configurations, .vscode/, or a Python virtual environment (.venv/). The default setting is `false`. | 
-| _**scm-do-build-during-deployment**_ | (Optional) Whether the App Service deployment site (Kudu) performs predeployment operations. The deployment site for your function app can be found at `https://<APP_NAME>.scm.azurewebsites.net/`. Change this setting to `true` when you need to control the deployments in Kudu rather than resolving the dependencies in the GitHub Actions workflow. The default value is `false`. For more information, see the [SCM_DO_BUILD_DURING_DEPLOYMENT](./functions-app-settings.md#scm_do_build_during_deployment) setting. |
-| _**enable-oryx-build**_ |(Optional) Whether the Kudu deployment site resolves your project dependencies by using Oryx. Set to `true` when you want to use Oryx to resolve your project dependencies by using a remote build instead of the GitHub Actions workflow. When `true`, you should also set `scm-do-build-during-deployment` to `true`. The default value is `false`.|
+|_**sku**_ | Set this to `flexconsumption` when authenticating with publish-profile. When using RBAC credentials or deploying to a non-Flex Consumption plan, the Action can resolve the value, so the parameter does not need to be included. |
+|_**remote-build**_ | Set this to `true` to enable a build action from Kudu when the package is deployed to a Flex Consumption app. Oryx build is always performed during a remote build in Flex Consumption; do not set **scm-do-build-during-deployment** or **enable-oryx-build**. By default, this parameter is set to `false`. |
+
+The following parameters are specific to the Consumption, Elastic Premium, and App Service (Dedicated) plans:
+
+|Parameter |Explanation  |
+|---------|---------|
+|_**scm-do-build-during-deployment**_ | (Optional) Allow the Kudu site (e.g. `https://<APP_NAME>.scm.azurewebsites.net/`) to perform pre-deployment operations, such as [remote builds](functions-deployment-technologies.md#remote-build). By default, this is set to `false`. Set this to `true` when you do want to control deployment behaviors using Kudu instead of resolving dependencies in your GitHub workflow. For more information, see the [`SCM_DO_BUILD_DURING_DEPLOYMENT`](./functions-app-settings.md#scm_do_build_during_deployment) setting.|
+|_**enable-oryx-build**_ | (Optional) Allow Kudu site to resolve your project dependencies with Oryx. By default, this is set to `false`. If you want to use [Oryx](https://github.com/Microsoft/Oryx) to resolve your dependencies instead of the GitHub Workflow, set both **scm-do-build-during-deployment** and **enable-oryx-build** to `true`.|
+
+Optional parameters for all function app plans:
+
+|Parameter |Explanation  |
+|---------|---------|
+| ***slot-name*** | This is the [deployment slot](functions-deployment-slots.md) name to be deployed to. By default, this value is empty, which means the GitHub Action will deploy to your production site. When this setting points to a non-production slot, please ensure the **publish-profile** parameter contains the credentials for the slot instead of the production site. _Currently not supported in Flex Consumption_. |
+|***publish-profile*** | The name of the GitHub secret that contains your publish profile.|
+| _**respect-pom-xml**_ | Used only for Java functions. Whether it's required for your app's deployment artifact to be derived from the pom.xml file. When deploying Java function apps, you should set this parameter to `true` and set `package` to `.`. By default, this parameter is set to `false`, which means that the `package` parameter must point to your app's artifact location, such as `./target/azure-functions/` |
+| _**respect-funcignore**_ | Whether GitHub Actions honors your .funcignore file to exclude files and folders defined in it. Set this value to `true` when your repository has a .funcignore file and you want to use it exclude paths and files, such as text editor configurations, .vscode/, or a Python virtual environment (.venv/). The default setting is `false`. |
 
 ### Considerations
 

articles/azure-functions/functions-how-to-github-actions.md

@@ -18,7 +18,7 @@ ms.author: v-vprasannak
 An email domain that is provisioned to send email has a default MailFrom address, formatted as `[email protected]`. If you configure a custom domain such as `notification.azuremails.net`, then the default MailFrom address has `[email protected]` added. You can configure and add more MailFrom addresses and FROM display names to use values that are easier to read.
 
 > [!NOTE]
-> Sender usernames cannot be enabled for Azure Managed Domains or custom domains with default sending limits. For more information, see [Service limits for Azure Communication Services](../../../concepts/service-limits.md#rate-limits).
+> Sender usernames cannot be enabled for Azure Managed Domains regardless of the sending limits or custom domains with default sending limits. For more information, see [Service limits for Azure Communication Services](../../../concepts/service-limits.md#rate-limits).
 
 1. Open the Overview page of the Email Communication Service resource that you created in [Get started with Creating Email Communication Resource](../../../quickstarts/email/create-email-communication-resource.md).
 2. Click **Provision Domains** on the left navigation panel to see list of provisioned domains.

articles/communication-services/quickstarts/email/includes/create-sender-username-resource-az-portal.md

@@ -5,7 +5,7 @@ services: dns
 author: greg-lindsay
 ms.service: azure-dns
 ms.topic: how-to
-ms.date: 08/12/2024
+ms.date: 09/11/2024
 ms.author: greglin
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ---
@@ -241,7 +241,7 @@ No. Azure supports a single reverse DNS record for each Azure Cloud Service or P
 
 ### Can I configure reverse DNS for IPv6 PublicIpAddress resources?
 
-Yes. See [Azure support for reverse DNS](/azure/dns/dns-reverse-dns-overview#azure-support-for-reverse-dns).
+No. Azure DNS does not currently support reverse DNS (PTR records) for public IPv6 addresses.
 
 ### Can I send emails to external domains from my Azure Compute services?
 

articles/dns/dns-reverse-dns-for-azure-services.md

@@ -4,7 +4,7 @@ description: Learn how to use Azure DNS to host the reverse DNS lookup zones for
 author: greg-lindsay
 ms.service: azure-dns
 ms.topic: how-to
-ms.date: 06/07/2024
+ms.date: 09/12/2024
 ms.author: greglin
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ms.devlang: azurecli