You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Az.Fleet] Generate Compute Fleet 2026-08-01 GA powershell SDK - #30302
️✔️PowerShell Core - Windows️✔️Windows PowerShell - Windows
⚠️Az.ComputeFleet
️✔️Build
️✔️PowerShell Core - Windows️✔️Windows PowerShell - Windows
️✔️Breaking Change Check
️✔️PowerShell Core - Windows️✔️Windows PowerShell - Windows
⚠️Signature Check
⚠️PowerShell Core - Windows
Type
Cmdlet
Description
Remediation
⚠️
Get-AzComputeFleet
Get-AzComputeFleet Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.
Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️
Get-AzComputeFleet
Get-AzComputeFleet changes the confirm impact. Please ensure that the change in ConfirmImpact is justified
Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️
Get-AzComputeFleetVirtualMachine
Get-AzComputeFleetVirtualMachine Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.
Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️
Get-AzComputeFleetVirtualMachine
Get-AzComputeFleetVirtualMachine changes the confirm impact. Please ensure that the change in ConfirmImpact is justified
Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️
Get-AzComputeFleetVirtualMachineScaleSet
Get-AzComputeFleetVirtualMachineScaleSet Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.
Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️
Get-AzComputeFleetVirtualMachineScaleSet
Get-AzComputeFleetVirtualMachineScaleSet changes the confirm impact. Please ensure that the change in ConfirmImpact is justified
Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️Windows PowerShell - Windows
Type
Cmdlet
Description
Remediation
⚠️
Get-AzComputeFleet
Get-AzComputeFleet Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.
Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️
Get-AzComputeFleet
Get-AzComputeFleet changes the confirm impact. Please ensure that the change in ConfirmImpact is justified
Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️
Get-AzComputeFleetVirtualMachine
Get-AzComputeFleetVirtualMachine Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.
Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️
Get-AzComputeFleetVirtualMachine
Get-AzComputeFleetVirtualMachine changes the confirm impact. Please ensure that the change in ConfirmImpact is justified
Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️
Get-AzComputeFleetVirtualMachineScaleSet
Get-AzComputeFleetVirtualMachineScaleSet Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.
Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️
Get-AzComputeFleetVirtualMachineScaleSet
Get-AzComputeFleetVirtualMachineScaleSet changes the confirm impact. Please ensure that the change in ConfirmImpact is justified
Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️Help Example Check
⚠️PowerShell Core - Windows
Type
Cmdlet
Example
Line
RuleName
Description
Extent
Remediation
⚠️
Get-AzComputeFleet
4
2
Mismatched_Parameter_Value_Type
Get-AzComputeFleet -InputObject $fleet is not an expected parameter value type.
-InputObject
Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).
⚠️
Remove-AzComputeFleet
3
2
Mismatched_Parameter_Value_Type
Remove-AzComputeFleet -InputObject $fleet is not an expected parameter value type.
-InputObject
Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).
⚠️
Get-AzComputeFleet
4
2
Mismatched_Parameter_Value_Type
Get-AzComputeFleet -InputObject $fleet is not an expected parameter value type.
-InputObject
Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).
⚠️
Remove-AzComputeFleet
3
2
Mismatched_Parameter_Value_Type
Remove-AzComputeFleet -InputObject $fleet is not an expected parameter value type.
-InputObject
Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).
⚠️Windows PowerShell - Windows
Type
Cmdlet
Example
Line
RuleName
Description
Extent
Remediation
⚠️
Get-AzComputeFleet
4
2
Mismatched_Parameter_Value_Type
Get-AzComputeFleet -InputObject $fleet is not an expected parameter value type.
-InputObject
Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).
⚠️
Remove-AzComputeFleet
3
2
Mismatched_Parameter_Value_Type
Remove-AzComputeFleet -InputObject $fleet is not an expected parameter value type.
-InputObject
Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).
⚠️
Get-AzComputeFleet
4
2
Mismatched_Parameter_Value_Type
Get-AzComputeFleet -InputObject $fleet is not an expected parameter value type.
-InputObject
Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).
⚠️
Remove-AzComputeFleet
3
2
Mismatched_Parameter_Value_Type
Remove-AzComputeFleet -InputObject $fleet is not an expected parameter value type.
-InputObject
Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).
️✔️Help File Existence Check
️✔️PowerShell Core - Windows️✔️Windows PowerShell - Windows
⚠️File Change Check
⚠️PowerShell Core - Windows
Type
Cmdlet
Description
Remediation
⚠️
AssemblyInfo.cs will be updated automatically. Please do not update it manually.
Revert AssemblyInfo.cs to its last version.
⚠️Windows PowerShell - Windows
Type
Cmdlet
Description
Remediation
⚠️
AssemblyInfo.cs will be updated automatically. Please do not update it manually.
Revert AssemblyInfo.cs to its last version.
️✔️UX Metadata Check
️✔️PowerShell Core - Windows️✔️Windows PowerShell - Windows
Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)
Next action: Re-record Update-AzComputeFleet for API 2026-08-01 and inspect request/response changes; do not substitute version strings.
Verify: Run Update-AzComputeFleet playback on this platform, then the ComputeFleet suite.
Test validation
Agent live test: Not run; this is a review-only PR. Check author-provided test evidence and upstream CI separately.
Regression coverage: Not applicable to the changed files.
The PowerShell coverage helper is not applicable; it does not verify the API-upgrade scenario. No tests or recordings changed. src/ComputeFleet/ComputeFleet.Autorest/test/Update-AzComputeFleet.Tests.ps1 creates fleets in BeforeAll; logs show the new PUT key is absent from Update-AzComputeFleet.Recording.json, so update assertions never execute. Re-record against the new API, then run focused playback and the module suite. Inspect create/update payloads, returned capacity/provisioning state, identity-based update and preserved properties; replacing API-version strings cannot establish compatibility. No Agent live test ran.
Release artifact finding
src/ComputeFleet/ComputeFleet/ChangeLog.md:21 describes tooling only, although ComputeFleet.Autorest/UX/Microsoft.AzureFleet/fleets.json:3 changes the API to 2026-08-01 and generated/published New, Set and Update help removes ZoneAllocationPolicyDistributionStrategy and ZoneAllocationPolicyZonePreference. Document the API upgrade and parameter compatibility impact. Confirm regenerated command metadata and existing-script parameter binding, then regenerate matching help. The changed help establishes documentation removal, not a separately executed binding test.
Both Copilot comments are corroborated: the recording concern by task logs, and the release-note concern by changed metadata/help. They are consolidated above, not duplicate findings.
Risk assessment — 18/100 · Low
The Low rating is driven by no changed regression test.
Change scope: 21 changed files, 340 changed lines (+94 / -246), including 1 production file.
Affected components:computefleet
Risk drivers: no changed regression test (+10)
Regression evidence: No changed regression test was detected for the production changes, increasing risk.
Confidence: High because changed-line patches were available for every production file.
Required review: Owning-squad review is recommended for computefleet before merge.
Please revert this whitespace-only change. tools/StaticAnalysis/FileChangeAnalyzer/Test-FileChange.ps1:62–68 flags every modification to AssemblyInfo.cs, since release automation owns this file; these added blank lines trigger the reported File Change Check warning.
Azure Pipelines:
Successfully started running 3 pipeline(s).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NoriZC
added
the
Request X Engineering Agent
molikkiddmsft
changed the title
x-engineering-agent
Bot
added
the
X Engineering Agent Reviewed
🤖 PR Validation —⚠️ Review suggested
️✔️Az.Accounts
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.