Setup guide
Microsoft 365 setup
kailenty runs on top of Microsoft 365, so your calendars stay the source of truth and there is nothing new to keep in sync. This guide connects Outlook and Exchange, turns on Teams meeting links, and walks an administrator through the Microsoft Entra ID app registration and consent.
Before you start
Requirements
- A Microsoft 365 account on a business or enterprise plan, with Outlook or Exchange Online calendars.
- A Microsoft 365 administrator (a Global Administrator, or someone with rights to grant app consent) available for the one-time approval.
- A Teams licence on any account that should generate Microsoft Teams meeting links.
- Permission, under your own policies, to connect a third-party scheduling app to your tenant.
You do not need to migrate any data. kailenty reads availability from the calendars you already keep in Microsoft 365 and writes confirmed bookings back to them.
Step by step
Connect your calendar
- 1
Open your workspace and start the Microsoft connection
From your kailenty workspace settings, choose to connect Microsoft 365. kailenty redirects you to Microsoft to sign in. - 2
Sign in with your Microsoft 365 account
Authenticate with the work account whose calendar you want to use. Microsoft, not kailenty, handles the password and any multi-factor prompts. - 3
Review and approve the access kailenty requests
Microsoft shows the permissions kailenty is asking for. They are listed in full under Permissions kailenty requests. Approve to continue. If your tenant requires administrator approval, you will be told an admin needs to consent first. - 4
Confirm the calendar is live
Back in kailenty, your calendar now appears as connected. Availability is read from it immediately, and confirmed bookings will be written back to it.
For administrators
App registration and admin consent
kailenty connects to Microsoft 365 as a registered application in Microsoft Entra ID (formerly Azure AD). For most tenants, the consent prompt during the connection step is all that is needed — an administrator approves the requested permissions once, on behalf of the organisation, and users can then sign in normally.
If your tenant restricts user consent for third-party apps — a common, sensible default — the first connection will require an administrator. Here is what that involves.
- 1
An administrator starts the connection
Have a Global Administrator (or a role permitted to grant tenant-wide consent) run the connection flow, or open the admin consent prompt kailenty surfaces when a user is blocked. - 2
Grant consent for the organisation
On the Microsoft consent screen, choose to consent on behalf of your organisation. This registers kailenty as an enterprise application in your tenant with the permissions shown. - 3
Confirm the app in Microsoft Entra
In the Microsoft Entra admin centre, under Enterprise applications, kailenty now appears. From there an administrator can review the granted permissions, see which users have signed in, and revoke access at any time. - 4
Let your team sign in
Once consent is granted, individual users connect with their own Microsoft accounts without seeing the consent prompt again.
Granting consent does not give kailenty a password or standing access to your whole tenant. It authorises the specific permissions below, scoped to the accounts that sign in, and you can withdraw it from Microsoft Entra whenever you choose.
What and why
Permissions kailenty requests
kailenty asks for the narrowest set of Microsoft Graph permissions that lets it read availability, write bookings, and create Teams links. Each one maps to a feature you can see.
- Read calendar availabilityread
Works out free and busy time from Outlook and Exchange so only genuinely open slots are offered.
- Read your profile and emailread
Identifies the signed-in user and the workspace they belong to, and addresses calendar invites correctly.
- Create and update calendar eventswrite
Writes each confirmed booking back to the host calendar, and updates or cancels it when a meeting changes.
- Create Teams meetingswrite
Generates a Microsoft Teams join link for bookings set to meet over Teams.
- Receive change notificationsread
Subscribes to calendar webhooks so availability stays current when events change outside kailenty.
The exact Microsoft Graph permission names are shown on the consent screen and remain visible in Microsoft Entra. kailenty never asks for access it does not use.
Conferencing
Teams meeting links
When a booking is set to meet over Microsoft Teams, kailenty creates a Teams meeting on the host’s calendar and includes the join link in the confirmation, the calendar invite, and any updates or reminders that follow.
Teams links require a Teams licence on the host account. Bookings set to meet in person or by phone carry the location you choose instead of a Teams link. Reschedules and cancellations update the Teams meeting along with the calendar event, so the link a guest holds always points at the current meeting.
Good to know
Tenant configuration notes
One tenant, one source of truth
kailenty reads and writes the Microsoft 365 calendars in the tenant you connect. It does not maintain a second calendar — Microsoft 365 stays authoritative.
Conditional access still applies
Sign-in runs through Microsoft, so your conditional access, multi-factor, and device policies apply exactly as they do for any other Microsoft 365 sign-in.
Shared and room calendars
Where a host can see free/busy for shared mailboxes or room calendars in Microsoft 365, that availability can inform scheduling. Access follows your existing Microsoft 365 permissions.
Revoke any time
An administrator can revoke kailenty from Microsoft Entra. Access to read and write calendars stops immediately when consent is withdrawn.
When something is off
Troubleshooting
The connect step says an administrator is required.
Some Microsoft 365 tenants require an administrator to approve third-party apps before any user can grant access. Ask a Global Administrator or Privileged Role Administrator to complete the consent prompt once for the workspace. After that, individual users can sign in without seeing it again.
Times look wrong or slots appear outside my working hours.
Check the timezone on your availability and that your Outlook calendar shows free/busy correctly for the period in question. kailenty offers slots from the intersection of your availability rules and your real calendar, so a stray all-day event or a mismatched timezone is usually the cause. Setting hours, buffers, and overrides is covered in the implementation guide.
Bookings are confirmed but no Teams link appears.
Teams links are only created when a booking is set to meet over Teams and the account is licensed for Teams. Confirm the meeting location is Teams rather than in-person or phone, and that the signed-in user has a Teams licence in Microsoft 365. In-person and phone meetings deliberately carry no join link.
A user cannot sign in even though others can.
Only active accounts can connect. A user who is pending, disabled, or outside the consented tenant is turned away at sign-in. Confirm the account is active in your workspace and that it belongs to the Microsoft 365 tenant you granted consent for.
We need to review exactly what kailenty can access.
The permissions kailenty requests are listed on this page and are visible in your Microsoft Entra admin centre under Enterprise applications, where an administrator can review the granted permissions and revoke access at any time. Revoking access stops kailenty from reading or writing calendars immediately.
Connected, and ready to roll out?
With Microsoft 365 connected, the next step is configuring availability and routing for your team. The implementation guide covers a phased rollout, round-robin pools, and adoption. If consent or sign-in is giving you trouble, write to us — a real person will help.
More resources