
FORTRESS INSIDE MICROSOFT 365
Deployed from your own Microsoft 365 admin centre · no desktop install
Draft, redline and rewrite against your own precedent — and save back to the matter
Triage the inbox, draft replies into Drafts, and file mail and attachments to the matter
Build and explain models, and pull structured data out of documents into a sheet
Build the deck from the document, the matter or the data — in your template
THE PROBLEM
WORD
OUTLOOK
Mail classified and summarised by matter, urgency and what it is asking for — so the first ten minutes of the day are spent deciding rather than reading.
Responses written from the thread and the matter behind it, in your voice, with the attachments and authority already pulled.
A message and its attachments logged to the matter or account record — so the file is complete without anyone maintaining it by hand.
AI projects, knowledge bases and matters are reachable from Outlook directly, so a question about a matter does not require opening another application.
Review rules can run in the background for the users who want them, and stay off for the users and organisations that do not.
THE RULE WE DO NOT BEND
Automations never send email. They draft into your Drafts folder and stop there — a person reads it and a person sends it. Every time.
EXCEL
Extract from documents into rows
Contract terms, deal points, valuation inputs, obligation dates — pulled from the underlying documents into a structured table, each cell traceable to the page it came from.
Explain a workbook you inherited
What the model does, which cells drive the output, where the hard-coded assumptions are and what changed between two versions.
Build the analysis
Formulas, pivots and summary tables built from a plain-language description of what you are trying to show.
Live data from the platform
Matter lists, obligation calendars, caseload, portfolio metrics — pulled into the sheet from Fortress rather than re-exported by hand each month.
Reconcile two sources
Two schedules, two exports or two versions compared, with the differences listed rather than eyeballed.
POWERPOINT
WHAT IS ACTUALLY BEHIND IT
SETUP
01
IT deploys centrally
From your Microsoft 365 admin centre, to the users or groups you choose. No download, no local install, nothing for a user to configure.
02
The user connects once
Profile icon, top right → Settings → External Credentials → allow iManage, allow Outlook. That one step is what bridges the connection.
03
The pane appears
Fortress shows up in the ribbon in Word, Outlook, Excel and PowerPoint, already pointed at the user’s matters and knowledge bases.
SECURITY
Nothing gets pasted anywhere
The draft stays in the document and the mail stays in the mailbox. The most common way confidential material escapes simply does not happen.
Your own tenant
Fortress runs in your organisation’s environment on Salesforce infrastructure, not as a shared consumer service sitting outside your security boundary.
Your data is not training data
What goes through the plug-ins is not used to train models, in language a security questionnaire can be answered with.
Graph permissions match the product
The permission list reflects what the add-in actually does — not a broad grant asked for once and never explained.
Automations never send
Background review can draft, but only into your own Drafts folder. A person reads it and a person sends it. Organisations that want automations off entirely get them off.
Configurable per user and per org
What the assistant is allowed to do is set by the organisation and, within that, by the user — not assumed on at install.











