Table of Contents
Calendar Agent Struggles to Cope with Scheduling Meetings
I really want to use Copilot to help manage my calendar. For me, that’s one of the best use cases for an agentic assistant that can take useful actions on my behalf. As someone who works with teams spread from California to Ukraine, and who travels frequently for work, I am eternally hopeful that agentic tools will help me schedule, reschedule, and deconflict my personal and work schedules.
It was thus with great excitement that I started trying to use the Outlook calendar agent when it was introduced at the end of April 2026. My early experiments didn’t go well, but I reasoned that it was a new implementation and deserved some grace, and I gave the team plenty of in-app feedback via the “thumbs down” button in Copilot.
Today I decided to try again.
See, I’ve taken a long break from road cycling, and wanted to start rebuilding my aerobic cycling base by using my indoor smart trainer to ride at whatever power level keeps my heart rate steady in zone 2. That steady-state, low-intensity training is the foundation of base building. I was easily able to connect Claude to the Strava fitness application I use and then asked it to create an 8-week cycling plan for me based on all the data it had about my running, weightlifting, and other exercise over the past year.
Problem #1 is that Claude has an M365 connector that can read, but not write to, user calendars, so I couldn’t just ask Claude to schedule the workouts. Instead, I had it create a Markdown file that grouped the workouts by week and included times and intensity levels. Then I asked Copilot to add the workouts to my calendar.
A Seemingly Simple task Made Complex by the Calendar Agent
That led me to problem #2: apparently the task as prompted was too difficult:
That earned the calendar agent an immediate thumbs-down, although it did correctly parse the schedule and understood that there should have been two separate calendar appointments during week 1. “I’ll work with that,” I thought, and tried again…
One very important thing you should know: each time the Outlook agent creates a calendar item, it asks you to confirm it. It only asked for one confirmation; it turns out that’s because it scheduled both rides at the same time on Friday. Another thumbs-down, and then I tried again.
It’s odd, not to say concerning, that the agent can’t inspect the work that it just did to verify its correctness.
Trial and Error, Mostly Error
I’ll spare you the back-and-forth but here are a few representative samples of the ongoing dialog.
I thought that perhaps explicitly instructing the agent not to double- or triple-book my calendar work work better. It didn’t.
At that point, I gave up. It would be faster, and work better, for me at this point to ask Claude to write a script to use Graph to plug these appointments into my calendar instead of wasting more time asking the Outlook agent to “help” me.
Huge Investment in the Calendar Agent, But are The Results Worthwhile?
Microsoft is reputed to have spent billions of dollars on AI (including its investment in compute to run the Azure AI service family and its payments to various AI model providers). Three years later, the quality of the service remains terribly inconsistent. The summarization and Work IQ-powered features in Outlook are generally quite good, and some agents do better, like the Planner agent, but the calendar agent is clearly not ready for prime time yet.
I’ll keep trying, and giving feedback through the interface, but it’s frustrating to see such an obviously useful feature that remains so limited.
Support the work of the Microsoft 365 for IT Pros team by subscribing to the Microsoft 365 for IT Pros eBook. Your support pays for the time we need to track, analyze, and document the changing world of Microsoft 365 and Office 365. Only humans contribute to our work!