Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

YPO Technology Network AI Brief

YPO Technology Network AI Brief artwork

AI Vendor Risk: When Outlook Goes Down, Your Agents Go With It

Nov 16, 20266 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Microsoft's Outlook and much of Microsoft 365 went down late Thursday 12 November and were not fully restored, by Microsoft's public account, until Saturday morning 14 November. Microsoft says this was a technical issue, not a cyberattack and not AI, from a problem in an earlier network capacity upgrade that showed up after a recent network change. The CEO lesson is that agents sitting on Outlook, the calendar, and Microsoft Graph went down with that pipe. Key takeaways. Have a way to reach people that does not run through Outlook or Teams, and test it. List every mail and calendar agent and what it should do when Graph times out. A service credit is bookkeeping, not a recovery plan. Decide ahead of time how long you will wait before you fail over, knowing a DNS change can take an hour. Checklist (as spoken). You do not need to write this down while you listen. A way to reach staff and key customers that does not run through Outlook or Teams. And test it. A phone tree, a text, or a second messaging tool is enough. The test is the part most companies skip. For us, Slack covered the inside of the company. It did not cover customers. Why: most customer communication still goes through email. A short list of every agent or workflow that reads mail, sends mail, or touches the calendar through Graph. Write down what each one should do when those requests time out. Stop and alert a person. Queue the work. Or fail closed. An agent that keeps retrying in the dark is worse than an agent that stops. Why: Graph requests may time out, and an agent can keep running with nothing useful to work with. Know what the contract actually pays you when the service is down. If you are on a paid business plan, you can ask for a service credit. It is a reduction on a future bill for the service that was down. It is not automatic, and it is not payment for lost work. You have to show that your own users were hit, and you have to ask by the end of next month. Treat that as bookkeeping, not a recovery plan. If email is how you sell, book, or approve work, you need a second path, not a better invoice credit. Why: the credit will not send the stuck messages. The plan is the second path, and how long you will wait before you use it. Timeline (Dublin / US Eastern). 12 Nov, 17:54 Dublin / 12:54 p.m. ET: EX1550543 opened. 18:35 / 1:35 p.m. ET: MO1550821. 13 Nov, 16:40 Dublin / 11:40 a.m. ET: preliminary cause. 14 Nov, 06:09 Dublin / 1:09 a.m. ET: customers restored, 36 hours later. Admin-center recaps list a different Friday end time than the Saturday public post used on air. Terms. Microsoft Graph: the interface agents use for mail, calendar, and contacts. DNS failover: changing where your mail is delivered, which can take an hour. SLA credit: a future-bill reduction on the down service if you ask by the end of next month. Examples named. Our company kept a Gmail standby ready in about fifteen minutes and did not flip, because nothing critical needed it and DNS can take an hour. Bots still ran but not off incoming mail. Slack was fine. OpenAI and Anthropic Microsoft 365 connectors failed. ChatGPT Wallet launched 13 Nov. OpenAI Control Room stops research-system work within 35 seconds and fails closed. Sources: First acknowledgment; Cause statement; Saturday restoration; Wallet; Control Room. The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. AI Vendor Keys: Cursor's Breach And Why Agent Logs Are Sensitive Data

    Nov 20, 20267 minAudio

    Cursor's breach didn't start with a bug in the app. It started with an access key Cursor issued to a vendor, Fireworks. That key opened old coding-agent session logs, some still holding pasted credentials, which led...

    Credit the people on this episode

  2. AI Plumbing: Microsoft Just Ran The Pipes Through Your Tenant

    Nov 19, 20267 minAudio

    Microsoft Ignite's biggest news was plumbing: who each agent is, who it reports to, what it can touch and what it costs, built into the Microsoft 365 tenant you already pay for. Satya Nadella called Agent 365 Business...

    Credit the people on this episode

  3. AI For CEOs: Hear What The Summary Leaves Out

    Nov 18, 20266 minAudio

    Episode 200. Stephen started this show because almost nobody was talking to CEOs about AI: plenty of tabloid headlines and valuations, little on where the technology is going, what a busy CEO needs to know, and how to...

    Credit the people on this episode

  4. AI Always-On Agents: The Real Risk Is They Break Silently

    Nov 17, 20266 minAudio

    On 13 November 2026, Anthropic published a guide on agents that keep working when nobody is in the chat. Always on is the experience, not staying awake all night. The agent sleeps, wakes for a short run, saves what...

    Credit the people on this episode

  5. AI Computer Use: Connectors First, Screens Last

    Nov 14, 202613 minAudio

    Can your AI actually use your computer? Claude, ChatGPT, and Grok Bot all can, but there are four very different ways an agent touches your systems. Stephen Forte explains why legacy work still needs computer and...

    Credit the people on this episode