Merge pull request #263916 from MashaMSFT/patch-119

Added Azure CLI & PowerShell links

Author: prmerger-automator[bot]

articles/virtual-machines/disks-deploy-premium-v2.md

@@ -3,7 +3,7 @@ title: Deploy a Premium SSD v2 managed disk
 description: Learn how to deploy a Premium SSD v2 and about its regional availability.
 author: roygara
 ms.author: rogarana
-ms.date: 01/16/2024
+ms.date: 01/23/2024
 ms.topic: how-to
 ms.service: azure-disk-storage
 ms.custom: references_regions, devx-track-azurecli, devx-track-azurepowershell
@@ -21,12 +21,12 @@ Premium SSD v2 support a 4k physical sector size by default, but can be configur
 
 ## Determine region availability programmatically
 
-To use a Premium SSD v2, you need to determine the regions and zones where it's supported. Not every region and zones support Premium SSD v2. For a list of regions, see [Regional availability](#regional-availability).
-
-To determine regions, and zones support premium SSD v2, replace `yourSubscriptionId` then run the following command:
+Since not every region and zone supports Premium SSD v2, you can use the Azure CLI or PowerShell to determine region and zone supportability. For a list of supported regions, see [Regional availability](#regional-availability).
 
 # [Azure CLI](#tab/azure-cli)
 
+To determine the regions and zones that support Premium SSD v2, replace `yourSubscriptionId` with your subscription, and then run the [az vm list-skus](/cli/azure/vm#az-vm-list-skus) command:
+
 ```azurecli
 az login
 
@@ -39,6 +39,8 @@ az vm list-skus --resource-type disks --query "[?name=='PremiumV2_LRS'].{Region:
 
 # [PowerShell](#tab/azure-powershell)
 
+To determine the regions and zones that support Premium SSD v2, replace `yourSubscriptionId` with your subscription, and then run the [Get-AzComputeResourceSku](/powershell/module/az.compute/get-azcomputeresourcesku) command:
+
 ```powershell
 Connect-AzAccount
 
@@ -51,7 +53,7 @@ Get-AzComputeResourceSku | where {$_.ResourceType -eq 'disks' -and $_.Name -eq '
 
 # [Azure portal](#tab/portal)
 
-To programmatically determine the regions and zones you can deploy to, use either the Azure CLI or Azure PowerShell Module.
+To programmatically determine the regions and zones you can deploy to, use either the Azure CLI, Azure PowerShell Module. 
 
 ---
 
@@ -61,7 +63,9 @@ Now that you know the region and zone to deploy to, follow the deployment steps
 
 # [Azure CLI](#tab/azure-cli)
 
-Create a Premium SSD v2 disk in an availability zone. Then create a VM in the same region and availability zone that supports Premium Storage and attach the disk to it. The following script creates a Premium SSD v2 with a 4k sector size, to deploy one with a 512 sector size, update the `$logicalSectorSize` parameter. Replace the values of all the variables with your own, then run the following script:
+Create a Premium SSD v2 disk in an availability zone by using the [az disk create](/cli/azure/disk#az-disk-create) command. Then create a VM in the same region and availability zone that supports Premium Storage and attach the disk to it by using the [az vm create](/cli/azure/vm#az-vm-create) command. 
+
+The following script creates a Premium SSD v2 with a 4k sector size, to deploy one with a 512 sector size, update the `$logicalSectorSize` parameter. Replace the values of all the variables with your own, then run the following script:
 
 ```azurecli-interactive
 ## Initialize variables
@@ -99,7 +103,9 @@ az vm create -n $vmName -g $resourceGroupName \
 
 # [PowerShell](#tab/azure-powershell)
 
-Create a Premium SSD v2 disk in an availability zone. Then create a VM in the same region and availability zone that supports Premium Storage and attach the disk to it. The following script creates a Premium SSD v2 with a 4k sector size, to deploy one with a 512 sector size, update the `$logicalSectorSize` parameter. Replace the values of all the variables with your own, then run the following script:
+Create a Premium SSD v2 disk in an availability zone by using the [New-AzDiskConfig](/powershell/module/az.compute/new-azdiskconfig) to define the configuration of your disk and the [New-AzDisk](/powershell/module/az.compute/new-azdisk) command to create your disk. Next, create a VM in the same region and availability zone that supports Premium Storage by using the [az vm create](/cli/azure/vm#az-vm-create). Finally, attach the disk to it by using the [Get-AzVM](/powershell/module/az.compute/get-azvm) command to identify variables for the virtual machine, the [Get-AzDisk](/powershell/module/az.compute/get-azdisk) command to identify variables for the disk, the [Add-AzVMDataDisk](/powershell/module/az.compute/add-azvmdatadisk) command to add the disk, and the [Update-AzVM](/powershell/module/az.compute/update-azvm) command to attach the new disk to the virtual machine. 
+
+The following script creates a Premium SSD v2 with a 4k sector size, to deploy one with a 512 sector size, update the `$logicalSectorSize` parameter. Replace the values of all the variables with your own, then run the following script:
 
 ```powershell
 # Initialize variables
@@ -184,28 +190,34 @@ You've now deployed a VM with a premium SSD v2.
 
 ## Adjust disk performance
 
-Unlike other managed disks, the performance of a Premium SSD v2 can be configured independently of its size. For conceptual information on this, see [Premium SSD v2 performance](disks-types.md#premium-ssd-v2-performance).
+Unlike other managed disks, the performance of Premium SSD v2 disks can be configured independently of its size by using the Azure CLI and PowerShell. Making adjustments to disk performance by using the Azure portal is not currently supported. 
+
+For conceptual information on adjusting disk performance, see [Premium SSD v2 performance](disks-types.md#premium-ssd-v2-performance).
 
 # [Azure CLI](#tab/azure-cli)
 
-The following command changes the performance of your disk, update the values as you like, then run the command:
+Use the [az disk update](/cli/azure/disk#az-disk-update) command to change the performance configuration of your Premium SSD v2 disk. For example, you can use the `disk-iops-read-write` parameter to adjust the max IOPS limit, and the `disk-mbps-read-write` parameter to adjust the max throughput limit of your Premium SSD v2 disk.  
+
+The following command adjusts the performance of your disk. Update the values in the command, and then run it:
 
 ```azurecli
 az disk update --subscription $subscription --resource-group $rgname --name $diskName --disk-iops-read-write=5000 --disk-mbps-read-write=200
 ```
 
 # [PowerShell](#tab/azure-powershell)
 
-The following command changes the performance of your disk, update the values as you like, then run the command:
+Use the [New-AzDiskUpdateConfig](/powershell/module/az.compute/new-azdiskupdateconfig) command to define your new performance configuration values for your Premium SSD v2 disks, and then use the [Update-AzDisk](/powershell/module/az.compute/update-azdisk) command to apply your configuration changes to your disk. For example, you can use the `DiskIOPSReadWrite` parameter to adjust the max IOPS limit, and the `DiskMBpsReadWrite` parameter to adjust the max throughput limit of your Premium SSD v2 disk.  
+
+The following command adjusts the performance of your disk. Update the values in the command, and then run it:
 
 ```azurepowershell
-$diskupdateconfig = New-AzDiskUpdateConfig -DiskMBpsReadWrite 2000
+$diskupdateconfig = New-AzDiskUpdateConfig -DiskIOPSReadWrite 5000 -DiskMBpsReadWrite 200
 Update-AzDisk -ResourceGroupName $resourceGroup -DiskName $diskName -DiskUpdate $diskupdateconfig
 ```
 
 # [Azure portal](#tab/portal)
 
-Currently, adjusting disk performance is only supported with Azure CLI or the Azure PowerShell module.
+Currently, adjusting disk performance is only supported with the Azure CLI or Azure PowerShell module.
 
 ---
 
@@ -219,6 +231,6 @@ Currently, adjusting disk performance is only supported with Azure CLI or the Az
 
 ## Next steps
 
-Add a data disk using either the [Azure portal](linux/attach-disk-portal.md), [CLI](linux/add-disk.md), or [PowerShell](windows/attach-disk-ps.md).
+Add a data disk by using either the [Azure portal](linux/attach-disk-portal.md), [Azure CLI](linux/add-disk.md), or [PowerShell](windows/attach-disk-ps.md).
 
 Provide feedback on [Premium SSD v2](https://aka.ms/premium-ssd-v2-survey).

articles/virtual-machines/disks-types.md

@@ -102,6 +102,7 @@ Premium SSD v2 is suited for a broad range of workloads such as SQL server, Orac
 
 Premium SSD v2 support a 4k physical sector size by default, but can be configured to use a 512E sector size as well. While most applications are compatible with 4k sector sizes, some require 512 byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks.
 
+
 ### Differences between Premium SSD and Premium SSD v2
 
 Unlike Premium SSDs, Premium SSD v2 doesn't have dedicated sizes. You can set a Premium SSD v2 to any supported size you prefer, and make granular adjustments to the performance without downtime. Premium SSD v2 doesn't support host caching but, benefits significantly from lower latency, which addresses some of the same core problems host caching addresses. The ability to adjust IOPS, throughput, and size at any time also means you can avoid the maintenance overhead of having to stripe disks to meet your needs.