Outlook Calendar
The Outlook Calendar integration shows your employees’ approved time off in their Outlook (Microsoft 365 / Exchange Online) calendars, so colleagues booking a meeting can see that someone is away. Every entry says only “Out of office” — so colleagues see that someone is away, never why.
Like the Google Calendar integration, it syncs no employee data and works on each person’s own calendar. Each employee connects their own work Microsoft account. If your organisation prefers that nobody has to connect, mTime can instead reach every employee’s calendar through your own app registration — see Tenant-wide access below.
What it does
Shows approved time off in Outlook. When time off is approved, mTime adds an all-day entry to the employee’s calendar, shown as Away (out of office), covering the days they take in full. When the time off is cancelled or moved, mTime removes or moves the entry.
Never says why. Every entry is titled “Out of office” in the employee’s language, whatever kind of time off it is — sick leave included. It never contains the type of time off, the reason the employee wrote, or the manager’s note, and the entry has no description, attendees or reminder.
Changes in Outlook stay as the employee made them. mTime updates the entry when the time off is approved, changed or cancelled in mTime. It does not check the calendar afterwards, so an entry the employee deletes or moves in Outlook is not restored. mTime only ever touches the entries it created itself, and never declines or cancels a meeting.
Pre-fills timesheets from finished meetings, exactly as with Google Calendar: meetings that have already ended are offered as time the employee can put on their timesheet.
Configuration
Go to , select Outlook Calendar, and turn it on. There is nothing else to set: every approved time off is shown, of every type.
Only days taken in full get an entry, as with Google Calendar. A half day does not appear.
What your Microsoft 365 administrator needs to allow
mTime asks each employee for permission to read and write their own calendar (the delegated Microsoft Graph permissions Calendars.ReadWrite and offline_access). It is not a permission over every mailbox in your organisation: mTime acts only as the employee who connected, on that employee’s calendar, and an employee who never connects is never touched.
Whether employees can grant that themselves is a setting in your Microsoft Entra ID:
- If employees may approve apps themselves, nothing is needed — each employee approves mTime when they connect.
- If only administrators may approve apps (common in larger and public-sector organisations), an administrator grants consent once, for the whole organisation, to the mTime app for those two permissions. Employees then connect without seeing an approval request.
Only work and school accounts can connect; personal Outlook.com accounts cannot.
Tenant-wide access
If your organisation would rather not have each employee connect, turn on Tenant-wide access . mTime then writes to every employee’s Outlook calendar through an app registration in your own Microsoft Entra ID, and nobody has to connect on the Security page.
Your Microsoft 365 administrator:
- Registers an app in Microsoft Entra ID (App registrations → New registration).
- Gives it the Microsoft Graph application permission Calendars.ReadWrite and grants admin consent for it.
- Creates a client secret for it.
- Enters the Directory (tenant) ID , the Application (client) ID and the Client secret on the Outlook Calendar integration and saves. mTime checks with Microsoft that they work before saving.
mTime finds each employee’s mailbox by the email address on their employee record, so that must be their Microsoft 365 address. An employee without one gets no entries; everyone else is unaffected.
What each employee sees
Each employee goes to , finds Outlook Calendar under Connected accounts and clicks Connect . Microsoft asks them to sign in and confirm, and they come back connected. Approved time off they already had from today onward is added to their calendar straight away.
A few things worth knowing when helping someone:
- They can connect a different Microsoft account than the one they sign in to mTime with. mTime says so on the page; it uses the calendar of the connected account.
- Their organisation may require them to sign in again from time to time. When that ends the connection, the row says to reconnect, and their entries stop updating until they do.
- Disconnecting is always available from the same page. Entries mTime already wrote stay in their calendar.
The Conflicting meetings preference does not apply to Outlook: an Outlook entry never declines meetings. When your workspace has Google Calendar enabled as well, the preference still applies to Google calendars.
Troubleshooting
| Issue | Solution |
|---|---|
| An employee doesn’t see Outlook Calendar on their Security page | The integration is not turned on for the workspace. |
| Microsoft says the app needs an administrator’s approval | Your organisation only lets administrators approve apps. An administrator grants consent once — see What your Microsoft 365 administrator needs to allow. |
| The Security page says to reconnect | The connection ended — the employee removed mTime’s access, or their organisation’s sign-in rules expired it. They reconnect from . |
| A time off doesn’t appear in Outlook | Check that it is approved and that it covers whole days. |
| An entry deleted in Outlook didn’t come back | That is expected: mTime doesn’t restore entries that were changed or deleted in Outlook. |
| Saving tenant-wide access says Microsoft issued no token | The directory ID, application ID or client secret is wrong, or the secret has expired. Create a new secret in Microsoft Entra ID and enter it again. |
| With tenant-wide access, one employee gets no entries | Check that the email address on their employee record is their Microsoft 365 address, and that your app’s access covers their mailbox. |
Next steps
See Integrations for how to turn an integration off and what happens to its data.