How to Use AI in Outlook Calendar for Bookings - Zian AI

How to Use AI in Outlook Calendar for Bookings

Quick answer: To use AI in Outlook calendar for bookings, connect it through Microsoft Graph or Microsoft Bookings. On Microsoft 365, the AI checks free/busy with getSchedule (up to 20 people, under 62 days) and books with Calendars.ReadWrite; app-only agents need admin consent and should be fenced with an Exchange Online RBAC scope. Outlook.com accounts cannot use getSchedule, findMeetingTimes or the Bookings API.

Every Microsoft fact here comes from Microsoft Learn, read on 30 October 2026, except the Copilot section, which uses Microsoft’s support site. For the Google version of the same job, see how to connect AI to Google Calendar for bookings. For whether a vendor’s calendar tool can reschedule, cancel and avoid double-bookings, see how deep AI agent calendar booking integrations go.

Where Zian fits in an Outlook calendar booking setup

Zian AI is the platform pick when bookings start as phone calls or messages rather than clicks on a booking page. Its agents answer inbound calls 24/7 as an AI receptionist, qualify and book, and set appointments from inbound and outbound voice, SMS, email, WhatsApp, Instagram DM and Facebook Messenger conversations, in 30+ languages, with an Appointment Show-Specialist agent for follow-up.

zian.ai says you can “Connect Zian AI to your CRM, comms, calendars, knowledge bases, and more. Use our API for custom workflows”, and names HubSpot, Salesforce, HighLevel and Zapier integrations. Its home and Features + Integrations pages do not name Outlook or Microsoft 365 as at 30 October 2026, so ask which calendar route your account will use, then run the nine checks further down. For operators who want booked appointments without running any of this, LeadsNow.ai is the done-for-you option: a pay-per-result AI appointment-setting service that runs on Zian and answers leads in under 60 seconds, 24/7. Zian is in a partnership-application beta.

Outlook.com or Microsoft 365: which account are you connecting?

The first decision is the account type, because Microsoft Graph supports far less for a personal Outlook.com account than for a Microsoft 365 work or school account. Microsoft’s calendar API overview says most calendar features apply to both, but it marks free/busy lookup and findMeetingTimes as work or school only. Microsoft’s permissions overview adds that “not all” delegated permissions are valid for personal Microsoft accounts.

What the AI needs Personal Microsoft account (Outlook.com) Microsoft 365 work or school account Microsoft source
Read events in a date range (calendarView) Yes, Calendars.ReadBasic Yes, Calendars.ReadBasic List calendarView
Free/busy for one or more people (getSchedule) Not supported Yes, delegated or application calendar: getSchedule
Suggested meeting times (findMeetingTimes) Not supported Delegated only; application not supported user: findMeetingTimes
Create the booking (create event) Yes, Calendars.ReadWrite Yes, delegated or application Create event
Book without a signed-in user (application permissions) No tenant administrator to consent Yes, after admin consent Permissions overview
Microsoft Bookings API Not supported Shared bookings only Bookings API overview

The practical rule: on Outlook.com, an AI can only read events with calendarView, work out the gaps itself and create the event. Other people’s availability, app-only access and Microsoft Bookings all need a Microsoft 365 tenant.

How to use AI in Outlook calendar for bookings: the three ways in

There are three ways for an AI booking tool to reach an Outlook calendar, and the route decides who must consent, what the app can touch, and which Microsoft limits apply. Microsoft’s permissions overview says application permissions “are highly privileged” and that “the delegated permission model is the recommended approach whenever it meets the application’s requirements.”

Route Who grants access Fits when Microsoft’s catch
1. Delegated access (a person signs in) The calendar owner, unless tenant consent policy or the permission requires an administrator One or a few calendars; the only route for Outlook.com; the only route that can call findMeetingTimes The app “can’t access anything the signed-in user couldn’t access”; refresh tokens default to 90 days, or 24 hours for single-page apps
2. Application access (no one signed in) A Privileged Role Administrator or Global Administrator consents once for the tenant An in-house or vendor agent booking into many staff calendars inside one Microsoft 365 tenant Calendars.ReadWrite as an application permission covers “all calendars” until you scope it with Exchange Online RBAC for Applications
3. Microsoft Bookings as the booking layer An administrator sets up a shared Bookings calendar; the app gets Bookings permissions You want services, staff, business hours, buffers and lead times enforced by Bookings rather than by the AI’s prompt The Graph API “applies only to shared bookings”; app-permission writes must follow the business rules

