Merge pull request #307660 from MicrosoftDocs/main

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

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

articles/databox/data-box-disk-limits.md

@@ -62,7 +62,7 @@ Here are the limits on the size of data that can be copied into a storage accoun
 
 | Type of data             | Default limit          |
 |--------------------------|------------------------|
-| block blob, page blob    | For current information about these limits, see [Azure Blob storage scale targets](../storage/blobs/scalability-targets.md#scale-targets-for-blob-storage), [Azure standard storage scale targets](../storage/common/scalability-targets-standard-account.md#scale-targets-for-standard-storage-accounts), and [Azure Files scale targets](../storage/files/storage-files-scale-targets.md). <br /><br /> The limits include data from all the sources, including Data Box Disk.|
+| block blob, page blob    | For current information about these limits, see [Azure Blob storage scale targets](../storage/blobs/scalability-targets.md#scale-targets-for-blob-storage), [Azure standard storage scale targets](../storage/common/scalability-targets-standard-account.md#scale-targets-for-standard-storage-accounts-and-disk-access-resources), and [Azure Files scale targets](../storage/files/storage-files-scale-targets.md). <br /><br /> The limits include data from all the sources, including Data Box Disk.|
 
 ## Azure object size limits
 

articles/energy-data-services/release-notes.md

@@ -104,7 +104,7 @@ Effective June 1, 2024, the monthly base instance fee of the Developer tier of A
 ## April 2024
 
 ### Azure Data Manager for Energy in Qatar Central Region
-Azure Data Manager for Energy is now available in the Qatar Central Region. This new region is enabled for both the Standard and Developer tiers of Azure Data Manager for Energy, and is available for select customers and partners only. Please reach out to your designated Microsoft account team member to unlock access. Once access is provided, you can select "Qatar" as your preferred region when creating Azure Data Manager for Energy resource, using the [Azure portal](https://ms.portal.azure.com/#create/Microsoft.AzureDataManagerforEnergy) or your preferred provisioning method. Qatar Central region supports zone-redundant storage (ZRS) with 3 availability zones for disaster recovery. Data is stored at rest in Qatar in compliance with data residency requirements. For more details on zonal replication, please review the [documentation](../site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md) page. Note that the default maximum ingress per general purpose v2 and Blob storage accounts in Qatar Central is 25 Gbps. For more details, please review scalability and performance [targets](../storage/common/scalability-targets-standard-account.md#scale-targets-for-standard-storage-accounts).
+Azure Data Manager for Energy is now available in the Qatar Central Region. This new region is enabled for both the Standard and Developer tiers of Azure Data Manager for Energy, and is available for select customers and partners only. Please reach out to your designated Microsoft account team member to unlock access. Once access is provided, you can select "Qatar" as your preferred region when creating Azure Data Manager for Energy resource, using the [Azure portal](https://ms.portal.azure.com/#create/Microsoft.AzureDataManagerforEnergy) or your preferred provisioning method. Qatar Central region supports zone-redundant storage (ZRS) with 3 availability zones for disaster recovery. Data is stored at rest in Qatar in compliance with data residency requirements. For more details on zonal replication, please review the [documentation](../site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md) page. Note that the default maximum ingress per general purpose v2 and Blob storage accounts in Qatar Central is 25 Gbps. For more details, please review scalability and performance [targets](../storage/common/scalability-targets-standard-account.md#scale-targets-for-standard-storage-accounts-and-disk-access-resources).
 
 ## March 2024
 

articles/sentinel/datalake/sentinel-lake-onboarding.md

@@ -96,7 +96,7 @@ To onboard to the Microsoft Sentinel data lake and graph (preview) in Microsoft
 
 To configure billing and enable asset data ingestion into the data lake, the following roles must be assigned to the tenant [member](/entra/fundamentals/users-default-permissions) account:
 
-+ Azure Subscription owner for billing setup
++ Azure Subscription owner or Subscription contributor for billing setup
 + Microsoft Entra Global Administrator, or Security Administrator for data ingestion authorization from Microsoft Entra, Microsoft 365, and Azure
 + Read access to all workspaces to enable their attachment to the data lake
 

articles/storage/common/scalability-targets-standard-account.md

@@ -7,7 +7,7 @@ author: akashdubey-ms
 
 ms.service: azure-storage
 ms.topic: concept-article
-ms.date: 05/25/2022
+ms.date: 10/31/2025
 ms.author: akashdubey
 ms.subservice: storage-common-concepts
 # Customer intent: "As a cloud architect, I want to understand the scalability and performance targets for standard storage accounts, so that I can ensure that our storage solutions meet our application demands."
@@ -19,7 +19,7 @@ ms.subservice: storage-common-concepts
 
 The service-level agreement (SLA) for Azure Storage accounts is available at [SLA for Storage Accounts](https://azure.microsoft.com/support/legal/sla/storage/v1_5/).
 
-## Scale targets for standard storage accounts
+## Scale targets for standard storage accounts and disk access resources
 
 [!INCLUDE [azure-storage-account-limits-standard](../../../includes/azure-storage-account-limits-standard.md)]
 

includes/azure-data-lake-store-limits.md

@@ -13,7 +13,7 @@
 **Azure Data Lake Storage Gen2** is not a dedicated service or storage account type. It is the latest release of capabilities that are dedicated to big data analytics.  These capabilities are available in a general-purpose v2 or BlockBlobStorage storage account, and you can obtain them by enabling the **Hierarchical namespace** feature of the account. For scale targets, see these articles. 
 
 - [Scale targets for Blob storage](../articles/storage/blobs/scalability-targets.md#scale-targets-for-blob-storage).
-- [Scale targets for standard storage accounts](../articles/storage/common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json#scale-targets-for-standard-storage-accounts).
+- [Scale targets for standard storage accounts](../articles/storage/common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json#scale-targets-for-standard-storage-accounts-and-disk-access-resources).
 
 **Azure Data Lake Storage Gen1** is a dedicated service. It's an enterprise-wide hyper-scale repository for big data analytic workloads. You can use Data Lake Storage Gen1 to capture data of any size, type, and ingestion speed in one single place for operational and exploratory analytics. There's no limit to the amount of data you can store in a Data Lake Storage Gen1 account.
 

includes/azure-stack-edge-gateway-storage-acct-limits.md

@@ -6,7 +6,7 @@ ms.date: 01/30/2019
 ms.author: alkohli
 ---
 
-Here are the limits on the size of the data that is copied into storage account. Make sure that the data you upload conforms to these limits. For the most up-to-date information on these limits, go to [Azure blob storage scale targets](../articles/storage/common/scalability-targets-standard-account.md#scale-targets-for-standard-storage-accounts) and [Azure Files scale targets](../articles/storage/common/scalability-targets-standard-account.md#scale-targets-for-standard-storage-accounts).
+Here are the limits on the size of the data that is copied into storage account. Make sure that the data you upload conforms to these limits. For the most up-to-date information on these limits, go to [Azure blob storage scale targets](../articles/storage/common/scalability-targets-standard-account.md#scale-targets-for-standard-storage-accounts-and-disk-access-resources) and [Azure Files scale targets](../articles/storage/common/scalability-targets-standard-account.md#scale-targets-for-standard-storage-accounts-and-disk-access-resources).
 
 | Size of data copied into Azure storage account                      | Default Limit          |
 |---------------------------------------------------------------------|------------------------|

includes/azure-storage-account-limits-standard.md

@@ -5,12 +5,12 @@ title: include file
  author: tamram
  ms.service: azure-storage
  ms.topic: include
- ms.date: 04/24/2024
+ ms.date: 10/31/2025
  ms.author: tamram
  ms.custom: include file, references_regions
 ---
 
-The following table describes default limits for Azure general-purpose v2 (GPv2), general-purpose v1 (GPv1), and Blob storage accounts. The *ingress* limit refers to all data that is sent to a storage account. The *egress* limit refers to all data that is received from a storage account.
+The following table describes default limits for Azure general-purpose v2 (GPv2), general-purpose v1 (GPv1), and Blob storage accounts. A few entries in the table also apply to disk access resources, these are explicitly labeled. The *ingress* limit refers to all data that is sent to a storage account. The *egress* limit refers to all data that is received from a storage account.
 
 Microsoft recommends that you use a GPv2 storage account for most scenarios. You can easily upgrade a GPv1 or a Blob storage account to a GPv2 account with no downtime and without the need to copy data. For more information, see [Upgrade to a GPv2 storage account](/azure/storage/common/storage-account-upgrade).
 
@@ -23,13 +23,13 @@ Microsoft recommends that you use a GPv2 storage account for most scenarios. You
 | Maximum number of storage accounts with Azure DNS zone endpoints (preview) per region per subscription, including standard and premium storage accounts. | 5000 (preview) |
 | Default maximum storage account capacity | 5 PiB <sup>2</sup> |
 | Maximum number of blob containers, blobs, directories and subdirectories (if Hierarchical Namespace is enabled), file shares, tables, queues, entities, or messages per storage account. | No limit |
-| Default maximum request rate per general-purpose v2 and Blob storage account in the following regions:<br /><ul><li>East Asia</li><li>Southeast Asia</li><li>Australia East</li><li>Brazil South</li><li>Canada Central</li><li>China East 2</li><li>China North 3</li><li>North Europe</li><li>West Europe</li><li>France Central</li><li>Germany West Central</li><li>Central India</li><li>Japan East</li><li>Jio India West</li><li>Korea Central</li><li>Norway East</li><li>South Africa North</li><li>Sweden Central</li><li>UAE North</li><li>UK South</li><li>Central US</li><li>East US</li><li>East US 2</li><li>USGov Virginia</li><li>USGov Arizona</li><li>North Central US</li><li>South Central US</li><li>West US</li><li>West US 2</li><li>West US 3</li></ul>| 40,000 requests per second<sup>2</sup> |
-| Default maximum request rate per general-purpose v2 and Blob storage account in regions that aren't listed in the previous row. | 20,000 requests per second<sup>2</sup> |
-| Default maximum ingress per general-purpose v2 and Blob storage account in the following regions:<br /><ul><li>East Asia</li><li>Southeast Asia</li><li>Australia East</li><li>Brazil South</li><li>Canada Central</li><li>China East 2</li><li>China North 3</li><li>North Europe</li><li>West Europe</li><li>France Central</li><li>Germany West Central</li><li>Central India</li><li>Japan East</li><li>Jio India West</li><li>Korea Central</li><li>Norway East</li><li>South Africa North</li><li>Sweden Central</li><li>UAE North</li><li>UK South</li><li>Central US</li><li>East US</li><li>East US 2</li><li>USGov Virginia</li><li>USGov Arizona</li><li>North Central US</li><li>South Central US</li><li>West US</li><li>West US 2</li><li>West US 3</li></ul>| 60 Gbps<sup>2</sup> |
-| Default maximum ingress per general-purpose v2 and Blob storage account in regions that aren't listed in the previous row. | 25 Gbps<sup>2</sup> |
+| Default maximum request rate per general-purpose v2, Blob storage account, and disk access resources in the following regions:<br /><ul><li>East Asia</li><li>Southeast Asia</li><li>Australia East</li><li>Brazil South</li><li>Canada Central</li><li>China East 2</li><li>China North 3</li><li>North Europe</li><li>West Europe</li><li>France Central</li><li>Germany West Central</li><li>Central India</li><li>Japan East</li><li>Jio India West</li><li>Korea Central</li><li>Norway East</li><li>South Africa North</li><li>Sweden Central</li><li>UAE North</li><li>UK South</li><li>Central US</li><li>East US</li><li>East US 2</li><li>USGov Virginia</li><li>USGov Arizona</li><li>North Central US</li><li>South Central US</li><li>West US</li><li>West US 2</li><li>West US 3</li></ul>| 40,000 requests per second<sup>2</sup> |
+| Default maximum request rate per general-purpose v2, Blob storage account, and disk access resources in regions that aren't listed in the previous row. | 20,000 requests per second<sup>2</sup> |
+| Default maximum ingress per general-purpose v2, Blob storage account, and disk access resources in the following regions:<br /><ul><li>East Asia</li><li>Southeast Asia</li><li>Australia East</li><li>Brazil South</li><li>Canada Central</li><li>China East 2</li><li>China North 3</li><li>North Europe</li><li>West Europe</li><li>France Central</li><li>Germany West Central</li><li>Central India</li><li>Japan East</li><li>Jio India West</li><li>Korea Central</li><li>Norway East</li><li>South Africa North</li><li>Sweden Central</li><li>UAE North</li><li>UK South</li><li>Central US</li><li>East US</li><li>East US 2</li><li>USGov Virginia</li><li>USGov Arizona</li><li>North Central US</li><li>South Central US</li><li>West US</li><li>West US 2</li><li>West US 3</li></ul>| 60 Gbps<sup>2</sup> |
+| Default maximum ingress per general-purpose v2, Blob storage account, and disk access resources in regions that aren't listed in the previous row. | 25 Gbps<sup>2</sup> |
 | Default maximum ingress for general-purpose v1 storage accounts (all regions) | 10 Gbps<sup>2</sup> |
-| Default maximum egress for general-purpose v2 and Blob storage accounts in the following regions:<br /><ul><li>East Asia</li><li>Southeast Asia</li><li>Australia East</li><li>Brazil South</li><li>Canada Central</li><li>China East 2</li><li>China North 3</li><li>North Europe</li><li>West Europe</li><li>France Central</li><li>Germany West Central</li><li>Central India</li><li>Japan East</li><li>Jio India West</li><li>Korea Central</li><li>Norway East</li><li>South Africa North</li><li>Sweden Central</li><li>UAE North</li><li>UK South</li><li>Central US</li><li>East US</li><li>East US 2</li><li>USGov Virginia</li><li>USGov Arizona</li><li>North Central US</li><li>South Central US</li><li>West US</li><li>West US 2</li><li>West US 3</li></ul> | 200 Gbps<sup>2</sup> |
-| Default maximum egress for general-purpose v2 and Blob storage accounts in regions that aren't listed in the previous row. | 50 Gbps<sup>2</sup> |
+| Default maximum egress for general-purpose v2, Blob storage accounts, and disk access resources in the following regions:<br /><ul><li>East Asia</li><li>Southeast Asia</li><li>Australia East</li><li>Brazil South</li><li>Canada Central</li><li>China East 2</li><li>China North 3</li><li>North Europe</li><li>West Europe</li><li>France Central</li><li>Germany West Central</li><li>Central India</li><li>Japan East</li><li>Jio India West</li><li>Korea Central</li><li>Norway East</li><li>South Africa North</li><li>Sweden Central</li><li>UAE North</li><li>UK South</li><li>Central US</li><li>East US</li><li>East US 2</li><li>USGov Virginia</li><li>USGov Arizona</li><li>North Central US</li><li>South Central US</li><li>West US</li><li>West US 2</li><li>West US 3</li></ul> | 200 Gbps<sup>2</sup> |
+| Default maximum egress for general-purpose v2, Blob storage accounts, and disk access resources in regions that aren't listed in the previous row. | 50 Gbps<sup>2</sup> |
 | Maximum egress for general-purpose v1 storage accounts (US regions) | 20 Gbps if RA-GRS/GRS is enabled, 30 Gbps for LRS/ZRS |
 | Maximum egress for general-purpose v1 storage accounts (non-US regions) | 10 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS/ZRS |
 | Maximum number of IP address rules per storage account | 400 |