AZ-400 · Question #586
You have an Azure DevOps organization that contains a repo named Repo1 that contains infrastructure as code (IaC) resources. You plan to deploy the resources by using a GitHub Actions workflow. You ne
The correct answer is C. a Microsoft Entra user-assigned managed identity. To connect a GitHub Actions workflow to an Azure DevOps repo for infrastructure as code (IaC) deployments, authentication is typically achieved using Personal Access Tokens (PATs), Service Principals with OpenID Connect (OIDC), or Managed Identities. PATs offer a straightforward
Question
Options
- Aa GitHub token
- Ban X.509 certificate
- Ca Microsoft Entra user-assigned managed identity
- Da Microsoft Entra external identity
How the community answered
(65 responses)- A3% (2)
- B6% (4)
- C80% (52)
- D11% (7)
Explanation
To connect a GitHub Actions workflow to an Azure DevOps repo for infrastructure as code (IaC) deployments, authentication is typically achieved using Personal Access Tokens (PATs), Service Principals with OpenID Connect (OIDC), or Managed Identities. PATs offer a straightforward approach, while Service Principals and Managed Identities provide more robust and secure authentication for automated deployments. Note: Use GitHub Actions to connect to Azure The Azure Login action supports different ways of authenticating with Azure: Sign in with OpenID Connect using a Microsoft Entra application or a user-assigned managed Sign in with a managed identity configured on an Azure virtual machine (Only available for self- hosted GitHub runners) Sign in with a service principal and secret (Not recommended) https://learn.microsoft.com/en-us/azure/developer/github/connect-from-azure
Topics
Community Discussion
No community discussion yet for this question.