Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

.openpublishing.redirection.json

@@ -1045,6 +1045,11 @@
       "redirect_url": "/azure/migrate/discover-and-assess-using-private-endpoints",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/operator-call-protection/index.yml",
+      "redirect_url": "https://learn.microsoft.com",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/operator-5g-core/index.yml",
       "redirect_url": "https://learn.microsoft.com",
@@ -2005,6 +2010,21 @@
       "redirect_url": "./azure-resource-manager/management/deployment-models",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/azure-functions/functions-add-output-binding-storage-queue-java.md",
+      "redirect_url": "/azure/azure-functions/functions-add-output-binding-storage-queue-cli?pivots=programming-language-java",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/azure-functions/create-first-function-arc-custom-container.md",
+      "redirect_url": "/azure/azure-functions/functions-how-to-custom-container?pivots=azure-arc",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/azure-functions/create-first-function-arc-cli.md",
+      "redirect_url": "/azure/azure-functions/functions-how-to-custom-container?pivots=azure-arc",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/azure-functions/create-first-function-vs-code-web.md",
       "redirect_url": "/azure/azure-functions",

articles/api-management/api-management-region-availability.md

@@ -39,7 +39,7 @@ Information in the following table is updated regularly. Capacity availability i
 | Korea Central | ✅ | ✅ | ✅ | | 
 | North Central US | ✅ | ✅ |  | ✅ |
 | North Europe | ✅ | ✅ |  | ✅ |
-| Norway East | ✅ | ✅ | ✅ | |
+| Norway East | ✅ | ✅ | ✅ | ✅ |
 | South Africa North | ✅ | ✅ | |  |
 | South Central US | ✅ | ✅ |  |  |
 | South India | ✅ | ✅ |  |  |

articles/application-gateway/create-url-route-portal.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: tutorial
-ms.date: 09/03/2024
+ms.date: 02/05/2025
 ms.author: greglin
 #Customer intent: As an IT administrator, I want to use the Azure portal to set up an application gateway so I can route my app traffic based on path-based routing rules.
 ---
@@ -25,15 +25,12 @@ In this article, you learn how to:
 
 :::image type="content" source="./media/application-gateway-create-url-route-portal/scenario.png" alt-text="Diagram of application gateway URL routing example." lightbox="./media/application-gateway-create-url-route-portal/scenario.png":::
 