Copilot in Outlook is not on that list: it schedules your own meetings, not callers’ (see its section below).

Your day-one setup, whichever route you pick:

  1. Confirm the account type: an Outlook.com address or a Microsoft 365 work or school mailbox.
  2. Write down the one calendar the AI books into and every mailbox whose free/busy should block a booking.
  3. Pick delegated or application access, then choose the narrowest permissions from the chooser below.
  4. Register the app in Microsoft Entra ID (or connect the vendor’s app) and get the right person to consent.
  5. For application access, scope the app to named mailboxes with RBAC for Applications and remove the unscoped tenant grant.
  6. Run the nine-check connection test before the AI talks to a customer.

You are finished when a test booking lands on the right calendar at the right local time, a retried request creates one event rather than two, the app is refused on a mailbox outside its scope, and a revoked connection makes the AI hand over to a person instead of confirming a booking that does not exist.

Which Microsoft Graph permission does an AI booking agent need?

An AI booking agent needs two things from Microsoft Graph: read availability, and write one event. Microsoft’s Graph permissions reference lists eight permissions whose names start with “Calendars.” as at 30 October 2026 (two of them, Calendars.Read.All and Calendars.ReadWrite.All, cover work hours and locations rather than events), and each Graph API page names the least privileged one for that call. The chooser below maps each booking job to Microsoft’s own least-privileged choice.

What the AI needs to do Delegated (signed-in user) Application (no user) Admin consent by default? Microsoft source
Read events in a range on the user’s own calendar Calendars.ReadBasic (also personal accounts) Calendars.ReadBasic.All (listed as Calendars.ReadBasic on the calendarView page) Delegated no; application yes List calendarView
Free/busy for staff, rooms or distribution lists (getSchedule) Calendars.ReadBasic Listed as Calendars.ReadBasic on the getSchedule page Delegated no; application yes calendar: getSchedule
Suggested times across attendees (findMeetingTimes) Calendars.Read.Shared Not supported No user: findMeetingTimes
Create, move or cancel bookings on the user’s own calendars Calendars.ReadWrite: “Have full access to user calendars” Calendars.ReadWrite: “Read and write calendars in all mailboxes” Delegated no; application yes Create event
Book into a calendar shared or delegated to the signed-in user Calendars.ReadWrite.Shared No application form No Permissions reference
Create appointments in a shared Bookings calendar BookingsAppointment.ReadWrite.All (work accounts only) BookingsAppointment.ReadWrite.All Delegated no; application yes Create bookingAppointment
Not needed for booking Bookings.Manage.All Bookings.Manage.All Delegated no; application yes Permissions reference

Least privilege for an AI receptionist booking one person’s own Outlook calendar is Calendars.ReadWrite, delegated, on its own: the getSchedule and calendarView pages list Calendars.ReadWrite as a higher privileged option, so it already covers reading availability, and adding Calendars.ReadBasic grants nothing extra. Microsoft’s create-event page lists only Calendars.ReadWrite, so the write grant always covers the whole calendar, which is why Microsoft’s scoping tools matter.

One documentation inconsistency to know about: the getSchedule page lists the application permission as Calendars.ReadBasic, while the permissions reference names the application form Calendars.ReadBasic.All, “Read basic details of calendars in all mailboxes”. Microsoft’s older free/busy guide, last updated 7 November 2024, still says getSchedule’s least privileged permission is Calendars.Read. For app-only free/busy, Calendars.ReadBasic.All is the narrowest named grant, but it is tenant-wide, and RBAC for Applications has no ReadBasic role to scope it (see the next section). A booking agent scoped with Application Calendars.ReadWrite needs no separate read grant, because the getSchedule page lists Calendars.ReadWrite as a higher privileged option. If a Calendars.ReadBasic.All call is rejected, move up to Calendars.Read, the next permission on the getSchedule page.

