Merge pull request #66 from MicrosoftDocs/main

8/30/2024 AM Publish

articles/virtual-machines/includes/disks-premv2-regions.md

@@ -42,4 +42,4 @@ Currently only available in the following regions:
 - West US 2 (Three availability zones)
 - West US 3 (Three availability zones)
 
-To learn when support for particular regions was added, see either [Azure Updates](https://azure.microsoft.com/updates/?query=disk%20storage) or [What's new for Azure Disk Storage](../disks-whats-new.md).
+To learn when support for particular regions was added, see either [Azure Updates](https://azure.microsoft.com/updates/?query=disk%20storage) or [What's new for Azure Disk Storage](/azure/virtual-machines/disks-whats-new).

articles/virtual-machines/includes/managed-disks-bursting-2.md

@@ -10,9 +10,9 @@
 ---
 ### On-demand bursting
 
-Premium SSD managed disks using the on-demand bursting model of disk bursting can burst beyond original provisioned targets, as often as needed by their workload, up to the max burst target. For example, on a 1-TiB P30 disk, the provisioned IOPS is 5000 IOPS. When disk bursting is enabled on this disk, your workloads can issue IOs to this disk up to the max burst performance of 30,000 IOPS and 1,000 MBps. For the max burst targets on each supported disk, see [Scalability and performance targets for VM disks](../disks-scalability-targets.md#premium-ssd-managed-disks-per-disk-limits).
+Premium SSD managed disks using the on-demand bursting model of disk bursting can burst beyond original provisioned targets, as often as needed by their workload, up to the max burst target. For example, on a 1-TiB P30 disk, the provisioned IOPS is 5000 IOPS. When disk bursting is enabled on this disk, your workloads can issue IOs to this disk up to the max burst performance of 30,000 IOPS and 1,000 MBps. For the max burst targets on each supported disk, see [Scalability and performance targets for VM disks](/azure/virtual-machines/disks-scalability-targets#premium-ssd-managed-disks-per-disk-limits).
 
-If you expect your workloads to frequently run beyond the provisioned perf target, disk bursting won't be cost-effective. In this case, we recommend that you change your disk's performance tier to a [higher tier](../disks-performance-tiers.md) instead, for better baseline performance. Review your billing details and assess that against the traffic pattern of your workloads.
+If you expect your workloads to frequently run beyond the provisioned perf target, disk bursting won't be cost-effective. In this case, we recommend that you change your disk's performance tier to a [higher tier](/azure/virtual-machines/disks-performance-tiers) instead, for better baseline performance. Review your billing details and assess that against the traffic pattern of your workloads.
 
 Before you enable on-demand bursting, understand the following:
 
@@ -35,11 +35,11 @@ Disk configuration: Premium SSD – 1 TiB (P30), Disk bursting enabled.
 
 In this billing hour, the cost of bursting consists of two charges:
 
-The first charge is the burst enablement flat fee of $X (determined by your region). This flat fee is always charged on the disk disregard of the attach status until it is disabled. 
+The first charge is the burst enablement flat fee of $X (determined by your region). This flat fee is always charged on the disk disregard of the attach status until it's disabled. 
 
-Second is the burst transaction cost. Disk bursting occurred in two time slots. From 00:10:01 – 00:10:10, the accumulated burst transaction is (6,000 – 5,000) X 10 = 10,000. From 00:59:01 – 01:00:00, the accumulated burst transaction is (7,000 – 5,000) X 60 = 120,000. The total burst transactions are 10,000 + 120,000 = 130,000. Burst transaction cost will be charged at $Y based on 13 units of 10,000 transactions (based on regional pricing).
+Second is the burst transaction cost. Disk bursting occurred in two time slots. From 00:10:01 – 00:10:10, the accumulated burst transaction is (6,000 – 5,000) X 10 = 10,000. From 00:59:01 – 01:00:00, the accumulated burst transaction is (7,000 – 5,000) X 60 = 120,000. The total burst transactions are 10,000 + 120,000 = 130,000. Burst transaction cost is charged at $Y based on 13 units of 10,000 transactions (based on regional pricing).
 
-With that, the total cost on disk bursting of this billing hour equals to $X + $Y. The same calculation would apply for bursting over provisioned target of MBps. We translate the overage of MB to transactions with IO size of 256KB. If your disk traffic exceed both provisioned IOPS and MBps target, you can refer to the example below to calculate the burst transactions. 
+With that, the total cost on disk bursting of this billing hour equals to $X + $Y. The same calculation would apply for bursting over provisioned target of MBps. We translate the overage of MB to transactions with IO size of 256 KB. If your disk traffic exceed both provisioned IOPS and MBps target, you can refer to the example below to calculate the burst transactions. 
 
 Disk configuration: Premium SSD – 1 TB (P30), Disk bursting enabled.
 
@@ -51,7 +51,7 @@ The burst transaction is accounted as the max number of transactions from either
 You can refer to the [Managed Disks pricing page](https://azure.microsoft.com/pricing/details/managed-disks/) for details on pricing and use [Azure Pricing Calculator](https://azure.microsoft.com/pricing/calculator/?service=storage) to make the assessment for your workload. 
 
 
-To enable on-demand bursting, see [Enable on-demand bursting](../disks-enable-bursting.md).
+To enable on-demand bursting, see [Enable on-demand bursting](/azure/virtual-machines/disks-enable-bursting).
 
 ### Credit-based bursting
 
@@ -60,7 +60,7 @@ For Premium SSD managed disks, credit-based bursting is available for disk sizes
 ## Virtual machine-level bursting
 
 
-VM-level bursting only uses the credit-based model for bursting, it is enabled by default for most Premium Storage supported VMs.
+VM-level bursting only uses the credit-based model for bursting, it's enabled by default for most Premium Storage supported VMs.
 
 
 ## Bursting flow
@@ -69,7 +69,7 @@ The bursting credit system applies in the same manner at both the VM level and d
 
 ![Bursting bucket diagram.](media/managed-disks-bursting/bucket-diagram.jpg)
 
-How you spend your available credits is up to you. You can use your 30 minutes of burst credits consecutively or sporadically throughout the day. When resources are deployed they come with a full allocation of credits. When those deplete, it takes less than a day to restock. Credits can be spent at your discretion, the burst bucket does not need to be full in order for resources to burst. Burst accumulation varies depending on each resource, since it is based on unused IOPS and MB/s below their performance targets. Higher baseline performance resources can accrue their bursting credits faster than lower baseline performing resources. For example, a P1 disk idling will accrue 120 IOPS per second, whereas an idling P20 disk would accrue 2,300 IOPS per second.
+How you spend your available credits is up to you. You can use your 30 minutes of burst credits consecutively or sporadically throughout the day. When resources are deployed, they come with a full allocation of credits. When those deplete, it takes less than a day to restock. Credits can be spent at your discretion. The burst bucket doesn't need to be full in order for resources to burst. Burst accumulation varies depending on each resource, since it's based on unused IOPS and MB/s below their performance targets. Higher baseline performance resources can accrue their bursting credits faster than lower baseline performing resources. For example, a P1 disk idling accrues 120 IOPS per second, whereas an idling P20 disk would accrue 2,300 IOPS per second.
 
 ## Bursting states
 There are three states your resource can be in with bursting enabled:
@@ -79,9 +79,9 @@ There are three states your resource can be in with bursting enabled:
 
 ## Bursting examples
 
-The following examples show how bursting works with various VM and disk combinations. To make the examples easy to follow, we will focus on MB/s, but the same logic is applied independently to IOPS.
+The following examples show how bursting works with various VM and disk combinations. To make the examples easy to follow, we focus on MB/s, but the same logic is applied independently to IOPS.
 
-### Burstable virtual machine with non-burstable disks
+### Burstable virtual machine with nonburstable disks
 **VM and disk combination:** 
 - Standard_L8s_v2 
     - Uncached MB/s: 160
@@ -93,7 +93,7 @@ The following examples show how bursting works with various VM and disk combinat
     - Provisioned MB/s: 250
     - On-Demand Bursting: **not enabled**
 
- After the initial boot up, an application is run on the VM and has a non-critical workload. This workload requires 30 MB/s that gets spread evenly across all the disks.
+ After the initial boot up, an application is run on the VM and has a noncritical workload. This workload requires 30 MB/s that gets spread evenly across all the disks.
 ![Application sends request for 30 MB/s of throughput to VM, VM takes request and sends each of its disks a request for 10 MB/s, each disk returns 10 MB/s, VM returns 30 MB/s to application.](media/managed-disks-bursting/bursting-vm-nonbursting-disk/burst-vm-nonbursting-disk-normal.jpg)
 
 Then the application needs to process a batched job that requires 600 MB/s. The Standard_L8s_v2 bursts to meet this demand and then requests to the disks get evenly spread out to P50 disks.
@@ -112,11 +112,11 @@ Then the application needs to process a batched job that requires 600 MB/s. The
     - Provisioned MB/s: 25
     - Max burst MB/s: 170 
 
-When the VM starts, it will burst to request its burst limit of 1,280 MB/s from the OS disk and the OS disk will respond with its burst performance of 170 MB/s.
+When the VM starts, it will burst to request its burst limit of 1,280 MB/s from the OS disk, and the OS disk will respond with its burst performance of 170 MB/s.
 
 ![At startup, the VM bursts to send a request of 1,280 MB/s to the OS disk, OS disk bursts to return the 1,280 MB/s.](media/managed-disks-bursting/bursting-vm-bursting-disk/burst-vm-burst-disk-startup.jpg)
 
-After startup, you start an application that has a non-critical workload. This application requires 15 MB/s that gets spread evenly across all the disks.
+After startup, you start an application that has a noncritical workload. This application requires 15 MB/s that gets spread evenly across all the disks.
 
 ![Application sends request for 15 MB/s of throughput to VM, VM takes request and sends each of its disks a request for 5 MB/s, each disk returns 5 MB/s responses, VM returns 15 MB/s to application.](media/managed-disks-bursting/bursting-vm-bursting-disk/burst-vm-burst-disk-idling.jpg)
 

articles/virtual-machines/includes/managed-disks-ultra-disks-ga-scope-and-limitations.md

@@ -15,12 +15,12 @@ The following list contains Ultra Disk's limitations:
 - Currently, Ultra Disks only support Single VM and Availability zone infrastructure options.
 - Ultra Disks don't support availability sets.
 - The size of an Ultra Disk can't be expanded without either deallocating the VM or detaching the Ultra Disk.
-- Existing disks currently can't change their type to an Ultra Disk. They must be [migrated](../disks-convert-types.md#migrate-to-premium-ssd-v2-or-ultra-disk-using-snapshots).
-- Currently, Azure Government and Azure China don't support [customer-managed keys](../disk-encryption.md#customer-managed-keys) for Ultra disks.
+- Existing disks currently can't change their type to an Ultra Disk. They must be [migrated](/azure/virtual-machines/disks-convert-types?tabs=azure-powershell#migrate-to-premium-ssd-v2-or-ultra-disk-using-snapshots).
+- Currently, Azure Government and Azure China don't support [customer-managed keys](/azure/virtual-machines/disk-encryption#customer-managed-keys) for Ultra disks.
 - Azure Disk Encryption isn't supported for VMs with Ultra Disks. Instead, you should use encryption at rest with platform-managed or customer-managed keys.
 - Azure Site Recovery isn't supported for VMs with Ultra Disks.
 - Ultra Disks don't support disk caching.
-- Snapshots are supported with [other limitations](../disks-incremental-snapshots.md#incremental-snapshots-of-premium-ssd-v2-and-ultra-disks).
+- Snapshots are supported with [other limitations](/azure/virtual-machines/disks-incremental-snapshots?tabs=azure-powershell#incremental-snapshots-of-premium-ssd-v2-and-ultra-disks).
 - Azure Backup support for VMs with Ultra Disks is [generally available](/azure/backup/backup-support-matrix-iaas#vm-storage-support). Azure Backup has limitations when using Ultra Disks, see [VM storage support](/azure/backup/backup-support-matrix-iaas#vm-storage-support) for details.
 
 Ultra Disks support a 4k physical sector size by default but also supports a 512E sector size. Most applications are compatible with 4k sector sizes, but some require 512-byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks. For older versions of Oracle DB, 512-byte sector size is required.
@@ -41,9 +41,9 @@ Not every VM size is available in every supported region with Ultra Disks. The f
 
 |VM Type     |Sizes    |Description  |
 |------------|---------|-------------|
-| General purpose|[DSv3-series](../dv3-dsv3-series.md#dsv3-series), [Ddsv4-series](../ddv4-ddsv4-series.md#ddsv4-series), [Dsv4-series](../dv4-dsv4-series.md#dsv4-series), [Dasv4-series](../dav4-dasv4-series.md#dasv4-series), [Dsv5-series](../dv5-dsv5-series.md#dsv5-series), [Ddsv5-series](../ddv5-ddsv5-series.md#ddsv5-series), [Dasv5-series](../dasv5-dadsv5-series.md#dasv5-series)| Balanced CPU-to-memory ratio. Ideal for testing and development, small to medium databases, and low to medium traffic web servers.|
-| Compute optimized|[FSv2-series](../fsv2-series.md)| High CPU-to-memory ratio. Good for medium traffic web servers, network appliances, batch processes, and application servers.|
-| Memory optimized|[ESv3-series](../ev3-esv3-series.md#esv3-series), [Easv4-series](../eav4-easv4-series.md#easv4-series), [Edsv4-series](../edv4-edsv4-series.md#edsv4-series), [Esv4-series](../ev4-esv4-series.md#esv4-series), [Esv5-series](../ev5-esv5-series.md#esv5-series), [Edsv5-series](../edv5-edsv5-series.md#edsv5-series), [Easv5-series](../easv5-eadsv5-series.md#easv5-series), [Ebsv5 series](../ebdsv5-ebsv5-series.md#ebsv5-series), [Ebdsv5 series](../ebdsv5-ebsv5-series.md#ebdsv5-series), [M-series](../m-series.md), [Mv2-series](../mv2-series.md), [Msv2/Mdsv2-series](../msv2-mdsv2-series.md)|High memory-to-CPU ratio. Great for relational database servers, medium to large caches, and in-memory analytics.
-| Storage optimized|[LSv2-series](../lsv2-series.md), [Lsv3-series](../lsv3-series.md), [Lasv3-series](../lasv3-series.md)|High disk throughput and IO ideal for Big Data, SQL, NoSQL databases, data warehousing, and large transactional databases.|
-| GPU optimized|[NCv2-series](../ncv2-series.md), [NCv3-series](../ncv3-series.md), [NCasT4_v3-series](../nct4-v3-series.md), [ND-series](../nd-series.md), [NDv2-series](../ndv2-series.md), [NVv3-series](../nvv3-series.md), [NVv4-series](../nvv4-series.md), [NVadsA10 v5-series](../nva10v5-series.md)| Specialized virtual machines targeted for heavy graphic rendering and video editing, as well as model training and inferencing (ND) with deep learning. Available with single or multiple GPUs.|
-| <nobr>Performance optimized</nobr> |[HB-series](../hb-series.md), [HC-series](../hc-series.md), [HBv2-series](../hbv2-series.md)|The fastest and most powerful CPU virtual machines with optional high-throughput network interfaces (RDMA).|
+| General purpose|[DSv3-series](/azure/virtual-machines/dv3-dsv3-series#dsv3-series), [Ddsv4-series](/azure/virtual-machines/ddv4-ddsv4-series#ddsv4-series), [Dsv4-series](/azure/virtual-machines/dv4-dsv4-series#dsv4-series), [Dasv4-series](/azure/virtual-machines/dav4-dasv4-series#dasv4-series), [Dsv5-series](/azure/virtual-machines/dv5-dsv5-series#dsv5-series), [Ddsv5-series](/azure/virtual-machines/ddv5-ddsv5-series#ddsv5-series), [Dasv5-series](/azure/virtual-machines/dasv5-dadsv5-series#dasv5-series)| Balanced CPU-to-memory ratio. Ideal for testing and development, small to medium databases, and low to medium traffic web servers.|
+| Compute optimized|[FSv2-series](/azure/virtual-machines/fsv2-series)| High CPU-to-memory ratio. Good for medium traffic web servers, network appliances, batch processes, and application servers.|
+| Memory optimized|[ESv3-series](/azure/virtual-machines/ev3-esv3-series#esv3-series), [Easv4-series](/azure/virtual-machines/eav4-easv4-series#easv4-series), [Edsv4-series](/azure/virtual-machines/edv4-edsv4-series#edsv4-series), [Esv4-series](/azure/virtual-machines/ev4-esv4-series#esv4-series), [Esv5-series](/azure/virtual-machines/ev5-esv5-series#esv5-series), [Edsv5-series](/azure/virtual-machines/edv5-edsv5-series#edsv5-series), [Easv5-series](/azure/virtual-machines/easv5-eadsv5-series#easv5-series), [Ebsv5 series](/azure/virtual-machines/ebdsv5-ebsv5-series#ebsv5-series), [Ebdsv5 series](/azure/virtual-machines/ebdsv5-ebsv5-series#ebdsv5-series), [M-series](/azure/virtual-machines/m-series), [Mv2-series](/azure/virtual-machines/mv2-series), [Msv2/Mdsv2-series](/azure/virtual-machines/msv2-mdsv2-series)|High memory-to-CPU ratio. Great for relational database servers, medium to large caches, and in-memory analytics.
+| Storage optimized|[LSv2-series](/azure/virtual-machines/lsv2-series), [Lsv3-series](/azure/virtual-machines/lsv3-series), [Lasv3-series](/azure/virtual-machines/lasv3-series)|High disk throughput and IO ideal for Big Data, SQL, NoSQL databases, data warehousing, and large transactional databases.|
+| GPU optimized|[NCv2-series](/azure/virtual-machines/ncv2-series), [NCv3-series](/azure/virtual-machines/ncv3-series), [NCasT4_v3-series](/azure/virtual-machines/nct4-v3-series), [ND-series](/azure/virtual-machines/nd-series), [NDv2-series](/azure/virtual-machines/ndv2-series), [NVv3-series](/azure/virtual-machines/nvv3-series), [NVv4-series](/azure/virtual-machines/nvv4-series), [NVadsA10 v5-series](/azure/virtual-machines/nva10v5-series)| Specialized virtual machines targeted for heavy graphic rendering and video editing, as well as model training and inferencing (ND) with deep learning. Available with single or multiple GPUs.|
+| <nobr>Performance optimized</nobr> |[HB-series](/azure/virtual-machines/hb-series), [HC-series](/azure/virtual-machines/hc-series), [HBv2-series](/azure/virtual-machines/hbv2-series)|The fastest and most powerful CPU virtual machines with optional high-throughput network interfaces (RDMA).|

articles/virtual-machines/includes/virtual-machines-disks-encryption-at-host-restrictions.md

@@ -12,7 +12,7 @@ ms.custom:
 ---
 - Supported for 4k sector size Ultra Disks and Premium SSD v2.
 - Only supported on 512e sector size Ultra Disks and Premium SSD v2 if they were created after 5/13/2023.
-    - For disks created before this date, [snapshot your disk](../disks-incremental-snapshots.md) and create a new disk using the snapshot.
+    - For disks created before this date, [snapshot your disk](/azure/virtual-machines/disks-incremental-snapshots) and create a new disk using the snapshot.
 - Can't be enabled on virtual machines (VMs) or virtual machine scale sets that currently or ever had Azure Disk Encryption enabled. 
 - Azure Disk Encryption can't be enabled on disks that have encryption at host enabled.
 - The encryption can be enabled on existing virtual machine scale sets. However, only new VMs created after enabling the encryption are automatically encrypted.