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

Author: Learn Build Service GitHub App

.openpublishing.redirection.json

@@ -3749,6 +3749,21 @@
       "source_path_from_root": "/articles/virtual-network/tutorial-connect-virtual-networks-cli.md",
       "redirect_url": "/azure/virtual-network/tutorial-connect-virtual-networks",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/virtual-network/ip-services/public-ip-upgrade-portal.md",
+      "redirect_url": "/azure/virtual-network/ip-services/public-ip-upgrade",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/virtual-network/ip-services/public-ip-upgrade-cli.md",
+      "redirect_url": "/azure/virtual-network/ip-services/public-ip-upgrade",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/virtual-network/ip-services/public-ip-upgrade-powershell.md",
+      "redirect_url": "/azure/virtual-network/ip-services/public-ip-upgrade",
+      "redirect_document_id": false
     }
   ]
 }

articles/app-service/environment/app-service-app-service-environment-network-architecture-overview.md

@@ -61,27 +61,10 @@ If the endpoint being called is **inside** of the virtual network topology, the
 
 However, since an App Service Environment is always located within a subnet, you're guaranteed that the internal IP address of a compute resource running an app will always lie within the CIDR range of the subnet.  As a result, when fine-grained ACLs or network security groups are used to secure access to other endpoints within the virtual network, the subnet range containing the App Service Environment needs to be granted access.
 
-The following diagram shows these concepts in more detail:
-
-![Outbound Network Addresses][OutboundNetworkAddresses]
-
-In the above diagram:
-
-* Since the public VIP of the App Service Environment is 192.23.1.2, that is the outbound IP address used when making calls to "Internet" endpoints.
-* The CIDR range of the containing subnet for the App Service Environment is 10.0.1.0/26.  Other endpoints within the same virtual network infrastructure will see calls from apps as originating from somewhere within this address range.
-
 ## Calls Between App Service Environments
 
 A more complex scenario can occur if you deploy multiple App Service Environments in the same virtual network, and make outbound calls from one App Service Environment to another App Service Environment.  These types of cross App Service Environment calls will also be treated as "Internet" calls.
 
-The following diagram shows an example of a layered architecture with apps on one App Service Environment (for example "Front door" web apps) calling apps on a second App Service Environment (for example internal back-end API apps not intended to be accessible from the Internet).
-
-![Calls Between App Service Environments][CallsBetweenAppServiceEnvironments]
-
-In the example above the App Service Environment "ASE One" has an outbound IP address of 192.23.1.2.  If an app running on this App Service Environment makes an outbound call to an app running on a second App Service Environment ("ASE Two") located in the same virtual network, the outbound call will be treated as an "Internet" call.  As a result the network traffic arriving on the second App Service Environment will show as originating from 192.23.1.2 (that is, not the subnet address range of the first App Service Environment).
-
-Even though calls between different App Service Environments are treated as "Internet" calls, when both App Service Environments are located in the same Azure region the network traffic will remain on the regional Azure network and won't physically flow over the public Internet.  As a result you can use a network security group on the subnet of the second App Service Environment to only allow inbound calls from the first App Service Environment (whose outbound IP address is 192.23.1.2), thus ensuring secure communication between the App Service Environments.
-
 ## Additional Links and Information
 
 Details on inbound ports used by App Service Environments and using network security groups to control inbound traffic is available [here][controllinginboundtraffic].
@@ -96,5 +79,3 @@ Details on using user-defined routes to grant outbound Internet access to App Se
 <!-- IMAGES -->
 [GeneralNetworkFlows]: ./media/app-service-app-service-environment-network-architecture-overview/NetworkOverview-1.png
 [OutboundIPAddress]: ./media/app-service-app-service-environment-network-architecture-overview/OutboundIPAddress-1.png
-[OutboundNetworkAddresses]: ./media/app-service-app-service-environment-network-architecture-overview/OutboundNetworkAddresses-1.png
-[CallsBetweenAppServiceEnvironments]: ./media/app-service-app-service-environment-network-architecture-overview/CallsBetweenEnvironments-1.png

articles/app-service/environment/media/app-service-app-service-environment-network-architecture-overview/CallsBetweenEnvironments-1.png

@@ -219,8 +219,6 @@ To create the same routes manually, follow these steps:
 
 5. After you create the new route table, go to the subnet. Select your route table from the list in the portal. After you save the change, you should then see the NSGs and routes noted with your subnet.
 
-    ![Screenshot that shows NSGs and routes.][7]
-
 ## Service endpoints
 
 Service endpoints enable you to restrict access to multi-tenant services to a set of Azure virtual networks and subnets. For more information, see [Virtual Network service endpoints][serviceendpoints].
@@ -235,7 +233,6 @@ When service endpoints are enabled on a subnet with an instance of Azure SQL, al
 [1]: ./media/network_considerations_with_an_app_service_environment/networkase-overflow.png
 [2]: ./media/network_considerations_with_an_app_service_environment/networkase-overflow2.png
 [6]: ./media/network_considerations_with_an_app_service_environment/networkase-udr.png
