Understand the working context

Organisation approval and individual consent play different roles. A tenant administrator may approve the application and its requested capabilities. A colleague then connects their own account within the permissions and policies that apply. The exact permissions determine whether a feature can read mailbox items, send email or create calendar entries. Access should be matched to the actions the team wants to use, rather than treating a connected account as unrestricted access to Microsoft 365.

Put it into practice

  • Confirm the centrally configured application and tenant.
  • Review the capabilities requested during organisation approval.
  • Let each colleague connect the appropriate personal work account.
  • Test the specific mail or calendar action the team needs.

A practical example

An administrator approves the organisation connection. A salesperson then connects their mailbox so they can preview supported items and review a customer email before sending it. Another colleague must connect their own mailbox; the first person’s consent is not a shared login for the team.

HOW THIS RELATES TO ATLAS

In the current workspace

Atlas supports organisation approval and individual mailbox consent, with bounded previews and explicit email/calendar actions. Provider setup and live consent are required; full mailbox-history synchronisation is not included.

Explore the product

Further reading

For more detail on the general topic:

Atlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.