# Microsoft 365 outage disrupts services and AI connectors Canonical: https://www.oktsec.com/radar/microsoft-365-outage-ai-connectors-november-2026 Publisher: Oktsec Language: en Published: 2026-11-12T20:41:00Z Updated: 2026-11-12T23:07:39Z Record reviewed: 2026-11-12T23:07:39Z Latest evidence check: 2026-11-12T23:07:39Z Disclosed: 2026-11-12 Microsoft expanded its availability incident to include Intune, selected Purview functions and other services. OpenAI still reports Microsoft connector errors; Anthropic confirms that most mail, calendar and search requests remain affected. ## Evidence and response priority - Category: Platform incident - Oktsec priority: Act now - Rationale: An ongoing availability incident can interrupt business workflows and leave connector actions incomplete or uncertain. Immediate attention concerns continuity and safe retries, not confirmed exploitation. - Evidence: Incident confirmed by provider - Verification: Vendor confirmed - Fix status: Not applicable - Exposure requirement: Application or configuration dependent - Vendor: Microsoft - Products: Microsoft 365, Microsoft connectors in ChatGPT, Microsoft 365 connector in Claude ## Technical overview Microsoft’s November 12, 22:11 UTC update says earlier recovery actions did not provide the expected relief. A core process was overwhelming servers, reducing available capacity. Microsoft was isolating infrastructure, restarting components and gradually reintroducing traffic; this was not a recovery confirmation. The expanded service list includes Intune, Defender for Office 365 and selected Purview functions alongside Exchange Online, Teams, SharePoint Online, Copilot, Defender XDR, Planner and To Do. Microsoft also lists intermittent Power BI exports of reports with sensitivity labels to PDF and Cloud Update, Cloud Policy and Inventory functions in the Microsoft 365 Apps admin center. The impact is specific to the operations described in the status notice, not every function of each product. OpenAI’s Microsoft connector incident remains under investigation. Its notice covers new connections and connector tools. Anthropic’s 22:23 UTC update attributes the issue to the Microsoft 365 incident: most mail, calendar and search requests still fail, and Claude for Outlook remains affected. These are availability notices. They do not establish an attack, data theft or an outage of all ChatGPT or Claude functionality. Oktsec recommends preserving uncertain operation results and checking what actually completed before retrying messages or calendar changes. Resume dependent workflows only after testing the relevant integration. ## Recommended response Check provider status and identify affected workflows. Hold repeated writes when outcomes are unknown; verify sent messages, calendar changes and pending jobs before retrying. Relevant to: Microsoft 365 administrators, operations teams and teams using Microsoft connectors in ChatGPT, Claude or automated workflows. ## Affected systems and fixes ### Microsoft 365 business and enterprise services Affected: Microsoft lists potential impact to Exchange Online, Teams, SharePoint Online, Copilot, Defender XDR, Planner, To Do, Intune, Defender for Office 365, selected Purview functions, Power BI exports with sensitivity labels and Microsoft 365 Apps admin center functions. Fixed release / action: Provider recovery in progress at the review cutoff; no customer software patch is identified in this status notice. ### Microsoft connectors in ChatGPT Affected: OpenAI reports that new connections may fail and connector tools may not work as expected. This notice does not establish an outage of all ChatGPT or API functionality. Fixed release / action: OpenAI is investigating; validate connector operations before resuming dependent workflows. ### Microsoft 365 connector in Claude and Claude for Outlook Affected: Anthropic reports failures for most mail, calendar and search requests; new connections may not complete. Claude for Outlook mail/calendar actions and opening the add-in may also fail. Fixed release / action: Anthropic is working with its upstream provider; validate operations after recovery is announced. Confirm the running version against the vendor advisory, including any distribution backports. ## Response checklist 1. **Identify dependent services and workflows** — Check Microsoft’s public status page and the OpenAI or Anthropic incident relevant to each connector. Oktsec recommends recording which mail, calendar, search and automation workflows are actually failing in your environment. 2. **Preserve operations with an unknown result** — Oktsec recommends retaining timestamps, job identifiers and errors. A timeout does not prove that a message was not sent or a calendar change was not applied; check the authoritative result before repeating the action. 3. **Pause repeated writes and use agreed alternatives** — Oktsec recommends holding automatic retries for actions that could duplicate work and using established continuity channels for urgent tasks. Avoid repeatedly reconnecting accounts or changing credentials solely because of this outage. 4. **Verify recovery before clearing the backlog** — After the relevant provider reports recovery, Oktsec recommends checking reads and writes through each affected integration, reconciling uncertain operations and resuming queued work gradually. Recovery of one service does not verify all connectors. ## Relevance to AI environments A connector error can leave an action’s outcome unknown. Oktsec recommends pausing dependent agent writes, retaining job identifiers and reconciling results before retries so failed reads do not produce misleading conclusions and repeated writes do not duplicate work. ## Sources - [Microsoft 365 service disruption: November 12, 22:11 UTC update](https://status.cloud.microsoft/) — Microsoft; Vendor notice; checked 2026-11-12T23:02:46Z - [Microsoft public status details](https://status.cloud.microsoft/api/posts/mac) — Microsoft; Vendor notice; checked 2026-11-12T23:02:46Z - [Microsoft connector incident updates](https://status.openai.com/incidents/01M78GAT3AK9P9W8Z230KHFVE8) — OpenAI; Vendor notice; checked 2026-11-12T23:03:52Z - [Microsoft connector incident updates](https://status.claude.com/incidents/sqn3fg1l96dl) — Anthropic; Vendor notice; checked 2026-11-12T23:03:52Z ## Editorial record - 2026-11-12T20:41:00Z: Added the confirmed availability incident, separate connector impacts and operational guidance with an explicit source cutoff. - 2026-11-12T23:07:39Z: Expanded the Microsoft service scope and replaced the initial recovery hypothesis with the 22:11 UTC update. Rechecked both connector notices, including Anthropic’s 22:23 UTC confirmation; recovery remains unconfirmed. ## Use this advisory in Radar Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment. [Open advisory](https://www.oktsec.com/radar/microsoft-365-outage-ai-connectors-november-2026) · [Build a response plan](https://www.oktsec.com/radar/microsoft-365-outage-ai-connectors-november-2026#review-workspace) - [AI agent review consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=microsoft-365-outage-ai-connectors-november-2026&service=agent_review) ## Scope and corrections Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure. [Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.