From 85f8f212030075eee09f18b28b7e3c35d53b2fcf Mon Sep 17 00:00:00 2001 From: Balaga Gayatri Date: Mon, 18 Apr 2022 22:50:06 +0530 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 19349dc6..80adc350 100644 --- a/README.md +++ b/README.md @@ -240,7 +240,7 @@ You can add federated credentials in the Azure portal or with the Microsoft Grap 7. For **Entity type**, select **Environment**, **Branch**, **Pull request**, or **Tag** and specify the value, based on how you have configured the trigger for your GitHub workflow. For a more detailed overview, see [GitHub OIDC guidance]( https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#defining-[…]dc-claims). 8. Add a **Name** for the federated credential. 9. Click **Add** to configure the federated credential. -10. Make sure the above created application has the `contributor` access to the provided subscription. +10. Make sure the above created application has the `contributor` access to the provided subscription. Visit [role-based-access-control](https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal?tabs=current#prerequisites) for more details. For a more detailed overview, see more guidance around [Azure Federated Credentials](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation-create-trust-github).