You own the best document archive in your industry and you still start from a copy

Here is a scene that plays out in most Microsoft-shop consultancies on a Monday morning. A senior consultant wins the right to bid on a state government ICT advisory panel. She opens the firm's SharePoint site, navigates to Bids > 2025 > Won, finds the closest prior submission, and does what everyone does: opens it, saves a copy into the new engagement folder, and starts deleting the previous client's name.

Nothing about that workflow is broken, exactly. The archive is excellent. Permissions are right. Versioning works. Two people can co-author the same section on the same afternoon without emailing attachments back and forth. Retention policies are enforced centrally, and if the firm is ever asked to produce every document touching a given client, eDiscovery answers in an hour.

And yet the first complete draft of that panel submission will land in nine days, because copying a prior document is not the same as knowing what the new one should say. The archive holds the output of the firm's standard. It does not hold the standard itself. That distinction is the whole subject of this post.

What Microsoft 365 is genuinely good at (keep all of it)

It is worth being precise about this, because the reflex when a new tool appears is to ask what it replaces. In our pilot workspaces, the answer for the Microsoft stack has been: almost nothing. Five things the stack does that a drafting tool should not try to take over.

Storage and permissions. A SharePoint document library with the right site permissions is a solved problem. Client-confidential material stays scoped to the engagement team, and the audit trail is real.
Co-authoring and comments. Word's simultaneous editing, tracked changes, and comment threads are the best review surface most firms have. Partners know how to use them. Clients know how to read them.
The delivery artefact. Whatever your drafting process is, the thing that reaches the client is almost always a .docx or a PDF rendered from one. Procurement portals want Word. Legal wants Word. The format is not negotiable.
The engagement conversation. Teams channels hold the context that never makes it into a formal document: the call where the client said the migration window is non-negotiable, the file someone dropped at 9pm.
Governance. Retention labels, sensitivity labels, DLP, and eDiscovery. If you are in a regulated sector, this is not optional, and rebuilding it elsewhere is a bad idea.

So the question is not whether to leave Microsoft 365. It is what sits between “we have every document we have ever written” and “the next one is drafted”.

Where the stack stops short

A folder is not a template

Firms conflate these constantly. Bids > 2025 > Won is an archive of instances. A template is the abstraction over them: which sections a panel submission must contain, what each one is for, which are decisive and which are boilerplate, and what information you must have in hand before you can write it honestly.

A .dotx file gets you part of the way, in the sense that it holds heading styles and a cover page. It does not hold the reason Section 4 exists, the fact that evaluators score it against three specific criteria, or the rule that your firm never claims methodology experience it cannot name a project for. That knowledge is real, it is firm-specific, and in most practices it lives in two or three heads. We wrote about that at length in templates as institutional memory.

Copilot drafts from a document, not from a standard

Microsoft 365 Copilot is good at what it is designed for. Ask it to summarise a 40-page requirements pack, pull the themes out of a Teams channel, or expand a bulleted outline into readable prose, and it earns its licence fee. Point it at a reference file and it will write in something adjacent to that file's register.

What it does not do is enforce a firm standard across a document type over time. The reference file you point at today is not the same as the reference file the next consultant points at. There is no per-section guideline that says this section must lead with the client's stated risk and close with the mitigation owner. There is no criticality flag separating the two sections that decide the bid from the eight that merely have to be present. And there is no mechanism that makes an edit you made in Section 3 change how Section 9 is written, which is the difference between a document and nine essays under one cover page.

Nothing asks you a question

This is the failure mode that costs the most and shows up the latest. Given a source pack that does not contain the answer, a general-purpose assistant produces a fluent sentence anyway. The draft comes back reading beautifully, with an implementation timeline nobody committed to and a claim about ISO 27001 coverage that is true of a different client. The reviewer catches most of it. Most is not all.

The alternative behaviour is for the tool to surface what it does not know, at the moment it notices, before the assumption propagates through the following fifteen sections. Our five-probe test for source-grounded output is a fast way to find out which behaviour a given tool actually has.

The seam: sources in, .docx out

Once you draw the boundary that way, the integration shape is obvious. Microsoft 365 remains the system of record on both ends, and the drafting workflow sits in the middle.

