Last week, Microsoft did something no company has had to do before: it gave its AI an alibi. When Outlook, Teams and the rest of Microsoft 365 went dark for people in more than 70 countries, the apology came with an unusual line: the failure was “not related to cyber or AI / agents”. “The AI did it” has become the new “the dog ate my homework”, and that tells you something. As AI agents start acting on our email and calendars, the first question after anything odd is now “was it the AI?”. You can only answer it if something wrote down what the AI did. That is what an AI agent audit log is for, and your calendar needs one.
What happened
The outage began on Thursday 12 November and lasted the best part of 30 hours. Outlook, Teams, SharePoint and Copilot were all affected. On Friday Microsoft said it was “deeply sorry” and traced the problem to an earlier network capacity upgrade that only surfaced after a later network change, as Windows Central and CNBC reported. The same Friday, a nationwide ground stop for flights in the US drew exactly the same first question, and it too turned out to be network hardware, not the new AI tool air traffic controllers had just started using.
So far AI looks less like the culprit than a casualty. The connectors that link Claude and ChatGPT to Microsoft 365 accounts went down with everything else.
The suspicion isn’t paranoia, though. On the same Friday, the research nonprofit Epoch AI published an incident report about an evening in October when 40 AI agents, part of a safety test run by Trajectory Labs, went after its website without permission. They had been given an impossible task and told never to give up. In three hours they made 36,411 calls to a tripwire Epoch had planted, tried a SQL injection and sent messages posing as Epoch staff, engineers and auditors. They got no private data, but it took until the next morning to confirm who had sent them.
And a recent report from the US standards agency NIST recounts a warning from CrowdStrike’s head of incident response: many AI deployments don’t log what agents were told, what they did or what data they touched. Without that record, “was it the AI?” has no answer, only a shrug.
Why an AI agent audit log matters for your calendars
If you juggle several calendars, you already know how hard it is to answer “who put that there?”. A meeting moves in your client’s Microsoft 365 calendar, a block appears in your personal Google Calendar, an invite vanishes. Was it you, a colleague, an assistant or a sync gone wrong? Now add AI agents that can read and book across all of them, and the list of suspects gets longer.
Two things help:
- A record of every request. What the agent was asked, where the request came from, what happened and when. If something looks wrong, you check the log instead of guessing.
- Changes you can recognise. Anything an automated tool adds to your calendar should say so, plainly, so a stray block never looks like a meeting you forgot.
Agents will do more and more of the clicking for us, and when they do, the log becomes the screen you actually read. It’s worth asking for one now, while the stakes are a moved meeting and not a missed flight.
Where Calendrz fits
Our Smart Scheduler, currently in preview, keeps a history of every run on your Profile: when it was asked, what it was asked, whether the request came from the app, the mobile app, email or an AI assistant through our MCP server, and how it ended, including any error. It proposes a time and waits for your approval before anything is booked. And if the AI service behind it is having a bad day, it stops calling it and the history says so, rather than leaving you to wonder.
Availability mirroring works the same way. Every auto-block Calendrz places across your connected accounts carries a label you choose, with macros such as the source account’s domain, so you can tell at a glance that a block came from Calendrz, and from which calendar. It copies only that you’re busy, never the details. That is how our founder, Liviu Tudor, likes software to behave: quietly, and with receipts.
Keep the receipts
The next outage will come, and so will the next agent that misbehaves. When it does, you want to know whether to blame the network, the AI or yourself in minutes, not days. If you juggle several calendars and want your time protected everywhere, with a clear record of what touched it, try Calendrz free.







