PROVIDER Β· the automation scripting language of the Windows ecosystem

PowerShell

PowerShell is the native automation language for Windows and Microsoft cloud where cmdlet object pipelines pass structured data, official modules cover AD, Exchange, Azure, and M365, and PowerShell 7 is fully open source and cross-platform.

Programming Languages & Frameworks United States 2026.11.16
Programming Languages & Frameworks United States the automation scripting language of the Windows ecosystem
4.3pts

Pros

4 items
Object pipelines pass structured data with direct property and method access
Complete official modules for Windows and Microsoft cloud including AD, Exchange, Azure, and M365
PowerShell 7 is open source and cross-platform on Linux and macOS
Deep .NET integration calls any .NET library

Cons

4 items
Verbose Verb-Noun syntax with many parameters hurts readability
Execution policies and permission models often block scripts
Linux adoption below bash with cross-platform ops still bash-centric
Windows PowerShell 5.1 and PowerShell 7 coexistence causes confusion

Product Information

powershell
Category Programming Languages & Frameworks
Company PowerShell
Service Region United States
Recommendation Score 4.3 pts
Published 2026-11-16

Detailed Notes

Overview

PowerShell was championed by Microsoft's Jeffrey Snover and released in 2006 as a scripting language for Windows administration built on cmdlets and object pipelines, passing structured objects rather than plain text so properties and methods are directly accessible.

For Programming Languages & Frameworks work the value is native automation for Windows and Microsoft cloud, since Exchange, Active Directory, Microsoft 365, and Azure all ship official modules, PowerShell 7 is fully open source and cross-platform administering Azure from Linux, and object pipelines remove text parsing.

Weigh the trade-offs, because verbose Verb-Noun syntax and many parameters invite hard-to-maintain scripts, execution policies and permission models frequently block scripts, and Linux ecosystem adoption trails bash so cross-platform operations still centre on bash.

Core Strengths

  • Object pipelines pass structured data with direct property and method access
  • Complete official modules for Windows and Microsoft cloud including AD, Exchange, Azure, and M365
  • PowerShell 7 is open source and cross-platform on Linux and macOS
  • Deep .NET integration calls any .NET library

Product Ecosystem

Core syntax

Cmdlets with object pipelines, parameter binding, script blocks, and functions organised into modules.

Administration

Active Directory, Exchange, Azure, Microsoft 365, and WinRM remote management.

Toolchain

VS Code extension, Pester testing, and PSScriptAnalyzer linting.

Drawbacks

  • Verbose Verb-Noun syntax with many parameters hurts readability
  • Execution policies and permission models often block scripts
  • Linux adoption below bash with cross-platform ops still bash-centric
  • Windows PowerShell 5.1 and PowerShell 7 coexistence causes confusion

Use Cases

  • Windows server operations (β˜…β˜…β˜…β˜…β˜…) - The native choice
  • Azure and M365 automation (β˜…β˜…β˜…β˜…β˜…) - Official modules
  • Enterprise desktop management (β˜…β˜…β˜…β˜…β˜…) - Domain integration
  • Linux automation (β˜…β˜…) - Bash is more common

Pricing

Plan Price Scope
PowerShell 7 and Windows PowerShell $0 MIT licensed, free
Official modules such as Az and ExchangeOnline $0 Free downloads
Enterprise support Microsoft contracts Via Azure or enterprise agreements

The language and modules are free with cost in Windows licensing and learning, and while Azure Automation bills by run volume, most enterprises run PowerShell on existing servers at no extra cost.

FAQ

  • Must PowerShell run on Windows? No, PowerShell 7 supports Linux and macOS though Windows-only modules such as AD still require Windows.

  • What if scripts are blocked? Execution policy usually, temporarily bypassed with Set-ExecutionPolicy -Scope Process Bypass and solved properly through code signing in production.

  • Is it used alongside bash? Commonly bash on Linux and PowerShell for Windows and Microsoft cloud, dispatched separately from CI.

Code Examples

Batch check site status

$urls = Get-Content .\sites.txt

$urls | ForEach-Object {
    $r = Invoke-WebRequest -Uri $_ -Method Head -TimeoutSec 5 -SkipHttpErrorCheck
    [pscustomobject]@{ Url = $_; Status = $r.StatusCode }
} | Where-Object Status -ne 200 | Format-Table

-SkipHttpErrorCheck returns objects for 4xx and 5xx instead of throwing, key for batch probing.

Object pipelines

Get-Process | Where-Object WorkingSet64 -gt 500MB |
    Sort-Object WorkingSet64 -Descending |
    Select-Object -First 5 Name, @{N='MB';E={ [math]::Round($_.WorkingSet64/1MB) }}

Pipelines pass objects rather than text, which is why PowerShell suits operations work.

Community & Resources

Communities and official channels

Learning resources and tools

Visit PowerShell Website β†’ https://microsoft.com/powershell
Visit Website β†—