FigsFlow › Platform › Microsoft 365
Live · not a roadmap itemRuns inside the tenant you already own
FigsFlow does not ask your practice 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, authentication and permissions remain inside your own SharePoint. Zero third-party file storage.
Microsoft 365 is the foundation, not a connector
Most practice software treats Microsoft as one integration among many. FigsFlow is built the other way round: your tenant is where the work already lives, and the platform arranges itself around it.
Hover or tab a service to inspect it
Graph is the ring, not a spoke. It is the layer everything else travels over — how documents are written, read back and detected, and how mail stays in step in both directions.
Eight 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 practice 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 practices 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 practice enforces applies unchanged.
Counts describe how the integration is built, not a performance claim.
What stays with Microsoft, and what FigsFlow actually holds
The honest version of this answer is a short list on each side. Pick a surface to see the split — this is the slide your IT lead will ask for.
SharePoint and OneDrive remain the master repository. The file itself never becomes FigsFlow’s to hold.
A pointer and the context around it — which client, which job, which stage, and whether it arrived.
Mail continues to live in your Microsoft 365 mailboxes, under the same Entra ID and retention policy IT already governs.
Ownership and status — the layer a shared inbox has never had.
Entra ID remains the source of truth for who works at your practice and what they can reach.
What each person does inside the practice, not who they are.
Teams is where the message lands. FigsFlow does not build a competing chat surface.
The reason a notification was worth sending in the first place.
Not a one-way import that drifts by Thursday
A read-only copy of a mailbox is a copy that starts lying the moment somebody deletes something. Mail syncs both ways — so what your team sees in Outlook and what they see in FigsFlow cannot disagree.
Delete it in Outlook and it is gone in FigsFlow. Mark it read on your phone and it is read in both. The sync covers emails, deletions, read status and flags — which is the difference between an integration and an export.
A signed engagement letter, from click to filed
The clearest way to explain the integration is to watch a single file move through it — and notice how little of the journey belongs to FigsFlow.
The client signs in the portal
A tokenised link, no account to create. The document is produced by FigsFlow from your approved wording — nothing has touched your tenant yet.
Graph writes it to SharePoint
On completion the file is written into your library through Microsoft Graph, using the folder structure and naming convention your practice already uses.
Entra ID decides who can open it
Permissions are inherited from your existing group structure rather than recreated. Your retention policy applies from the moment it lands.
Teams tells the people who care
A notification lands in the channel your team already watches, because the job it unblocked has an owner and a deadline.
FigsFlow keeps the context
What FigsFlow retains is the pointer and the story around it: which client, which engagement, which job it released, and when. The file itself was never ours.
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 practice runs on Google Workspace, the documents module is not built for you today. Mail is the exception — Gmail connects for practices that do not run on Microsoft 365.
Not supportedTax and accounts production software
Direct connections to tax and accounts production tools do not exist today, and the Microsoft integration does not bridge that gap. Ask us about your specific stack on a call rather than assuming either way.
Ask on the callIt 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.
Outlook mailboxes synced both ways, with an owner on every message.
Outlook Meetings and schedulingOutlook calendars and Teams invitations, without a second diary to keep.
Calendar CRM and pipelineNew senders become client records without leaving the inbox.
Client record Jobs, tasks and deadlinesTeams notifications when a job opens, moves or runs late.
Teams Client portalWhat clients upload lands straight in your tenant, not a vendor vault.
Uploads E-signature and approvalsEnvelopes delivered on your own mail, signed copies filed to SharePoint.
Filing Forms and requestsRecord requests chased through Outlook, with answers filed where they belong.
Requests Timesheets and billingInvoices and statements filed to the client folder like everything else.
FilingWhat 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.
Your documents and mail never leave your own Microsoft 365 tenant, so their residency is whatever your tenant is already configured for. What FigsFlow holds is the practice record around them — and we will confirm where that sits in writing before you sign anything.
Partly. Gmail connects for practices 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.
The exact consent scopes are confirmed in writing before you sign anything, and your admin sees them on the Microsoft consent screen rather than taking our word for it. We would rather give you the current list from documentation than paraphrase it on a marketing page.
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.