Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-ta1

Author: halkazwini

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 08/09/2024
+ms.date: 12/31/2024
 ms.author: anfdocs
 ---
 # Resource limits for Azure NetApp Files
@@ -31,7 +31,7 @@ The following table describes resource limits for Azure NetApp Files:
 |  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,024 TiB |    No    |
+|  Maximum size of a single [large volume](large-volumes-requirements-considerations.md)    | 1,024 TiB |    Yes**    |
 | Maximum size of a single large volume on dedicated capacity (preview) | 2,048 TiB | No |
 |  Maximum size of a single file     |    16 TiB    |    No    |    
 |  Maximum size of directory metadata in a single directory      |    320 MB    |    No    |    
@@ -52,6 +52,10 @@ The following table describes resource limits for Azure NetApp Files:
 
 \* [!INCLUDE [Limitations for capacity pool minimum of 1 TiB](includes/2-tib-capacity-pool.md)]
 
+
+
+\** 2-PiB [large volume](large-volumes-requirements-considerations.md) large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team. 
+
 For more information, see [Capacity management FAQs](faq-capacity-management.md).
 
 For limits and constraints related to Azure NetApp Files network features, see [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md#considerations).

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: references_regions
 ms.topic: conceptual
-ms.date: 10/07/2024
+ms.date: 12/31/2024
 ms.author: anfdocs
 ---
 # Requirements and considerations for large volumes
@@ -18,7 +18,7 @@ This article describes the requirements and considerations you need to be aware
 The following requirements and considerations apply to large volumes. For performance considerations of *regular volumes*, see [Performance considerations for Azure NetApp Files](azure-netapp-files-performance-considerations.md).
 
 * 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. A single volume can't exceed 1 PiB.  
+* 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, though 2-PiB large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team. 
 * You can't resize a large volume to less than 50 TiB.
     A large volume cannot 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).
 * Large volumes are currently not supported with Azure NetApp Files backup.

articles/backup/azure-file-share-support-matrix.md

@@ -2,7 +2,7 @@
 title: Support Matrix for Azure file share backup by using Azure Backup
 description: Provides a summary of support settings and limitations when backing up Azure file shares.
 ms.topic: reference
-ms.date: 11/27/2024
+ms.date: 12/31/2024
 ms.custom: references_regions, engagement-fy24
 ms.service: azure-backup
 author: AbhishekMallick-MS
@@ -99,13 +99,19 @@ Cross Subscription Backup (CSB) for Azure File share (preview) is currently avai
 
 ## Backup limits
 
+| Setting                                                      | Limit |
+| --- | --- |
+| Maximum number of discoveries of containers that can be backed up to Recovery Services Vault per day  | 50 |
+| Maximum number of inquiries for protectable items under the given container per day | 25 |
+| Maximum number of Configure backup per day | 200 |
+| Maximum number of on-demand backups per day | 10 |
+
 **Choose a backup tier**:
 
 # [Snapshot tier](#tab/snapshot-tier)
 
 | Setting                                      | Limit |
 | -------------------------------------------- | ----- |
-| Maximum  number of on-demand backups per day | 10   |
 | Maximum  number of scheduled backups per day | 6    |
 
 # [Vault-standard tier (preview)](#tab/vault-tier)
@@ -115,17 +121,23 @@ Cross Subscription Backup (CSB) for Azure File share (preview) is currently avai
 | Maximum size of file share              | 8 TB      |
 | Maximum number of files in a file share | 8 million |
 
+>[!Note]
+>If you have multiple backups scheduled per day, only the last scheduled backup of the day is transferred to the vault.
+
 ---
 
 ## Restore limits
 
+| Setting | Limit |
+| --- | --- |
+| Maximum number of restore per day                           | 20      |
+
 **Choose a backup tier**:
 
 # [Snapshot tier](#tab/snapshot-tier)
 
 | Setting                                                      | Limit   |
 | ------------------------------------------------------------ | ------- |
-| Maximum number of restore per day                           | 20      |
 | Maximum size of a file (if the destination account is in a Vnet) | 1TB |
 | Maximum  number of individual files or folders per restore, if ILR (Item level recovery)                         | 99      |
 | Maximum  recommended restore size per restore for large file shares | 15  TiB |