On consent, Microsoft’s user-consent page says “by default, all users are allowed to consent to applications for permissions that don’t require administrator consent”, and recommends allowing it only for apps from a verified publisher. If your tenant has limited user consent, a staff member who clicks Connect is stopped at an approval request. Microsoft’s permissions overview says only a Privileged Role Administrator or Global Administrator can consent to application permissions.

How to restrict an app-only booking agent to named mailboxes

Application access with Calendars.ReadWrite lets an app “create, read, update, and delete events of all calendars without a signed-in user”, so a booking agent with that grant can reach the chief executive’s calendar as easily as the sales team’s. Exchange Online’s RBAC for Applications is Microsoft’s current way to fence it in. Microsoft says this feature “replaces Application Access Policies”, and the New-ApplicationAccessPolicy cmdlet page now says “Don’t create new App Access Policies”. Microsoft’s permissions reference still says administrators “can configure application access policy” to limit calendar access, so expect to see both terms.

The setup Microsoft documents, using Exchange Online PowerShell as a member of the Organization Management role group:

  1. Create a scope for the bookable mailboxes, either a management scope with a recipient filter or a Microsoft Entra administrative unit.
  2. Create an Exchange pointer to the app’s service principal with New-ServicePrincipal, using the app’s application ID and its service principal object ID; Microsoft warns “Don’t use the IDs from the App Registrations page, as it shows different values.”
  3. Assign the role, for example New-ManagementRoleAssignment -App <ObjectID> -Role "Application Calendars.ReadWrite" -CustomResourceScope "Bookable staff".
  4. Remove the unscoped Calendars.ReadWrite application grant from Microsoft Entra ID.
  5. Test with Test-ServicePrincipalAuthorization -Identity <AppID> -Resource <mailbox>, which reports InScope true or false for each permission.

These are Microsoft’s documented cmdlets; we have not run them against a tenant. Step 4 is the one people miss. Microsoft’s FAQ says the two grants are “a union operation”, and its example is that an unscoped Microsoft Entra grant plus a scoped RBAC grant of the same permission “results in no effective resource scoping”. Permission changes also sit in a cache “between 30 minutes and 2 hours”. Microsoft says the test command bypasses this cache, but live booking calls do not, so a real API call straight after a change can still reflect the old permissions. RBAC for Applications offers “Application Calendars.Read” and “Application Calendars.ReadWrite” roles; there is no ReadBasic role in the list, so a scoped free/busy-only app uses Application Calendars.Read.

getSchedule or findMeetingTimes: which availability call should the AI use?

For an AI that books callers into staff calendars, getSchedule is usually the right call, because it works app-only and returns raw busy blocks the AI can apply its own rules to. findMeetingTimes adds Microsoft’s own scoring but needs a signed-in user. Microsoft’s comparison page puts it plainly: findMeetingTimes “supports only delegated scenarios”, while getSchedule “supports both delegated and app-only scenarios.”

Question getSchedule findMeetingTimes
What it returns Busy items, working hours and an availabilityView string: 0 free or working elsewhere, 1 tentative, 2 busy, 3 out of office Ranked suggestions, each with a confidence from 0 to 100%, or an emptySuggestionsReason
Access types Delegated and application (work or school only) Delegated only (work or school only)
Least privileged permission Calendars.ReadBasic Calendars.Read.Shared
Size limits Up to 20 users or resources; a period under 62 days; slot interval default 30 minutes, minimum 5, maximum 1,440 Default meeting length 30 minutes; default minimum attendee confidence 50%
Default hours searched The whole period you ask for Work hours: “Monday to Friday, 8am to 5pm” in the mailbox’s time zone unless the user changed them
Time zone of the response UTC unless you send Prefer: outlook.timezone UTC unless you send Prefer: outlook.timezone
Microsoft’s warning Assumes time with no events is free; over 1,000 entries returns error 5006 Results “may differ over time” even when inputs do not change

findMeetingTimes scores a slot by averaging each attendee’s chance of attending: 100% if free, 49% if unknown, 0% if busy. Microsoft’s own example of one free, one unknown and one busy attendee works out at (100 + 49 + 0) / 3 = 49.66%. Microsoft tests that example against an 80% minimum; it also falls below the 50% default, so with default settings that slot is not suggested.

The getSchedule warning matters more for bookings. Microsoft says it “assumes the remaining time in that time period to be free”, and that if it “cannot identify a specified user or resource, it returns a single schedule item and indicates the error.” Read each scheduleInformation’s error field before trusting a gap: a calendar the app could not read must count as “unknown”, never “free”. Here is a getSchedule body for one staff member on Tuesday 10 November 2026, with the response asked for in Sydney time:

POST https://graph.microsoft.com/v1.0/users/{booking-mailbox}/calendar/getSchedule
Prefer: outlook.timezone="Australia/Sydney"
Content-Type: application/json

{
  "schedules": ["[email protected]"],
  "startTime": { "dateTime": "2026-11-10T09:00:00", "timeZone": "Australia/Sydney" },
  "endTime":   { "dateTime": "2026-11-10T17:00:00", "timeZone": "Australia/Sydney" },
  "availabilityViewInterval": 15
}

With a 15-minute interval, the 9am to 5pm window returns a 32-character availabilityView, one digit per slot. A 2pm, 30-minute booking is free only if the two digits for 2:00 and 2:15 are both 0.

Creating the booking: the event request, time zones, retries and a Teams link

The booking itself is one POST to the calendar’s events collection, and Microsoft documents three behaviours an AI booking tool must handle. First, invitations: Microsoft says that when an event includes attendees, “the server sends invitations to all attendees” and this “can’t be configured”. There is no option to stay silent, so add the caller as an attendee only when you mean to email them.

Second, retries. The event’s transactionId is “a custom identifier specified by a client app for the server to avoid redundant POST operations in case of client retries”, aimed at a client that times out before it hears back. Generate one per booking attempt and reuse it on every retry of that attempt.

Third, time zones. start and end are dateTimeTimeZone values, a local date-time plus a zone name. Microsoft accepts Windows zone names and a published list that includes Australia/Sydney, Australia/Brisbane, Australia/Adelaide, Australia/Darwin, Australia/Hobart and Australia/Perth, but warns that “methods such as create or update might not support all” of them. Australia/Melbourne is not on that list, so call GET /me/outlook/supportedTimeZones once to see the names the mailbox accepts. Microsoft lists that call as delegated only (User.Read; application access not supported), so an app-only agent needs a signed-in user to run it once.

POST https://graph.microsoft.com/v1.0/users/{booking-mailbox}/calendar/events
Prefer: outlook.timezone="Australia/Sydney"
Content-Type: application/json

{
  "subject": "Consultation (booked by AI receptionist)",
  "start": { "dateTime": "2026-11-10T14:00:00", "timeZone": "Australia/Sydney" },
  "end":   { "dateTime": "2026-11-10T14:30:00", "timeZone": "Australia/Sydney" },
  "showAs": "busy",
  "allowNewTimeProposals": false,
  "isOnlineMeeting": true,
  "onlineMeetingProvider": "teamsForBusiness",
  "transactionId": "5b0c2f9e-7d41-4a8e-9f3a-2c6d1e8b4a70"
}

Set allowNewTimeProposals to false: Microsoft’s default is true, which lets an invitee propose a different time. showAs takes free, tentative, busy, oof, workingElsewhere or unknown; setting busy makes the booking block the slot for the next getSchedule.

The two online-meeting lines add a Teams link. Microsoft says the calendar must support the provider (check the calendar’s allowedOnlineMeetingProviders), Teams comes “as part of a Microsoft 365 business or enterprise suite”, and once a meeting is online “you cannot change the onlineMeetingProvider property, nor set isOnlineMeeting to false”. Read the join link from onlineMeeting.joinUrl; Microsoft says onlineMeetingUrl “will soon be deprecated”. On a personal Outlook.com calendar, check allowedOnlineMeetingProviders before you promise callers a link.

Microsoft Bookings as the booking layer, and its Graph API

