fix: downmerge from main to dev#363
Merged
Roopan-Microsoft merged 14 commits intodevfrom Mar 11, 2026
Merged
Conversation
chore: Dev to main
docs: Update Troubleshoot document
Added AI and Data Engineering playbooks with descriptions.
Removed the Data playbook entry from the README.
Updated the wording for clarity regarding AI Engineering best practices.
docs: Add AI Engineering playbooks to README
chore: Dev to main
…dows.yml since it's no longer needed
ci: Migrated GitHub Actions authentication from client secrets to OIDC and combined Ubuntu & Windows workflows into a single pipeline
Roopan-Microsoft
approved these changes
Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces several important updates to the GitHub Actions workflows, primarily focusing on simplifying and unifying deployment pipelines, improving security and authentication mechanisms, and enhancing flexibility for deployment environments. The main changes include refactoring Docker build and deployment workflows to use Azure federated authentication, consolidating Linux and Windows deployment workflows into a single, parameterized workflow, and updating permissions for OIDC-based authentication.
Workflow Refactoring and Unification
The separate Windows deployment workflow (
deploy-windows.yml) has been removed and its functionality integrated into a single, renamed workflow (deploy-v2.yml), which now supports both Linux and Windows deployments via a newrunner_osinput parameter. This reduces duplication and centralizes deployment logic. [1] [2] [3] [4] [5] [6] [7] [8]The deployment orchestrator workflow (
deploy-orchestrator.yml) has been simplified by removing explicit permissions, relying on those set by the calling workflow.Authentication and Security Improvements
Docker build and deployment workflows now use Azure federated identity (OIDC) for authentication via the
azure/login@v2action, removing the need to store and pass Docker registry passwords and service principal secrets directly. [1] [2] [3] [4] [5] [6] [7]The
id-token: writepermission has been added to workflows that require OIDC authentication. [1] [2] [3]Parameterization and Flexibility
The new
runner_osinput allows selection between Linux and Windows runners for deployment, validated and mapped internally to the correct GitHub Actions runner label. [1] [2] [3] [4]Additional workflow inputs and outputs have been updated to support this flexibility and improve validation of deployment parameters. [1] [2] [3] [4]
Environment and Permissions Consistency
environment: productionattribute has been added to relevant jobs for improved environment scoping and secrets management. [1] [2]Most Important Changes
1. Workflow Unification and Refactoring
deploy-v2.yml), removing the now-redundantdeploy-windows.ymland adding arunner_osinput to control the deployment environment. [1] [2] [3] [4] [5] [6] [7] [8]2. Azure Federated Authentication (OIDC)
azure/login@v2), removing the need for Docker registry passwords and service principal secrets. [1] [2] [3] [4] [5] [6] [7]3. Enhanced Permissions and Security
id-token: writepermission to workflows that require OIDC authentication for Azure login. [1] [2] [3]4. Improved Parameterization and Validation
runner_osparameter for deployment workflows, allowing dynamic selection of runner environment and improving input validation. [1] [2] [3] [4]5. Environment Scoping
environment: productionto relevant jobs for improved environment management and secrets handling. [1] [2]Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information