[Feature] PowerShell CLI Friendly

[soroshsabz]

ITNOA

Description of the new feature/enhancement

As you can know PowerShell is great Scripting Language for Automation and Administration of system. and it is built by Microsoft, so I think it is very good for Azure Dev CLI to get compatible with PowerShell and make native PowerShell Cmdlet to provide a native and consistent user experience in Microsoft Ecosystem.

Note: As you can know PowerShell Core is portable PowerShell so I think if Microsoft provide native PowerShell Cmdlet for azure cli all azure cli community in all platform (such as linux or mac) can achieve unified development and operation (DevOps) experience in Microsoft ecosystem.

Proposed technical implementation details (optional)

I think PowerShell has many guideline and documentation about writing and designing great Cmdlet and modules that Azure Dev CLI teams have to follow it for example

Windows PowerShell Cmdlet Concepts
Writing a Windows PowerShell Module
PowerShell Script Module Design: Building Tools to Automate the Process
Powershell: DSL design patterns

[soroshsabz]

related to #6165

[soroshsabz]

As you can see in another Microsoft open source CLI - WinGet CLI, PowerShell native CLI became very popular very quickly from its initial release.

related issues on that projects

• PowerShell CLI Friendly microsoft/winget-cli#1088
• Add Native PowerShell Support microsoft/winget-cli#221
• When do we begin to see the PowerShell cmdlets? microsoft/winget-cli#674

[vhvb1989]

Daniel Jurek (@danieljurek) Wes Haggard (@weshaggard) , what would it be your thoughts on adding azd- pwsh cmdlets? In your experience, does it bring extra benefits compared to the cli binary?

[spboyer]

We'd like to better understand the specific gaps before investing in a native PowerShell module. azd already has solid PowerShell support:

• ✅ Tab completion: azd completion powershell | Out-String | Invoke-Expression
• ✅ JSON pipeline: azd env list --output json | ConvertFrom-Json | Where-Object { ... }
• ✅ PowerShell hook scripts in azure.yaml (.ps1 files)
• ✅ Cross-platform installer: install-azd.ps1
• ✅ PowerShell 7 (pwsh) and 5.1 (powershell) fallback support

What we need to understand:

1. What specific workflows are blocked or painful without native Cmdlets?
2. Is the primary ask about PSObject pipeline output, or full Cmdlet wrappers?
3. How many users in your org use azd from PowerShell vs bash/zsh?
4. Would better documentation of existing PowerShell patterns (completion setup, JSON pipeline examples) address the core need?

The WinGet comparison is noted, but WinGet has a fundamentally different interaction model (package install/search) vs azd's multi-step deployment workflows. A thin wrapper module is feasible but we want to make sure it solves real pain points.

Please share specific examples of what you're trying to accomplish that doesn't work well today.

[soroshsabz]

Shayne Boyer (@spboyer) no it is not native way, your working PowerShell like linux shell, that every things is strings, but the main power of PowerShell is every things are objects. so you can working very safer and cleaner