-[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
-
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
 ## Prerequisites
 
 - An Azure subscription
 
-
 ## Create virtual machines
 
 In this example, you create three virtual machines to be used as backend servers for the application gateway. You also install IIS on the virtual machines to verify that the application gateway works as expected.
@@ -125,7 +122,7 @@ In this example, you create three virtual machines to be used as backend servers
 
 ### Backends tab
 
-The backend pool is used to route requests to the backend servers that serve the request. Backend pools can be composed of NICs, virtual machine scale sets, public IPs, internal IPs, fully qualified domain names (FQDN), and multi-tenant backends like Azure App Service.
+The backend pool is used to route requests to the backend servers that serve the request. Backend pools can be composed of NICs, virtual machine scale sets, public IPs, internal IPs, fully qualified domain names (FQDN), and multitenant backends like Azure App Service.
 
 1. On the **Backends** tab, select **Add a backend pool**.
 
@@ -159,21 +156,22 @@ On the **Configuration** tab, you'll connect the frontend and backend pool you c
 
 4. On the **Backend targets** tab, select **myBackendPool** for the **Backend target**.
 
-5. For the **HTTP setting**, select **Add new** to create a new HTTP setting. The HTTP setting will determine the behavior of the routing rule. 
+5. For the **Backend settings**, select **Add new** to create a new HTTP setting. The HTTP setting will determine the behavior of the routing rule. 
 
-6. In the **Add an HTTP setting** window that opens, enter *myHTTPSetting* for the **HTTP setting name**. Accept the default values for the other settings in the **Add an HTTP setting** window, then select **Add** to return to the **Add a routing rule** window.
+6. In the **Add Backend setting** window that opens, enter *myHTTPSetting* for the **Backend settings name**. Accept the default values for the other settings in the **Add Backend setting** window, then select **Add** to return to the **Add a routing rule** window.
 7. Under **Path-based routing**, select **Add multiple targets to create a path-based rule**.
-8. For **Path**, type */images/*\*.
-9. For **Target name**, type *Images*.
-10. For **HTTP setting**, select **myHTTPSetting**
-11. For **Backend target**, select **Images**.
-12. Select **Add** to save the path rule and return to the **Add a routing rule** tab.
-13. Repeat to add another rule for Video.
-14. Select **Add** to add the routing rule and return to the **Configuration** tab.
-15. Select **Next: Tags** and then **Next: Review + create**.
+1. Under **Path based rules**, select **Add multiple targets to create a path-based rule**.
+1. For **Path**, type */images/*\*.
+1. For **Target name**, type *Images*.
+1. For **Backend settings**, select **myHTTPSetting**
+1. For **Backend target**, select **myBackendPool**.
+1. Select **Add** to save the path rule and return to the **Add a routing rule** tab.
+1. Repeat to add another rule for Video.
+1. Select **Add** to add the routing rule and return to the **Configuration** tab.
+1. Select **Next: Tags** and then **Next: Review + create**.
 
 > [!NOTE]
-> You do not need to add a custom */** path rule to handle default cases. This is automatically handled by the default backend pool.
+> You don't need to add a custom */** path rule to handle default cases. This is automatically handled by the default backend pool.
 
 > [!NOTE]
 > Wildcard delimiter **\*** is only honored at the end of the rule. For more information and supported path based rules examples, see [URL Path Based Routing overview](url-route-overview.md#pathpattern).
@@ -187,7 +185,7 @@ Review the settings on the **Review + create** tab, and then select **Create** t
 
 1. Select **All resources**, and then select **myAppGateway**.
 
-    ![Screenshot of record application gateway public IP address.](./media/application-gateway-create-url-route-portal/application-gateway-record-ag-address.png)
+    :::image type="content" source="./media/application-gateway-create-url-route-portal/application-gateway-record-ag-address.png" alt-text="Screenshot of record application gateway public IP address.":::
 
 2. Copy the public IP address, and then paste it into the address bar of your browser. Such as, http:\//203.0.113.10:8080.
 

articles/application-gateway/media/application-gateway-create-url-route-portal/application-gateway-iistest-images.png

@@ -115,14 +115,6 @@
           - name: ARM template
             displayName: Resource Manager
             href: functions-create-first-function-resource-manager.md
-        - name: Azure Arc (preview)
-          items:
-            - name: Code-only publishing
-              displayName: Arc, container, Kubernetes
-              href: create-first-function-arc-cli.md
-            - name: Custom container
-              displayName: Arc, container, Kubernetes, Docker
-              href: create-first-function-arc-custom-container.md
         - name: Azure Container Apps
           href: functions-deploy-container-apps.md
           displayName: container, Docker, ACA
@@ -522,13 +514,11 @@
                 - name: Azure portal
                   href: functions-integrate-storage-queue-output-binding.md
                 - name: Visual Studio Code
-                  href: ./functions-add-output-binding-storage-queue-vs-code.md
+                  href: functions-add-output-binding-storage-queue-vs-code.md
                 - name: Visual Studio
-                  href: ./functions-add-output-binding-storage-queue-vs.md
-                - name: Java
-                  href: functions-add-output-binding-storage-queue-java.md
-                - name: Python
-                  href: ./functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-python
+                  href: functions-add-output-binding-storage-queue-vs.md
+                - name: Command line
+                  href: functions-add-output-binding-storage-queue-cli.md
         - name: Debug
           items:
             - name: Debug local PowerShell functions

articles/application-gateway/media/application-gateway-create-url-route-portal/application-gateway-iistest-video.png

@@ -3,24 +3,25 @@ title: How to use a secured storage account with Azure Functions
 description: Learn how to use a secured storage account in a virtual network as the default storage account for a function app in Azure Functions.
 ms-service: azure-functions
 ms.topic: how-to
-ms.date: 06/27/2024
+ms.date: 01/03/2025
 ms.custom: template-how-to, build-2024, ignite-2024
 # Customer intent: As a developer, I want to understand how to use a secured storage account in a virtual network as the default storage account for my function app, so that my function app can be secure.
 ---
 
 # How to use a secured storage account with Azure Functions
 
-This article shows you how to connect your function app to a secured storage account. For an in-depth tutorial on how to create your function app with inbound and outbound access restrictions, see the [Integrate with a virtual network](functions-create-vnet.md) tutorial. To learn more about Azure Functions and networking, see [Azure Functions networking options](functions-networking-options.md).
+Azure Functions requires an Azure Storage account when you create a function app instance. This default storage account is used by the Functions runtime to maintain the health of your function app. For more information, see [Storage considerations for Azure Functions](storage-considerations.md). This article shows you how to use a secured storage account as the default storage account. For an in-depth tutorial on how to create your function app with inbound and outbound access restrictions, see the [Integrate with a virtual network](functions-create-vnet.md) tutorial. To learn more about Azure Functions and networking, see [Azure Functions networking options](functions-networking-options.md).
 
 ## Restrict your storage account to a virtual network
 
-When you create a function app, you either create a new storage account or link to an existing one. Currently, only the Azure portal, [ARM template deployments](functions-infrastructure-as-code.md?tabs=json&pivots=premium-plan#secured-deployments), and [Bicep deployments](functions-infrastructure-as-code.md?tabs=bicep&pivots=premium-plan#secured-deployments) support function app creation with an existing secured storage account.
+When you create a function app, you either create a new storage account or link to an existing one. Keep these considerations in mind when working with secured storage account. 
 
-> [!NOTE]  
-> Secured storage accounts are supported for all tiers of the [Dedicated (App Service) plan](./dedicated-plan.md) and the [Elastic Premium plan](./functions-premium-plan.md). They're also supported by the [Flex Consumption plan](./flex-consumption-plan.md).
-> The [Consumption plan](consumption-plan.md) doesn't support virtual networks.
-
-For a list of all restrictions on storage accounts, see [Storage account requirements](storage-considerations.md#storage-account-requirements).
++ To create a function app that uses an existing secured storage account as the default storage account, you must create your app either in the [Azure portal](https://portal.azure.com) or by using [ARM template](functions-infrastructure-as-code.md?tabs=json&pivots=premium-plan#secured-deployments) or [Bicep](functions-infrastructure-as-code.md?tabs=bicep&pivots=premium-plan#secured-deployments) deployments.
++ When using a secured storage account with a dynamic scale plan, you should host your functions in the [Flex Consumption plan](./flex-consumption-plan.md). This plan supports both secured storage accounts and managed identity-based connections to storage, which is the most secure connection option.    
++ All tiers of both the [Dedicated (App Service) plan](./dedicated-plan.md) and the [Elastic Premium plan](./functions-premium-plan.md) also support secure storage accounts. However, there are trade-offs when using managed identities to connect from a Premium plan app. For more information, see [Create an app without Azure Files](storage-considerations.md#create-an-app-without-azure-files). 
++ The [Consumption plan](consumption-plan.md) doesn't support virtual networks, so you can't connect to a secured storage account when running in the Consumption plan. To take advantage of serverless function hosting, you should instead recreate your app to run in Flex Consumption plan.
++ This article currently shows you how to create a function app in a Premium plan that connects to a secured storage account using the storage account connection string. To provide the best protection of storage account credentials, you should instead use managed identities when connecting to a storage account. Instead follow the [Quickstart: Create and deploy functions to Azure Functions using the Azure Developer CLI](create-first-function-azure-developer-cli.md) to create a function app in the Flex Consumption plan that connects to a new secured storage account using managed identities. 
++ For a list of all restrictions on storage accounts, see [Storage account requirements](storage-considerations.md#storage-account-requirements).
 
 ## Secure storage during function app creation
 
@@ -59,7 +60,7 @@ Set up a secured storage account for your function app:
 
 1. [Create a second storage account](../storage/common/storage-account-create.md). This storage account is the secured storage account for your function app to use instead of its original unsecured storage account. You can also use an existing storage account not already being used by Functions.
 
-1. Save the connection string for this storage account to use later.
+1. Save the connection string for this storage account to use later. 
 
 1. [Create a file share](../storage/files/storage-how-to-create-file-share.md#create-a-file-share) in the new storage account. For your convenience, you can use the same file share name from your original storage account. Otherwise, if you use a new file share name, you must update your app setting.