Skip to content
Merulan

Microsoft mailbox setup

What an operator supplies to connect the Microsoft mailbox Source, and the verification the provider requires.

Connecting Microsoft mailbox redirects the operator to the provider and returns with a grant. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Microsoft mailbox refuses the connection until every item holds.

  • A Microsoft work or personal mailbox the operator may sign in to.
  • A tenant administrator who grants consent when the tenant requires it for third-party applications.

Credentials

Microsoft mailbox stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. The browser grant returns an access token and a refresh token, and Merulan seals both.

Scopes

Microsoft mailbox requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • Mail.Read
  • Mail.Send
  • Calendars.Read
  • offline_access

The offline access scope is what keeps the mailbox connected without a fresh sign-in each day.

Verification

Provider app review governs the Microsoft mailbox connection. Microsoft asks for publisher verification on the registered application, and a tenant administrator may still refuse consent for the tenant.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.