But it’s also possible to just add what you need, which is a good thing in the sense of the ‘Least Privilege’ principle. I’ve used the documentation to add all permissions that can be used. I personally like to use the CLI for Microsoft 365 for this. Step 2: Adding permissionsĪdding permissions to service principals cannot be done using the Azure AD Portal currently. Copy the object Id of the Service Principal from the identity blade and add it to your Automation Account variables. In that case you’ll need to have created a managed identity resource first though.Įnabling managed identity will create a Service Principal in Azure AD, that you can assign permissions and roles. If you want to use a User Assigned Managed Identity, you can add one by clicking on the Add button. You can enable a System Assigned Managed Identity by switching a simple toggle. Just open the Automation Account and click on the Identity blade. How to set it up Step 1: Enabling Managed IdentityĮnabling Managed Identity is as easy as it is on any resource. In this blog post I’ll share my findings and the steps I took to get it working. I used the Microsoft Teams PowerShell module and tried out a few routes before being succesful. I was recently creating a script that would need to connect to Microsoft Teams using Managed Identity in an Azure Automation Runbook.
0 kommentar(er)
