Merge pull request #312831 from MicrosoftDocs/main

Taojunshen · web-flow · commit 1e542d5504be · 2026-03-10T01:08:00.000+08:00
3/9/2026 AM Publishing
diff --git a/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-purge.md b/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-purge.md
@@ -15,7 +15,7 @@ Autopurge operates asynchronously in the background, optimized to minimize syste
 
 ## How it works
 
-Autopurge is an opt-in feature. You can enable it by defining retention policies that control how long to keep the data of orchestrations in certain statuses. The autopurge feature purges orchestration data associated with terminal statuses. "Terminal" refers to orchestrations that have reached a final state with no further scheduling, event processing, or work item generation. Terminal statuses include:
+Autopurge is enabled by default with a 30 day policy, but it can be customized. You can modify it by defining retention policies that specify how long to keep orchestration data for certain statuses. The autopurge feature removes orchestration data that is in terminal statuses. A terminal status means the orchestration has reached a final state and will no longer schedule tasks, process events, or generate work items. Terminal statuses include:
 - `Completed`
 - `Failed`
 - `Canceled`
diff --git a/articles/azure-netapp-files/azure-netapp-files-resource-limits.md b/articles/azure-netapp-files/azure-netapp-files-resource-limits.md
@@ -37,10 +37,9 @@ The following table describes resource limits for the Flexible, Standard, Premiu
 |  Minimum size of a single regular volume    |    50 GiB    |    No    |
 |  Maximum size of a single regular volume     |    100 TiB    |    No    |
 |  Minimum size of a single [large volume](large-volumes-requirements-considerations.md) | 50 TiB | No |
-| Large volume size increase | 30% of lowest provisioned size | Yes |
 |  Maximum size of a single [large volume](large-volumes-requirements-considerations.md) | 1 PiB | Yes** |
 | Maximum size of a single large volume with breakthrough mode (preview) | 2,400 TiB | No |
