Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Microsoft 365 connectors need explicit account and tenant selection [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19489•Fetched 2026-04-26 05:16:24
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
StonemageStonemage
Participants
StonemageStonemage
Timeline (top)
labeled ×4

The Microsoft 365 connectors are unsafe and not fit for purpose for multi-account or migration workflows unless Codex can explicitly select the Microsoft account, tenant, and mailbox context being used.

In a real migration workflow, the user may be signed into multiple Microsoft accounts. The connector can bind to an unexpected primary identity, while the user intends to inventory or migrate data from a different tenant/account. That makes even read-only inventory unsafe: the tool can access or attempt to access the wrong tenant before the user has a chance to correct it.

Root Cause

Migration and admin workflows often require moving data from one Microsoft 365 account/tenant to another. Multi-account operation is not an edge case; it is the core workflow. If Codex silently chooses the wrong Microsoft identity, the connector becomes unusable for professional M365 migration work.

RAW_BUFFERClick to expand / collapse

Summary

The Microsoft 365 connectors are unsafe and not fit for purpose for multi-account or migration workflows unless Codex can explicitly select the Microsoft account, tenant, and mailbox context being used.

In a real migration workflow, the user may be signed into multiple Microsoft accounts. The connector can bind to an unexpected primary identity, while the user intends to inventory or migrate data from a different tenant/account. That makes even read-only inventory unsafe: the tool can access or attempt to access the wrong tenant before the user has a chance to correct it.

Why this matters

Migration and admin workflows often require moving data from one Microsoft 365 account/tenant to another. Multi-account operation is not an edge case; it is the core workflow. If Codex silently chooses the wrong Microsoft identity, the connector becomes unusable for professional M365 migration work.

Required behavior

  • Show the active Microsoft account and tenant before any Outlook, Calendar, Teams, or SharePoint connector call.
  • Allow explicit account/tenant selection per Microsoft connector connection.
  • Support multiple named Microsoft connections, e.g. "Outlook - Source Tenant" and "Outlook - Destination Tenant".
  • Let tool calls target a specific named connection/account.
  • Fail closed if the requested account/tenant does not match the active connector identity.
  • Never silently fall back to another signed-in Microsoft account.
  • Expose delegated/shared mailbox context separately from the authenticated primary identity.

Expected result

Codex should make it impossible to accidentally inventory, read, or mutate the wrong Microsoft 365 tenant. Account and tenant identity need to be explicit, visible, and enforceable at the connector/tool-call layer.

Actual result

The connector can resolve to a Microsoft identity other than the one intended for the migration. The user cannot reliably force the connector to use the intended signed-in account from within Codex, making the workflow unsafe.

Severity

High for M365 migration, admin, and multi-tenant consulting workflows. This is both a usability blocker and a data-boundary safety issue.

extent analysis

TL;DR

To ensure safe and reliable Microsoft 365 connector usage, Codex should be modified to explicitly select the Microsoft account, tenant, and mailbox context being used, allowing for multiple named connections and preventing silent fallbacks to unexpected identities.

Guidance

  • Modify the Microsoft 365 connector to display the active account and tenant before making any connector calls, ensuring transparency and control.
  • Implement a feature to allow users to explicitly select the account and tenant for each connector connection, supporting multiple named connections (e.g., "Outlook - Source Tenant" and "Outlook - Destination Tenant").
  • Introduce a mechanism to target specific named connections for tool calls, ensuring that the intended account and tenant are used.
  • Develop a fail-safe mechanism that prevents the connector from silently falling back to another signed-in Microsoft account if the requested account/tenant does not match the active connector identity.

Example

No code snippet is provided due to the lack of specific technical details in the issue.

Notes

The proposed solution focuses on enhancing the Microsoft 365 connector's functionality to prioritize explicit account and tenant selection, transparency, and control. This approach aims to address the identified usability and data-boundary safety issues.

Recommendation

Apply a workaround by modifying the Microsoft 365 connector to prioritize explicit account and tenant selection, as the current implementation poses significant risks to data safety and workflow reliability.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#search optimization#API routing#API middleware#SSR setup#ISR setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING