Merge pull request #100388 from tamram/tamram-0107

GitHubber17 · web-flow · commit a50459947ad1 · 2020-01-07T20:55:49.000-08:00
update links to scalability targets
diff --git a/articles/storage/blobs/scalability-targets-premium-page-blobs.md b/articles/storage/blobs/scalability-targets-premium-page-blobs.md
@@ -43,3 +43,4 @@ If you cannot migrate to managed disks, then build your application to use multi
 
 - [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-account.md)
 - [Scalability targets for premium block blob storage accounts](../blobs/scalability-targets-premium-block-blobs.md)
+- [Azure subscription limits and quotas](../../azure-resource-manager/management/azure-subscription-service-limits.md)
diff --git a/articles/storage/blobs/scalability-targets.md b/articles/storage/blobs/scalability-targets.md
@@ -26,3 +26,4 @@ ms.subservice: common
 - [Scalability targets for standard storage accounts](../common/scalability-targets-standard-account.md)
 - [Scalability targets for premium block blob storage accounts](scalability-targets-premium-block-blobs.md)
 - [Scalability targets for the Azure Storage resource provider](../common/scalability-targets-resource-provider.md)
+- [Azure subscription limits and quotas](../../azure-resource-manager/management/azure-subscription-service-limits.md)
diff --git a/articles/storage/blobs/storage-blob-storage-tiers.md b/articles/storage/blobs/storage-blob-storage-tiers.md
@@ -123,7 +123,7 @@ The following table shows a comparison of premium performance block blob storage
 <sup>2</sup> Archive Storage currently supports 2 rehydrate priorities, High and Standard, that offers different retrieval latencies. For more information, see [Rehydrate blob data from the archive tier](storage-blob-rehydration.md).
 
 > [!NOTE]
-> Blob storage accounts support the same performance and scalability targets as general-purpose v2 storage accounts. For more information, see [Azure Storage Scalability and Performance Targets](../common/storage-scalability-targets.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).
+> Blob storage accounts support the same performance and scalability targets as general-purpose v2 storage accounts. For more information, see [Scalability and performance targets for Blob storage](scalability-targets.md).
 
 ## Quickstart scenarios
 
@@ -226,7 +226,7 @@ Azure portal, PowerShell, and CLI tools and .NET, Java, Python, and Node.js clie
 
 **How much data can I store in the hot, cool, and archive tiers?**
 
-Data storage along with other limits are set at the account level and not per access tier. You can choose to use all of your limit in one tier or across all three tiers. For more information, see [Azure Storage scalability and performance targets](../common/storage-scalability-targets.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).
+Data storage along with other limits are set at the account level and not per access tier. You can choose to use all of your limit in one tier or across all three tiers. For more information, see [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).
 
 ## Next steps
 
diff --git a/articles/storage/blobs/storage-blobs-introduction.md b/articles/storage/blobs/storage-blobs-introduction.md
@@ -69,5 +69,5 @@ A number of solutions exist for migrating existing data to Blob storage:
 
 ## Next steps
 
-* [Create a storage account](../common/storage-create-storage-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json)
-* [Azure Storage scalability and performance targets](../common/storage-scalability-targets.md)
+- [Create a storage account](../common/storage-create-storage-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json)
+- [Scalability and performance targets for Blob storage](scalability-targets.md)
diff --git a/articles/storage/blobs/storage-blobs-latency.md b/articles/storage/blobs/storage-blobs-latency.md
@@ -63,5 +63,5 @@ To assess latency, first establish baseline metrics for your scenario. Baseline
 
 ## Next steps
 
-- [Azure Storage scalability and performance targets for storage accounts](../common/storage-scalability-targets.md)
-- [Azure Storage performance and scalability checklist](../common/storage-performance-checklist.md)
+- [Scalability and performance targets for Blob storage](scalability-targets.md)
+- [Performance and scalability checklist for Blob storage](storage-performance-checklist.md)
diff --git a/articles/storage/blobs/storage-performance-checklist.md b/articles/storage/blobs/storage-performance-checklist.md
@@ -15,7 +15,7 @@ ms.subservice: blobs
 
 Microsoft has developed a number of proven practices for developing high-performance applications with Blob storage. This checklist identifies key practices that developers can follow to optimize performance. Keep these practices in mind while you are designing your application and throughout the process.
 
