Merge pull request #109433 from yuemlu/master

ShannonLeavitt · web-flow · commit 55602ed2d141 · 2020-03-29T14:24:13.000+04:00
Update for Disk GA
diff --git a/articles/virtual-machines/linux/disk-bursting.md b/articles/virtual-machines/linux/disk-bursting.md
@@ -3,16 +3,16 @@ title: Managed disk bursting
 description: Learn about disk bursting and how it works for Azure premium SSDs.
 author: roygara
 ms.author: rogarana
-ms.date: 10/22/2019
+ms.date: 03/28/2019
 ms.topic: conceptual
 ms.service: virtual-machines
 ms.subservice: disks
 ---
 
-# Premium SSD bursting (preview)
+# Premium SSD bursting
 
 [!INCLUDE [managed-disks-bursting](../../../includes/managed-disks-bursting.md)]
 
 ## Next steps
 
-[Use the portal to attach a data disk to a Linux VM](attach-disk-portal.md)
+[Use the portal to attach a data disk to a Linux VM](attach-disk-portal.md)
diff --git a/articles/virtual-machines/windows/disk-bursting.md b/articles/virtual-machines/windows/disk-bursting.md
@@ -3,16 +3,16 @@ title: Managed disk bursting
 description: Learn about disk bursting and how it works for Azure premium SSDs.
 author: roygara
 ms.author: rogarana
-ms.date: 10/22/2019
+ms.date: 03/28/2019
 ms.topic: conceptual
 ms.service: virtual-machines-windows
 ms.subservice: disks
 ---
 
-# Premium SSD bursting (preview)
+# Premium SSD bursting
 
 [!INCLUDE [managed-disks-bursting](../../../includes/managed-disks-bursting.md)]
 
 ## Next steps
 
-[Attach a managed data disk to a Windows VM by using the Azure portal](attach-managed-disk-portal.md)
+[Attach a managed data disk to a Windows VM by using the Azure portal](attach-managed-disk-portal.md)
diff --git a/includes/disk-storage-premium-ssd-sizes.md b/includes/disk-storage-premium-ssd-sizes.md
@@ -5,20 +5,17 @@
  author: roygara
  ms.service: virtual-machines
  ms.topic: include
- ms.date: 01/07/2020
+ ms.date: 03/28/2020
  ms.author: rogarana
  ms.custom: include file
 ---
 
-| Premium SSD sizes | P1* | P2* | P3* | P4 | P6 | P10 | P15 | P20 | P30 | P40 | P50 | P60 | P70 | P80 |
+| Premium SSD sizes | P1 | P2 | P3 | P4 | P6 | P10 | P15 | P20 | P30 | P40 | P50 | P60 | P70 | P80 |
 |-------------------|----|----|----|----|----|-----|-----|-----|-----|-----|-----|------|------|------|
 | Disk size in GiB | 4 | 8 | 16 | 32 | 64 | 128 | 256 | 512 | 1,024 | 2,048 | 4,096 | 8,192 | 16,384 | 32,767 |
-| IOPS per disk | 120 | 120 | 120 | 120 | 240 | 500 | 1,100 | 2,300 | 5,000 | 7,500 | 7,500 | 16,000 | 18,000 | 20,000 |
-| Throughput per disk | 25 MiB/sec | 25 MiB/sec | 25 MiB/sec | 25 MiB/sec | 50 MiB/sec | 100 MiB/sec | 125 MiB/sec | 150 MiB/sec | 200 MiB/sec | 250 MiB/sec | 250 MiB/sec| 500 MiB/sec | 750 MiB/sec | 900 MiB/sec |
-| Max burst IOPS per disk** | 3,500 | 3,500 | 3,500 | 3,500 | 3,500 | 3,500 | 3,500 | 3,500 |
-| Max burst throughput per disk** | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec |
-| Max burst duration** | 30 min  | 30 min  | 30 min  | 30 min  | 30 min  | 30 min  | 30 min  | 30 min  |
+| Provisioned IOPS per disk | 120 | 120 | 120 | 120 | 240 | 500 | 1,100 | 2,300 | 5,000 | 7,500 | 7,500 | 16,000 | 18,000 | 20,000 |
+| Provisioned Throughput per disk | 25 MiB/sec | 25 MiB/sec | 25 MiB/sec | 25 MiB/sec | 50 MiB/sec | 100 MiB/sec | 125 MiB/sec | 150 MiB/sec | 200 MiB/sec | 250 MiB/sec | 250 MiB/sec| 500 MiB/sec | 750 MiB/sec | 900 MiB/sec |
+| Max burst IOPS per disk | 3,500 | 3,500 | 3,500 | 3,500 | 3,500 | 3,500 | 3,500 | 3,500 |
+| Max burst throughput per disk | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec | 170 MiB/sec |
+| Max burst duration | 30 min  | 30 min  | 30 min  | 30 min  | 30 min  | 30 min  | 30 min  | 30 min  |
 | Eligible for reservation | No  | No  | No  | No  | No  | No  | No  | No  | Yes, up to one year | Yes, up to one year | Yes, up to one year | Yes, up to one year | Yes, up to one year | Yes, up to one year |
