Skip to content

Add DiskIOPSReadWrite and DiskMBpsReadWrite parameters to Add-AzVMDataDisk#29107

Draft
Copilot wants to merge 3 commits intomainfrom
copilot/support-disk-iops-mbps-si-vms
Draft

Add DiskIOPSReadWrite and DiskMBpsReadWrite parameters to Add-AzVMDataDisk#29107
Copilot wants to merge 3 commits intomainfrom
copilot/support-disk-iops-mbps-si-vms

Conversation

Copy link
Contributor

Copilot AI commented Jan 27, 2026

Enables setting custom IOPS and throughput during implicit disk creation for UltraSSD_LRS and PremiumV2_LRS data disks on Single Instance VMs.

Changes

  • Add-AzVMDataDisk cmdlet: Added DiskIOPSReadWrite (long?) and DiskMBpsReadWrite (long?) parameters, scoped to VmManagedDiskParameterSet only
  • StorageAccountType: Added PremiumV2_LRS to PSArgumentCompleter
  • Help: Added Example 5 demonstrating UltraSSD with custom performance values
  • Tests: Added Test-VMDataDiskIOPSMBPS to verify parameter mapping

Usage

$vm = New-AzVMConfig -VMName "VM01" -VMSize "Standard_D4s_v3"
$vm = Add-AzVMDataDisk -VM $vm -Name 'UltraData1' -Lun 0 -CreateOption Empty `
    -DiskSizeInGB 10 -StorageAccountType UltraSSD_LRS -Caching None `
    -DiskIOPSReadWrite 5000 -DiskMBpsReadWrite 200

Parameters map directly to existing DataDisk.DiskIOPSReadWrite and DataDisk.DiskMBpsReadWrite SDK properties.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • 1mcvsblobprodwus2174.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • 2d2vsblobprodwus2127.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • 40vvsblobprodwus2135.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • 5azvsblobprodwus2162.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • 6yfvsblobprodwus2121.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • 7q7vsblobprodwus2144.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • 84hvsblobprodwus2148.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • 8wdvsblobprodwus2137.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • 9yyvsblobprodwus2157.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • b53vsblobprodwus2154.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • ba0vsblobprodwus2130.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • balvsblobprodwus2129.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • cbvvsblobprodwus2131.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • cffvsblobprodwus218.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • d94vsblobprodwus2119.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • ezcvsblobprodwus2170.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • faxvsblobprodwus2122.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • g3xvsblobprodwus2151.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • i01vsblobprodwus216.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • ia4vsblobprodwus2112.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • isovsblobprodwus211.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • isvvsblobprodwus2147.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • jhgvsblobprodwus2167.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • k4pvsblobprodwus2140.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • kafvsblobprodwus2165.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • km4vsblobprodwus2183.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • ldhvsblobprodwus2153.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • mt2vsblobprodwus2110.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • ox9vsblobprodwus2149.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • p2tvsblobprodwus2189.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • s8nvsblobprodwus2158.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • tn2vsblobprodwus2124.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • vd2vsblobprodwus2150.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • wlnvsblobprodwus2188.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • wztvsblobprodwus2155.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • xofvsblobprodwus2114.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • y1rvsblobprodwus2136.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
  • y5lvsblobprodwus2179.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • yf8vsblobprodwus212.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet dotnet build Compute.csproj -c Debug (dns block)
  • zaxvsblobprodwus215.vsblob.vsassets.io
    • Triggering command: /usr/bin/dotnet /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

This section details on the original issue you should resolve

<issue_title>Az.Compute- Disk IOPS/MBPS Support for SI VMs</issue_title>
<issue_description>

Guidelines

The purpose of the Azure PowerShell design review is to ensure that the cmdlets follow the same pattern across the Azure modules. An early design review reduces the risk of unnecessary implementation changes caused by a cmdlet syntax design change.

Please ensure your cmdlets comply with the design guidelines outlined in the PowerShell Design Guidelines document.

