Microsoft 365 and Google Workspace
Entra ID sign-on and directory sync, shared-mailbox email-to-ticket, SharePoint document linking and Teams notifications on Microsoft 365 — plus Google single sign-on, directory sync and mailbox ingestion.
The problem
Your service desk lives in a mailbox. Someone emails support@, a technician sees it in Outlook, replies from Outlook, and the ticket system finds out later — or never. Meanwhile a leaver keeps their portal access for a month because offboarding happened in Entra and nowhere else, and the one document that explains the client’s firewall is a SharePoint link pasted into a chat thread that nobody can find.
What Solidlio does about it
Solidlio connects to Microsoft Graph with an application credential your Global Administrator grants once. Shared mailboxes become ticket queues, with routing rules deciding where each message lands and replies sending from the same address. Entra groups map to Solidlio roles, so provisioning and deprovisioning follow your directory rather than a checklist. SharePoint documents attach to tickets by link. And Teams channels receive adaptive cards for the events each channel actually cares about.
Capabilities
| Capability | What it does |
|---|---|
| Entra ID single sign-on | Signs users in against your Microsoft tenant |
| Google single sign-on | Signs users in against Google Workspace |
| Directory sync | Syncs Entra users and groups incrementally, recovering automatically when the cursor expires |
| Group-to-role mapping | Maps an Entra group to a Solidlio role, with optional auto-provision and auto-deprovision |
| Shared-mailbox email-to-ticket | Turns a monitored mailbox into a ticket queue with routing rules and a default queue |
| Technician replies | Sends replies from the same shared mailbox the request arrived on |
| Auto-reply | Acknowledges inbound mail from the correct tenant’s mailbox and template |
| SharePoint document linking | Attaches SharePoint documents to tickets, and uploads to a site from Solidlio |
| Calendar integration | Two-way Outlook calendar sync and free/busy lookup for scheduling |
| Teams notifications | Posts adaptive cards to the channel whose purpose matches the event, with history and retry |
| Google mailbox ingestion | Polls a Google Workspace mailbox by service account for AP invoice processing |
| Subscription health | Reports Graph subscription count, expiry and renewal failures instead of failing silently |
Security
- Solidlio runs on an application credential granted by your Global Administrator. Tokens are encrypted at rest and never displayed again.
- A feature that is toggled on but lacks consent is blocked with the exact missing permissions named, rather than being allowed through to fail at Microsoft with an opaque error.
- Inbound change notifications are authenticated on every delivery, and the mailbox a notification may act on is derived from the subscription itself — not from the notification body — so a forged notification cannot reach another mailbox in your tenant.
- Directory sync cannot alter a person’s role grants outside the connected organization, and cannot bind an existing person from another tenant by matching their email address.
- Mailbox routing, auto-reply and ticket creation are pinned to the integration that owns the mailbox, so two tenants monitoring the same address cannot apply each other’s rules.
- Inbound message de-duplication is scoped per organization, so a message delivered to two tenants reaches both.
- Teams channel webhook URLs are treated as credentials: never returned by the API, and every read route requires organization administrator.
Editions
| Capability | Free | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|---|
| Microsoft 365 integration | — | — | ● | ● | ● |
| Email-to-ticket mailbox | — | — | ● | ● | ● |
| Microsoft Teams notifications | — | — | — | ● | ● |
| Google Workspace mailbox | — | — | — | ● | ● |
| Entra ID / Google single sign-on | — | — | — | — | ● |
Customer-plan equivalents: Essentials, Professional, Business, Enterprise.
Current limitations
Worth knowing before you buy:
- Calendar sync was repaired in this release and has not yet been verified against a live tenant. Two of the Graph routes previously in use were not valid Graph routes at all; both are now correct and unit-tested. We are not claiming real-time calendar sync until it has run against a real mailbox.
- Near-real-time mail requires a publicly reachable webhook address to be configured; otherwise ingestion polls about once a minute.
- Change-management events do not yet post to Teams. Tickets, assets and invoices do.