Most organisations deploy Microsoft 365 and use Outlook, Teams, and SharePoint in isolation. Emails are in Outlook. Documents are in SharePoint. The connection between them — which email relates to which document, which case, which client — exists only in someone's head or in a folder structure that requires local knowledge to navigate.
Power Automate changes that. Here's what's actually possible when you connect Outlook to SharePoint — and the specific patterns we've built and deployed in production.
Email inboxes were designed for communication, not record-keeping. But in most professional services firms, the most important business records — instructions from clients, correspondence with courts or regulators, expert reports, case updates — arrive by email and stay in email.
The consequences are predictable. Only the recipient can find the email. When that person is on leave or leaves the firm, the records are inaccessible. Searching across a mailbox is limited and slow. And there's no connection between the email and the SharePoint document it relates to.
The principle we work to is simple: Outlook is how emails arrive, SharePoint is where they live. Power Automate is what moves them — automatically, consistently, with metadata.
The most common starting point. A shared mailbox (enquiries@, cases@, info@) receives emails that need to be associated with a case or client. A Power Automate flow monitors the mailbox and captures every email — subject, sender, recipients, received date, body — into a SharePoint list.
This gives you a central, searchable log of all incoming correspondence. Every team member with access to the SharePoint list can see every email that's been received, regardless of who the Outlook user was.
Once emails are in the SharePoint list, a second flow handles enrichment. It reads the email subject line for a reference number — a quote reference, case reference, matter number, or client code — and looks that up in the relevant SharePoint list.
When a match is found, the email record is enriched with the metadata from the case or client record: client name, instruction type, case status, responsible fee earner. The email record now carries context that wasn't in the original email.
The final stage moves the enriched email — as a SharePoint item with all its metadata — to the correct folder within the document library. In our forensic case management system: the email moves from the Email Filing Review list into the Correspondence subfolder of the correct case in Active Case Files.
What arrives in the case folder is not just an email — it's an email with Case Reference, Client Name, Instruction Type, and Received Date metadata already populated. It appears in the correct filtered views automatically.
The choice between two-stage (human review before filing) and automatic (flow files immediately on receipt) depends on the confidence you have in the reference matching:
For the forensic practice, we used two-stage because instructions come from solicitors and courts who use their own reference formats. The review step adds a few minutes of human time but eliminates mis-filing entirely.
From the user's point of view, emails simply appear in the right case folder in SharePoint — with all their context — without anyone doing anything. The only interaction is the occasional review step for emails that couldn't be automatically matched. The shared mailbox continues to function normally in Outlook. The filing to SharePoint is invisible to the person sending the email.
Book a free consultation. We'll understand your mailbox structure, your reference system, and your filing requirements — and tell you exactly how to build it.
Book Free Consultation →