Skip to content

Chore: Change Azure AD refs to Microsoft Entra (#204) #13

Chore: Change Azure AD refs to Microsoft Entra (#204)

Chore: Change Azure AD refs to Microsoft Entra (#204) #13

Triggered via push March 19, 2024 16:09
Status Failure
Total duration 58s
Artifacts
prepare-environment
5s
prepare-environment
Terraform CICD (Hub Multi-tenant Secure Baseline)  /  Validate and Plan
26s
Terraform CICD (Hub Multi-tenant Secure Baseline) / Validate and Plan
Terraform CICD (Hub Multi-tenant Secure Baseline)  /  Deploy
0s
Terraform CICD (Hub Multi-tenant Secure Baseline) / Deploy
Terraform CICD (Spoke Multi-tenant Secure Baseline)  /  Validate and Plan
Terraform CICD (Spoke Multi-tenant Secure Baseline) / Validate and Plan
Terraform CICD (Spoke Multi-tenant Secure Baseline)  /  Deploy
Terraform CICD (Spoke Multi-tenant Secure Baseline) / Deploy
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Terraform CICD (Hub Multi-tenant Secure Baseline) / Validate and Plan
AADSTS700213: No matching federated identity record found for presented assertion subject 'repo:Azure/appservice-landing-zone-accelerator:ref:refs/heads/main'. Please check your federated identity credential Subject, Audience and Issuer against the presented assertion. https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation Trace ID: 21a1ea5a-5cbc-4cab-b1ed-e17da44c5700 Correlation ID: 3136c3cc-4a4b-4a4f-ad44-5903ca530659 Timestamp: 2024-03-19 16:09:52Z
Terraform CICD (Hub Multi-tenant Secure Baseline) / Validate and Plan
Interactive authentication is needed. Please run: az login
Terraform CICD (Hub Multi-tenant Secure Baseline) / Validate and Plan
Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
Terraform CICD (Hub Multi-tenant Secure Baseline) / Validate and Plan
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: azure/login@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.