articles/backup/backup-azure-files.md

@@ -2,7 +2,7 @@
 title: Back up Azure File shares in the Azure portal
 description: Learn how to use the Azure portal to back up Azure File shares in the Recovery Services vault
 ms.topic: how-to
-ms.date: 12/20/2024
+ms.date: 12/31/2024
 ms.service: azure-backup
 ms.custom: engagement-fy23
 author: AbhishekMallick-MS
@@ -232,7 +232,7 @@ To run an on-demand backup, follow these steps:
 
 * Don't delete snapshots created by Azure Backup. Deleting snapshots can result in loss of recovery points and/or restore failures.
 
-* Don't remove the lock taken on the storage account by Azure Backup. Deletion of the lock can make your storage account prone to accidental deletion.
+* Don't remove the lock taken on the storage account by Azure Backup. Deletion of the lock can make your storage account prone to accidental deletion. Learn more [about protect your resources with lock](/azure/azure-resource-manager/management/lock-resources).
 
 ## Next steps
 

articles/backup/backup-azure-integrate-microsoft-defender-using-logic-apps.md

@@ -3,7 +3,7 @@ title: Integrate Microsoft Defender's ransomware alerts to preserve Azure Backup
 description: Learn how to integrate Microsoft Defender for Cloud and Azure Backup using logic app.
 ms.topic: how-to
 ms.custom: references_regions
-ms.date: 12/30/2022
+ms.date: 03/13/2024
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-abhmallick

articles/backup/backup-azure-reserved-pricing-optimize-cost.md

@@ -3,7 +3,7 @@ title: Optimize costs for Azure Backup Storage with reserved capacity
 description: This article explains about how to optimize costs for Azure Backup Storage with reserved capacity.
 ms.topic: how-to
 ms.service: azure-backup
-ms.date: 11/01/2023
+ms.date: 04/16/2024
 ms.custom: engagement-fy24
 author: AbhishekMallick-MS
 ms.author: v-abhmallick

articles/backup/protect-backups-from-ransomware-faq.yml

@@ -4,7 +4,7 @@ metadata:
   description: In this article, discover answers to protect backups from ransomware with Azure Backup.
   ms.topic: faq
   ms.service: azure-backup
-  ms.date: 11/30/2024
+  ms.date: 12/04/2024
   author: AbhishekMallick-MS
   ms.author: v-abhmallick
 

articles/backup/scripts/microsoft-azure-recovery-services-powershell-all.md

@@ -3,7 +3,7 @@ title: Script Sample - Configuring Backup for on-premises Windows server
 description: Learn how to use a script to configure Backup for on-premises Windows server.
 ms.topic: sample
 ms.custom: devx-track-azurepowershell
-ms.date: 06/23/2021
+ms.date: 12/03/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---

articles/hdinsight/kafka/kafka-mirrormaker-2-0-guide.md

@@ -42,7 +42,7 @@ The summary of the broker setup process is as follows:
 
 **MirrorCheckpointConnector:**
 
-  1. Consumes offset-syncsr.
+  1. Consumes offset-syncs.
   1. Emits checkpoints to enable failover points.
 
 **MirrorHeartBeatConnector:**

articles/migrate/concepts-assessment-calculation.md

@@ -33,7 +33,7 @@ There are three types of assessments you can create using Azure Migrate: Discove
 **Azure VMware Solution (AVS)** | Assessments to migrate your on-premises servers to [Azure VMware Solution (AVS)](../azure-vmware/introduction.md). You can assess your on-premises [VMware VMs](how-to-set-up-appliance-vmware.md) for migration to Azure VMware Solution (AVS) using this assessment type. [Learn more](concepts-azure-vmware-solution-assessment-calculation.md)
 
 > [!NOTE]
-> If the number of Azure VM or AVS assessments are incorrect on the Discovery and assessment tool, click on the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessments. The Discovery and assessment tool will then show the correct count for that assessment type. 
+> If the number of Azure VM or AVS assessments are incorrect on the Discovery and assessment tool, select the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessments. The Discovery and assessment tool will then show the correct count for that assessment type. 
 
 Assessments you create with Azure Migrate are a point-in-time snapshot of data. An Azure VM assessment provides two sizing criteria options: