Sam selected the recommended follow-up to reconnect or refresh the Codex Teams connector token after the ChatGPT enterprise app was granted the missing Graph scopes.
Team.ReadBasic.All, Channel.ReadBasic.All, and ChannelMessage.Send._validate_write_target against the known Intake Alerts Team/channel IDs. This returned can_post_directly: true._resolve_team, _list_channels, and _resolve_channel still returned 403 with the old token scope list.The live website Teams alert is not blocked by this connector issue. The website alert uses the Power Automate webhook and is covered by the daily health check. The only remaining issue is the Codex Teams connector discovery token, which still lacks the new scopes during name-based resolution.
The remaining definitive connector test would call _send_channel_message to the known Intake Alerts IDs. If the connector has the send scope, that will post a real message in the live Teams channel. Because that is a live third-party communication, the next agent should ask for action-time approval before sending. Suggested harmless message: Connector health test: Codex Teams connector can post to Intake Alerts after Graph permission refresh.
If Sam approves the test message, send it with team_id=2effd266-ac77-42e9-bfd8-d16eeda6220c and channel_id=19:hPATasUw4lsUNvGzjPbMTK0zxfK2M2zU3bBXpFdTHHU1@thread.tacv2. If it succeeds, record that direct posting works while discovery may need a full connector reconnect. If it fails with the old scope list, the only remaining path is reconnecting the Microsoft Teams connector through the ChatGPT/Codex connector UI.
Sam approved running the test immediately. The Teams connector successfully sent the health-test message to Intake Alerts.
1781444011707/teams/2effd266-ac77-42e9-bfd8-d16eeda6220c/channels/19:hPATasUw4lsUNvGzjPbMTK0zxfK2M2zU3bBXpFdTHHU1@thread.tacv2/messages/1781444011707_resolve_team and _list_channels now work for Intake Alerts.run-teams-connector-health-test was deleted after the immediate successful run.