-[7]: ./media/network_considerations_with_an_app_service_environment/networkase-subnet.png
 [8]: ./media/network_considerations_with_an_app_service_environment/serviceendpoint.png
 
 <!--Links-->

articles/app-service/environment/media/app-service-app-service-environment-network-architecture-overview/OutboundNetworkAddresses-1.png

@@ -57,8 +57,8 @@ You can use rewrite conditions to evaluate the content of HTTP(S) requests and r
 
   An action can have the following value types or their combinations:
   * Text.
-  * Request header's value - To use a captured request header value, specify the syntax as `{http_req_headerName}`.
-  * Response header's value - To use a captured response header value from the preceding Condition, specify the syntax as `{http_resp_headerName}`. You can use `{capt_header_value_matcher}` when the value is captured from Action Set's "Set-Cookie" response header. Know more about [capture under Action set](#syntax-for-capturing).
+  * Request header's value - To use a captured Request header's value, specify the syntax as `{http_req_headerName}`.
+  * Response header's value - To use a captured Response header's value from the preceding Condition, specify the syntax as `{http_resp_headerName}`. The Rewrite Action block also supports the "Header Value Matcher" field for Set-Cookie header. This optional field lets you match as well as capture the value of a specific header when multiple Set-Cookie headers with the same name exist. To manipulate that specific cookie's captured value, you can then use `{capt_header_value_matcher}`. Know more about [capture under Action set](#syntax-for-capturing).
   * Server variable - To use a server variable, specify the syntax as `{var_serverVariable}`. [List of supported Server variables](#server-variables).
 
 > [!Note]

articles/app-service/environment/media/network_considerations_with_an_app_service_environment/networkase-subnet.png

@@ -3,7 +3,7 @@ title: Back up Azure Blobs using Azure CLI
 description: Learn how to back up Azure Blobs using Azure CLI.
 ms.topic: how-to
 ms.custom: devx-track-azurecli
-ms.date: 07/24/2024
+ms.date: 11/26/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
@@ -241,6 +241,16 @@ Once all the relevant permissions are set, configure the backup by running the f
 > [!IMPORTANT]
 > Once a storage account is configured for blobs backup, a few capabilities such as change feed and delete lock are affected. [Learn more](blob-backup-configure-manage.md#effects-on-backed-up-storage-accounts).
 
+## Update a backup instance
+
+After you have configured the backup, you can change the associated policy with a backup instance. For vaulted backups, you can also change the containers selected for backup. 
+
+To update the backup instance, run the following command:
+
+1. Validate if the backup instance is ready for configuring backup by using the [az dataprotection backup-instance validate-for-backup](/cli/azure/dataprotection/backup-instance?view=azure-cli-latest&preserve-view=true#az-dataprotection-backup-instance-validate-for-backup) command . The command fails if the backup instance isn't ready.
+1. Change the Backup policy used for backing up the Azure Blobs by using the [az dataprotection backup-instance update](/cli/azure/dataprotection/backup-instance?view=azure-cli-latest&preserve-view=true#az-dataprotection-backup-instance-update-policy). Specify the relevant backup item and the new backup policy.
+
+
 ## Next steps
 
 [Restore Azure Blobs using Azure CLI](restore-blobs-storage-account-cli.md)

articles/app-service/environment/network-info.md

@@ -3,7 +3,7 @@ title: Back up Azure blobs within a storage account using Azure PowerShell
 description: Learn how to back up all Azure blobs within a storage account using Azure PowerShell.
 ms.topic: how-to
 ms.custom: devx-track-azurepowershell
-ms.date: 07/24/2024
+ms.date: 11/27/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
@@ -144,6 +144,19 @@ blobrg-PSTestSA-3df6ac08-9496-4839-8fb5-8b78e594f166 Microsoft.DataProtection/ba
 
 ---
 
+## Update a backup instance
+
+After you have configured the backup, you can change the associated policy with a backup instance. For vaulted backups, you can also change the containers selected for backup. 
+
+To update the backup instance, run the following cmdlets:
+
+1. Validate if the backup instance is ready for configuring backup using the [Test-AzDataProtectionBackupInstanceReadiness](/powershell/module/az.dataprotection/test-azdataprotectionbackupinstancereadiness?view=azps-13.0.0&preserve-view=true) command. The command fails if the   backup instance is not ready.
+
+   You can also use this command to check if the backup vault has all the necessary permissions to configure backup.
+
+1. Change the policy used for backing up the Azure Blobs by using the [Update-AzDataProtectionBackupInstance](/powershell/module/az.dataprotection/update-azdataprotectionbackupinstance?view=azps-13.0.0&preserve-view=true). Specify the relevant backup item and the new backup policy.
+
+
 ## Next steps
 
 [Restore Azure blobs using Azure PowerShell](restore-blobs-storage-account-ps.md)