Merge pull request #294398 from MicrosoftDocs/main

2/10/2025 PM Publish

Author: Taojunshen

articles/application-gateway/configuration-infrastructure.md

@@ -87,7 +87,9 @@ Depending on whether you're creating new resources or using existing ones, add t
 | Subnet | Use existing| Microsoft.Network/virtualNetworks/subnets/read<br>Microsoft.Network/virtualNetworks/subnets/join/action |
 | IP addresses| Create new| Microsoft.Network/publicIPAddresses/write<br>Microsoft.Network/publicIPAddresses/join/action |
 | IP addresses  | Use existing| Microsoft.Network/publicIPAddresses/read<br>Microsoft.Network/publicIPAddresses/join/action |
-| ApplicationGatewayWebApplicationFirewallPolicies | Create new / Update existing | Microsoft.Network/ApplicationGatewayWebApplicationFirewallPolicies/write Microsoft.Network/ApplicationGatewayWebApplicationFirewallPolicies/join/action |
+| ApplicationGatewayWebApplicationFirewallPolicies | Create new / Update existing | Microsoft.Network/ApplicationGatewayWebApplicationFirewallPolicies/write 
+Microsoft.Network/ApplicationGatewayWebApplicationFirewallPolicies/read 
+Microsoft.Network/ApplicationGatewayWebApplicationFirewallPolicies/join/action |
 
 For more information, see [Azure permissions for Networking](../role-based-access-control/permissions/networking.md) and [Virtual network permissions](../virtual-network/virtual-network-manage-subnet.md#permissions).
 ## Roles scope

articles/application-gateway/rewrite-http-headers-url.md

@@ -256,7 +256,7 @@ For a URL redirect, Application Gateway sends a redirect response to the client
 - Rewrites aren't supported when the application gateway is configured to redirect the requests or to show a custom error page.
 - Request header names can contain alphanumeric characters and hyphens. Headers names containing other characters will be discarded when a request is sent to the backend target.
 - Response header names can contain any alphanumeric characters and specific symbols as defined in [RFC 7230](https://tools.ietf.org/html/rfc7230#page-27).
-- Connection and upgrade headers cannot be rewritten
+- X-Original-Host, Connection, and upgrade headers cannot be rewritten
 - Rewrites aren't supported for 4xx and 5xx responses generated directly from Application Gateway
 
 ## Next steps

articles/azure-functions/functions-consumption-costs.md

@@ -1,7 +1,7 @@
 ---
 title: Estimating consumption-based costs in Azure Functions
 description: Learn how to better estimate the costs that you might incur when running your function app in either the Consumption plan or the Flex Consumption plan in Azure Functions.
-ms.date: 11/05/2024
+ms.date: 02/10/2025
 ms.topic: conceptual
 ms.custom:
   - build-2024
@@ -52,24 +52,24 @@ Consider a function app that is comprised only of HTTP triggers with and these b
 + HTTP triggers handle 10 concurrent requests.
 + The instance memory size setting is `2048 MB`. 
 + There are _no always ready instances configured_, which means the app can scale to zero.
-<!--- Update these example calculations after 12/1 based on GA pricing -->
+
 In a situation like this, the pricing depends more on the kind of work being done during code execution. Let's look at two workload scenarios:
 
 + **CPU-bound workload:** In a CPU-bound workload, there's no advantage to processing multiple requests in parallel in the same instance. This means that you're better off distributing each request to its own instance so requests complete as a quickly as possible without contention. In this scenario, you should set a low [HTTP trigger concurrency](./functions-concurrency.md#http-trigger-concurrency) of `1`. With 10 concurrent requests, the app scales to a steady state of roughly 10 instances, and each instance is continuously active processing one request at a time. 
 
-    Because the size of each instance is ~2 GB, the consumption for a single continuously active instance is `2 GB * 3600 s = 7200 GB-s`, which at the assumed on-demand execution rate (without any free grants applied) is `$0.1152 USD` per hour per instance. Because the CPU-bound app is scaled to 10 instance, the total hourly rate for execution time is `$1.152 USD`.
+    Because the size of each instance is ~2 GB, the consumption for a single continuously active instance is `2 GB * 3600 s = 7200 GB-s`. Assuming an on-demand execution rate of $0.000026 GB-s (without any free grants applied) becomes `$0.1872 USD` per hour per instance. Because the CPU-bound app is scaled to 10 instance, the total hourly rate for execution time is `$1.872 USD`.
 
-    Similarly, the on-demand per-execution charge (without any free grants) of 40 requests per second is equal to `40 * 3600 = 144,000` or 0.144 million executions per hour. The total (grant-free) hourly cost of executions is then `0.144 * $0.20`, which is `$0.0288` per hour.
+    Similarly, the on-demand per-execution charge (without any free grants) of 40 requests per second is equal to `40 * 3600 = 144,000` or `0.144 million` executions per hour. Assuming an on-demand rate of `$0.40` per million executions, the total (grant-free) hourly cost of executions is `0.144 * $0.40`, which is `$0.0576` per hour.
 
-    In this scenario, the total hourly cost of running on-demand on 10 instances is `$1.152 + $0.0288 = $1.1808 USD`.
+    In this scenario, the total hourly cost of running on-demand on 10 instances is `$1.872 + $0.0576s = $1.9296 USD`.
 
 + **IO bound workload:** In an IO-bound workload, most of the application time is spent waiting on incoming request, which might be limited by network throughput or other upstream factors. Because of the limited inputs, the code can process multiple operations concurrently without negative impacts. In this scenario, assume you can process all 10 concurrent requests on the same instance. 
 
-    Because consumption charges are based only on the memory of each active instance, the consumption charge calculation is simply `2 GB * 3600 s = 7200 GB-s`, which at the assumed on-demand execution rate (without any free grants applied) is `$0.1152 USD` per hour for the single instance.
+    Because consumption charges are based only on the memory of each active instance, the consumption charge calculation is simply `2 GB * 3600 s = 7200 GB-s`, which at the assumed on-demand execution rate (without any free grants applied) is `$0.1872 USD` per hour for the single instance.
 
-    As in the CPU-bound scenario, the on-demand per-execution charge (without any free grants) of 40 requests per second is equal to `40 * 3600 = 144,000` or 0.144 million executions per hour. In this case, the total (grant-free) hourly cost of executions `0.144 * $0.20`, which is `$0.0288` per hour.
+    As in the CPU-bound scenario, the on-demand per-execution charge (without any free grants) of 40 requests per second is equal to `40 * 3600 = 144,000` or 0.144 million executions per hour. In this case, the total (grant-free) hourly cost of executions `0.144 * $0.40`, which is `$0.0576` per hour.
 
-    In this scenario, the total hourly cost of running on-demand on a single instance is `$0.1152 + $0.0288 = $0.144 USD`. 
+    In this scenario, the total hourly cost of running on-demand on a single instance is `$0.1872 + $0.0576 = $0.245 USD`. 
 
 ### [Consumption plan](#tab/consumption-plan)
 

articles/azure-resource-manager/management/create-private-link-access-portal.md

@@ -2,7 +2,7 @@
 title: Create private link for managing resources - Azure portal
 description: Use Azure portal to create private link for managing resources.
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 02/09/2025
 ---
 
 # Use portal to create private link for managing Azure resources
@@ -13,7 +13,7 @@ This article explains how to use [Azure Private Link](../../private-link/index.y
 
 ## Create resource management private link
 
-When you create a resource management private link, the private link association is automatically created for you.
+When you create a resource management private link, the portal automatically creates the private link association for you.
 
 1. In the [portal](https://portal.azure.com), search for **Resource management private links** and select it from the available options.
 

articles/azure-resource-manager/management/delete-resource-group.md

@@ -1,8 +1,8 @@
 ---
-title: Delete resource group and resources
-description: Describes how to delete resource groups and resources. It describes how Azure Resource Manager orders the deletion of resources when a deleting a resource group. It describes the response codes and how Resource Manager handles them to determine if the deletion succeeded.
+title: Delete Resource Groups and Resources
+description: Describes how to delete resource groups and resources. It describes how Azure Resource Manager orders the deletion of resources when you delete a resource group. It describes the response codes and how Resource Manager handles them to determine if the deletion succeeded.
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 02/09/2025
 ms.custom: devx-track-arm-template
 content_well_notification: 
   - AI-contribution
@@ -17,7 +17,7 @@ This article shows how to delete resource groups and resources. It describes how
 > To delete a resource group, you must first remove any underlying resource locks and backup data.
 >
 
-## How order of deletion is determined
+## How Resource Manager determines the order of deletion
 
 When you delete a resource group, Resource Manager determines the order to delete resources. It uses the following order:
 
@@ -27,7 +27,7 @@ When you delete a resource group, Resource Manager determines the order to delet
 
 3. The remaining resources are deleted after the previous two categories.
 
-After the order is determined, Resource Manager issues a DELETE operation for each resource. It waits for any dependencies to finish before proceeding.
+After Resource Manager determines the order, it issues a DELETE operation for each resource. It waits for any dependencies to finish before proceeding.
 
 For synchronous operations, the expected successful response codes are:
 
@@ -36,18 +36,17 @@ For synchronous operations, the expected successful response codes are:
 * 404
 
 For asynchronous operations, the expected successful response is 202. Resource Manager tracks the location header or the azure-async operation header to determine the status of the asynchronous delete operation.
-  
 ### Deletion errors
 
-When a delete operation returns an error, Resource Manager retries the DELETE call. Retries happen for the 5xx, 429 and 408 status codes. By default, the time period for retry is 15 minutes.
+When a delete operation returns an error, Resource Manager retries the DELETE call. Retries happen for the 5xx, 429, and 408 status codes. By default, the time period for retry is 15 minutes.
 
 ## After deletion
 
-Resource Manager issues a GET call on each resource that it tried to delete. The response of this GET call is expected to be 404. When Resource Manager gets a 404, it considers the deletion to have completed successfully. Resource Manager removes the resource from its cache.
+Resource Manager issues a GET call on each resource that it tried to delete. The response of this GET call is expected to be 404. When Resource Manager gets a 404, it considers the deletion to be successful. Resource Manager removes the resource from its cache.
 
 However, if the GET call on the resource returns a 200 or 201, Resource Manager recreates the resource.
 
-If the GET operation returns an error, Resource Manager retries the GET for the following error code:
+If the GET operation returns an error, Resource Manager retries the GET for the following error codes:
 
 * Less than 100
 * 408
@@ -57,11 +56,11 @@ If the GET operation returns an error, Resource Manager retries the GET for the
 For other error codes, Resource Manager fails the deletion of the resource.
 
 > [!IMPORTANT]
-> Resource Group deletion is irreversible.
+> Resource group deletion is irreversible.
 
 ## Delete resource group
 
-Use one of the following methods to delete the resource group.
+To delete the resource group, use one of the following methods.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -81,9 +80,9 @@ az group delete --name ExampleResourceGroup
 
 1. Select **Delete resource group**.
 
-   :::image type="content" source="./media/delete-resource-group/delete-group.png" alt-text="Screenshot of the Delete resource group button in the Azure portal.":::
+   :::image type="content" source="./media/delete-resource-group/delete-group.png" alt-text="Screenshot of the 'Delete resource group' button in the Azure portal.":::
 
-1. To confirm the deletion, type the name of the resource group
+1. To confirm the deletion, type the name of the resource group.
 
 # [Python](#tab/azure-python)
 
@@ -104,7 +103,7 @@ rg_result = resource_client.resource_groups.begin_delete("exampleGroup")
 
 ## Delete resource
 
-Use one of the following methods to delete a resource.
+To delete a resource, use one of the following methods.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -164,34 +163,34 @@ resource_client.resources.begin_delete_by_id(
 To delete a resource group, you need access to the delete action for the **Microsoft.Resources/subscriptions/resourceGroups** resource.
 
 > [!IMPORTANT]
-> The only permission required to delete a resource group is permission to the delete action for deleting resource groups.  You do **not** need permission to delete individual resources within that resource group.  Additionally, delete actions that are specified in **notActions** for a roleAssignment are superseded by the resource group delete action.  This is consistent with the scope hierarchy in the Azure role-based access control model.
+> The only permission required to delete a resource group is permission to the delete action for deleting resource groups. You don't need permission to delete individual resources within that resource group. Additionally, delete actions that are specified in **notActions** for a roleAssignment are superseded by the resource group delete action. This requirement is consistent with the scope hierarchy in the Azure role-based access control model.
 
 For a list of operations, see [Azure resource provider operations](../../role-based-access-control/resource-provider-operations.md). For a list of built-in roles, see [Azure built-in roles](../../role-based-access-control/built-in-roles.md).
 
-If you have the required access, but the delete request fails, it may be because there's a [lock on the resources or resource group](lock-resources.md). Even if you didn't manually lock a resource group, [a related service may have automatically locked it](lock-resources.md#managed-applications-and-locks). Or, the deletion can fail if the resources are connected to resources in other resource groups that aren't being deleted. For example, you can't delete a virtual network with subnets that are still in use by a virtual machine.
+If you have the required access, but the delete request fails, it might be because there's a [lock on the resources or resource group](lock-resources.md). Even if you didn't manually lock a resource group, [a related service might automatically lock it](lock-resources.md#managed-applications-and-locks). Or, the deletion can fail if the resources are connected to resources in other resource groups that aren't being deleted. For example, you can't delete a virtual network with subnets that a virtual machine uses.
 
 ## Can I recover a deleted resource group?
 
 No, you can't recover a deleted resource group. However, you might be able to restore some recently deleted resources.
 
 Some resource types support *soft delete*. You might have to configure soft delete before you can use it. For information about enabling soft delete, see:
 
-* [Azure Key Vault soft-delete overview](/azure/key-vault/general/soft-delete-overview)
-* [Azure Storage - Soft delete for containers](../../storage/blobs/soft-delete-container-overview.md)
-* [Azure Storage - Soft delete for blobs](../../storage/blobs/soft-delete-blob-overview.md)
+* [Soft-delete overview - Azure Key Vault](/azure/key-vault/general/soft-delete-overview)
+* [Soft delete for containers - Azure Storage](../../storage/blobs/soft-delete-container-overview.md)
+* [Soft delete for blobs - Azure Storage](../../storage/blobs/soft-delete-blob-overview.md)
 * [Soft delete for Azure Backup](../../backup/backup-azure-security-feature-cloud.md)
 * [Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads](../../backup/soft-delete-sql-saphana-in-azure-vm.md)
 * [Soft delete for virtual machines](../..//backup/soft-delete-virtual-machines.md)
 
 To restore deleted resources, see:
 
 * [Recover deleted Azure AI services resources](/azure/ai-services/manage-resources)
-* [Microsoft Entra - Recover from deletions](../../active-directory/architecture/recover-from-deletions.md)
+* [Recover from deletions - Microsoft Entra](../../active-directory/architecture/recover-from-deletions.md)
 
 You can also [open an Azure support case](/azure/azure-portal/supportability/how-to-create-azure-support-request). Provide as much detail as you can about the deleted resources, including their resource IDs, types, and resource names. Request that the support engineer check if the resources can be restored.
 
 > [!NOTE]
-> Recovery of deleted resources is not possible under all circumstances. A support engineer will investigate your scenario and advise you whether it's possible.
+> Recovery of deleted resources isn't possible under all circumstances. A support engineer investigates your scenario and advises you whether it's possible.
 
 ## Next steps
 

articles/azure-resource-manager/management/extension-resource-types.md

@@ -1,13 +1,13 @@
 ---
-title: Extension resource types
-description: Lists the Azure resource types are used to extend the capabilities of other resource types.
+title: Extension Resource Types
+description: Lists the Azure resource types that you use to extend the capabilities of other resource types.
 ms.topic: conceptual
-ms.date: 07/24/2024
+ms.date: 02/09/2025
 ---
 
 # Resource types that extend capabilities of other resources
 
-An extension resource is a resource that adds to another resource's capabilities. For example, resource lock is an extension resource. You apply a resource lock to another resource to prevent it from being deleted or modified. It doesn't make sense to create a resource lock by itself. An extension resource is always applied to another resource.
+An extension resource is a resource that adds to another resource's capabilities. For example, resource lock is an extension resource. You apply a resource lock to another resource to prevent it from being deleted or modified. It doesn't make sense to create a resource lock by itself. You always apply an extension resource to another resource.
 
 ## Microsoft.Advisor
 

articles/azure-resource-manager/management/manage-private-link-access-commands.md

@@ -1,14 +1,14 @@
 ---
-title: Manage resource management private links
+title: Manage Resource Management Private Links
 description: Use APIs to manage existing resource management private links
 ms.topic: conceptual
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
-ms.date: 09/26/2024
+ms.date: 02/09/2025
 ---
 
 # Manage resource management private links
 
-This article explains how you to work with existing resource management private links. It shows API operations for getting and deleting existing resources.
+This article explains how to work with existing resource management private links. It shows API operations for getting and deleting existing resources.
 
 If you need to create a resource management private link, see [Use portal to create private link for managing Azure resources](create-private-link-access-portal.md) or [Use APIs to create private link for managing Azure resources](create-private-link-access-commands.md).