Microsoft Bookings is Microsoft’s own booking-page product, and an AI can book through it instead of writing raw calendar events. Bookings then enforces services, staff, business hours and buffers. Microsoft’s Bookings page lists it in Office 365 A3, A5, E1, E3, E5, F1, F3, G1, G3 and G5, and in Microsoft 365 A3, A5, E1, E3, E5, F1, F3, Business Basic, Business Standard, Business Premium, Teams Essentials and Teams Premium. The Graph API overview’s setup steps start with a Microsoft 365 Business Premium subscription, so check your plan against both pages before you build.

Two Microsoft rules shape what an AI can do with Bookings. The Graph API “applies only to shared bookings” and “is not applicable for personal bookings”, so a personal booking page cannot be driven through Graph. And for apps using application permissions, Microsoft says writes “must adhere to business rules”: no appointment outside business hours, the same duration as the service, minimum and maximum lead times, and allowStaffSelection set to true before the app names a staff member. Pre- and post-buffers are added to the staff calendar entry.

Bookings job Graph call Least privileged permission Account types
Check staff availability POST /solutions/bookingBusinesses/{id}/getStaffAvailability Bookings.Read.All (application only; delegated not supported) Work or school tenant
Create the appointment POST /solutions/bookingBusinesses/{id}/appointments BookingsAppointment.ReadWrite.All Delegated (work or school) or application; personal accounts not supported
Read appointments in a date range GET /solutions/bookingBusinesses/{id}/calendarView Bookings.Read.All Delegated (work or school) or application; personal accounts not supported
Change services, staff or the business bookingService, bookingStaffMember, bookingBusiness Bookings.ReadWrite.All or Bookings.Manage.All Not needed by a booking agent

The narrowest Bookings set for an AI receptionist is BookingsAppointment.ReadWrite.All, which Microsoft describes as reading and writing appointments and customers while only reading businesses, services and staff. Microsoft’s Bookings page adds that an appointment booked as an online meeting “creates a unique meeting link” in Teams.

Want the bookings without the plumbing? Zian AI answers inbound calls 24/7 as an AI receptionist and books appointments from calls and messages. Apply For Partnership

Outlook and Bookings throttling limits, and the errors that break a connection

Microsoft publishes per-mailbox throttling limits for Outlook, and an AI that re-polls availability in a loop reaches them sooner than one that books. The Outlook service allows 10,000 API requests in a 10-minute period and four concurrent requests for each app and mailbox pair, and Microsoft says “exceeding the limit for one mailbox doesn’t affect the ability of the application to access another mailbox.” The Bookings service allows four concurrent requests for each app and booking mailbox pair. At two requests per booking (one getSchedule, one create), 10,000 requests in 10 minutes is 5,000 bookings into one mailbox, so the four-concurrent-request cap is the limit to design around when several calls book into the same calendar at once.

Symptom in the AI tool Microsoft’s response What Microsoft says it means Fix
Bookings fail at busy times 429 Too Many Requests with Retry-After Throttled; Microsoft says waiting the Retry-After delay “is the fastest way to recover” Wait the stated seconds; cap parallel calls per mailbox at four
Access denied on a mailbox 403 Forbidden “The user does not have enough permission or does not have a required license” Check the RBAC scope with Test-ServicePrincipalAuthorization, the permission, and the mailbox licence
A busy day shows as free getSchedule item with an error The user or resource could not be identified Treat as unknown; fix the address
A long free/busy window fails Response code 5006 A time slot “contains more than 1000 entries” Shorten the window
Worked for weeks, then sign-in fails Refresh token rejected Refresh tokens expire after their lifetime and “can be revoked by the sign-in service at any time” Send the owner back through sign-in; alert a person

Microsoft’s throttling guidance adds that requests in a JSON batch “are evaluated individually against throttling limits”, so a batch can return 200 while some of its bookings failed with 429. Check every response inside the batch.

Copilot in Outlook: what it schedules and what it does not

Copilot in Outlook schedules meetings for the person using Outlook; it is not a way for customers or an outside AI agent to book into your calendar. Microsoft’s support page for Outlook for Microsoft 365 describes “Chat Assisted Scheduling”: you type a request such as a 30-minute Teams meeting, and “Copilot in Outlook will check the calendars of all the attendees and recommend a mutually convenient time to meet.”