Please generate cmdlets syntax using GenerateCmdletDesignMarkdown.ps1 for review if your cmdlet is generated from API spec directly by Autorest.PowerShell.

If you just add parameter to existing cmdlets and parameter definition complies with guideline, the design review is not expected.

  • Have you read above statement?

    • { Yes }

Service Release Details

  • Is this an Embargoed Preview, A Public Preview, or a General Release?

    • { GA }
  • What is the expected service release date?

    • {Q1 2026 }
  • Which Powershell module are these changes being made in?

    • {Az.Compute }

Contact Information

  • Main developer contacts (emails + github aliases)

    • { yaminibansal@microsoft.com, linugeorge@microsoft.com }
  • PM contact (email + github alias)

    • { ryandraper@microsoft.com }
  • Other people who should attend a design review (email)

    • { ppusuluri@microsoft.com }

High Level Scenarios

  • Describe how your feature is intended to be used by customers.

    • { Customers will be able to set the values of DiskIOPSReadWrite and DiskMBPSReadWrite parameters while implicit disk creation of UltraSSD or Premium V2 data disks for SI VMs }
  • Piping scenarios / how these cmdlets are used with existing cmdlets

    • { These are existing cmdlets and the new feature parameter will not change the piping scenarios }
  • Sample of end-to-end usage

    • Please provide comprehensive examples that don't assume additional setup. It helps the audience understand your feature.

    • `{ Scenario: Setting values of IOPS/MBPS while implicit disk creation

Add-AzVMDataDisk -VM $vm -Name 'UltraData1' -Lun 0 -CreateOption Empty -DiskSizeGB 10 -Caching None -StorageAccountType UltraSSD_LRS -DiskIOPSReadWrite 100 -DiskMBpsReadWrite 1
``
}`

Syntax changes

Indicate if you are requesting an edit to existing cmdlets, adding new cmdlets, or both. Then edit the corresponding section below.

- { Existing }

Changed cmdlet

List the names of the cmdlets that are being edited.

- { Add-AzVMDataDisk }

List the new parameters for the cmdlet, the parameter types, and their allowed values if applicable.

- { -DiskIOPSReadWrite Type: Int64
- -DiskMBpsReadWrite Type: Int64 }

Please describe the new business logic of the cmdlet and parameters here.

- {  It allows to set the values of DiskIOPSReadWrite and DiskMBPSReadWrite parameters while implicit disk creation of UltraSSD or Premium V2 data disks for SI VMs}

Link to diff between markdown help files, or sample syntax as above.

- { CHANGED CMDLETS HERE }

Indicate which parameter sets on the cmdlet are affected by this change.

- { INPUT HERE }

Specific test cases

Please provide a link to the API tests that exist for this feature.

  • { ENTER LINK HERE }

Additional information

For example:
    - New parameter A can only be used when old parameter B is set to value C. 
    - This feature requires the subscription to be on the 'allowlist' for X feature. 
- { INPUT HERE }

</issue_description>

Comments on the Issue (you are @copilot in this section)

@haagha PS Cmdlet Assistant is preparing code for this request. Please wait for the base PR to be created.

Custom agent used: Compute PowerShell Pull Request Agent
Specialized agent for creating PowerShell pull requests based on a design request

  • Fixes Azure/azure-powershell-cmdlet-review-pr#1531

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

@azure-client-tools-bot-prd
Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

Copilot AI and others added 2 commits January 27, 2026 21:39
…aDisk cmdlet

Co-authored-by: audreyttt <225061541+audreyttt@users.noreply.github.com>
… and add PremiumV2_LRS

Co-authored-by: audreyttt <225061541+audreyttt@users.noreply.github.com>
Copilot AI changed the title [WIP] Add Disk IOPS/MBPS support for SI VMs Add DiskIOPSReadWrite and DiskMBpsReadWrite parameters to Add-AzVMDataDisk Jan 27, 2026
Copilot AI requested a review from audreyttt January 27, 2026 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants