FigsFlow › Integrations › Microsoft 365
Live · not a roadmap itemRuns inside the tenant you already own
FigsFlow does not ask your firm to move its files, its mail or its identity anywhere. Documents stay in your SharePoint, mail stays in your mailboxes, people sign in with Entra ID — and the permissions and retention policy your IT already governs stay exactly as they are.
Files, auth and permissions remain inside your own SharePoint. Zero third-party file storage.
Four Microsoft surfaces, each doing the job it is already good at
FigsFlow is not trying to replace any of these. It uses them — which is why there is no migration, no second archive and no new place for your team to look.
SharePoint & OneDrive
The master document repository, in your own tenant. FigsFlow does the filing, naming and syncing into it — every client document saved to your library using the folder structure and naming convention your firm already has. No separate archive, and no second place to search.
Outlook
Personal or shared mailboxes, synced both directions — emails, deletions, read status and flags. Shared inboxes like info@ and accounts@ connect with no separate login, so the mail nobody owns finally gets an owner.
Entra ID
Single sign-on, and the permission structure documents inherit. Joiners and leavers are handled where your IT already handles them.
Teams
Notifications land where your team already talks, rather than in another app nobody has open.
Microsoft Graph
How documents are written, read back and detected, and how mail syncs. OAuth 2.0 keeps mailbox credentials with Microsoft.
OneDrive
For firms that keep working files in personal libraries rather than a team site. Same filing, same inheritance, same tenant.
Exchange Online
The mail service underneath Outlook. Your transport rules, journaling and retention keep running exactly as configured.
Microsoft authentication
Sign-in happens on Microsoft’s screen, not ours. Whatever MFA and conditional access your firm enforces applies unchanged.
Sign in with Microsoft. That is most of it.
There is no migration project because nothing moves. You are pointing FigsFlow at what you already have.
Sign in with Microsoft 365
Entra ID single sign-on. Your admin grants consent once, and mailbox credentials stay with Microsoft under OAuth 2.0.
Point it at your SharePoint
Choose the library and the folder structure you already use. FigsFlow files into it rather than building its own.
Import your client list
The client record is the one new thing, and it is the thing every other module hangs from.
Nothing is configured before you can see it working. If it does not fit your folder convention on the call, that is worth finding out on the call.
Where this integration stops
Being Microsoft-first has a cost, and it is fairer to state it here than to discover it in week two.
Google Drive is not supported
If your firm runs on Google Workspace, the documents module is not built for you today. Mail is the exception — Gmail connects for firms that do not run on Microsoft 365.
Not supportedCanadian tax-preparation software
Profile, TaxCycle, DT Max and similar connections do not exist today — and the Microsoft integration does not bridge that gap.
Not availableIt does not replace your security posture
FigsFlow layers on top of your mailbox and library. Your spam filtering, conditional access, DLP and retention rules remain yours to run.
By designEvery module leans on this integration
Microsoft 365 is not a page in the platform — it is the floor the other modules stand on. Here is what each one does with it.
Filing, naming and syncing into the library you already own.
SharePoint EmailOutlook mailboxes synced both ways, with an owner on every message.
Outlook CRMNew senders become client records without leaving the inbox.
Client record Jobs and workflowTeams notifications when a job opens, moves or runs late.
Teams Client portalWhat clients upload lands straight in your tenant, not a vendor vault.
Uploads Time and billingInvoices and statements filed to the client folder like everything else.
Filing API and webhooksDocuments exposed as metadata and a SharePoint pointer, never file content.
Graph All integrationsXero, QuickBooks Online, Stripe and what is missing.
Everything elseWhat IT asks first
No. SharePoint and OneDrive stay the master repository inside your own tenant. FigsFlow does the filing, naming and syncing into your library, and holds a pointer plus the context around it — not a copy of the file. There is no third-party file storage.
With Microsoft. The connection uses OAuth 2.0 and Microsoft Graph, so FigsFlow never holds a mailbox password. Access is granted by admin consent and can be withdrawn the same way.
They stay where they are. Documents inherit the permission structure from Entra ID rather than having it recreated, and your retention policy is left untouched. That inheritance is the whole reason the integration works this way.
Yes, and without a separate login. Personal and shared Microsoft 365 mailboxes both connect — which matters because the shared inbox is usually where things go unowned and unanswered.
Both directions — emails, deletions, read status and flags. Delete in Outlook and it is gone in FigsFlow; mark it read on a phone and it is read in both.
Partly. Gmail connects for firms not on Microsoft 365, but Google Drive is not supported, so the documents module is not built for you today. We would rather say that plainly than sell you a workaround.
FigsFlow processes data under a written agreement with your firm. Your firm remains the data controller. Documents stay in your own Microsoft 365 tenant under your retention policy, and FigsFlow holds the workflow and the audit trail — not the files. For firms with Quebec clients, Law 25 obligations are supported by the same architecture: the data never leaves the tenant your firm already governs.
See it running against your own tenant
Thirty minutes, your SharePoint library and your own mailboxes — so your IT lead can watch a document file itself into the folder convention you already use.
Microsoft 365 is confirmed live — not a roadmap item.