Microsoft 365 and identity connections
Connect Microsoft 365 to relevant email, directory and scheduling workflows. Use supported single sign-on options on eligible plans.
Connect the work your team already uses
The Microsoft 365 connection supports organization-level directory and mailbox workflows. Personal Outlook calendar sync is a separate connection. Teams notifications and single sign-on have their own plan requirements.
Capabilities and scope
| Capability | What it supports |
|---|---|
| Microsoft 365 directory | Synchronize users and groups from the connected Microsoft organization. |
| Group-to-role mapping | Map connected directory groups to Solidlio roles, subject to administrator configuration. |
| Shared-mailbox email-to-ticket | Bring monitored mailbox messages into ticket queues with routing and replies. |
| SharePoint links | Attach relevant document links to work records. |
| Personal Outlook calendar | Synchronize an individual’s calendar for scheduling. |
| Microsoft Teams | Send supported ticket, asset and invoice notifications to configured channels. |
| Microsoft Entra ID or Google single sign-on | Authenticate through a configured identity provider on an eligible SSO plan. |
Plan requirements
The organization Microsoft 365 connection starts at MSP Growth or Organization Professional. Teams starts at MSP Scale or Organization Business. Single sign-on is available on MSP Scale and Enterprise, and Organization Enterprise.
Personal Outlook calendar sync is not subject to the organization Microsoft 365 connector gate. Administrator consent, account permissions and the relevant external vendor licences still apply.
Review integration requirements and compare plans.
Google Workspace: a clear boundary
Google single sign-on is implemented. A broad Google Workspace integration covering Calendar, Drive and general Gmail workflows is not available. Gmail-based invoice capture is a separate implemented workflow and is not a full Workspace connector.
Setup and access
An administrator grants the connection the permissions it needs. Connected organization workflows remain scoped to that organization. Review the consent requirements and configuration before enabling mailbox or directory actions.