From 52ea23151d8cfd9b923f960a07263e474dc4588e Mon Sep 17 00:00:00 2001 From: Martin Ehrnst Date: Fri, 5 Aug 2022 12:48:33 +0200 Subject: [PATCH] Update org.md Add example on how to assign Microsoft Graph permission on a managed identity, as this is not possible through the Azure Portal. Up until recently no official Microsoft documentation existed for it, but now it does Signed-off-by: Martin Ehrnst --- docs/integrations/azure/org.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/azure/org.md b/docs/integrations/azure/org.md index 56d37369dd..b31f8e89f2 100644 --- a/docs/integrations/azure/org.md +++ b/docs/integrations/azure/org.md @@ -96,7 +96,7 @@ To authenticate with a certificate rather than a client secret, you can set the If deploying to resources that supports Managed Identity, and has identities configured (e.g. Azure App Services, Azure Container Apps), Managed Identity should be picked up without any additional configuration. If your app has multiple managed identities, you may need to set the `AZURE_CLIENT_ID` environment variable to tell Azure Identity which identity to use. -You will need to grant the same permissions to your identity as described for App Registrations above. +To grant the managed identity the same permissions as mentioned in *App Registration* above, [please follow this guide](https://docs.microsoft.com/en-us/azure/app-service/tutorial-connect-app-access-microsoft-graph-as-app-javascript?tabs=azure-powershell) ## Filtering imported Users and Groups