-| Maximum size of a large volume up to 7.2 PiB** | 7.2 PiB | Yes** |
+| Maximum size of a large volume up to 7.2 PiB*** | 7.2 PiB | Yes** |
 |  Maximum size of a single file     |    16 TiB    |    No    |    
 |  Maximum size of directory metadata in a single directory      |    320 MB    |    No    |    
 |  Maximum number of files in a single directory  | *Approximately* 4 million. <br> See [Determine if a directory is approaching the limit size](directory-sizes-concept.md#directory-limit).  |    No    |   
diff --git a/articles/azure-netapp-files/faq-smb.md b/articles/azure-netapp-files/faq-smb.md
@@ -21,6 +21,25 @@ Azure NetApp Files supports SMB 2.1 and SMB 3.1 (which includes support for SMB
 
 Yes, Windows Server 2025 domain controllers are supported as of September 9, 2025. Windows Server 2025 domain controllers must have all cumulative security updates installed, including [KB5065426](https://support.microsoft.com/en-us/topic/september-9-2025-kb5065426-update-for-windows-server-2025-os-build-26100-6584-6a59dc6a-1ff2-48f4-b375-81e93deee5dd), released on September 9, 2025. You must also enable AES encryption (AES-256) on the Active Directory connection if you plan to introduce any Windows Server 2025 domain controllers into your Active Directory environment. For more information, see [Create and Manage Active Directory connections for Azure NetApp Files](create-active-directory-connections.md).
 
+## What SMB minimum version should be configured on Windows Server 2025 domain controllers for Azure NetApp Files?
+
+For Azure NetApp Files communication with Windows Server 2025 domain controllers, set the SMB minimum dialect to SMB 3.0. If required by your environment, SMB 2.1 can be used. Although Windows Server 2025 supports SMB 3.1.1, enforcing SMB 3.1.1 for this communication can break domain controller communication and prevent authentication to Azure NetApp Files SMB shares.
+
+Run one of the following commands on each Windows Server 2025 domain controller, based on your requirements:
+
+```
+Set-SmbServerConfiguration -Smb2DialectMin SMB211
+```
+
+```
+Set-SmbServerConfiguration -Smb2DialectMin SMB300
+```
+
+>[!NOTE] 
+>This configuration must be applied individually on all Windows Server 2025 domain controllers. It doesn't replicate across the domain.
+
+As an alternative, update the Active Directory site used by Azure NetApp Files so it includes only domain controllers that aren't running Windows Server 2025.
+
 ## Does Azure NetApp Files support access to ‘offline files’ on SMB volumes?
 
 Azure NetApp Files supports 'manual' offline files, allowing users on Windows clients to manually select files to be cached locally.
diff --git a/articles/azure-netapp-files/large-volumes-requirements-considerations.md b/articles/azure-netapp-files/large-volumes-requirements-considerations.md
@@ -12,7 +12,7 @@ ms.author: anfdocs
 ---
 # Requirements and considerations for Azure NetApp Files large volumes
 
-Large volumes are Azure NetApp Files volumes with a size of 50 TiB to 1,024 TiB.
+Azure NetApp Files large volumes support sizes between 50 TiB  and 1,024 TiB.
 
 With breakthrough mode, you can create large volumes at sizes between 2,400 GiB and 2,400 TiB. You must [request the feature](#register-for-breakthrough-mode) before using it for the first time. With cool access enabled, large volumes can scale to 7.2 PiB in certain situations; for more information, see [large volumes up to 7.2 PiB](#requirements-and-considerations-for-large-volumes-up-to-72-pib-preview).
 
@@ -25,7 +25,6 @@ The following requirements and considerations apply to large volumes. For perfor
 * A regular volume can’t be converted to a large volume.
 * You must create a large volume at a size of 50 TiB or larger. The maximum size of a large volume is 1,024 TiB.
 * You can't resize a large volume to less than 50 TiB.
-    * A large volume can't be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits). When requesting the resize, specify the desired size in TiB. 
     * When reducing the size of a large volume, the size depends on the size of files written to the volume and the snapshots currently active on the volumes. 
 * You can't create a large volume with application volume groups.
 * Currently, large volumes aren't suited for database (HANA, Oracle, SQL Server, etc.) data and log volumes. For database workloads requiring more than a single volume’s throughput limit, consider deploying multiple regular volumes. To optimize multiple volume deployments for databases, use [application volume groups](application-volume-group-concept.md).
@@ -39,11 +38,11 @@ The following requirements and considerations apply to large volumes. For perfor
       </tr></thead>
     <tbody>
       <tr>
-        <td>Capacity tier</td>
+        <td>Service level</td>
         <td>Minimum volume size<br>(TiB)</td>
-        <td>Maximum volume size (TiB)*</td>
-        <td>Minimum throughput for capacity tier (MiB/s)</td>
-        <td>Maximum throughput for capacity tier (MiB/s)</td>
+        <td>Maximum volume size (TiB)</td>
+        <td>Base throughput (MiB/s) at 50TiB</td>
+        <td>Maximum throughput for service level (MiB/s)</td>
       </tr>
       <tr>
         <td>Standard (16 MiB/s per TiB)</td>
diff --git a/articles/azure-netapp-files/whats-new.md b/articles/azure-netapp-files/whats-new.md
@@ -17,6 +17,13 @@ ms.author: anfdocs
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
 
+
+## March 2026
+
+* [Large volumes improvement:](large-volumes-requirements-considerations.md#requirements-and-considerations) removed 30% default limit imposed on large volumes
+
+    Large volumes operational improvement no longer requires a support ticket to increase a large volume past the 30% imposed limit. This allows customer to automate their large volume size increases without waiting for approval and human intervention.
+    
 ## January 2026
 
 * [Elastic zone-redundant storage service level](elastic-zone-redundant-concept.md) (preview)
diff --git a/articles/azure-vmware/toc.yml b/articles/azure-vmware/toc.yml
@@ -288,6 +288,8 @@ items:
     href: ecosystem-external-storage-solutions.md
   - name: Configure Azure Elastic SAN
     href: configure-azure-elastic-san.md
+  - name: Performance with Elastic SAN
+    href: ../storage/elastic-san/elastic-san-performance-on-azure-vmware-solutions.md?context=%2fazure%2fazure-vmware%2fcontext%2fcontext
   - name: Configure Azure NetApp Files
     items:
     - name: Attach Azure NetApp Files datastores to Azure VMware Solution hosts
diff --git a/articles/backup/backup-azure-system-state.md b/articles/backup/backup-azure-system-state.md
@@ -2,7 +2,7 @@
 title: Back up Windows system state to Azure using Azure Backup
 description: Learn how to back up Windows Server system state to Azure using Azure Backup.
 ms.topic: how-to
-ms.date: 02/17/2026
+ms.date: 03/09/2026
 author: AbhishekMallick-MS
 ms.author: v-mallicka
 ms.service: azure-backup
@@ -142,6 +142,9 @@ To complete the initial backup, use the Microsoft Azure Recovery Services agent.
 >
 >
 
+[!INCLUDE [end-of-support-notes-windows-server-2008.md](../../includes/end-of-support-notes-windows-server-2008.md)]
+
+
 ### Schedule the backup job
 
 To schedule the backup job, follow these steps:
diff --git a/articles/backup/backup-mabs-protection-matrix.md b/articles/backup/backup-mabs-protection-matrix.md
@@ -1,7 +1,7 @@
 ---
 title: MABS (Azure Backup Server) V4 protection matrix
 description: This article provides a support matrix listing all workloads, data types, and installations that Azure Backup Server v4 protects.
-ms.date: 02/10/2026
+ms.date: 03/09/2026
 ms.topic: reference
 ms.service: azure-backup
 ms.custom: linux-related-content, engagement-fy24
@@ -73,6 +73,9 @@ For on-premises or hosted environments that you can't upgrade or migrate to Azur
 |------------|-----------|---------------|--------------|--------------|
 |Servers (64-bit) | Windows Server 2008 R2 SP1, Windows Server 2008 SP2 (You need to install [Windows Management Framework](https://www.microsoft.com/download/details.aspx?id=54616)), Windows Server 2012, Windows Server 2012 R2. | Physical server <br><br> Hyper-V virtual machine <br><br> VMware virtual machine | Volume, share, folder, file, system state/bare metal |
 
+[!INCLUDE [end-of-support-notes-windows-server-2008.md](../../includes/end-of-support-notes-windows-server-2008.md)]
+
+
 ## Cluster support
 
 Azure Backup Server can protect data in the following clustered applications:
diff --git a/articles/backup/backup-support-matrix-mars-agent.md b/articles/backup/backup-support-matrix-mars-agent.md
@@ -1,7 +1,7 @@
 ---
 title: Support matrix for the MARS agent
 description: This article summarizes Azure Backup support when you back up machines that are running the Microsoft Azure Recovery Services (MARS) agent.
-ms.date: 11/24/2025
+ms.date: 03/09/2026
 ms.topic: reference
 ms.custom: engagement-fy24
 author: AbhishekMallick-MS
@@ -13,6 +13,9 @@ ms.author: v-mallicka
 
 You can use the [Azure Backup service](backup-overview.md) to back up on-premises machines and apps and to back up Azure virtual machines (VMs). This article summarizes support settings and limitations when you use the Microsoft Azure Recovery Services (MARS) agent to back up machines.
 
+[!INCLUDE [end-of-support-notes-windows-server-2008.md](../../includes/end-of-support-notes-windows-server-2008.md)]
+
+
 ## The MARS agent
 
 Azure Backup uses the MARS agent to back up data from on-premises machines and Azure VMs to a backup Recovery Services vault in Azure. The MARS agent can:
diff --git a/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md b/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md
@@ -1,7 +1,7 @@
 ---
 title: MABS (Azure Backup Server) V3 UR1 protection matrix
 description: This article provides a support matrix listing all workloads, data types, and installations that Azure Backup Server protects.
-ms.date: 07/17/2025
+ms.date: 03/09/2026
 ms.topic: reference
 ms.custom: engagement-fy24, linux-related-content
 ms.service: azure-backup
@@ -87,6 +87,9 @@ For on-premises or hosted environments that you can't upgrade or migrate to Azur
 |------------|-----------|---------------|--------------|--------------|
 |Servers (64-bit) | Windows Server 2008 R2 SP1, Windows Server 2008 SP2 (You need to install [Windows Management Framework](https://www.microsoft.com/download/details.aspx?id=54616)) | Physical server <br><br> Hyper-V virtual machine <br><br> VMware virtual machine | Volume, share, folder, file, system state/bare metal |
 
+[!INCLUDE [end-of-support-notes-windows-server-2008.md](../../includes/end-of-support-notes-windows-server-2008.md)]
+
+
 ## Cluster support
 
 Azure Backup Server can protect data in the following clustered applications:
diff --git a/articles/backup/microsoft-azure-backup-server-protection-v3.md b/articles/backup/microsoft-azure-backup-server-protection-v3.md
@@ -1,7 +1,7 @@
 ---
 title: What Azure Backup Server V3 RTM can back up
 description: This article provides a protection matrix listing all workloads, data types, and installations that Azure Backup Serve V3 RTM protects.
-ms.date: 07/14/2025
+ms.date: 03/09/2026
 ms.topic: reference
 ms.service: azure-backup
 author: AbhishekMallick-MS
@@ -11,6 +11,9 @@ ms.author: v-mallicka
 
 # Azure Backup Server V3 RTM protection matrix
 
+[!INCLUDE [end-of-support-notes-windows-server-2008.md](../../includes/end-of-support-notes-windows-server-2008.md)]
+
+
 The following matrix lists what can be protected with Azure Backup Server V3 RTM and earlier versions.
 
 ## Protection support matrix
diff --git a/articles/cost-management-billing/manage/account-admin-tasks.md b/articles/cost-management-billing/manage/account-admin-tasks.md
@@ -2,12 +2,12 @@
 title: Payment method tasks in the Azure portal
 description: Describes how to perform payment method operations in the Azure portal
 author: kennyday
-ms.reviewer: drjones
+ms.reviewer: souchak
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
 ms.date: 09/29/2025
-ms.author: drjones
+ms.author: souchak
 ms.custom: sfi-image-nochange
 service.tree.id: 3b35c9b8-bf14-4e4a-bc0d-21055e56b28c
 ---
diff --git a/articles/cost-management-billing/manage/create-subscription.md b/articles/cost-management-billing/manage/create-subscription.md
@@ -22,10 +22,13 @@ This article helps you create a [Microsoft Customer Agreement](https://azure.mic
 
 If you want to create a Microsoft Customer Agreement subscription in a different Microsoft Entra tenant, see [Create an MCA subscription request](create-subscription-request.md). 
 
-If you want to create subscriptions for Enterprise Agreements, see [Create an EA subscription](create-enterprise-subscription.md). If you're a Microsoft Partner and you want to create a subscription for a customer, see [Create a subscription for a partner's customer](create-customer-subscription.md). Or, if you have a Microsoft Online Service Program (MOSP) billing account, also called pay-as-you-go, you can create subscriptions starting in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Billing/SubscriptionsBlade) and then you complete the process at https://signup.azure.com/.
+If you want to create subscriptions for Enterprise Agreements, see [Create an EA subscription](create-enterprise-subscription.md). If you're a Microsoft Partner and you want to create a subscription for a customer, see [Create a subscription for a partner's customer](create-customer-subscription.md).
 
 [!INCLUDE [cost-management-billing-subscription-b2b-b2c-note](../../../includes/cost-management-billing-subscription-b2b-b2c-note.md)]
 
+>[!NOTE]
+> Microsoft Online Services Program (MOSP) billing account is no longer able to add Azure subscriptions at https://signup.azure.com/.
+
 To learn more about billing accounts and identify your billing account type, see [View billing accounts in Azure portal](view-all-accounts.md).
 
 ## Permission required to create Azure subscriptions
diff --git a/articles/cost-management-billing/understand/pay-bill.md b/articles/cost-management-billing/understand/pay-bill.md
@@ -3,8 +3,8 @@ title: Pay your Microsoft Customer Agreement or Microsoft Online Subscription Pr
 description: Learn how to pay your bill in the Azure portal. You must be a billing profile owner, contributor, or invoice manager to pay in the portal.
 keywords: billing, past due, balance, pay now,
 author: kennyday
-ms.author: drjones
-ms.reviewer: drjones
+ms.author: souchak
+ms.reviewer: souchak
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
diff --git a/articles/iot-operations/develop-edge-apps/overview-iot-operations-development.md b/articles/iot-operations/develop-edge-apps/overview-iot-operations-development.md
diff --git a/articles/iot-operations/develop-edge-apps/quickstart-get-started-sdks.md b/articles/iot-operations/develop-edge-apps/quickstart-get-started-sdks.md
diff --git a/articles/migrate/insights-overview.md b/articles/migrate/insights-overview.md
diff --git a/articles/nat-gateway/manage-nat-gateway-v2.md b/articles/nat-gateway/manage-nat-gateway-v2.md
diff --git a/articles/sentinel/connect-aws-configure-environment.md b/articles/sentinel/connect-aws-configure-environment.md
diff --git a/articles/storage/blobs/network-file-system-protocol-support.md b/articles/storage/blobs/network-file-system-protocol-support.md
diff --git a/includes/end-of-support-notes-windows-server-2008.md b/includes/end-of-support-notes-windows-server-2008.md
