PowerShell is a stand-alone installation that uses. Windows PowerShell is the standard scripting shell that comes preinstalled with most Windows operating systems.
Windows PowerShell or PowerShell must be used to install the Az module. However, they do change your command-line experience.Īzure CLI has an installer that makes its commands executable in all four shell environments.Īzure PowerShell is set of cmdlets packaged as a PowerShell module named Az not an executable.
The differences in the shell environment doesn't change how Azure CLI and Azure PowerShell operate. Your shell environment not only determines which tools you can use but also changes your command-line experience.įor example, for the line continuation character, Bash uses the backslash \ while Windows PowerShell uses the backtick `. Windows PowerShell, PowerShell, Cmd, and Bash are shell environments.
Even though you don't have to worry about the data center, you still have to patch and troubleshoot Azure VMs, failover databases, and configure virtual networks.īy using the existing automation that runs Azure, command-line tools reduce that overhead. As your rate of adoption with Azure increases so will the overhead. Moving your workload to Azure lifts some of the administrative burden but not all.
Every action you take inside the portal translates somewhere to code being executed to read, create, modify, or delete resources. What's the advantage of using an Azure command-line tool?Īzure runs on automation. Use this guide to determine which is the right tool for you. Each operates differently, and the language is sometimes confused with the environment. This article compares the Azure CLI and Azure PowerShell language and gives a comparison of the shell environments on which they run.Īzure CLI, Azure PowerShell, and Azure Cloud Shell have overlapping functionality. When it comes to managing Azure, you have many options.