Session

Controlling multiple Azure tenants with Microsoft365DSC and Azure Pipelines

Do you have multiple tenants in Azure that should all be configured the same? You have separate Azure tenants for Dev, Test and Prod and these tenants should be configured almost the same? A greenfield approach is always easy, but what about when you have an already production tenant and want to bring it into control? How can you export the configuration data from a tenant and turn it into something readable and manageable?

All this can be achieved with Microsoft365DSC if you build appropriate tooling around it. But in this session, we go one step further and combine Microsoft365DSC with Azure Pipelines and all the best practices we have learned in the DSC community over the last years to build a comfortable and robust release pipeline. The approach shown does not only work in theory but is already being implemented by a number of companies.

Raimund Andrée

PFE, Microsoft Germany

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top