Azure CLI vs Powershell?
Azure CLI is a PowerShell-like-tool available for all platforms. You can use the same commands no matter what platform you use: Windows, Linux or Mac.
Now, there are two version Azure CLI. The Azure CLI 1.0 was written with Node.js to achieve cross-platform capabilities, and the new Azure CLI 2.0 is written in Python to offer better cross-platform capabilities. Both are Open Source and available on Github. However, for now, only certain PowerShell cmdlets support use on Linux.
Is it targetted for the audience who want to manage Azure IAAS from Linux environment?
I think the answer is yes. For a Linux or Mac developer, I think they more likely to use Azure CLI.
Both, Azure CLI and the PowerShell package use the REST API of Azure.
As one of our Microsoft contacts said: Use whatever you like and you prefer.
There are some pros for Azure CLI:
- Open Source - which has many advantages. It might be developing faster in the future. You can view what is really in the Code, the community might or will be bigger, and so on.
- Azure CLI can be used with Groovy, Python, Ruby or any other scripting language. It is easier to get good developers for this languages than an experienced PowerShell developer. For example: I took Groovy because of Java. It is easier to use this combination then learning PowerShell scripting....
Currently there is 1 really big positive for PowerShell: there is a huge repository of PowerShell script examples for Azure. BUT: often you have to do it on your own to fit your requirements - therefore an example might be a good starting point - sometimes it is easier to begin from scratch.
My recommendation would be: Use Azure CLI --> For Scripting use the language your company is familiar with.
Just wanted to add my experience with both Azure Cli and Az PowerShell.
As per 2019, both are cross-platform so it should only be a language/syntax preference but with Azure Cli all/most commands are idempotent.
I've ended up replacing all my ARM Templates with Azure Cli scripts as it is less verbose and easy to read.
With Az Powershell, you still need to check if the resource exists before creating it otherwise it will throw an exception so scripts can become very complicated for no reason.
We're using both Azure Cli and Az Powershell with Azure DevOps. Azure Cli command can now be executed from bash (Linux) or bat (Windows) scripts. So it is not optimum... (EDIT 2020 You can now run Azure CLI using Powershell scripts as well)
- We deploy resources with Azure Cli because it is easy to read and commands are idempotent.
- For complex scripting I prefer using PowerShell as there are a lot of useful language features.
EDIT 2021
With the new Azure Bicep, I've started going back to "ARM type" deployment: Bicep is really easy to use if you understand ARM template and stay readable even with complex deployments.
In addition to Az CLI (Powershell core) it handles most of the scripting i need to do.