Microsoft 365 is where your staff work, and where your automation should run.
We connect SharePoint, Outlook, Entra ID, Groups, Teams and Planner to your legal systems, and we run that automation inside your own tenant.
Microsoft 365 integration, built around your firm
Microsoft 365 is the one system everyone in the firm uses all day. Email arrives in Outlook, documents sit in SharePoint and OneDrive, matter teams meet in Teams, and Entra ID decides who can sign in to what. It is also where your security policies, retention and eDiscovery already apply.
Left unconnected, it fills up with copies and loose ends. Matter email stays in personal inboxes. SharePoint libraries are created by hand without metadata, so documents are hard to find later. Matter teams in Teams drift away from the staffing in the practice management system. Follow-ups promised on a call never become a task anyone sees.
We use Microsoft Graph, Microsoft's API for Microsoft 365, to connect your tenant to your practice management, document management, docketing and phone systems. Matter groups, Teams and SharePoint sites are provisioned from templates when a matter opens. Mail is filed by rule. Tasks and calendar entries land with the right person. Because the code runs in your Azure subscription under identities your firm owns, Microsoft 365 is both a system we connect and the platform everything else runs on.
The Microsoft 365 data we work with
SharePoint and OneDrive
Create folders, upload and download files, set metadata columns, and track what changed in a library through Graph's change feed.
Outlook and Exchange
Read, move, categorize and send mail, and create or update events on user calendars, in the mailboxes your firm approves.
Entra ID users and groups
Read staff accounts and group membership, and keep matter groups in step with the team in your practice management system.
Microsoft 365 Groups and Teams
Create a group per matter, turn it into a Team from your template, add channels, and manage members and owners.
Planner and To Do
Create and update tasks with owners and due dates, in a matter's plan or a person's own task list.
How the Microsoft 365 integration works
- An app registration your firm owns. The automation signs in through an Entra ID app registration in your tenant. Permissions that work without a signed-in user always need an administrator's consent, and your IT team can revoke them at any time.
- Least privilege, scoped down. SharePoint access can be limited to specific sites with Sites.Selected, and Exchange Online can restrict which mailboxes an application can reach. We ask for the narrowest permission that does the job and list each one in writing.
- Change notifications, with a safety net. Graph pushes notifications for mail, user calendars, files, lists, users, groups and Teams. Subscriptions expire and must be renewed, and notifications can be delayed or dropped, so we also run delta queries to reconcile. Planner tasks and group calendar events have no notifications, so those are checked on a schedule.
- Group calendars need a signed-in account. Events on a Microsoft 365 group calendar can only be written with delegated (signed-in user) permissions, not by an application on its own. Where a flow writes to group calendars, we use a dedicated account your firm controls and document the trade-off.
- Power Automate where it fits. Simple, single-step jobs often belong in Power Automate, and we build those there. Anything that writes to a system of record or crosses several systems gets tested code with an audit trail.
Where Microsoft 365 fits
Signed client → matter open everywhere at once
Matter opening goes from days of handoffs to minutes, and every system starts with the same data.
Email and documents filed by rule
Complete matter files without anyone dragging and dropping.
Two-way matter sync: practice management ↔ docketing
One matter, identical in every system, without anyone keying it twice.
Often connected with
Questions about connecting Microsoft 365
Why not just build all of this in Power Automate?
For simple jobs, we do. Flows often run on one person's connection and can be edited live by anyone with maker rights, which is fine for low-risk work. For automation that writes into your matters or spans several systems, we use tested code that runs under its own identity and changes only through reviewed releases.
Will the app be able to read every mailbox in the firm?
Not unless you allow it, and we won't ask. Application mail permissions cover the whole tenant by default, so we pair them with Exchange Online controls that restrict the app to the mailboxes in scope, such as a docketing or intake mailbox.
What do you need from our IT team?
An Azure subscription or resource group for the deployment, an administrator to approve the app registration and its permissions, and your security policies for vendors. We document every permission we request and why.
Some of our mailboxes are still on an on-premises Exchange server. Do they work?
Not through Microsoft Graph. Mailboxes still hosted on-premises in a hybrid Exchange setup can't be reached by Graph's mail and calendar APIs, so they need to move to Exchange Online first.
Running Microsoft 365 with other systems?
Tell us what you use and where your staff re-key data. We’ll tell you honestly what’s possible, and what your vendors already cover.