From b1aafe40a3e1326079456e0a932f55c86caa13e3 Mon Sep 17 00:00:00 2001 From: Usha N Date: Fri, 22 Oct 2021 16:01:28 +0530 Subject: [PATCH] Update README.md --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8def8ab0..9922634e 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,10 @@ With the [Azure Login](https://github.com/Azure/login/blob/master/action.yml) Ac 2. In your GitHub workflow, Set `permissions:` with `id-token: write` at workflow level or job level based on whether the OIDC token needs to be auto-generated for all Jobs or a specific Job. 3. Within the Job deploying to Azure, add Azure/login action and pass the `client-id`, `tenant-id` and `subscription-id` of the Azure service principal associated with an OIDC Federated Identity Credential credeted in step (i) -Note: Currently OIDC login is supported for public clouds. Support for other clouds like Government clouds, Azure Stacks would be added soon. +Note: + - OIDC support in Azure is in Public Preview and is supported only for public clouds. Support for other clouds like Government clouds, Azure Stacks would be added soon. + - GitHub runners will soon be updating the with the Az CLI and PowerShell versions that support with OIDC. Hence the below sample workflows include explicit instructions to download the same during workflow execution. + - By default, Azure access tokens issued during OIDC based login could have limited validity. This expiration time is configurable in Azure. ## Sample workflow that uses Azure login action to run az cli