There is an existing azure.azcollection, which supports a lot of different types of azure resources, includes examples and documentation.

Unforturnately, there are some problems with maintenance:

• it is still based on the old versions of Microsoft Azure API and is having problems updating its dependencies ansible-collections/azure#477
• does not include all resources Azures supports, especially the new ones
• lacks support for advanced options for many resources, especially for hosting resource inside virtual private networks (relevant for my enterprise customers)
• conflicts with official azure command line client az - it is not possible/easy to use the both on the same computer

Explanation for that: ansible-collections/azure development is not scalable. While Microsoft constantly expands and changes its API by introducing new resources and new features to existing resources, every such change requires adjustment to the implementation of these ansible modules, which is not feasible for a project driven by a couple of enthusiasts.

Heavily inspired by resource and resource_info modules of the azcollection, without the ballast of obsolete dependencies, it supports all Azure resources with the newest API and allows for a high-productivity workflow, described below.

Welcome to azbare!

For a cloud engineer productivity following workflow would be desirable:

Assuming you've already created a resource group like

Try out something with resource specific az command like

The extensive documentation behind az servicebus --help helps a lot. Alternatively or optionaly you can check/edit the resource interactively via Azure Portal.

Find out the resource id with az servicebus namespace list -o yaml | grep myexample | grep id

Now print a generic resource definition. You can already filter out some null values with grep: az resource show -o yaml --ids /subscriptions/xxxxx-...-xxxx/resourceGroups/experimental-ap plicationdevelopment/providers/Microsoft.ServiceBus/namespac es/myexample-bus1 | grep -v ': null'