What is the difference between PowerShell and Bash?

PowerShell pipelines pass .NET objects; Bash pipelines pass text you must parse. PowerShell also uses Verb-Noun naming, built-in help, and native JSON/XML cmdlets. Bash wins for POSIX scripts and classic Unix glue.

Is PowerShell free to use?

PowerShell itself is free under the MIT License. Cloud services you manage with it may cost money.

Should I use PowerShell or Zsh on Mac?

Use Zsh for general interactive terminal work and Unix tools. Use PowerShell for structured data, Azure/M365 admin, or scripts that must run on Mac and Windows. Many people keep both and switch by task.

Can I run bash scripts in PowerShell?

Not directly; PowerShell is not POSIX-compliant. Call bash with `bash -c 'your-command'` or invoke a .sh file. Simple aliases like `ls` map to cmdlets such as `Get-ChildItem` for interactive use.

Which PowerShell version should Mac users install in August 2026?

Prefer 7.6.4 LTS for production automation, or 7.5.9 if you explicitly want the current non-LTS stable line documented beside it. Both have arm64 and x64 macOS packages on Microsoft Learn. Homebrew's stable formula tracks 7.6.4 with Tahoe bottles on Apple Silicon.

PublishedJanuary 1, 2026•UpdatedSeptember 4, 2026

PowerShell

Name: PowerShell
Availability: InStock

Cross-platform command-line shell and scripting language

Developer ToolsFree

Are you the maker of PowerShell?

Install with Homebrew

brew install --cask powershell

Quick Take: PowerShell

4.5

On Mac in August 2026, PowerShell is mature, free, and supported through macOS Tahoe with 7.6 LTS packages (7.6.4) and notarized installers. It will not replace zsh for general Mac development. For Azure, Microsoft 365, Windows remoting, and object-pipeline automation it still has no real peer. Install the arm64 build, keep it beside your Unix shell, and stop cargo-culting Gatekeeper bypasses on current packages.

Best For

•Cloud and DevOps engineers managing Azure or AWS
•IT administrators working with Microsoft 365
•Developers building cross-platform automation scripts

What is PowerShell?

PowerShell is Microsoft's cross-platform shell and scripting language. It runs on macOS, Linux, and Windows. You install it on a Mac when you manage Windows servers, work with Azure or Microsoft 365, or want object pipelines for structured data that bash handles poorly. As of August 2026, PowerShell on Mac is current and supported. Microsoft Learn's install guide (updated July 2026) lists PowerShell 7.6.4 (LTS) and 7.5.9 packages for macOS arm64 and x64, with 7.4.x LTS still available and 7.7 previews on the release train. Homebrew's powershell formula reports stable 7.6.4 with bottles for macOS Tahoe on Apple Silicon plus Sequoia and Sonoma. Beginning with the May 2026 releases, macOS PKG packages are notarized and signed by Microsoft, which removes a class of Gatekeeper friction that plagued earlier side-load instructions. Supported macOS versions explicitly include macOS 26 (Tahoe), macOS 15 (Sequoia), and macOS 14 (Sonoma) on both Arm64 and x64. The main difference from bash, zsh, or fish is the pipeline: PowerShell passes .NET objects, not text streams. Cmdlets like Where-Object and Select-Object filter on properties, so process lists, REST responses, and cloud inventory break less often than regex-over-text pipelines. On a Mac it rarely replaces zsh as the default interactive login shell for app developers. For cross-platform automation shared with Windows teams, and for Azure or Graph admin work, it remains the pragmatic standard. PowerShell is free and open source under the MIT License. There is no paid "Pro shell". What costs money is the cloud estate you manage with it. If your Mac never touches Microsoft ecosystems, you can ignore PowerShell entirely. If it does, install the arm64 build and keep pwsh a keystroke away. Install notes that still trip people up: prefer the notarized PKG or current Homebrew bottles over old blog posts that teach Gatekeeper bypasses. After install, run Update-Help once so offline help matches 7.6.x, and create ~/.config/powershell/Microsoft.PowerShell_profile.ps1 if you want aliases and PSReadLine predictions every session. Preview builds remain available via brew install powershell/tap/powershell-preview when you need to test 7.7-train behaviour before it hits stable.

Closer look: PowerShell on Mac

How PowerShell moved from a Windows-only admin shell to a cross-platform automation tool that Mac users actually install for cloud and Microsoft 365 work.

History & Background

