Connect Microsoft Outlook

Nothing to install. One thing to know, and it is the reason the fourth connection exists:

• Some tenants require an administrator to approve the application. Reading your own calendar is a permission most Microsoft accounts can grant themselves, but an organization can turn that off for everyone in it. If yours has, the sign-in page will say so rather than fail quietly, and a calendar link gets you the same result with nothing for IT to approve.

Both kinds of account work: a work or school account, and a personal outlook.com account.

1. Open Earkeep and press Settings, at the bottom of the left rail.
2. Go to Calendar.
3. On the Microsoft Outlook row, press Connect. Your browser opens at Microsoft's own sign-in page.
4. Sign in and approve the request. Earkeep asks to read your calendars and to keep the connection alive, and nothing beyond that.
5. Microsoft sends you back to a page that says you can close the tab. Close it and return to Earkeep. The row now reads Connected, followed by the account's address.
6. Turn on Create spans from events if you want each event to become a meeting on its own.

While the browser is doing the sign-in the row shows Connecting… and a Cancel button. That button exists because the browser tab is invisible to Earkeep: if you close it or change your mind, Cancel is how you tell the app to stop waiting.

Read-only, and only calendars. Earkeep requests permission to read your calendars, and one to keep that access working without asking you again every hour. It cannot create, move or delete an event, and it never asked for your mail, your files or your Teams messages.

No client secret is involved. Earkeep signs in as a public client, which is what a desktop application is: the security of the flow rests on the sign-in happening in your browser and the response coming back to your own machine, not on a password baked into the app.

The token lives in your system keychain, managed by the operating system. Earkeep's configuration file holds only which provider is connected, the account label, and whether it is enabled.

Your events are not copied to a server. Earkeep talks to Microsoft directly from your device, and there is no Earkeep server in between, because there is no Earkeep server. See private by design.

All-day events, declined invitations and cancelled events never become spans, and neither does an event during which nobody said anything. Those rules are the same for every provider and are described on calendar connection.

"No OAuth client id configured." This build was compiled without Microsoft credentials, which happens with a build you made yourself rather than one downloaded from this site. The other three connections still work, and a calendar link is the closest substitute.

"Need admin approval", or a message from your organization. Your tenant does not let its users approve applications themselves. You can ask an administrator, or you can sidestep the question: publish your calendar as a link and paste that into Earkeep instead. Publishing is a feature of Outlook itself, so there is no application to approve.

The browser opened and nothing came back. Press Cancel on the row and try again. Sign-in has a time limit, and a tab left open past it has to be restarted rather than resumed.

Events look stale. Press Sync now. Earkeep refreshes on its own as the day goes on, and this just skips the wait.

• Calendar connection: what an automatic span is, and what happens when the meeting doesn't match the invite.
• Connect a calendar link (ICS): the path for a workplace that won't approve an application.
• Connect Apple Calendar: reads every calendar in the macOS Calendar app, Exchange accounts included.
• All Earkeep how-tos.