Booking into a Microsoft 365 tenant, including the admin consent part
The calendar connection is native. The part most vendors skip is who in your organization has to approve it, so this page starts there.
Caller
“Your office is closed, isn't it? I just need to get in front of someone about a contract renewal this month.”
What happened next
- Read free/busy across the shared bookings mailbox for the next ten working days
- Booked Thursday next week, 11am, 30 minutes, in the tenant calendar
- Flagged the call as a renewal so the account manager sees it first thing
How GreetKeeper connects to Microsoft 365
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Microsoft 365 | Writes directly |
What Microsoft 365 is doing in this setup
Microsoft 365 is the subscription behind your organization's email, calendars and files. The calendars inside it are Outlook calendars, which is why the two pages overlap.
What makes a tenant different from a personal account is governance. An administrator decides which outside apps may read calendar data, and that decision is made once for everybody.
GreetKeeper connects through Microsoft Graph with calendar permissions. Your admin sees exactly what is being asked for on the consent screen, and can withdraw it later from the Microsoft 365 admin center.
Where the booking lands
In a calendar inside your own tenant. Nothing is copied into a system you cannot audit.
Most organizations point GreetKeeper at a shared mailbox rather than an individual. A shared bookings calendar is visible to the whole reception team, and it does not break when one person leaves.
Free/busy is read before any time is spoken aloud. Rooms and resources that are booked as calendar objects block the slot the same way a person does.
The event carries the caller's name, their number and what they said they wanted. Your team opens it in Outlook and has the context without listening to anything.
Connecting it
Two of these four steps belong to your IT administrator, so start with them.
Check whether your tenant requires admin consent
Many do. If yours does, a global administrator approves the calendar permission once, and after that any nominated user can complete the connection.
Decide which mailbox holds bookings
A shared mailbox is the usual answer. Create one first if you do not have it, because moving bookings to a different calendar later means re-pointing the connection.
Authorize and select the calendar
Sign in, approve, then pick the calendar from the list GreetKeeper shows you. That list comes from your tenant, so if the mailbox is missing, permissions are the reason.
Test from a mobile, not from your desk
Call in as a customer would and book a real slot. Check it in Outlook, then remove it. Testing from a mobile also tells you how the greeting sounds on a normal phone line.
What this connection does not do
Questions about Microsoft 365 and GreetKeeper
Does GreetKeeper need a Microsoft 365 license of its own?
No. It connects as an authorized application against the mailbox you nominate, so there is no extra seat to buy on the Microsoft side.
Can we restrict it to one calendar only?
Yes, and we recommend it. Point the connection at a single shared bookings calendar, and nothing else in the tenant is touched.
How do we disconnect it?
An administrator removes the app's consent in the Microsoft 365 admin center. Access stops immediately, and the calls keep being answered without the booking step.
Bring your IT lead to the demo
We will show exactly which permission is requested and why.