Introducing: Azure CLI

Although not as popular as AWS or gcloud, Microsoft Azure has already created a resiliant community on our platform. Right now, you can use Buddy to easily automate deployment to the Azure App Service. In two weeks time, however, we are going to deliver support for Azure Storage, followed by the much requested integration with Microsoft Teams (currently in production).

This week we released yet another new action called Azure CLI. The action acts as an API client, allowing you to run basically any type of operation in the Microsoft’s cloud: from creating a virtual machine, to managing App Service instances, to orchestrating containers on an AKS cluster.

Azure CLI in the DevOps action roster


To use the integration, you need to create and provide an Azure service principal:

Adding Azure Cloud integration

Now you can define the commands that you want to run. Once the pipeline is triggered, Buddy will launch a container with pre-installed Azure CLI and execute the commands using the configured authentication data:

Azure action configuration

Example use case

Buddy’s powerful pipelines allow you to automate various types of workflows. Here’s an example pipeline that will create and launch a stage instance on Azure and notify the QA team they can begin the tests . Once the tests have completed, the team can manually resume the pipeline and run yet another Azure CLI action that will delete the VM from Azure:

Example Azure pipeline

When adding integrations, Buddy offers various scopes of management access: from workspace-level (all workspace members are allowed to modify the commands and associated accounts), to admin, group, project (perfect for YAML-managed projects), to private (restricted to the integration creator only). Please mind, however, that once the action is added to a pipeline, every developer with permissions to that pipeline can run it.

Buddy is 100% customer-driven. If there’s a feature or integration you miss, let us know in the comments below or directly at

Continue reading

This post was originally published on this site