Announcements
Let's revisit how scheduling assistant works in Outlook: In Outlook/Exchange, free/busy information is exposed through Microsoft Graph / Exchange Web Services. By default, within the same organization (tenant), users can see each other’s free/busy slots without needing explicit sharing. That’s why Scheduling Assistant “just works” inside your company/organization.
MCP Agent's attitude is bit different! The MCP Calendar server needs permission tokens to access a user’s calendar. If the invitee is in your tenant and has not restricted free/busy visibility, you can query their availability. If they are external (outside your org) or have locked down permissions, you’ll get the “not shared” message.
These are the steps we need to be mindful:
Same-tenant users: Let's make sure your MCP Calendar server is connected with organizational credentials (via Microsoft Graph). Then you can query free/busy without explicit sharing, just like Scheduling Assistant.
Cross-tenant or external users: They must share their calendar or accept the invite before you can see availability. MCP cannot override Outlook’s permission model.
Integration pattern Should be
Use Contact MCP to resolve invitee addresses.
Use Calendar MCP (with Graph API) to call findMeetingTimes or getSchedule.
If the API returns “not shared,” fall back to proposing times and letting the invitee confirm.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Vish WR 238
Valantis 238
Romain The Low-Code... 212 Super User 2026 Season 1