Connect your Microsoft 365 (or personal Outlook.com) calendar and your Mucka jobs and appointments land in it automatically, as you book them. Change something either side and the other keeps up.
Connect your account
Head to Settings → Connections → 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)
- Read calendars shared with you (only used for the ones you switch on)
- 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.
More than one calendar
Got a work calendar, a personal one and one your partner shares with you? Mucka can read all of them.
Under Calendars Mucka reads on the same page you'll see every calendar on your Microsoft account. Switch on the ones you want, and for each one Mucka asks: Should this block time in your diary?
- Yes, I'm busy. Events on it block your time, exactly like your main calendar. Nothing gets booked over them, not even by the AI receptionist.
- No, just show it. Events show on your diary, faded, so you can see them, but Mucka still books work over them. Good for a partner's calendar.
You can change the answer any time, including for your main calendar. Mucka reads up to five extra calendars.
One event at a time works too: an event you've set to show as free in Outlook shows on your diary but doesn't block the time. All-day events are the exception. Outlook sets those to free unless you change it, so Mucka keeps treating an all-day event as busy. That way a holiday never gets booked over.
Your jobs still only go onto your main calendar. The others are read, never written to.
Events from a calendar someone shared with you show to your team as "Personal time" unless you tick Show event titles to your team under it.
Can't read a calendar someone shared with you? If you connected before October 2026, tap Reconnect and approve the extra permission — Mucka needs it to read shared calendars.
What syncs
- 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
- Pencilled bookings show as pencils, titled Pencilled and marked tentative, until you confirm them. Want only confirmed work on your calendar? Switch off Pencilled bookings on your calendar in Settings → Work → Diary.
- Personal appointments and time off both ways, so nothing gets booked over them — not even by the AI receptionist
Reminders you've set on a Mucka appointment come across as Outlook's own alerts.
What a job looks like on your calendar
The title starts with the job number, then the customer and the job: J-014 · Pat Example — Boiler service. That's the number your engineers read to the merchant, and it tells two jobs at the same customer apart at a glance. Jobs already on your calendar pick it up the next time they change.
Each job goes on at the job's own address. If the job is at a property, that's the property, not the customer who pays the bill, so on a rented house it's the house and not the letting agent's office. Tap the address and your maps app takes you there.
The details on the event say who the customer is and how to reach them, then the address, what the job is, and how you're getting in (Key collect, Someone home and so on) if you've recorded it. Your own notes on the job follow underneath.
Every job carries the Mucka category. If you colour jobs by where they're at, each one also gets a category like Mucka: Invoiced: give each of those a colour once in Outlook and your week is colour-coded. See Colour your calendar by where each job is at.
Disconnect any time
Same page has a Disconnect button. Tapping it:
- Removes Mucka's stored tokens for your account and stops syncing straight away
- Takes your Outlook events off your Mucka diary. Every busy block from that Microsoft account (and any extra calendars you had switched on) comes off your Mucka diary at once.
- Leaves your Mucka jobs and appointments where they are. Anything you turned into a job stays, because it's a Mucka job now.
Mucka asks before it disconnects. The box Also remove all Mucka events from this calendar is ticked to start with. Leave it ticked and Mucka takes the jobs and appointments it put in your Outlook calendar back out. Untick it and they stay in Outlook. Events you made in Outlook yourself are never touched.
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.
- Outlook won't let Mucka change one of its events. It happens if the event was moved somewhere Mucka can't edit. The job stays in Mucka, and Mucka stops updating that one event rather than trying again and again. The next time you change the job, it goes back on your calendar as a fresh event.
- 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.