Although most organizations, especially with centralized IT management, prefer to build and operate their infrastructure within a single Azure AD tenant, there are still enough corner cases when you need to span your deployment process across multiple tenants.
Next week, on April 29, 2020, I will be doing a demo on the webinar hold by Infopulse, an outsourcing company that is a part of the TietoEVRY group. This webinar will be dedicated to using Azure DevOps services for achieving maximum business value in common and some specialized cases.
In my last post, I showed you how to use Azure Artifacts to host your PowerShell repository and publish your custom PowerShell modules to it. Here I would like to talk about accessing and using those modules by other Azure Pipelines.
Following my post on embracing DevOps practices in PowerShell automation, I decided to share a sample PowerShell module project with CI/CD pipeline that would put theory in practice.
After publishing my posts about deploying Azure Policy and Azure Policy initiatives from ARM templates, I got a few questions about performing such deployments from Azure DevOps pipelines. Indeed, there are a few things to pay attention to. So, I will try to shed some light on them in this article.