DWT announced the expansion on August 18, saying Harvey will support drafting, research, review, analysis, and document-heavy work, while Microsoft Copilot will be available in Teams, Outlook, Word, Excel, and PowerPoint. The firm says its program includes security review, governance, training, and professional supervision. No independent reporting has yet described DWT’s deployment scope, licensing volume, or which practice groups receive Harvey access first.
The announcement also contains a timing problem worth flagging for enterprise administrators. DWT says its adoption of Microsoft’s “AI Frontier Suite,” powered by Microsoft 365 E7, is expected to enable Copilot Agents and Copilot Cowork beginning in early 2027. Microsoft’s own product record says Microsoft 365 E7: The Frontier Suite became generally available on May 1, 2026, and its current documentation lists Copilot Cowork as generally available for work and school accounts. DWT may be describing its own internal rollout schedule rather than Microsoft’s availability, but the firm does not make that distinction.
For law firms considering the same path, that gap matters. Copilot Cowork is not a distant planning feature: it can perform multistep work across Microsoft 365, including drafting and sending email, scheduling meetings, creating documents, posting to Teams, and managing files. Microsoft says it pauses for approval before important actions, but an approval prompt does not substitute for tenant controls, matter-level access design, or review of the AI’s underlying analysis.
DWT is deploying a legal platform alongside the Microsoft work layer
DWT’s decision to deploy both Harvey and Microsoft Copilot reflects an increasingly practical division of labor in enterprise AI. Copilot is embedded in the collaboration and document tools where legal teams spend much of their day; Harvey is intended to apply legal-oriented research, drafting, document review, and analysis capabilities. The combination can reduce application switching, but it also creates two administrative surfaces rather than one.
Harvey has been building integrations for Microsoft 365, including Microsoft 365 Copilot, SharePoint, Word, and other services. Harvey says its Copilot integration can bring its legal intelligence and material in Harvey Vault into Microsoft 365, while its newer Cowork integration is designed to support multistep legal processes. That integration makes DWT’s dual-platform strategy more coherent than a simple “Copilot plus another chatbot” purchase.
But DWT’s statement does not say whether it has enabled Harvey inside Microsoft 365 Copilot, whether Harvey Vault will hold client or matter material, or whether lawyers will work primarily in Harvey’s own interface. Those are operationally different deployments. A firm can license both products while still keeping their document repositories, permissions, audit trails, and data-handling boundaries separate.
That omission is especially relevant because a Microsoft 365 Copilot deployment normally respects the user’s existing Microsoft 365 permissions. If a user already has access to a SharePoint site, Teams channel, OneDrive folder, or mailbox content, Copilot can use that information in response to authorized prompts. AI does not repair overshared workspaces; it can expose their practical consequences faster.
For a legal organization, the first security question is therefore not whether Copilot or Harvey has a general enterprise security program. It is whether the firm’s matter walls, ethical screens, client confidentiality classifications, guest access, legacy SharePoint permissions, and document-management integrations have been tested before the tools are allowed to synthesize information across them.
Copilot Cowork changes the risk from answers to actions
Microsoft’s current Copilot Cowork documentation describes a system that can break a request into steps, work through them, and ask the user to approve sensitive actions such as sending an email or scheduling a meeting. It runs across the Microsoft 365 environment and can interact with Outlook, Teams, Word, Excel, PowerPoint, OneDrive, SharePoint, calendars, and organization search.
That is a significant change from using Copilot merely to summarize a meeting transcript or create a first draft. In a law firm, a prompt such as “prepare the closing checklist, circulate the status update, and schedule a call with the transaction team” can implicate privileged documents, external communications, client names, and deadlines. Approval checkpoints reduce the chance of unattended execution, but they leave the firm responsible for deciding which actions deserve mandatory review and which users can invoke the agent at all.
Microsoft’s administrative guidance is unusually direct on this point. Frontier access is controlled at the tenant level, though administrators can assign access to all users or specific users. Microsoft also says that access to Frontier features varies by subscription and role, requires Microsoft 365 Copilot licensing, and that certain agents must be separately allowed in the Microsoft 365 admin center.
The practical implication for DWT and comparable firms is that firmwide Copilot availability should not be confused with firmwide Cowork permission. A controlled pilot can target a Microsoft Entra ID security group, assign a defined set of users, install and pin specific agents, and leave broader access disabled. Microsoft recommends this group-based approach for validating agents before wider rollout.
DWT’s release says key decisions and approvals will remain under user control. That is the right principle, but it does not answer the configuration questions that determine whether it works in practice:
- A firm needs to decide whether agent access is limited to particular roles, offices, practice groups, or matter teams rather than enabled indiscriminately.
- A firm needs to establish which external-facing actions always require approval, even if users choose settings that suppress repeated prompts for similar actions.
- A firm needs to test whether search results and generated drafts respect information barriers, ethical walls, sensitivity labels, and exclusions in real client-matter scenarios.
- A firm needs an audit process for both user prompts and agent actions that is usable when a client, regulator, or court asks how a document or communication was produced.
These are administration and process questions, not objections to using AI. DWT’s public statement promises governance, but its usefulness will depend on how specifically those controls are implemented and enforced.
The “Frontier Suite” is available now, but frontier features remain changeable
DWT calls its planned foundation “Microsoft’s AI Frontier Suite,” though Microsoft’s formal product name is Microsoft 365 E7: The Frontier Suite. Microsoft introduced E7 as a bundle of Microsoft 365 E5, Microsoft 365 Copilot, Agent 365, Microsoft Entra Suite, and advanced Defender, Intune, and Purview capabilities. Microsoft priced it at $99 per user monthly when announcing general availability on May 1.
That bundle matters to IT teams because the value proposition is not solely a more capable Copilot. E7 ties AI deployment to identity, endpoint management, data protection, security operations, and agent governance. A law firm that already has E5 may see E7 as a way to consolidate procurement and management; a firm without that baseline has a much larger architectural and financial decision to make.
DWT does not disclose whether it will use the complete E7 feature set, what it previously licensed, how many seats it is buying, or the commercial terms of its Harvey agreement. It also does not say whether the 90% adoption target applies to all employees, all attorneys, only Copilot users, or the combined Harvey and Copilot program. Adoption targets without a denominator make poor measures of deployment maturity.
There is another distinction: the Microsoft Frontier program remains Microsoft’s early-access channel for experimental features, while the E7 suite itself is generally available. Microsoft’s administrator documentation says Frontier features are previews and subject to change. Administrators can control access, and not every capability will be available to every subscription, user role, market, or configuration.
So the safest reading of DWT’s release is not that Cowork itself will arrive in early 2027. It is that DWT expects to expand its own use of Copilot Agents and Cowork on that timetable. Microsoft’s published product documentation says Cowork is already available for work and school accounts; DWT has not explained why its wider rollout would wait until next year.
The 90% target will test training more than licensing
DWT’s stated goal is to reach 90% AI adoption and place in the top quartile of law firms using AI to improve work delivery. That gives the initiative a measurable ambition, but it does not establish a useful success metric by itself. Opening Copilot, accepting a generated meeting recap, and using an AI system on a consequential research or contract-review task are not comparable forms of adoption.
The firm’s stronger claim is that it will keep professional judgment and verification central. In legal work, that cannot be a generic warning placed at the end of a training module. Verification must be designed into the workflow: attorneys need to know when an AI output is a starting draft, what source material was used, how citations or authorities are checked, when a supervising lawyer must review it, and how to avoid placing prohibited client information into unapproved services.
DWT has a pre-existing public page on its AI tools and has previously described Microsoft Copilot as part of its technology offerings. The August 18 announcement signals a broader commitment by adding Harvey firmwide and moving toward Microsoft’s agent-governance stack. What remains unreported is the implementation evidence that would show whether this is a controlled operational program rather than an access rollout: pilot results, training completion standards, exception handling, workflow restrictions, and the measures used to prove that turnaround time, consistency, or client budget predictability actually improved.
DWT is placing a legal-specialist AI service and Microsoft’s workplace AI stack into the same firmwide program at a moment when Copilot can do more than generate text. The next concrete milestone is therefore not the firm’s early-2027 Cowork target. It is whether DWT publishes the controls that determine who can let an agent act on client-connected Microsoft 365 data—and what must happen before those actions leave the draft stage.
