INTEGRATION · MICROSOFT 365

Use Outlook, calendar and Microsoft files with Voyager, or alongside Voyager's own.

Voyager's Microsoft Graph implementation connects Outlook mail and calendar, Microsoft files, contacts and directory context, and Teams conversations through separately activated capabilities. Provider permissions and Voyager authority remain separate controls.

The connection at a glance

What the current implementation supports.

Workflows it supports. Customer email and follow-up, calendar changes that affect delivery, files linked to work, contact/directory context and Teams conversations connected to owned action.

Connected systemMicrosoft 365

Microsoft Graph permissions are feature-specific. Some file, directory and Teams scopes require tenant administrator consent, and the corresponding Voyager feature must be enabled.

VoyagerBusiness context

Outlook mail, calendar events and availability, OneDrive and SharePoint files, contacts and directory data, and authorized Teams conversation context for activated features.

Where authorizedGoverned action

Implemented actions include Outlook draft/send/reply/forward and mailbox changes, calendar create/update/cancel, and scoped file, contact and Teams writes.

Voyager's own equivalentVoyager Inbox and Discuss, Schedule, Vault, Relations and native work coordination.

Keep it, replace it, or bothMicrosoft 365 can remain the mail, calendar, file and Teams system while Voyager coordinates work around it; selected work can move natively later.

01WHAT IT CONNECTS

Email, calendar, files and collaboration.

Outlook email and calendar, OneDrive and SharePoint files and Microsoft collaboration context become part of Voyager's picture of customers, work and time.

Outlook email
Calendar and meetings
OneDrive and SharePoint files

02WHAT IT ENABLES

A change in Microsoft 365 updates the work around it.

An email that moves a deadline or a rescheduled meeting is connected to the project, customer and follow-up it affects, with prepared changes for approval.

03YOUR CHOICE

Keep Microsoft 365, use Voyager natively, or mix them.

Many organizations keep Microsoft 365 for email and files and use Voyager for everything around them. Others move selected communication, scheduling or document work into Voyager. Both can continue indefinitely.

CONNECTION QUESTIONS

What to know before you connect.

Do we need to stop using Microsoft 365?: No. Microsoft 365 can remain your email, calendar and file system while Voyager works across it.
Does Voyager get access to every Microsoft service?: No. Access depends on your tenant authorization, the permissions granted and the features enabled for your deployment.
Where should we start?: With a workflow where email or calendar changes already create work elsewhere, such as client delivery, sales follow-up or approvals.

Get started

Start with the Microsoft 365 surface that creates the most downstream work.

Map a Microsoft 365 workflow Request access Explore integrations

We will map the Graph capability, tenant consent, Voyager authority and write boundary before activation.