How Microsoft consent and calendar sharing work together, and when a shared calendar can be a sync source or target.
A colleague's or room's calendar can appear under your connected Outlook account. You don't connect it as a second account. Microsoft must let your account access the calendar, and you choose what SYNCDATE may do with calendars your account can access.
The calendar owner or your Exchange admin must share the calendar with the Outlook account you will connect. Accept the invitation or add the calendar in Outlook, then check that you can see its events there. For a room calendar, being able to book the room is different from having its calendar shared with you. Ask your Exchange admin for access to the room's calendar if it is not visible in Outlook.
In SYNCDATE, open Settings → Accounts. When connecting another Outlook account, choose calendar access before continuing to Microsoft. For an account already connected, open its menu and choose Calendar permissions to change the selection. Microsoft may skip its consent screen if a permission was already approved.
The choices are:
| Selection | Microsoft calendar scope | What you can do in SYNCDATE |
|---|---|---|
| Read my calendars | Calendars.Read | Use your own calendars as sources. |
| Edit my calendars | Calendars.ReadWrite | Use your own calendars as sources or targets. |
| Read shared calendars | Calendars.Read.Shared | Use calendars shared with you as sources. |
| Edit shared calendars | Calendars.ReadWrite.Shared | Use a shared calendar as a target only if you also have edit rights from its owner. This scope includes access to your own calendars too. |
You can connect an additional Outlook account with no calendar access. On Microsoft sign-in, SYNCDATE still requests Calendars.ReadWrite for your own calendars. Unchecking edit later stops SYNCDATE from writing, but Microsoft may retain an earlier grant until you revoke it in your Microsoft account or organization.
Your Microsoft Entra app registration can list all four calendar scopes, and an admin may approve them for the tenant. SYNCDATE sends the scopes for your selection in the OAuth request. Admin approval does not share a room or colleague's calendar with you, and the consent screen does not let you choose individual calendars. Microsoft may show configured permissions beyond your selection on that screen.
Personal Microsoft accounts can consent to Calendars.Read.Shared. Microsoft does not list Calendars.ReadWrite.Shared as available for personal accounts. A work tenant's admin approval applies to work accounts in that tenant, even if a personal Microsoft account uses the same email address.
Once the shared calendar appears in SYNCDATE, choose it as a source in a Push sync when you only have read access. Choose it as a target only when you selected shared edit access in SYNCDATE and Outlook says you can edit that calendar. An editable OAuth scope never overrides the owner's sharing rights.
If it does not appear, check that it is visible to the same account in Outlook, then check that Read shared calendars is selected under Calendar permissions in SYNCDATE. If Outlook itself will not open for a work account, ask your admin to check that it has a working Exchange Online mailbox. If Microsoft says it did not grant the chosen scope, your account's SYNCDATE permission setting remains unchanged; ask your tenant admin to approve the requested delegated scope, then try again.
Verified against the product on .
Still stuck? Support will read your actual setup and tell you what it sees — describe what you expected and what you got.