Merge pull request #307726 from MicrosoftDocs/main

11/4/2025 11:00 AM IST Publish

Author: PhilKang0704

articles/application-gateway/migrate-v1-v2.md

@@ -6,7 +6,7 @@ author: mbender-ms
 ms.service: azure-application-gateway
 ms.custom: devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 01/23/2025
+ms.date: 11/3/2025
 ms.author: mbender
 # Customer intent: As an DevOps engineer, I want to migrate my Azure Application Gateway and Web Application Firewall from V1 to V2, so that I can leverage the improved features and performance while ensuring minimal downtime during the transition.
 ---
@@ -239,7 +239,6 @@ To run the script:
 * [Virtual network service endpoint policies](../virtual-network/virtual-network-service-endpoint-policies-overview.md) are currently not supported in an Application Gateway subnet.
 * To  migrate a TLS/SSL configuration, you must specify all the TLS/SSL certs used in your V1 gateway.
 * If you have FIPS mode enabled for your V1 gateway, it isn't migrated to your new V2 gateway. 
-* If you have a Private IP only V1 gateway, the script generates a private and public IP address for the new V2 gateway. The Private IP only V2 gateway is currently in public preview. Once it becomes generally available, customers can utilize the script to transfer their private IP only V1 gateway to a private IP only V2 gateway.
 * WAFv2 is created in old WAF config mode; migration to WAF policy is required.
 * The new WAFv2 is configured to use CRS 3.0 by default. However, since CRS 3.0 is on the path to deprecation, we recommend upgrading to the latest rule set, DRS 2.1 post migration. For more details, refer [CRS and DRS rule groups and rules](../web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md)
 

articles/azure-app-configuration/rest-api-snapshot.md

@@ -134,7 +134,7 @@ To improve client caching, use `If-Match` or `If-None-Match` request headers. Th
 The following request retrieves the snapshot only if the current representation doesn't match the specified `etag`:
 
 ```http
-GET /snapshot/{name}?api-version={api-version} HTTP/1.1
+GET /snapshots/{name}?api-version={api-version} HTTP/1.1
 Accept: application/vnd.microsoft.appconfig.snapshot+json;
 If-None-Match: "{etag}"
 ```
@@ -290,7 +290,7 @@ GET /snapshot?$select=name,status&api-version={api-version} HTTP/1.1
 | retention_period | no | Standard and Premium tiers <br/>&nbsp;&nbsp;&nbsp;&nbsp; 2592000 (30 days) <br/> Free tier and Developer tiers <br/> &nbsp;&nbsp;&nbsp;&nbsp; 604800 (seven days) | Standard and Premium tiers <br/> &nbsp;&nbsp;&nbsp;&nbsp; Minimum: 3600 (one hour) <br/> &nbsp;&nbsp;&nbsp;&nbsp; Maximum: 7776000 (90 days) <br/> Free tier and Developer tiers <br/> &nbsp;&nbsp;&nbsp;&nbsp; Minimum: 3600 (one hour) <br/> &nbsp;&nbsp;&nbsp;&nbsp; Maximum: 604800 (seven days) |
 
 ```http
-PUT /snapshot/{name}?api-version={api-version} HTTP/1.1
+PUT /snapshots/{name}?api-version={api-version} HTTP/1.1
 Content-Type: application/vnd.microsoft.appconfig.snapshot+json
 ```
 
@@ -334,8 +334,8 @@ Operation-Location: {appConfigurationEndpoint}/operations?snapshot={name}&api-ve
   ],
   "composition_type": "key",
   "created": "2023-03-20T21:00:03+00:00",