PowerShell began in 2006 as Monad, a Windows-only shell that treated everything as objects rather than text. For a decade it stayed on Windows as the backbone of Server administration. In 2016 Microsoft open-sourced PowerShell and shipped builds for Linux and macOS. PowerShell Core (v6) ran on .NET Core and traded some Windows-only features for real cross-platform support. PowerShell 7 arrived in 2020, unified the naming, and became the recommended version everywhere, with ongoing LTS and feature releases.

How It Works

PowerShell 7+ runs on the .NET runtime, so it can use .NET libraries and types. On macOS that includes native ARM64 for Apple Silicon. The core idea is the object pipeline: cmdlets receive and emit .NET objects with properties and methods that survive until the formatting system renders text at the end. That is why Get-Process | Where-Object { $_.CPU -gt 100 } | Stop-Process needs no text scraping. Formatting to text happens late on purpose. Until you print, you can select properties, sort, group, and export without writing parsers. That is the practical reason Mac admins keep pwsh around even when zsh stays the login shell.

Ecosystem & Integrations

The PowerShell Gallery hosts over 10,000 modules. Common ones: Az (Azure), AWS.Tools, Microsoft.Graph (Microsoft 365), VMware.PowerCLI, and Pester for tests. Modules use semantic versioning and dependency resolution similar to npm or pip. On macOS they install under ~/.local/share/powershell/Modules by default. The community also ships profile scripts, Oh-My-Posh themes, and VS Code extensions for IntelliSense, debugging, and analysis.

Future Development

Major versions land on a roughly annual schedule. Version 7.6 LTS (March 2026) is the current Long Term Support line, with faster startup, better tab completion, Apple Silicon work, and UTF-8 defaults for web cmdlets. Microsoft keeps PowerShell open source and cross-platform; Windows PowerShell 5.1 stays in maintenance for legacy Windows hosts.

Key Features

Object-Oriented Pipelines

Commands pass .NET objects instead of raw text. `Get-Process | Where-Object CPU -gt 100` filters process objects by the CPU property; you are not scraping columns with regex. Format changes that break bash pipelines usually leave PowerShell scripts intact.

Cross-Platform Consistency

Scripts written on macOS generally run on Windows and Linux without edits (aside from OS-specific paths). DevOps teams managing mixed fleets can share one automation codebase across servers.

Native Structured Data Support

JSON, CSV, XML, and YAML are first-class. `ConvertFrom-Json` turns API responses into queryable objects; `Export-Csv` serializes data without reaching for external tools. REST and config-file work needs fewer glue utilities than typical bash setups.

Predictive IntelliSense

PowerShell 7.6+ can suggest the next command, parameters, and values from history and context as you type. That cuts keystrokes and surfaces cmdlets you might not remember.

Parallel Processing with ForEach-Object

`ForEach-Object -Parallel` runs batch work across threads: files, API calls, or server configs. Pair it with `Start-Job` when you need background jobs for longer workloads.

Unified Cloud Management

Official modules cover major clouds: Az for Azure, AWSPowerShell for AWS, and GoogleCloud for GCP. Auth, error handling, and resource cmdlets stay in one shell instead of juggling three CLIs with different output shapes.

Who Should Use PowerShell?

1The Cloud Infrastructure Engineer

A DevOps engineer manages Windows servers on Azure and Linux containers on AWS. With the Az and AWS modules they write one deployment script that provisions resources, configures networking, and deploys apps across both clouds. Object pipelines filter and reshape infrastructure data without fragile text parsing, so scripts shrink from hundreds of bash lines to a shorter PowerShell flow.

2The Microsoft 365 Administrator

An IT administrator manages accounts, licenses, and security for a 5,000-person org. Microsoft Graph and Exchange Online modules handle bulk ops that would take days in the web UI: provision employees, adjust licenses by department, and generate compliance reports. They schedule those scripts with cron on their Mac.

3The Cross-Platform Developer

A .NET developer on a Mac builds, tests, and deploys apps that run on Windows and Linux. PowerShell gives the same scripting environment locally and in CI/CD. Because the shell sits on .NET, automation can call existing libraries and NuGet packages directly.

Install PowerShell on Mac

Install PowerShell on macOS via Homebrew, the official notarized PKG (preferred since May 2026 builds), .NET global tool, or binary archive. Current stable LTS highlighted in docs: 7.6.4. Current non-LTS stable packages include 7.5.9.

Install Homebrew

Common Mac path: install via Homebrew (brew install powershell / the powershell tap as documented), then run pwsh. Homebrew lists stable 7.6.4 with Tahoe support on Apple Silicon.

Install PowerShell Stable

Or run brew install --cask powershell for the latest stable cask build with Homebrew-managed updates.

Launch PowerShell

Open a new terminal and type pwsh. The PS prompt means you are inside PowerShell.

Verify Installation

Run $PSVersionTable and confirm PowerShell 7.6+ with PSEdition showing Core for the cross-platform build.

Pro Tips

• Install the preview version with brew install powershell/tap/powershell-preview if you want to test upcoming features.
• Create a profile at ~/.config/powershell/Microsoft.PowerShell_profile.ps1 for your customizations.
• Run Update-Help after installation to download the latest help documentation for offline access.

Configuration Tips

Create a custom profile

Profiles work like .zshrc. Create ~/.config/powershell/Microsoft.PowerShell_profile.ps1 for aliases, functions, and module imports. $PROFILE prints the exact path. Common additions: custom prompts, short aliases, and modules you always want loaded.

Tune PSReadLine

PSReadLine ships with PowerShell 7. Add Set-PSReadLineOption -PredictionSource History for history-based predictions, and Set-PSReadLineOption -PredictionViewStyle ListView for a dropdown of suggestions as you type.

Oh-My-Posh prompts

Install with brew install oh-my-posh, then add oh-my-posh init pwsh --config ~/.mytheme.omp.json | Invoke-Expression to your profile for git status, timing, and system info in the prompt (similar idea to Starship).

Alternatives to PowerShell

PowerShell is strong at structured data and cloud admin. Other Mac shells win for daily interactive Unix work or lighter syntax.

Zsh (Default macOS Shell)

Bash

Fish

Nushell

Pricing

Free & Open Source

PowerShell is free and open source under the MIT License. Source lives on GitHub at PowerShell/PowerShell. Microsoft publishes official macOS packages and documents Homebrew installs. No paid tiers or usage limits for the shell itself. Azure, Microsoft 365, and other cloud modules need the usual service subscriptions; those are not PowerShell license fees.

Pros

✓Object pipelines replace fragile grep/awk/sed parsing for structured data
✓Same scripts run on Mac, Windows, and Linux with few path tweaks
✓Official Azure, AWS, and GCP modules for cloud admin
✓Verb-Noun naming and Get-Help make discovery easier than ad-hoc flags
✓Try/Catch/Finally error handling familiar to programmers

Cons

✗Slower startup than Bash or Zsh, though improved in v7.6+
✗Verbose cmdlet names (Get-ChildItem vs ls) mean more typing without aliases
✗Not POSIX-compliant, so bash scripts need adaptation

Community & Support

PowerShell's open-source home is the GitHub repository, where Microsoft engineers respond to issues and pull requests. The team publishes release notes, runs community calls, and keeps docs on Microsoft Learn. For day-to-day questions, the PowerShell Discord and r/PowerShell are active, from beginners through Microsoft MVPs. The PowerShell Gallery (powershellgallery.com) hosts thousands of community modules for specific platforms and tasks.

Frequently Asked Questions about PowerShell

Yes. PowerShell 7+ runs on macOS with native Apple Silicon (M1/M2/M3/M4) packages. Install via Homebrew with brew install --cask powershell, then launch with pwsh.

About the Author

Alex Chen

Senior Developer Tools Specialist

Code Editors & IDEsTerminal EmulatorsVersion Control Tools

12+ years in software development · Former senior engineer at tech startups

Expert Tips for PowerShell

May 2026 notarization is the Mac-specific headline. Current docs should not lead with Gatekeeper bypass as the normal path.

Hands-on TestingHigh Confidence

Third-party Mac install blogs lag package numbers. Prefer Microsoft Learn monikered pages for 7.6.4/7.5.9 filenames.

Official DocsHigh Confidence

Mac usage stays specialised around Microsoft ecosystems. It is not a general zsh replacement; set expectations that way.

Hands-on TestingMedium Confidence

Related Technologies & Concepts

Microsoft.NET RuntimeAzureHomebrewPSReadLine

Sources & References

Fact-Checked

Last verified: Aug 9, 2026

Key Verified Facts

Microsoft documents PowerShell 7.6.4 and 7.5.9 macOS packages (arm64/x64) in the install guide updated July 2026.[cite-ps-learn]
Supported macOS versions include 26 Tahoe, 15 Sequoia, and 14 Sonoma on Arm64 and x64.[cite-ps-learn]
From May 2026 releases, macOS PKG packages are notarized and signed by Microsoft.[cite-ps-learn]
Homebrew lists stable PowerShell 7.6.4 with Apple Silicon Tahoe support.[cite-ps-brew]