Merge pull request #306783 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-10 11:00 UTC

Author: learn-build-service-prod[bot]

articles/application-gateway/application-gateway-private-deployment.md

@@ -169,17 +169,6 @@ A list of all Azure CLI references for Private Link Configuration on Application
 
 After registering the feature, configuration of NSG, Route Table, and private IP address frontend configuration can be performed using any methods. For example: REST API, ARM Template, Bicep deployment, Terraform, PowerShell, CLI, or Portal.
 
-## Resource Changes
-
-After your gateway is provisioned, a resource tag is automatically assigned with the name of **EnhancedNetworkControl** and value of **True**. See the following example:
-
- ![Screenshot of the EnhancedNetworkControl tag.](./media/application-gateway-private-deployment/tags.png)
-
-The resource tag is cosmetic, and serves to confirm that the gateway has been provisioned with the capabilities to configure any combination of the private only gateway features. Modification or deletion of the tag or value doesn't change any functional workings of the gateway. 
-
-> [!TIP]
-> The **EnhancedNetworkControl** tag can be helpful when existing Application Gateways were deployed in the subscription prior to feature enablement and you would like to differentiate which gateway can utilize the new functionality.	
-
 ## Application Gateway Subnet 
 
 Application Gateway Subnet is the subnet within the Virtual Network where the Application Gateway Resources will be deployed. In the Frontend Private Ip configuration, is important that this subnet can reach privately the resources that want to connect to your exposed app or site.

articles/azure-app-configuration/quickstart-deployment-overview.md

@@ -47,7 +47,7 @@ You can manage App Configuration data, such as key-values and snapshots, in depl
 - Data access can be attributed to the deployment caller for auditing purposes.
 
 > [!IMPORTANT]
-> App Configuration control plane API version `2023-08-01-preview` or later is required to configure the Azure Resource Manager authentication mode by using an [ARM template](./quickstart-resource-manager.md), [Bicep](./quickstart-bicep.md), or the REST API. For REST API examples, see the [azure-rest-api-specs](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/appconfiguration/resource-manager/Microsoft.AppConfiguration/preview/2023-08-01-preview/examples/ConfigurationStoresCreateWithDataPlaneProxy.json) GitHub repo.
+> App Configuration control plane API version `2023-08-01-preview` or later is required to configure the Azure Resource Manager authentication mode by using an [ARM template](./quickstart-resource-manager.md), [Bicep](./quickstart-bicep.md), or the REST API. For REST API examples, see the [azure-rest-api-specs](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/appconfiguration/resource-manager/Microsoft.AppConfiguration/AppConfiguration/preview/2025-02-01-preview/examples/ConfigurationStoresCreateWithDataPlaneProxy.json) GitHub repo.
 
 ### Azure Resource Manager authentication mode
 

articles/backup/azure-data-lake-storage-backup-overview.md

@@ -63,7 +63,6 @@ You can restore data from any point in time where a recovery point exists. Recov
 Azure Backup allows restoring data from any recovery point within the retention period set by the backup policy. Recovery points are created when the storage account is in protected state, and can be used to restore until they expire as per the retention policy. This solution allows performing granular recovery by selecting containers, applying a prefix-based filter, or restoring the full storage account.
 
 >[!Note]
->- To restore a recovery point to a different subscription, request the Azure Backup team to allowlist the required subscription and grant access by using the [signup form](https://forms.office.com/r/sixidTkYb4).
 >- Currently, the vaulted backup solution supports restoring data only to a different storage account within the same region as the vault. However, restoring data from older recovery points might result in a longer recovery time (higher [Recovery Time Objective](azure-backup-glossary.md#recovery-time-objective-rto)).
 
 ## Next steps