Connecting your Microsoft 365 (or personal Outlook.com) calendar tells Mucka who you are on Microsoft's side. Once the sync engine ships, your Mucka jobs and appointments will land in your Outlook calendar automatically and any changes either side will keep both in step.
Heads up: the connection is live today, the actual sync is shipping in a follow-up. Connect now and Mucka starts syncing the moment the engine goes live, no extra step needed.
Connect your account
Head to Settings → Integrations → Microsoft 365 and tap Connect.
Microsoft asks you to sign in and grant Mucka access to your calendar. The permissions you're granting:
- Read and write your calendars (so Mucka can add jobs)
- Sign in and read your profile (so Mucka can show "Connected as ryan@business.co.uk")
- Maintain access to data you've given Mucka (so the connection doesn't break overnight)
Approve and Microsoft sends you back to Mucka with a "Connected" confirmation.
Personal Outlook vs work Microsoft 365
Mucka works with both:
- Personal Outlook.com / Hotmail / Live accounts
- Microsoft 365 work accounts (the one your business pays for)
Same connect button, Microsoft figures out which one you're using when you sign in.
Each engineer connects their own
Calendar connections are per-user. Every engineer connects their own Microsoft account. The owner doesn't connect everyone, each person picks their own calendar.
The owner can see which engineers have connected and disconnect them if needed.
What's coming when sync goes live
Once the sync engine ships:
- Mucka jobs → Outlook Calendar automatically as you schedule them
- Outlook changes → Mucka when you reschedule or cancel in Outlook
- Cancel in one, cancel in both so you don't end up double-booked
- Time off / unavailable blocks flow both ways
We'll write the full sync article when it ships. For now, just connecting is enough to be ready.
Disconnect any time
Same page has a Disconnect button. Tapping it:
- Removes Mucka's stored tokens for your account
- Stops any syncing immediately (once sync is live)
- Doesn't delete events that were already synced
A quirk worth knowing: Microsoft (unlike Google) doesn't expose an API for apps to revoke their own access. If you want to revoke Mucka's access on Microsoft's side as well, head to Microsoft account → Privacy → Apps and services. Disconnecting in Mucka is enough for most people.
Common gotchas
- Work account blocked by admin. Microsoft 365 admins can lock down which third-party apps employees can connect. If you see "Need admin approval", ask your IT person to allow Mucka.
- "Needs calendar permission" after connecting. On the Microsoft consent screen, leave all the requested permissions ticked. If the calendar permission isn't granted, Mucka can sign you in but can't write jobs to your calendar, so nothing syncs. Tap Reconnect and accept the full set.
- Connected the wrong account. Disconnect and reconnect. Microsoft remembers your last sign-in, hit Use another account on the sign-in screen.
- Multi-factor auth (MFA) prompt every reconnection. Normal. Microsoft adds MFA on every fresh OAuth grant. Once connected, you stay connected.
- Tenant restrictions. If you're on a tightly-managed corporate tenant, your IT may require Mucka to be added as a service principal. Send them the help URL.