Every connection is a sign-in by the administrator who owns it, or a key you type once that is sealed on save. The platform reads what the other system knows and writes back only what you issue.
Commercial and GCC High. Sign-in, calendar and mail sync, tenant actions from the desk, Intune, Defender, Exchange Online, compliance reads, Entra reads, plays. Your customers' administrators consent in their own tenant; nothing is granted in ours.
Sign-in, calendar and Gmail sync, Admin SDK reads, the alert center, licences, actions and plays, Google Cloud projects.
Subscriptions, accounts and projects read for the compliance checks with read-only authority; GovCloud and management.usgovcloudapi.net for the government clouds.
Every issued invoice posted with the same number, lines, discount and tax; credit memos; balances read back nightly.
The mail server and the contact source: campaigns, sequences, transactional mail, inbound mail to the desk, segments as audiences.
Licence counts and suggested retail into the price book and the monthly period.
Devices, alerts, backup health and network gear into assets, tickets and the bill.
Datto EDR, RocketCyber, Huntress, SentinelOne, Microsoft Defender, plus any JSON webhook or alert mailbox with a field map.
The move: repeatable pulls, the mapping, the test period, cutover. ConnectWise next.
Texting and click-to-call through your own tenant; call records.
One script tag for first-party tracking, forms and brochures that credit the campaign.
A keyed REST API for contacts, tickets, time and more; webhooks for ticket and contact events.
Microsoft 365 GCC High tenants connect through login.microsoftonline.us and are read through graph.microsoft.us and outlook.office365.us; Azure Government through management.usgovcloudapi.net; AWS GovCloud through its own endpoints. The instructions in the product name the government portals, never the commercial ones.
Start the account, then connect Microsoft 365 or Google Workspace in the first hour.