Skip to content

fix: CI pipeline failure resolved by adding AZURE_TENANT_ID input to workflow#402

Merged
Prajwal-Microsoft merged 1 commit intodevfrom
update_CI_gihubworkflow
Jun 20, 2025
Merged

fix: CI pipeline failure resolved by adding AZURE_TENANT_ID input to workflow#402
Prajwal-Microsoft merged 1 commit intodevfrom
update_CI_gihubworkflow

Conversation

@Prasanjeet-Microsoft
Copy link
Copy Markdown
Contributor

Purpose

  • This PR addresses a failure in the CI pipeline caused by the missing AZURE_TENANT_ID input in the workflow file. The issue has been resolved by adding the required secret value under the $input block in the deployment step.

Does this introduce a breaking change?

  • Yes
  • No

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid:

  • Ensure AZURE_TENANT_ID is correctly referenced using ${{ secrets.AZURE_TENANT_ID }}
  • Validate that the pipeline now runs successfully in the CI
  • Confirm other required inputs (AZURE_SUBSCRIPTION_ID, ENVIRONMENT_NAME) are intact
  • Check for no unintended changes in the workflow

@Prajwal-Microsoft Prajwal-Microsoft merged commit a198f19 into dev Jun 20, 2025
5 checks passed
@Prasanjeet-Microsoft Prasanjeet-Microsoft deleted the update_CI_gihubworkflow branch July 3, 2025 19:45
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants