My Growing Love Affair with The Azure CLI
A colleague recently told me that in his experience, almost 90 percent of cloud projects fail (David Linthicum wrote perceptively about this in February of this year).
The reason? Enterprise IT personnel, increasingly pressed by the c-suite to deploy solutions in the cloud and reduce their organization’s data center footprint are recreating on-premises workloads without training or a thorough knowledge of cloud architecture patterns (such as AWS’s Well Architected Framework and examples provided Azure’s Solution Architecture ).
This leads to errors such as building over-provisioned virtual machines (instead of exploring PaaS and serverless alternatives) and running those machines non-stop, as you’d do within your data center, instead of running them only as needed to contain costs.
All well and good (and a topic I’ll dive into deeper in later posts) but what does that have to do with the Azure CLI?
Effectively managing cloud resources means learning new ways of doing things that at first look may seem familiar — such as creating virtual networks.
When you start working with Azure, it’s natural to depend upon the portal to create and configure your resources: it’s a powerful and versatile tool. The problem is that continued use of the portal alone limits your efficiency as you create complex solutions. It also, I argue, limits your understanding of the mechanics of Azure.
This is where the Azure CLI comes into play:
In future articles, I’ll demonstrate the power and utility of the Azure CLI by using it to build the real-world things you’ll need to deploy to solve actual problems.
In the meantime, try your hand at learning the CLI.