Approve inlark for your organization

inlark is an open-source email app for the desktop. Someone in your organization wants to read their Microsoft 365 mail with it, and Microsoft asks an administrator to approve that first. This page says what you would be approving.

The button opens Microsoft’s own consent page. You sign in there as an administrator, see the same list of permissions, and decide. Nothing is approved by visiting this page.

Why Microsoft asks you

Microsoft’s default for organizations lets people approve most apps themselves, but not an app that reads mail over IMAP. Only a handful of mail apps that Microsoft lists by name are exempt. For every other one, inlark included, an administrator approves once and everyone in the organization can then sign in.

Microsoft shows inlark as “unverified”. That label is about Microsoft’s partner programme, which inlark’s publisher has not joined; it says nothing about what the app does. The details below are what to go by.

What inlark asks for

Five delegated permissions. Each one works only for the person who signed in and only in their own mailbox. inlark asks for no application permissions and nothing that reaches other people’s mail, files, calendars or your directory.

IMAP.AccessAsUser.All

Microsoft calls it “Read and write access to your mail”

Shows a person their own mail and files, flags, moves and deletes it as they ask.

SMTP.Send

Microsoft calls it “Access to sending emails from your mailbox”

Sends the messages a person writes, from their own address.

Mail.Send

Microsoft calls it “Send mail as you”

Sends through Microsoft Graph instead, for mailboxes where SMTP is switched off.

offline_access

Microsoft calls it “Maintain access to data you have given it access to”

Keeps a person signed in, so they aren’t sent to Microsoft every hour.

openid, email

Microsoft calls it “View your email address”

Tells inlark which account signed in, so it opens the right mailbox.

What happens to the mail

Mail stays between the computer and Microsoft

inlark connects from the person’s computer straight to Microsoft’s servers. There is no inlark server in between, and no copy of anyone’s mail anywhere else.

Sign-in happens on Microsoft’s page

People sign in in their own browser, on Microsoft’s site, with whatever your organization requires: multi-factor, passkeys, conditional access. inlark never sees a password.

The sign-in stays on that computer

What Microsoft hands back is stored in the operating system’s keyring. On a computer without one, the person chooses whether inlark remembers it, in an unencrypted file only their own user account can read. Removing the account from inlark, or revoking the app in Entra, ends it.

No telemetry

inlark sends no usage data and has no analytics. Its source is public under the AGPL, so every claim on this page can be checked.

The registration

Application (client) ID
75e89ace-e7ac-4516-9e1c-daf835270869
Name shown by Microsoft
inlark
Kind of app
Desktop app for Linux, Windows and macOS. A public client: it holds no secret.
Kind of access
Delegated only. inlark acts as the person who signed in, in their own mailbox, and has no access of its own to your organization.

Two mailbox settings matter too

IMAP has to be enabled for the mailbox in Exchange Online, or inlark can sign in but not read mail. SMTP AUTH is optional: where it is disabled, inlark sends through Microsoft Graph, which limits a message to about 3 MB.

Taking the approval back

In the Microsoft Entra admin center, open Enterprise applications, find inlark by the ID above and delete it or remove its permissions. Everyone’s sign-in then stops working until it is approved again.

Not an administrator?

Send this page to whoever looks after Microsoft 365 where you work. Personal Outlook.com, Hotmail, Live and MSN accounts need no approval at all:download inlark and sign in.