-
-\*Denotes a disk size that is currently in preview, for regional availability information see [New disk sizes: Managed and unmanaged](https://docs.microsoft.com/azure/virtual-machines/linux/faq-for-disks#new-disk-sizes-managed-and-unmanaged).  
-\*\*Denotes a feature that is currently in preview, see [Disk bursting](https://docs.microsoft.com/azure/virtual-machines/linux/disk-bursting#regional-availability) for more information.
diff --git a/includes/disk-storage-standard-ssd-sizes.md b/includes/disk-storage-standard-ssd-sizes.md
@@ -5,15 +5,13 @@
  author: roygara
  ms.service: virtual-machines
  ms.topic: include
- ms.date: 11/06/2019
+ ms.date: 03/28/2019
  ms.author: rogarana
  ms.custom: include file
 ---
 
-| Standard SSD sizes | E1* | E2* | E3* | E4 | E6 | E10 | E15 | E20 | E30 | E40 | E50 | E60 | E70 | E80 |
+| Standard SSD sizes | E1 | E2 | E3 | E4 | E6 | E10 | E15 | E20 | E30 | E40 | E50 | E60 | E70 | E80 |
 |--------------------|----|----|----|----|----|-----|-----|-----|-----|-----|-----|------|------|------|
 | Disk size in GiB | 4 | 8 | 16 | 32 | 64 | 128 | 256 | 512 | 1,024 | 2,048 | 4,096 | 8,192 | 16,384 | 32,767 |
-| IOPS per disk | Up to 120 | Up to 120 | Up to 120 | Up to 120 | Up to 240 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 2,000 | Up to 4,000 | Up to 6,000 |
+| IOPS per disk | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 500 | Up to 2,000 | Up to 4,000 | Up to 6,000 |
 | Throughput per disk |  Up to 25 MiB/sec | Up to 25 MiB/sec | Up to 25 MiB/sec | Up to 25 MiB/sec |  Up to 50 MiB/sec  |  Up to 60 MiB/sec | Up to 60 MiB/sec | Up to 60 MiB/sec | Up to 60 MiB/sec | Up to 60 MiB/sec | Up to 60 MiB/sec| Up to 400 MiB/sec |  Up to 600 MiB/sec | Up to 750 MiB/sec |
-
-\*Denotes a disk size that is currently in preview, for regional availability information see [New disk sizes: Managed and unmanaged](https://docs.microsoft.com/azure/virtual-machines/linux/faq-for-disks#new-disk-sizes-managed-and-unmanaged).
diff --git a/includes/managed-disks-bursting.md b/includes/managed-disks-bursting.md
@@ -5,12 +5,12 @@
  author: roygara
  ms.service: virtual-machines
  ms.topic: include
- ms.date: 02/28/2020
+ ms.date: 03/29/2020
  ms.author: rogarana
  ms.custom: include file
 ---
 
-Disk bursting is currently a preview feature for premium SSDs. Bursting is supported on any premium SSD disk sizes <= 512 GiB (P20 or below). These disk sizes support bursting on a best effort basis and utilize a credit system to manage bursting. Credits accumulate in a burst bucket whenever disk traffic is below the provisioned performance target for their disk size, and consume credits when traffic bursts beyond the target. Disk traffic is tracked against both IOPS and bandwidth in the provisioned target. Disk bursting will not bypass virtual machine (VM) size limitations on IOPS or throughput.
+Disk bursting is supported for premium SSDs. Bursting is supported on any premium SSD disk sizes <= 512 GiB (P20 or below). These disk sizes support bursting on a best effort basis and utilize a credit system to manage bursting. Credits accumulate in a burst bucket whenever disk traffic is below the provisioned performance target for their disk size, and consume credits when traffic bursts beyond the target. Disk traffic is tracked against both IOPS and bandwidth in the provisioned target. Disk bursting will not bypass virtual machine (VM) size limitations on IOPS or throughput.
 
 Disk bursting is enabled by default on new deployments of the disk sizes that support it. Existing disk sizes, if they support disk bursting, can enable bursting through either of the following methods:
 
@@ -31,7 +31,7 @@ The disk sizes that provide bursting support along with the burst specifications
 
 ## Regional availability
 
-Currently, disk bursting is only available in the West Central US region.
+Disk bursting is available in all regions in Public Cloud.
 
 ## Disk sizes
 
diff --git a/includes/virtual-machines-managed-disks-types-ga.md b/includes/virtual-machines-managed-disks-types-ga.md
@@ -5,7 +5,7 @@ services: virtual-machines
 author: roygara
 ms.service: virtual-machines
 ms.topic: include
-ms.date: 02/28/2020
+ms.date: 03/28/2020
 ms.author: rogarana
 ms.custom: include file
 ---
@@ -21,11 +21,11 @@ To learn more about individual VM types and sizes in Azure for Windows, includin
 
 When you provision a premium storage disk, unlike standard storage, you are guaranteed the capacity, IOPS, and throughput of that disk. For example, if you create a P50 disk, Azure provisions 4,095-GB storage capacity, 7,500 IOPS, and 250-MB/s throughput for that disk. Your application can use all or part of the capacity and performance. Premium SSD disks are designed to provide low single-digit millisecond latencies and target IOPS and throughput described in the preceding table 99.9% of the time.
 
-## Bursting (preview)
+## Bursting
 
-Premium SSD sizes smaller than P30 now offer disk bursting (preview) and can burst their IOPS per disk up to 3,500 and their bandwidth up to 170 Mbps. Bursting is automated and operates based on a credit system. Credits are automatically accumulated in a burst bucket when disk traffic is below the provisioned performance target and credits are automatically consumed when traffic bursts beyond the target, up to the max burst limit. The max burst limit defines the ceiling of disk IOPS & Bandwidth even if you have burst credits to consume from. Disk bursting provides better tolerance on unpredictable changes of IO patterns. You can best leverage it for OS disk boot and applications with spiky traffic.    
+Premium SSD sizes smaller than P30 now offer disk bursting and can burst their IOPS per disk up to 3,500 and their bandwidth up to 170 Mbps. Bursting is automated and operates based on a credit system. Credits are automatically accumulated in a burst bucket when disk traffic is below the provisioned performance target and credits are automatically consumed when traffic bursts beyond the target, up to the max burst limit. The max burst limit defines the ceiling of disk IOPS & Bandwidth even if you have burst credits to consume from. Disk bursting provides better tolerance on unpredictable changes of IO patterns. You can best leverage it for OS disk boot and applications with spiky traffic.    
 
-Disks bursting support will be enabled on new deployments of applicable disk sizes in the [preview regions](https://docs.microsoft.com/azure/virtual-machines/linux/disk-bursting#regional-availability) by default, with no user action required. For existing disks of the applicable sizes, you can enable bursting with either of two the options: detach and reattach the disk or stop and restart the attached VM. All burst applicable disk sizes will start with a full burst credit bucket when the disk is attached to a Virtual Machine that supports a max duration at peak burst limit of 30 mins. To learn more about how bursting work on Azure Disks, see [Premium SSD bursting](../articles/virtual-machines/linux/disk-bursting.md). 
+Disks bursting support will be enabled on new deployments of applicable disk sizes by default, with no user action required. For existing disks of the applicable sizes, you can enable bursting with either of two the options: detach and reattach the disk or stop and restart the attached VM. All burst applicable disk sizes will start with a full burst credit bucket when the disk is attached to a Virtual Machine that supports a max duration at peak burst limit of 30 mins. To learn more about how bursting work on Azure Disks, see [Premium SSD bursting](../articles/virtual-machines/linux/disk-bursting.md). 
 
 ### Transactions
 