On the way in, the material that grounds a draft already exists in your tenant: the RFP pack in the bid library, the discovery workshop transcript, the prior submission that won, the technical reference document the delivery lead maintains. SkyDraft treats these as sources, consolidates them as cited context for every section, and works from them rather than from training-data guesses. You can upload them today, and Microsoft Graph and Google Workspace connectors that pull directly from SharePoint and Drive folders are rolling out per workspace.

On the way out, DOCX export is the point of handover. The draft returns to the library it came from, and the partner review happens where partner reviews have always happened: in Word, with tracked changes, in a file with the right sensitivity label on it. PDF and direct SharePoint delivery are rolling out per workspace during pilot.

There is a third connection point that firms miss. Your existing Word documents are the fastest way to build the template. Upload one strong prior submission and SkyDraft extracts the structure, the brand voice, the glossary, and the required-information checklist in a single pass. The archive you already have stops being a pile of instances and becomes the raw material for the standard. The how-it-works walkthrough covers what the extraction pass captures.

A concrete run

A 30-person infrastructure advisory firm, entirely on Microsoft 365, bidding a four-year state panel. Roughly 40 pages across eight response schedules, fourteen days to submit, three people on the bid alongside their delivery work.

Day one, morning. The bid manager uploads the tender pack, last year's near-miss submission for the same agency, and the transcript of the go/no-go call. Then she uploads a strong prior submission as the template source. The extraction pass returns a section structure, per-section guidelines, the firm's voice, and a required-information checklist. She spends forty minutes correcting it, because the extraction gets the shape right and the judgement calls need a human. Section 4 gets marked critical. A guideline goes on Schedule 6 saying personnel claims must map to a named project.

Day one, afternoon. First generation run, section by section, with a review gate on each. The methodology schedule drafts cleanly because the source pack is rich. The transition-in schedule comes back with two clarification questions: the tender asks for a named transition manager and the sources do not say who, and the mobilisation window in the pack conflicts with the one in last year's submission. Both are genuine gaps. Both would have been silently invented by a general assistant, and both would have been found in week two of review.

Day two. She answers the clarifications. The answers become persistent context, so the transition manager's name appears correctly in the three later schedules that reference them. The compliance matrix runs as a repeating section, one drafted entry per requirement discovered from the tender pack, which is the shape that stops requirements from quietly going missing.

Day three. Complete draft exported to .docx, filed into the bid library, and circulated to the two partners for review in Word. Eleven days left, and the remaining work is the work that actually wins panels: pricing strategy, the named personnel, sharpening the two schedules that carry the evaluation weight. Nobody spent day nine assembling a first draft.

What to keep in Microsoft 365 on purpose

Drawing this line badly is how firms end up with two systems of record and a governance problem. Four things should not move.

The final artefact and its label. The submitted version lives in the bid library with the sensitivity label applied, inside your retention policy. A drafting tool holds a working copy, not the record.
Partner review. Tracked changes in Word, with the reviewers who already know that surface. Section-level review during generation is a different gate at a different time, and it does not replace the partner read.
Client-facing collaboration. If the client comments on drafts, that happens in the channel and the library you already share with them.
Identity. Sign-in should run through your existing directory. Nobody needs another credential set for a tool that touches client-confidential material.

Four questions before you wire the two together

If you are evaluating this for a Microsoft-shop firm, these are the ones that decide whether the integration is real or decorative.

Which library holds the truth? Name it before you start. If the answer is ambiguous, you will end up with the final version in the wrong place at least once.
Does the .docx survive the round trip? Export a real document, open it in Word, and check the heading levels, tables, and numbering. A draft that needs twenty minutes of reformatting has given back the time it saved.
Who owns the template? One named person per document type, the way one person owns the .dotx today. Templates that everyone can edit and nobody maintains decay exactly like shared drives do.
What happens to a source after drafting? A confidential transcript uploaded as a source is client material. Know where it sits, who can see it, and how it is removed.

The short version

Microsoft 365 solves storage, permissions, collaboration, governance, and the delivery format. It does not encode what a good proposal looks like at your firm, it does not enforce that standard on the next junior who drafts one, and it does not ask you a question when the source material is silent. Those three gaps are where the day of drafting goes.

The useful mental model is not migration. It is a drafting stage that reads from your tenant and writes back to it, with the firm standard held as something executable in between. See the use cases for how that plays out across proposals, tenders, engagement reports, and compliance evidence.