-  "size": 2000,
-  "items_count": 4,
+  "size": 0,
+  "items_count": 0,
   "tags": {
     "t1": "value1",
     "t2": "value2"
@@ -359,7 +359,7 @@ Operation-Location: {appConfigurationEndpoint}/operations?snapshot={name}&api-ve
 | retention_period | no | Standard tier <br/>&nbsp;&nbsp;&nbsp;&nbsp; 2592000 (30 days) <br/> Free tier <br/> &nbsp;&nbsp;&nbsp;&nbsp; 604800 (7 days) | Standard tier <br/> &nbsp;&nbsp;&nbsp;&nbsp; Minimum: 3600 (1 hour) <br/> &nbsp;&nbsp;&nbsp;&nbsp; Maximum: 7776000 (90 days) <br/> Free tier <br/> &nbsp;&nbsp;&nbsp;&nbsp; Minimum: 3600 (1 hour) <br/> &nbsp;&nbsp;&nbsp;&nbsp; Maximum: 604800 (7 days) |
 
 ```http
-PUT /snapshot/{name}?api-version={api-version} HTTP/1.1
+PUT /snapshots/{name}?api-version={api-version} HTTP/1.1
 Content-Type: application/vnd.microsoft.appconfig.snapshot+json
 ```
 
@@ -405,8 +405,8 @@ Operation-Location: {appConfigurationEndpoint}/operations?snapshot={name}&api-ve
   ],
   "composition_type": "key",
   "created": "2023-03-20T21:00:03+00:00",
