WorkTracker › Connection guides › Microsoft 365

Connect Microsoft 365 to WorkTracker

Teams chats, sent Outlook mail and calendar meetings — one consent.

What you need

• A Microsoft 365 / Entra ID account with Teams and Outlook.
• The WorkTracker server must have a Microsoft app configured (self-hosting: an Azure App registration with redirect URI {APP_BASE_URL}/api/connectors/microsoft/callback and the delegated Graph permissions User.Read, Chat.Read, Mail.Read, Calendars.Read, offline_access).

Setup

1. Open Connections

   In WorkTracker open Connections and find the Microsoft 365 card.

2. Connect and consent

   Click “Connect Microsoft 365”. Sign in with your work account and accept the read-only permissions (profile, Teams chat, mail, calendar). All requested permissions are user-consentable — no admin approval is needed unless your tenant restricts consent.

3. Sync

   Back in WorkTracker, run a sync: Teams conversations, sent mail and meetings appear in your day view, ready to be turned into tracked time.

What WorkTracker collects

• Teams chat: your own messages, grouped into conversations per chat (message text is fetched transiently for AI summaries — never stored).
• Outlook: sent mail as zero-duration work items (subject and From/To/Cc; bodies are read transiently for AI summaries, never stored).
• Calendar: meetings you organized or accepted, counted as tracked time and deduplicated against Toggl.

All scopes are read-only. Chat messages and mail bodies are fetched only for the moment the AI writes a summary — WorkTracker stores the one-line summary, never the content. Covers 1:1, group and meeting chats; Teams channel posts are not read (that permission would require tenant-admin consent). Credentials are stored encrypted (AES-256-GCM) and are never shown again or returned by the API.

Troubleshooting

“Need admin approval” during consent

Your tenant restricts user consent. Ask IT to approve the WorkTracker app once (or grant admin consent for the listed read-only permissions) — after that every user can connect themselves.

Connected, but no Teams events appear

Only chats where you wrote messages produce events, and only 1:1/group/meeting chats are read — Teams channel posts are deliberately out of scope.