Skip to content
On this page

Outlook / Microsoft 365

Connect an Outlook or Microsoft 365 address to Elvo by signing in.

A direct connection to Outlook or Microsoft 365 works like Gmail: Elvo receives and sends mail on your behalf, and sent mail stays in sync.

Connect#

  1. Open Settings → Email and click Add account.
  2. Choose Microsoft.
  3. Sign in with your Microsoft account and approve the permissions.
  4. Once connected, the address appears in the list and mail starts arriving.

Microsoft 365 for business#

If your company uses Microsoft 365, an admin (Entra ID) may need to approve access for the organization. You can connect both personal and shared addresses you have access to.

If Microsoft answers Needs admin approval, send your admin or IT provider the page For IT admins. It has the approval link and the steps for a shared mailbox.

Permissions Elvo asks for#

The Microsoft app is registered as 2f461a90-c7b4-4098-9018-a7b271a0216a and uses delegated Graph permissions only: Elvo can do what the signed-in user can do, and nothing more.

When someone connects a mailbox, Elvo asks for:

  • Mail.ReadWrite and Mail.ReadWrite.Shared, to read mail and keep it in sync
  • Mail.Send and Mail.Send.Shared, to send your replies
  • MailboxSettings.Read, to read the mailbox time zone and language
  • User.Read, openid, email, profile, to confirm which address was connected
  • offline_access, so the connection keeps working without a new sign-in every hour

The .Shared permissions are what make shared mailboxes work.

When an admin approves Elvo for the whole tenant with the link on the For IT admins page, the approval also covers Elvo's calendar and contacts features. Elvo uses each permission only for the feature listed:

  • Calendars.ReadWrite and Calendars.ReadWrite.Shared, to show your own calendar and your shared mailboxes' calendars in Elvo
  • Contacts.ReadWrite, Contacts.ReadWrite.Shared and People.Read, to suggest recipients from Outlook
  • User.ReadBasic.All, to show your colleagues' names and profile pictures

Other features ask for their own approval when the company turns them on. For example, using SharePoint documents as a knowledge source asks for Sites.Read.All and Files.Read.All. Elvo never asks for these with the mailbox.

Users who connect a mailbox are never asked for the calendar and contacts permissions. Without the admin approval these features stay off, and mail works as before.

An admin can approve the app once for the whole tenant with the admin consent link on the For IT admins page, or by accepting the consent prompt on the first connection.

Signing in to Elvo with a Microsoft account is a separate app, 6c6a43bd-2674-4c52-8dbc-d6bf03f4c73b, which asks only for openid, email and profile. See Users & roles.

Working in Outlook alongside Elvo#

Elvo follows what you do in Outlook, one way. Elvo reads the changes and never moves, deletes or edits anything in your mailbox. Tags are Elvo's folders: a ticket carries the tag of the folder its email sits in.

  • Move a message to a folder and the ticket gets a tag with the folder's name and is archived in Elvo: it leaves the inbox and you find it in the Archive folder. Filing to "Invoices" in Outlook is the Invoices tag here. Move it on to another folder and the tag follows: the old folder's tag goes, the new one comes. A folder inside Archive works the same way; the Archive folder itself only archives, no tag.
  • Archive a message and the ticket is archived in Elvo, no tag.
  • Delete a message, from the inbox or from any folder, and an open ticket is deleted in Elvo. Deleting mail that was already handled changes nothing.
  • Move it to Junk Email and the ticket is ignored.
  • Move it back to the inbox and the ticket comes back to the inbox in Elvo, out of the Archive folder, and the folder's tag is removed. A message taken back out of Deleted Items or Junk reopens the ticket.
  • Mail that Outlook rules file straight into a folder becomes a ticket too, archived and tagged with that folder, so nothing routed past the inbox is missed.
  • Folders become tags when a mailbox is first connected too: everything already filed in a folder is imported with that folder's tag, archived, since it is already out of your inbox.

A new reply from the customer brings an archived ticket back to the inbox, as always. Some safeguards apply: a ticket is never deleted or ignored from Outlook while a newer message from the customer is waiting on it, and Outlook's own folders (Sent Items, Drafts, and so on) never become tags. Renaming a folder does not rename its tag. Outlook categories are not synced. Changes normally show up within seconds; if Outlook's notification is missed, within fifteen minutes.

Resolving is separate: marking a ticket resolved in Elvo is Elvo's own state and is never synced to Outlook in either direction, so you can file in Outlook and resolve in Elvo independently.

FAQ#

Is admin consent required? For business accounts, Microsoft may require an admin to authorize Elvo once. The steps for the admin are on For IT admins.

Does this work with Exchange? Yes, via the Microsoft 365 / Outlook connection.

What if the connection drops? Sign in again under Settings → Email.

Does the connection survive when the person who set it up leaves? Yes. A company mailbox belongs to the organization, and the permission comes from the Microsoft account signed in during consent, that is the mailbox itself. It only breaks from the Microsoft side: the account is deleted or disabled, or consent is withdrawn.