feat(vscode): Enable MI option in connector setup

[andrew-eldridge]

This reverts commit #9364

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope
• Medium - Moderate changes, some user impact
• High - Major changes, significant user/system impact

What & Why

Re-enable MI option for connectors auth since latest bundle includes fix for previously observed issues

Impact of Change

• Users: MI auth option can now be selected in connectors setup
• Developers: N/A
• System: N/A

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:

Contributors

@andrew-eldridge

[github-actions]

🤖 AI PR Validation Report

PR passes. The advised risk level matches the submitter's estimate (low), so no correction is needed.

---

Last updated: Mon, 13 Jul 2026 15:29:50 GMT

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: feat(vscode): Enable MI option in connector setup
• Issue: None — the title is clear, scoped, and describes the change well.
• Recommendation: No change needed.

---

⚠️ Commit Type

• Properly selected (feature).
• Only one commit type is checked, which matches the template requirement.

---

✅ Risk Level

• The selected label/body risk appears consistent with the diff and the checked risk:low label.

---

✅ What & Why

• Current: Re-enable MI option for connectors auth since latest bundle includes fix for previously observed issues
• Issue: None — concise and sufficient for this PR.
• Recommendation: No change needed.

---

✅ Impact of Change

• Impact is clearly described and appropriately limited.
• Recommendation:
  • Users: Correct: MI auth option becomes selectable in connector setup.
  • Developers: N/A is acceptable.
  • System: N/A is acceptable.

---

✅ Test Plan

• Passes: the diff includes updated unit tests in authenticationMethodStep.test.ts.
• No E2E test is required because unit tests are present.

---

✅ Contributors

• Listed contributor is present.

---

✅ Screenshots/Videos

• Not required for this change; no visual UI evidence requested.

---

Summary Table

Section	Status	Recommendation
Title	✅
Commit Type	✅
Risk Level	✅
What & Why	✅
Impact of Change	✅
Test Plan	✅
Contributors	✅
Screenshots/Videos	✅

---

This PR passes review for title/body compliance. The advised risk level remains low and matches the submitter’s assessment.

---

Last updated: Mon, 13 Jul 2026 15:29:42 GMT

[Copilot]

Pull request overview

This PR re-enables the Managed Identity (MI) authentication option in the VS Code Azure connector setup wizard by restoring the authentication-method prompt step behavior.

Changes:

• Restore AuthenticationMethodSelectionStep.shouldPrompt() so the wizard prompts for an auth method when Azure connectors are enabled and no method has been selected.
• Remove the prior “always default to rawKeys” behavior and its corresponding test expectations.
• Update unit tests to align with the re-enabled prompt flow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
apps/vs-code-designer/src/app/commands/workflows/authenticationMethodStep.ts	Restores prompt gating logic so users can select MI vs connection keys when connectors are enabled.
apps/vs-code-designer/src/app/commands/workflows/test/authenticationMethodStep.test.ts	Adjusts unit tests for the updated shouldPrompt behavior.

[github-actions]

📊 Coverage Check

🎉 All changed files have adequate test coverage!