In new Outlook, “Schedule with Copilot” turns an email thread into a draft invitation with a title, agenda and attendees. Microsoft notes this “is only available if you have a Microsoft Copilot (Work) license”. We found no Microsoft Learn page on these features as at 30 October 2026. For choosing between an assistant like Copilot, a booking page and an AI receptionist, see how to use AI to schedule appointments.

The Outlook booking connection test: nine checks before launch

The nine-check Outlook booking connection test proves the Microsoft connection itself, before you test the conversation. Run it with a test mailbox; any result other than the expected one points to a setting, not the AI’s prompt.

# Check How to run it Expected result Microsoft source
1 Account type matches the route Sign in with the account the AI will use A work or school account for getSchedule, findMeetingTimes, application access or Bookings Calendar API overview
2 Consent shows only what you chose Connect with a fresh test user, then open the app’s Permissions page under Security in Enterprise applications Only the calendar permissions in your chooser row; no Bookings.Manage.All Grant admin consent
3 Scope holds (application access) Run Test-ServicePrincipalAuthorization on one in-scope and one out-of-scope mailbox InScope true, then false; a booking call to the out-of-scope mailbox is refused RBAC for Applications
4 No leftover tenant grant List the app’s application permissions in Microsoft Entra ID No unscoped Calendars.ReadWrite left beside the RBAC assignment RBAC for Applications
5 Busy time is seen Put a busy event in the slot, then ask the AI for it Slot refused; availabilityView shows 2 for that slot and no error Get free/busy schedule
6 Time zone survives Book 2pm Tuesday 10 November 2026 on a Sydney calendar Event reads 2:00 pm in Outlook for a Sydney user; the API returns UTC unless the Prefer header is sent dateTimeTimeZone
7 A retry does not double-book Force a timeout and let the tool resend with the same transactionId One event on the calendar event resource
8 Teams link and invitation arrive Book with a test caller as attendee One invitation with an onlineMeeting.joinUrl; event shows as busy Online meetings
9 Revoked access fails safely Remove consent or revoke the user’s sessions, then try to book Booking fails visibly; the AI takes a message or hands to a person and never confirms a booking it did not make Refresh tokens

Check 4 matters most to an IT team: a leftover tenant grant leaves the app able to reach every calendar. Check 9 is the one that matters most to a caller: a disconnected calendar should produce a message or a call-back, not a confident “you’re booked”. If you are also putting a voice agent on your Microsoft phone system, see connecting an AI voice agent to Microsoft Teams Phone.

Ready to have calls and messages booked for you? Zian AI books from voice, SMS, WhatsApp, Instagram and Messenger conversations, in 30+ languages. Apply For Partnership

Frequently asked questions

How do I use AI in Outlook calendar for bookings?

Connect the AI to Microsoft Graph. On a Microsoft 365 work account it reads free/busy with getSchedule, then creates the event with Calendars.ReadWrite, sending a transactionId so a retry does not double-book. Use delegated access for one person’s calendar, or application access with admin consent and an Exchange Online RBAC scope for many staff calendars.

What Microsoft Graph permission does an AI booking agent need for Outlook?

Usually one: Calendars.ReadWrite, which creates the booking and also reads availability, because Microsoft lists it as a higher privileged option for getSchedule. Calendars.ReadBasic on its own suits a read-only tool. Use Calendars.ReadWrite.Shared only when the booking calendar is shared or delegated to the signed-in user. Microsoft’s getSchedule reference lists Calendars.ReadBasic as its least privileged permission, and the create event reference lists only Calendars.ReadWrite.

Can an AI book into a personal Outlook.com calendar?

Yes, but with less to work with. A personal Microsoft account can read events with calendarView and create events with Calendars.ReadWrite, but Microsoft marks getSchedule, findMeetingTimes and the Bookings API as not supported for personal accounts. The AI must work out free slots from the events it reads.

How do I stop an AI booking app from reaching every mailbox in Microsoft 365?

Use RBAC for Applications in Exchange Online: create a management scope or administrative unit for the bookable mailboxes, assign the Application Calendars.ReadWrite role to the app with that scope, and remove the unscoped grant in Microsoft Entra ID. Microsoft’s RBAC for Applications page says the two grants are a union, and that changes can take 30 minutes to 2 hours to apply.

Should my AI use getSchedule or findMeetingTimes?

Use getSchedule for an AI receptionist or any app running without a signed-in user. It supports app-only access, covers up to 20 people or rooms, and returns raw busy blocks. findMeetingTimes ranks suggested times but supports only delegated access, so it fits an assistant acting for one signed-in person.

Can Copilot in Outlook take bookings from customers?

No. Copilot in Outlook helps the person using Outlook schedule their own meetings: it checks attendees’ calendars and suggests a time, and Schedule with Copilot drafts an invitation from an email thread. Microsoft says Schedule with Copilot needs a Microsoft Copilot (Work) licence. Bookings from callers or customers need an AI connected through Microsoft Graph or Microsoft Bookings.

Can an AI book appointments through Microsoft Bookings?

Yes, for shared Bookings calendars in a Microsoft 365 tenant. The AI creates appointments through the Bookings Graph API with BookingsAppointment.ReadWrite.All, and an app using application permissions must follow the calendar’s business rules, such as business hours, service duration and lead times. Microsoft says the API does not apply to personal bookings, and personal Microsoft accounts are not supported.

Where every figure on this page comes from

Figure Who published it Link Date read
8 Calendars.* permissions; consent defaults; personal-account availability Microsoft Learn (Graph) Permissions reference 30 October 2026
Only Privileged Role Administrator or Global Administrator consent to application permissions Microsoft Learn (Graph) Permissions overview 30 October 2026
getSchedule: least privileged permission; personal accounts not supported; interval 30 default, 5 minimum, 1,440 maximum; 1,000 entries (5006) Microsoft Learn (Graph) calendar: getSchedule 30 October 2026
getSchedule: 20 entities, under 62 days; availabilityView 0 to 3; Calendars.Read (page updated 7 November 2024) Microsoft Learn (Graph) Get free/busy schedule 30 October 2026
findMeetingTimes: 30-minute default; 50% default confidence; 100%, 49%, 0%; 49.66% example; 8am to 5pm work hours Microsoft Learn (Graph) user: findMeetingTimes 30 October 2026
Create event: Calendars.ReadWrite; invitations cannot be configured Microsoft Learn (Graph) Create event 30 October 2026
transactionId, allowNewTimeProposals default, showAs values Microsoft Learn (Graph) event resource type 30 October 2026
Calendar time zone list (Australia/Sydney and others) Microsoft Learn (Graph) dateTimeTimeZone 30 October 2026
RBAC for Applications: union with Entra grants; 30 minutes to 2 hours cache Microsoft Learn (Exchange) RBAC for Applications 30 October 2026
App Access Policies replaced; do not create new ones Microsoft Learn (Exchange PowerShell) New-ApplicationAccessPolicy 30 October 2026
Bookings subscriptions list Microsoft Learn (Microsoft 365) Microsoft Bookings 30 October 2026
Bookings API: shared bookings only; Business Premium setup step Microsoft Learn (Graph) Bookings API overview 30 October 2026
Bookings appointment permissions Microsoft Learn (Graph) Create bookingAppointment 30 October 2026
getStaffAvailability: Bookings.Read.All, application only Microsoft Learn (Graph) getStaffAvailability 30 October 2026
Outlook: 10,000 requests per 10 minutes, 4 concurrent per app and mailbox; Bookings: 4 concurrent Microsoft Learn (Graph) Service-specific throttling limits 30 October 2026
Refresh tokens: 90 days default, 24 hours for single-page apps Microsoft Learn (Entra) Refresh tokens 30 October 2026
Copilot Chat Assisted Scheduling: 30-minute Teams meeting example Microsoft Support Schedule a meeting using Copilot 30 October 2026
Schedule with Copilot needs a Microsoft Copilot (Work) licence Microsoft Support Create a meeting agenda with Copilot in Outlook 30 October 2026
5,000 bookings per mailbox per 10 minutes (10,000 requests at 2 per booking); 32-slot availabilityView (8 hours at 15 minutes) Zian calculation from Microsoft’s published figures Service-specific throttling limits 30 October 2026

Related Blogs

Related from Zian AI