Productivity integration
Technician mailbox context on the customer hub, plus tenant-wide MFA + role signals that feed posture + compliance.
What Vectis syncs
The read side of the adapter. Pulled on a schedule and available everywhere the customer account surface lives.
Read-only today
This adapter pulls data into Vectis but doesn’t write back into Microsoft 365. Rules can still react to the synced data — for example, a Pax8 subscription change can open a ConnectWise ticket or a HaloPSA action. The write-back lands in the PSA, not in Microsoft 365.
How it correlates
Vectis is about Microsoft 365 joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
Open a customer and see recent technician emails about them without leaving the page — subject + preview only, never the body. Mailbox sync is scoped strictly to the technician UPNs you enumerate; nothing else is ever pulled.
Tenant-wide MFA coverage and privileged role assignments populate the security posture page and compliance evidence packs. Missing MFA surfaces as a posture finding, not something to audit by hand.
Setup snapshot
In Entra ID, register a Vectis app and grant it the minimum Microsoft Graph scopes needed (Mail.Read scoped to tech mailboxes, User.Read.All, Organization.Read.All, etc.). Paste the tenant ID, app client ID, and client secret (the secret Value, not Secret ID) into Vectis. Enumerate the technician mailboxes Vectis is allowed to pull context from — any mailbox not on this list is invisible to Vectis. Set a rotation reminder for the client secret; Entra secrets expire.
Full setup guideavailable after signup
14-day free trial. Connect Microsoft 365 at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.