-  "size": 2000,
-  "items_count": 4,
+  "size": 0,
+  "items_count": 0,
   "tags": {
     "t1": "value1",
     "t2": "value2"

articles/azure-functions/functions-scenarios.md

@@ -83,6 +83,7 @@ public static async Task Run([BlobTrigger("catalog-uploads/{name}", Source = Blo
 ::: zone-end
 
 ::: zone pivot="programming-language-java" 
++ [Blob trigger with the Event Grid source type quickstart sample)](https://github.com/Azure-Samples/functions-quickstart-java-azd-eventgrid-blob)
 + [Trigger Azure Functions on blob containers using an event subscription](functions-event-grid-blob-trigger.md?pivots=programming-language-java)
 ::: zone-end
 

articles/lab-services/vm-deletion-policy.md

@@ -11,12 +11,12 @@ ms.date: 04/23/2025
 
 [!INCLUDE [Retirement guide](./includes/retirement-banner.md)]
 
-On June 9, 2025, Azure Lab Services will delete all virtual machines (VMs) that have been inactive since July 1, 2023. 
+Starting June 9, 2025, Azure Lab Services will automatically delete any virtual machines (VMs) that have been inactive for more than two years, as part of a monthly cleanup process.
 
 A virtual machine is considered inactive if no operations were performed on it. These operations include actions such as starting, stopping, resetting passwords, and reimaging. Any associated labs for these virtual machines will also be deleted. This policy applies to template VMs and production VMs.
 
 After the virtual machines are deleted, we won't be able to recover them or their data.  
 
 **Recommended actions**: 
 1. Back up any required data from your inactive virtual machines. 
-1. Delete the virtual machines and the associated labs to avoid incurring any unnecessary charges. 
+1. Delete the virtual machines and the associated labs to avoid incurring any unnecessary charges. 

articles/load-balancer/network-load-balancing-aws-to-azure-how-to.md

@@ -83,7 +83,7 @@ This migration is designed as a cutover migration. With this approach, you build
 - Rollback time: 15-30 minutes if needed
 
 > [!NOTE]
-> Resetting your DNS TTL values to 300 seconds (5 minutes) before the cutover helps reduce DNS caching delays for many resolvers; reducing the TTL to 60 seconds (1 minute) can further speed propagation for resolvers that respect short TTLs. Propogation depends on upstream and recursive resolvers and can't be guaranteed for all clients—prepare monitoring and rollback plans accordingly.
+> Resetting your DNS TTL values to 300 seconds (5 minutes) before the cutover helps reduce DNS caching delays for many resolvers; reducing the TTL to 60 seconds (1 minute) can further speed propagation for resolvers that respect short TTLs. Propagation depends on upstream and recursive resolvers and can't be guaranteed for all clients—prepare monitoring and rollback plans accordingly.
 
 ## Step 1: Assessment
 

articles/load-balancer/tutorial-create-gateway-load-balancer.md

@@ -550,7 +550,7 @@ New-AzLoadBalancer @lb
 
 ## Add network virtual appliances to the Gateway Load Balancer backend pool
 > [!NOTE]
-> If leveraging your own custom network virtual appliance in the backend pool of a Gateway Load Balancer, please ensure the MTU of all NVA virtual machines are raised to a minimum of 1550 bytes to accomodate for the VXLAN encapsulated headers. This will allow source packets up to the limit of 1500 byte packets in Azure, avoiding fragmentation.
+> If leveraging your own custom network virtual appliance in the backend pool of a Gateway Load Balancer, please ensure the MTU of all NVA virtual machines are raised to a minimum of 1550 bytes to accommodate for the VXLAN encapsulated headers. This will allow source packets up to the limit of 1500 byte packets in Azure, avoiding fragmentation.
 
 # [Azure portal](#tab/azureportal)
 

articles/sap/workloads/get-started.md

@@ -57,7 +57,7 @@ In the SAP workload documentation space, you can find the following areas:
 ## Change Log
 
 - November 03, 2025: Deleted the document describing how to deploy SAP Business Suite on Windows and SQL Server in SAP Cloud Appliance Library (CAL) since offer was retired by SAP CAL
-October 31, 2025: Added clarification around Premium SSD Performance Plus and added storage configuration for Dv6/Ev6 certified HANA VMs in [SAP HANA Azure virtual machine Premium SSD storage configurations](./hana-vm-premium-ssd-v1.md)
+- October 31, 2025: Added clarification around Premium SSD Performance Plus and added storage configuration for Dv6/Ev6 certified HANA VMs in [SAP HANA Azure virtual machine Premium SSD storage configurations](./hana-vm-premium-ssd-v1.md)
 - September 10, 2025: Added a new document on [Azure Files NFS Encryption in Transit for SAP on Azure Systems](./sap-azure-files-nfs-encryption-in-transit-guide.md) and updated the Azure Files NFS related sections in the existing documents on how to configure and deploy the Encryption in Transit. 
 - August 4, 2025: Updated colocation constraint command for SAPHanaSR configuration in [High availability for SAP HANA on Azure VMs on SUSE Linux Enterprise Server](./sap-hana-high-availability.md)
 - August 4, 2025: Updated order constraints between SAPHana, SAPHanaTopology resources and Filesystem resources in [High availability of SAP HANA scale-up with Azure NetApp Files on RHEL](./sap-hana-high-availability-netapp-files-red-hat.md).

articles/sre-agent/overview.md

@@ -3,7 +3,7 @@ title: Overview of Azure SRE Agent Preview
 description: Learn how AI-enabled agents help solve problems and support resilient and self-healing systems on your behalf.
 author: craigshoemaker
 ms.topic: overview
-ms.date: 10/13/2025
+ms.date: 11/03/2025
 ms.author: cshoe
 ms.service: azure-sre-agent
 ---
@@ -91,6 +91,12 @@ Keep in mind the following considerations as you use Azure SRE Agent:
 - Availability varies by region and tenant configuration.  
 - Preview [billing](billing.md) begins *September 1, 2025*, via Azure agent units (AAUs).
 
+When you create an agent, following resources are also automatically created for you:
+
+- Azure Application Insights
+- Log Analytics workspace
+- Managed Identity
+
 ## Preview access
 
 While access to SRE Agent was previously only available to customers via a waitlist, the agent is now available to all customers through the [Azure portal](https://aka.ms/sreagent/portal).

articles/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md

@@ -4,7 +4,7 @@ description: Shows you how to use Resource Manager templates to upgrade from Azu
 author: normesta
 ms.service: azure-blob-storage
 ms.topic: concept-article
-ms.date: 11/15/2024
+ms.date: 11/03/2025
 ms.author: normesta
 ms.custom:
   - devx-track-azurepowershell
@@ -67,6 +67,10 @@ After the upgrade has completed, break the leases you created to resume allowing
 > [!WARNING]
 > Breaking an active lease without gracefully disabling applications or virtual machines that are currently accessing those resources could have unexpected results. Be sure to quiesce any current write activities before breaking any current leases.
 
+### Make any planned changes to the names of archived blobs
+
+If you plan the change the name of an archived blob or the name of any parent directory that leads up to the archived blob, make sure modifications **before** you upgrade. If you change the name of an archived blob or any parent directory leading to the archived blob **after** the upgrade, then you won't be able to rehydrate it. This is a temporary limitation of the current release. 
+
 ## Perform the upgrade
 
 ### [Portal](#tab/azure-portal)

articles/storage/file-sync/file-sync-scale-targets.md

@@ -1,26 +1,27 @@
 ---
-title: Azure File sync scalability and performance targets
-description: Learn about the scalability and performance targets for Azure File Sync, management and namespace limits.
+title: Azure File Sync Scale Targets
+description: Learn about the scalability and performance targets for Azure File Sync.
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: concept-article
-ms.date: 08/28/2025
+ms.date: 11/03/2025
 ms.author: kendownie
 ms.custom: references_regions
 ---
 
 # Scalability and performance targets for Azure File Sync
+
 [Azure File Sync](./file-sync-introduction.md) extends [Azure Files](../files/storage-files-introduction.md) to Windows Server, enabling local caching, multi-site sync, and cloud tiering for file shares. This article discusses the scalability and performance targets for Azure File Sync.
 
 Because Azure File Sync uses Azure Files as the backing store for data synced from your on-premises file servers, you should also consider the [scalability and performance targets for Azure Files](../files/storage-files-scale-targets.md?toc=/azure/storage/file-sync/toc.json).
 
 ## Azure File Sync scale targets
-The following table indicates which targets are soft, representing the Microsoft tested boundary, and hard, indicating an enforced maximum:
+
+The following table indicates which targets are soft, representing the Microsoft tested boundary, and hard, indicating an enforced maximum. An Azure File Sync endpoint can scale up to the size of an Azure file share. If the Azure file share size limit is reached, sync won't be able to operate.
 
 | Resource | Target | Hard limit |
 |-|-|-|
-| Storage Sync Services per region | 100 Storage Sync Services | Yes |
-| Storage Sync Services per subscription | 15 Storage Sync Services | Yes |
+| Storage Sync Services per subscription | 100 Storage Sync Services | Yes |
 | Sync groups per Storage Sync Service | 200 sync groups | Yes |
 | Registered servers per Storage Sync Service | 100 servers | Yes |
 | Private endpoints per Storage Sync Service | 100 private endpoints | Yes |
@@ -33,10 +34,8 @@ The following table indicates which targets are soft, representing the Microsoft
 | File size | 100 GiB | No |
 | Minimum file size for a file to be tiered | Based on file system cluster size (double file system cluster size). For example, if the file system cluster size is 4 KiB, the minimum file size is 8 KiB. | Yes |
 
-> [!NOTE]
-> An Azure File Sync endpoint can scale up to the size of an Azure file share. If the Azure file share size limit is reached, sync won't be able to operate.
-
 ## Azure File Sync performance metrics
+
 Since the Azure File Sync agent runs on a Windows Server machine that connects to the Azure file shares, the effective sync performance depends upon many factors in your infrastructure, including:
 
 - Windows Server and the underlying disk configuration
@@ -57,7 +56,7 @@ The following table indicates the Azure File Sync performance targets:
 | Full download throughput | 60 objects per second per server endpoint |
 
 > [!NOTE]
-> The actual performance will depend on multiple factors as outlined in the beginning of this section.
+> Actual performance will depend on multiple factors as outlined in the beginning of this section.
 
 As a general guide for your deployment, you should keep a few things in mind: