TECHNICAL NOTES · MICROSOFT 365

What happens behind the scenes? Background integrations with Microsoft 365

Automatic email filing, calendar synchronisation and document saving often run in the background, connecting the legal system to Microsoft 365 through Microsoft Graph. When they work, nobody notices. How they are built decides what happens when they do not.

Checking constantly, or being told

Some integrations repeatedly ask Microsoft 365 whether anything has changed. Others subscribe to change notifications and ask only for what has changed. Microsoft identifies constant polling as the pattern most likely to get an application throttled, and recommends change notifications and change tracking instead. The difference shows up as filing that is minutes behind, or filing that quietly stops at busy times.

What happens when Microsoft says "slow down"

Microsoft 365 limits how many requests an application can make. A well-built integration waits for the time Microsoft specifies and tries again. A poorly built one gives up, and an email that should have been filed to the matter simply is not. Ask how failures are detected, retried and reported, and who is told.

How much can it reach?

Background integrations usually act on their own rather than as a user, which by default can mean every mailbox or every SharePoint site in the firm. Microsoft now lets administrators narrow that: Exchange Online can restrict an application to specific mailboxes, and SharePoint access can be limited to named sites. If the integration only needs fee earners' mailboxes and one document site, that is all it should have.

Where does a copy end up?

Some integrations leave email and documents in Microsoft 365 and store a link. Others copy them into the vendor's own storage. Neither is wrong, but a copy means client data in a second place, with its own security, retention and exit questions.

What to ask, and what to see

  1. Does your integration poll, or use change notifications? Show the delay between an email arriving and it appearing on the matter.
  2. What happens when Microsoft throttles you, and how would we know an item was missed?
  3. Can your access be limited to specific mailboxes and sites?
  4. Do you copy content into your own storage, or reference it in ours?
  5. Who monitors the integration, and what do we see when something fails?

Technical notes: small decisions, big consequences

Start with the overview: The details that decide the project

Accounts and finance

Workflow, data and documents

Your types of work

Security and access

Microsoft 365

Data and decisions

Where does your firm stand?

Our free practice management review shows how much of your current system you really use and, if you are thinking of moving, builds an independent requirements specification that takes your reasons into account. Nothing is sent to us.

Start the free review Talk to us