Add ResiliencyView parameter to Get-AzVmssVM for Resilient Delete status

[Copilot]

Description

Adds -ResiliencyView switch parameter to Get-AzVmssVM cmdlet to expose real-time VM delete retry status for the Resilient Delete feature. When enabled, VMSS automatically retries failed VM deletions (max 5 retries). The new parameter surfaces ResilientVMDeletionStatus property indicating whether retries are in-progress, failed, or not started.

Changes

• VirtualMachineScaleSetVMGetMethod.cs: Added ResiliencyView parameter and logic to pass resiliencyView expand option to SDK
• PSVirtualMachineScaleSetVM.cs: Exposed ResilientVMDeletionStatus property (already in SDK model)
• Get-AzVmssVM.md: Documentation and example for new parameter
• VirtualMachineScaleSetTests.ps1: Added Test-VirtualMachineScaleSetResiliencyView test

Usage

# Get resiliency status for specific VM instance
Get-AzVmssVM -ResiliencyView -ResourceGroupName "rg" -VMScaleSetName "vmss" -InstanceId "0"

# Output includes ResilientVMDeletionStatus: "InProgress" | "Failed" | "NotStarted"

Follows existing UserData parameter pattern. SDK already supports VmssVMInstanceViewTypes.ResiliencyView.

Mandatory Checklist

• General release

• Public preview

• Private preview

• Engineering build

• No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

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 build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
• 1n8vsblobprodwus2184.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• 2d2vsblobprodwus2127.vsblob.vsassets.io
  • Triggering command: /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 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 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 build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• 7q7vsblobprodwus2144.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• 7t8vsblobprodwus2168.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• 84hvsblobprodwus2148.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• 8wdvsblobprodwus2137.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• b53vsblobprodwus2154.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• ba0vsblobprodwus2130.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• balvsblobprodwus2129.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• cbvvsblobprodwus2131.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• cffvsblobprodwus218.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• d94vsblobprodwus2119.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
• ezcvsblobprodwus2170.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/tools/VersionController/VersionController.Netcore.csproj -c Debug (dns block)
• faxvsblobprodwus2122.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• g3xvsblobprodwus2151.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• i01vsblobprodwus216.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• ia4vsblobprodwus2112.vsblob.vsassets.io
  • Triggering command: /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 build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• jhgvsblobprodwus2167.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• k4pvsblobprodwus2140.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• kafvsblobprodwus2165.vsblob.vsassets.io
  • Triggering command: /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 build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• mt2vsblobprodwus2110.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• nudvsblobprodwus214.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• ox9vsblobprodwus2149.vsblob.vsassets.io
  • Triggering command: /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 build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• tn2vsblobprodwus2124.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• vm9vsblobprodwus2190.vsblob.vsassets.io
  • Triggering command: /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 build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
  • Triggering command: /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 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 build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)
• yf8vsblobprodwus212.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet build /home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Azure.PowerShell.sln -c Debug -fl /flp1:logFile=/home/REDACTED/work/azure-powershell/azure-powershell/artifacts/Build.log;verbosity=quiet (dns block)

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

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>VMSS Resilient Deletion Status Powershell Support</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?

  • General Release

• What is the expected service release date?

  • November 31, 2025

• Which Powershell module are these changes being made in?

  • Az.Compute

Contact Information

• Main developer contacts (emails + github aliases)

  • abondalapati@microsoft.com

• PM contact (email + github alias)

  • Email: manasisoman@microsoft.com
  • GitHub: manasisoman-work

• Other people who should attend a design review (email)

  • bahram.AliZadeh@microsoft.com

High Level Scenarios

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

  • This functionality we'd like to add to Powershell is a part of an existing feature on VMSS called Resilient Delete. For some context, Resilient Delete automatically initiates "force delete" retries on VMs that did not delete properly (max number of retries is 5). This means that customers who enroll in this Resilient Delete feature don't have to manually mitigate those delete failures anymore, because VMSS will just perform retries on the customer's behalf. When VMSS initiates another delete operation on the failed VM, the VM's provisioning status will change from "Failed" to "Deleting". However, if that delete operation failed again, then the VM status would change from "Deleting" to "Failed" (more comprehensive example included later in this ticket). Therefore, if the customer needs to know if the retries are still in progress, we're requesting Powershell support for a new property called "ResiliencyView" which contains the real-time status of the VM delete retries ("in-progress", "failed", "not started").

• Piping scenarios / how these cmdlets are used with existing cmdlets

  • We aren't requesting a new cmdlet. Instead, we'd like to add a new property to the GetVmssVM cmdlet. Customers will use the cmdlet "GetVmssVM" and fetch the property "ResiliencyView".

• Sample of end-to-end usage

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

  • The customer has a Virtual Machine Scale Set (VMSS) that has the policy "Resilient Delete" enabled. Let's say the customer deletes 3 VMs within this VMSS. However, all 3 of those VMs fail to delete. Each of those VMs will now have a Provisioning Status as "Failed". Automatically, the Resilient Delete feature will kick in and initiate a new delete operation on the VM (this is defined as a "retry" and we have a max retry count of 5). Once the retry is initiated, the VM's provisioning status will switch to "Deleting". However, after 5 minutes, those VMs fail to delete again. So then the VM provisioning status changes from "Deleting" to "Failed". Then, Resilient Delete will kick in again and initiate a new delete operation on each VM. The VMs' provisioning status will go from "Failed" to "Deleting". This oscillation in Provisioning Status throughout the retries can be a bit confusing for the customer, since they don't know if a "Failed" VM provisioning status means that all retries have exhausted/hit the max retry count or if there's another retry left. Therefore, the customer can use the "ResiliencyView" property within the cmdlet "GetVmssVM" and see if the retries are In Progress, fully Failed, or Not Started.

Syntax changes

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

- Just editing existing cmdlets

...

Custom agent used: Powershell PR agent
This agent creates a Powershell PR

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

---

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