-Azure Storage has scalability and performance targets for capacity, transaction rate, and bandwidth. For more information about Azure Storage scalability targets, see [Azure Storage scalability and performance targets for storage accounts](../common/storage-scalability-targets.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).
+Azure Storage has scalability and performance targets for capacity, transaction rate, and bandwidth. For more information about Azure Storage scalability targets, see [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) and [Scalability and performance targets for Blob storage](scalability-targets.md).
 
 ## Checklist
 
@@ -281,5 +281,6 @@ Page blobs are appropriate if the application needs to perform random writes on
 
 ## Next steps
 
-- [Azure Storage scalability and performance targets for storage accounts](../common/storage-scalability-targets.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json)
+- [Scalability and performance targets for Blob storage](scalability-targets.md)
+- [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json)
 - [Status and error codes](/rest/api/storageservices/Status-and-Error-Codes2)
diff --git a/articles/storage/common/scalability-targets-resource-provider.md b/articles/storage/common/scalability-targets-resource-provider.md
@@ -22,4 +22,4 @@ ms.subservice: common
 ## See also
 
 - [Scalability and performance targets for standard storage accounts](scalability-targets-standard-account.md)
-- [Scalability targets for premium block blob storage accounts](../blobs/scalability-targets-premium-block-blobs.md)
+- [Azure subscription limits and quotas](../../azure-resource-manager/management/azure-subscription-service-limits.md)
diff --git a/articles/storage/common/scalability-targets-standard-account.md b/articles/storage/common/scalability-targets-standard-account.md
@@ -22,5 +22,5 @@ ms.subservice: common
 
 ## See also
 
-- [Scalability targets for premium block blob storage accounts](../blobs/scalability-targets-premium-block-blobs.md)
 - [Scalability targets for the Azure Storage resource provider](../common/scalability-targets-resource-provider.md)
+- [Azure subscription limits and quotas](../../azure-resource-manager/management/azure-subscription-service-limits.md)
diff --git a/articles/storage/common/storage-analytics.md b/articles/storage/common/storage-analytics.md
@@ -18,7 +18,7 @@ To use Storage Analytics, you must enable it individually for each service you w
 
 The aggregated data is stored in a well-known blob (for logging) and in well-known tables (for metrics), which may be accessed using the Blob service and Table service APIs.
 
-Storage Analytics has a 20 TB limit on the amount of stored data that is independent of the total limit for your storage account. For more information about storage account limits, see [Azure Storage Scalability and Performance Targets](storage-scalability-targets.md).
+Storage Analytics has a 20 TB limit on the amount of stored data that is independent of the total limit for your storage account. For more information about storage account limits, see [Scalability and performance targets for standard storage accounts](scalability-targets-standard-account.md).
 
 For an in-depth guide on using Storage Analytics and other tools to identify, diagnose, and troubleshoot Azure Storage-related issues, see [Monitor, diagnose, and troubleshoot Microsoft Azure Storage](storage-monitoring-diagnosing-troubleshooting.md).
 
diff --git a/articles/storage/common/storage-migration-to-premium-storage.md b/articles/storage/common/storage-migration-to-premium-storage.md
@@ -60,7 +60,8 @@ There are five types of disks that can be used with your VM and each has specifi
 Depending on your workload, determine if additional data disks are necessary for your VM. You can attach several persistent data disks to your VM. If needed, you can stripe across the disks to increase the capacity and performance of the volume. (See what is Disk Striping [here](../../virtual-machines/windows/premium-storage-performance.md#disk-striping).) If you stripe Premium Storage data disks using [Storage Spaces][4], you should configure it with one column for each disk that is used. Otherwise, the overall performance of the striped volume may be lower than expected due to uneven distribution of traffic across the disks. For Linux VMs you can use the *mdadm* utility to achieve the same. See article [Configure Software RAID on Linux](../../virtual-machines/linux/configure-raid.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json) for details.
 
 #### Storage account scalability targets
-Premium Storage accounts have the following scalability targets in addition to the [Azure Storage Scalability and Performance Targets](storage-scalability-targets.md). If your application requirements exceed the scalability targets of a single storage account, build your application to use multiple storage accounts, and partition your data across those storage accounts.
+
+Premium Storage accounts have the following scalability targets. If your application requirements exceed the scalability targets of a single storage account, build your application to use multiple storage accounts, and partition your data across those storage accounts.
 
 | Total Account Capacity | Total Bandwidth for a Locally Redundant Storage Account |
 |:--- |:--- |
@@ -158,7 +159,8 @@ For data disks, you can choose to keep some data disks in a standard storage acc
 You will need to find your container path and storage account key to process either of these two options. Container path and storage account key can be found in **Azure Portal** > **Storage**. The container URL will be like "https:\//myaccount.blob.core.windows.net/mycontainer/".
 
 ##### Option 1: Copy a VHD with AzCopy (Asynchronous copy)
-Using AzCopy, you can easily upload the VHD over the Internet. Depending on the size of the VHDs, this may take time. Remember to check the storage account ingress/egress limits when using this option. See [Azure Storage Scalability and Performance Targets](storage-scalability-targets.md) for details.
+
+Using AzCopy, you can easily upload the VHD over the Internet. Depending on the size of the VHDs, this may take time. Remember to check the storage account ingress/egress limits when using this option. See [Scalability and performance targets for standard storage accounts](scalability-targets-standard-account.md) for details.
 
 1. Download and install AzCopy from here: [Latest version of AzCopy](https://aka.ms/downloadazcopy)
 2. Open Azure PowerShell and go to the folder where AzCopy is installed.
@@ -255,7 +257,8 @@ Add-AzureVhd [-Destination] <Uri> [-LocalFilePath] <FileInfo>
 An example \<Uri> might be **_"https://storagesample.blob.core.windows.net/mycontainer/blob1.vhd"_**. An example \<FileInfo> might be **_"C:\path\to\upload.vhd"_**.
 
 ##### Option 2: Using AzCopy to upload the .vhd file
-Using AzCopy, you can easily upload the VHD over the Internet. Depending on the size of the VHDs, this may take time. Remember to check the storage account ingress/egress limits when using this option. See [Azure Storage Scalability and Performance Targets](storage-scalability-targets.md) for details.
+
+Using AzCopy, you can easily upload the VHD over the Internet. Depending on the size of the VHDs, this may take time. Remember to check the storage account ingress/egress limits when using this option. See [Scalability and performance targets for standard storage accounts](scalability-targets-standard-account.md) for details.
 
 1. Download and install AzCopy from here: [Latest version of AzCopy](https://aka.ms/downloadazcopy)
 2. Open Azure PowerShell and go to the folder where AzCopy is installed.
diff --git a/articles/storage/common/storage-monitoring-diagnosing-troubleshooting.md b/articles/storage/common/storage-monitoring-diagnosing-troubleshooting.md
@@ -412,7 +412,7 @@ If you are experiencing a delay between the time an application adds a message t
 * Examine the Storage Logging logs for any queue operations that have higher than expected **E2ELatency** and **ServerLatency** values over a longer period of time than usual.
 
 ### <a name="metrics-show-an-increase-in-PercentThrottlingError"></a>Metrics show an increase in PercentThrottlingError
-Throttling errors occur when you exceed the scalability targets of a storage service. The storage service throttles to ensure that no single client or tenant can use the service at the expense of others. For more information, see [Azure Storage Scalability and Performance Targets](storage-scalability-targets.md) for details on scalability targets for storage accounts and performance targets for partitions within storage accounts.
+Throttling errors occur when you exceed the scalability targets of a storage service. The storage service throttles to ensure that no single client or tenant can use the service at the expense of others. For more information, see [Scalability and performance targets for standard storage accounts](scalability-targets-standard-account.md) for details on scalability targets for storage accounts and performance targets for partitions within storage accounts.
 
 If the **PercentThrottlingError** metric show an increase in the percentage of requests that are failing with a throttling error, you need to investigate one of two scenarios:
 
diff --git a/articles/storage/common/storage-redundancy-gzrs.md b/articles/storage/common/storage-redundancy-gzrs.md
@@ -15,7 +15,7 @@ ms.subservice: common
 
 Geo-zone-redundant storage (GZRS) (preview) marries the high availability of [zone-redundant storage (ZRS)](storage-redundancy-zrs.md) with protection from regional outages as provided by [geo-redundant storage (GRS)](storage-redundancy-grs.md). Data in a GZRS storage account is replicated across three [Azure availability zones](../../availability-zones/az-overview.md) in the primary region and also replicated to a secondary geographic region for protection from regional disasters. Each Azure region is paired with another region within the same geography, together making a regional pair. For more details and exceptions refer to the [documentation](https://docs.microsoft.com/azure/best-practices-availability-paired-regions).
 
-With a GZRS storage account, you can continue to read and write data if an availability zone becomes unavailable or is unrecoverable. Additionally, your data is also durable in the case of a complete regional outage or a disaster in which the primary region isn’t recoverable. GZRS is designed to provide at least 99.99999999999999% (16 9's) durability of objects over a given year. GZRS also offers the same [scalability targets](storage-scalability-targets.md) as LRS, ZRS, GRS, or RA-GRS. You can optionally enable read access to data in the secondary region with read-access geo-zone-redundant storage (RA-GZRS) if your applications need to be able to read data in the event of a disaster in the primary region.
+With a GZRS storage account, you can continue to read and write data if an availability zone becomes unavailable or is unrecoverable. Additionally, your data is also durable in the case of a complete regional outage or a disaster in which the primary region isn’t recoverable. GZRS is designed to provide at least 99.99999999999999% (16 9's) durability of objects over a given year. GZRS also offers the same scalability targets as LRS, ZRS, GRS, or RA-GRS. You can optionally enable read access to data in the secondary region with read-access geo-zone-redundant storage (RA-GZRS) if your applications need to be able to read data in the event of a disaster in the primary region.
 
 Microsoft recommends using GZRS for applications requiring consistency, durability, high availability, excellent performance, and resilience for disaster recovery. For the additional security of read access to the secondary region in the event of a regional disaster, enable RA-GZRS for your storage account.
 
@@ -156,3 +156,4 @@ A support representative will contact you to provide assistance.
 - [Azure Storage replication](https://docs.microsoft.com/azure/storage/common/storage-redundancy)
 - [Locally redundant storage (LRS): Low-cost data redundancy for Azure Storage](https://docs.microsoft.com/azure/storage/common/storage-redundancy-lrs)
 - [Zone-redundant storage (ZRS): Highly available Azure Storage applications](https://docs.microsoft.com/azure/storage/common/storage-redundancy-zrs) 
+- [Scalability and performance targets for standard storage accounts](scalability-targets-standard-account.md)
diff --git a/articles/storage/common/storage-redundancy.md b/articles/storage/common/storage-redundancy.md
@@ -48,7 +48,7 @@ All data for all types of storage accounts are replicated, including block blobs
 For pricing information for each redundancy option, see [Azure Storage Pricing](https://azure.microsoft.com/pricing/details/storage/).
 
 > [!NOTE]
-> Azure Premium Disk Storage currently supports only locally redundant storage (LRS). Azure Premium Block Blob Storage supports locally redudant storage (LRS) and zone redudant storage (ZRS) in certain regions.
+> Azure Premium Disk Storage currently supports only locally redundant storage (LRS). Azure Premium Block Blob Storage supports locally redundant storage (LRS) and zone redundant storage (ZRS) in certain regions.
 
 ## Changing replication strategy
 
@@ -72,7 +72,7 @@ If you migrate your storage account from RA-GRS to GRS or LRS, that account is b
 - [Zone-redundant storage (ZRS): Highly available Azure Storage applications](storage-redundancy-zrs.md)
 - [Geo-redundant storage (GRS): Cross-regional replication for Azure Storage](storage-redundancy-grs.md)
 - [Geo-zone-redundant storage (GZRS) for highly availability and maximum durability (preview)](storage-redundancy-gzrs.md)
-- [Azure Storage scalability and performance targets](storage-scalability-targets.md)
+- [Scalability and performance targets for standard storage accounts](scalability-targets-standard-account.md)
 - [Designing highly available applications using RA-GRS Storage](../storage-designing-ha-apps-with-ragrs.md)
 - [Microsoft Azure Storage redundancy options and read access geo redundant storage](https://blogs.msdn.com/b/windowsazurestorage/archive/2013/12/11/introducing-read-access-geo-replicated-storage-ra-grs-for-windows-azure-storage.aspx)
 - [SOSP Paper - Azure Storage: A highly available cloud storage service with strong consistency](https://blogs.msdn.com/b/windowsazurestorage/archive/2011/11/20/windows-azure-storage-a-highly-available-cloud-storage-service-with-strong-consistency.aspx)
diff --git a/articles/storage/files/storage-files-planning.md b/articles/storage/files/storage-files-planning.md
@@ -19,7 +19,7 @@ ms.subservice: files
 
 ![File Structure](./media/storage-files-introduction/files-concepts.png)
 
-* **Storage Account**: All access to Azure Storage is done through a storage account. See [Scalability and Performance Targets](../common/storage-scalability-targets.md?toc=%2fazure%2fstorage%2ffiles%2ftoc.json) for details about storage account capacity.
+* **Storage Account**: All access to Azure Storage is done through a storage account. See [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-account.md?toc=%2fazure%2fstorage%2ffiles%2ftoc.json) for details about storage account capacity.
 
 * **Share**: A File Storage share is an SMB file share in Azure. All directories and files must be created in a parent share. An account can contain an unlimited number of shares and a share can store an unlimited number of files, up to the total capacity of the file share. The total capacity for premium and standard file shares is 100 TiB.
 
diff --git a/articles/storage/files/storage-files-scale-targets.md b/articles/storage/files/storage-files-scale-targets.md
@@ -110,4 +110,3 @@ As a general guide for your deployment, you should keep a few things in mind:
 
 - [Planning for an Azure Files deployment](storage-files-planning.md)
 - [Planning for an Azure File Sync deployment](storage-sync-files-planning.md)
-- [Scalability and performance targets for other storage services](../common/storage-scalability-targets.md)
diff --git a/articles/storage/queues/scalability-targets.md b/articles/storage/queues/scalability-targets.md
@@ -25,3 +25,4 @@ ms.subservice: queues
 - [Performance and scalability checklist for Queue storage](storage-performance-checklist.md)
 - [Scalability targets for standard storage accounts](../common/scalability-targets-standard-account.md)
 - [Scalability targets for the Azure Storage resource provider](../common/scalability-targets-resource-provider.md)
+- [Azure subscription limits and quotas](../../azure-resource-manager/management/azure-subscription-service-limits.md)
diff --git a/articles/storage/queues/storage-performance-checklist.md b/articles/storage/queues/storage-performance-checklist.md
diff --git a/articles/storage/queues/storage-queues-introduction.md b/articles/storage/queues/storage-queues-introduction.md
diff --git a/articles/storage/tables/scalability-targets.md b/articles/storage/tables/scalability-targets.md
diff --git a/articles/storage/tables/storage-performance-checklist.md b/articles/storage/tables/storage-performance-checklist.md

Original file line number	Diff line number	Diff line change
`@@ -43,3 +43,4 @@ If you cannot migrate to managed disks, then build your application to use multi`
`43`	`43`
`44`	`44`	`- [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-account.md)`
`45`	`45`	`- [Scalability targets for premium block blob storage accounts](../blobs/scalability-targets-premium-block-blobs.md)`
	`46`	`+- [Azure subscription limits and quotas](../../azure-resource-manager/management/azure-subscription-service-limits.md)`