Microsoft Copilot As The OS For Work – When The Front Door Moves, Frontier Enrollment Becomes The Control

Publication Record

Evidence current through: Thursday, November 19, 2026, at 12:58 a.m. UTC (7:58 p.m. ET and 4:58 p.m. PT on Wednesday, November 18), when every source had been read again.

Home, Office in Copilot, and Copilot Managed Runtime are generally available. Autopilot, Workspaces, Today, and Copilot Code are in Microsoft’s Frontier program, and the note reads each product at the status Microsoft gave it by the time above. Developments after that time are not reflected. Times in the text are given in UTC.

Research Note In Two MinutesNote synopsis · AI drafted · Analyst reviewed

Drafted by AI from the full research note and reviewed by a Greyhound Research analyst before publication. The analysis and conclusions are Greyhound Research’s own.

At Microsoft Ignite on November 17, 2026, Microsoft’s chief executive called Copilot the new OS for work. Microsoft made Home, a single starting page in the Copilot app, the place where work begins, and put Word, Excel, and PowerPoint inside it. Both are generally available, meaning fully released with support and service terms. Copilot Managed Runtime, which hosts the small apps employees build, is generally available too. The agents that do work on a person’s behalf are not. Autopilot, Workspaces, Today, and Copilot Code are in the Frontier program, Microsoft’s early access route for previews.

Greyhound Research’s position is that the front door has moved, and the control is now who walks through the Frontier side of it. The doorway change reaches every licensed user this winter, so training plans must move now. The agent features that justify the OS claim sit under preview terms. Those terms do not include HIPAA coverage, do not meet three ISO standards for security and privacy, and may not carry service levels. Greyhound Research reads this as a familiar stage of a platform shift, in which the interface is released ahead of the capability that justifies it. The companies likely to fare best will move every user to the new doorway now and treat each Frontier enrollment as a decision about data, not enthusiasm.

Three findings carry the argument. First, Home and Office in Copilot change where every user starts work, and Microsoft’s rollout notices carry no training guidance. Second, Microsoft’s Frontier page says HIPAA Business Associate Agreement coverage is not included and that Frontier features do not comply with ISO 27001, 27002, or 27018. Third, Microsoft’s launch post says Autopilot leaves a clear audit trail, while its own documentation says Autopilot activity is not a guarantee of a complete audit record.

The note sets out a ten-move Greyhound CXO Runbook, with seven exhibits, six tables, and six questions for Microsoft. None of the moves waits on Microsoft. The first three are simple to state. Retrain users on the new doorway by role this quarter. Enroll named pilot groups in Frontier, not all users. Keep regulated data out of Frontier features until their terms change.

The evidence has limits. Microsoft’s pages word some statuses differently, and the note gives both readings where they differ. Microsoft’s Cowork documentation is marked as prerelease and still describes a preview. The note reads Agent 365 economics and agent identity only where they touch the front end, and leaves both to companion Greyhound Research notes. Until Microsoft publishes release dates and terms for the agent features, the advice holds: move the doorway now, and enroll the agents slowly.

In This Research NoteSection guide · AI drafted · Analyst reviewed

Eighteen sections in nine parts, each with a short summary. Select a title to go straight to that section. Each section opens with a Greyhound Spotlight, the one fact in it a reader would not expect, and thirteen end with a block named The Deeper Read, which holds the fuller argument and the passages it rests on. Select any line in that block to open its full text.

  1. Part 1What Ignite Changed
  2. 1.1What Microsoft Announced: Eight Products, Three Release Tracks

    Home, Office in Copilot, and Managed Runtime are generally available. Cowork has been since June. Code, Autopilot, Workspaces, and Today sit in the Frontier program, with Code due in December.

  3. 1.2The Front Door Moves: What Changes For Every User This Winter

    Home becomes the starting point, Office opens inside Copilot, Notebooks become Workspaces, and the address changes. Who must act on each change, and when it arrives.

  4. Part 2The New Front End
  5. 2.1Adoption And Training: Teach The Doorway, Then The Delegation

    Five steps put a Frontier feature in a user’s hands. Microsoft has written the first four for Autopilot and none for training. Why adoption now means teaching people to delegate and check.

  6. 2.2Copilot Code And Managed Runtime: Every Employee A Builder

    Code lets anyone describe an app and get one. Managed Runtime hosts those apps in the tenant and is generally available. The new estate is many small apps, each with an owner to name.

  7. Part 3The Frontier Line
  8. 3.1Frontier Or General Availability: The Calendar Buyers Must Track

    The new Copilot arrives over nine months, from Cowork in June to Workspaces in the deferred ring in February. Which features land when, and on which ring.

  9. 3.2Frontier Terms: What The Preview Contract Leaves Out

    Frontier features run under the customer’s existing agreements, but without HIPAA coverage, without three ISO security standards, and possibly without service levels. The terms row by row.

  10. 3.3Whose Model: Claude Inside Copilot And The EU Boundary

    Cowork launched on Anthropic’s models, and Copilot lets users pick OpenAI or Anthropic. Anthropic’s models sit outside the EU Data Boundary and are off by default in Europe and the UK.

  11. Part 4Agents In The Front Door
  12. 4.1Autopilot: A Colleague With Its Own Name And Mailbox

    Autopilot is a standing agent with its own identity, memory, mailbox, and computer. Microsoft documents approval before consequential actions and leaves memory retention and audit completeness open.

  13. 4.2The Audit Gap: A Clear Trail In The Launch Post, No Guarantee In The Documentation

    Microsoft’s launch post says Autopilot’s actions are logged under its own name. Its documentation says activity is not a guarantee of a complete audit record. Which statement a buyer can rely on.

  14. Part 5The Platform Contest
  15. 5.1Two Front Doors Compared: Microsoft And Google

    Google announced a single Gemini agent for work in October, inside Workspace, in private preview. Microsoft is ahead on released features and has written its preview terms down.

  16. Part 6The Risks And The Counter-Argument
  17. 6.1Risks To Watch: Where The New Front Door Can Go Wrong

    Five risks, from a two-speed workforce to regulated data in Frontier, each with an early warning in the buyer’s own estate and an owner.

  18. 6.2The Strongest Objection: Frontier Is How Leaders Get Ahead

    The fair counter-case: early access builds skills, admins already control enrollment, and the core agreements carry over. It holds, except on regulated data.

  19. Part 7What To Do, By Role
  20. 7.1The Greyhound CXO Runbook: Ten Moves Before The Agents Arrive

    Ten moves for change and adoption leads, the CIO, data protection, security, procurement, platform owners, finance, people, architecture, and risk, each naming the assumption it corrects and who decides.

  21. 7.2Questions For Microsoft: What Buyers Will Ask Next

    Six questions only Microsoft can answer, on release dates, terms at release, the audit record, models, memory retention, and training. Each is tied to a Runbook move.

  22. Part 8The Final Greyhound Standpoint
  23. 8.1Copilot As The OS For Work: The Final Greyhound Standpoint

    The doorway is released, the agents are previews, and Frontier enrollment is the control. The limits of the evidence, and the signals that would change the view within twelve months.

  24. Part 9Appendix, Sources, And Disclosures
  25. 9.1Appendix: The Evidence Register, Source By Source

    Every source behind this research note, with when it was read and where it is used. Passages quoted in The Deeper Read are not repeated here.

  26. 9.2Sources And References: Every Document Behind Every Claim

    Thirty-four sources in five classes, from Microsoft’s announcements and documentation to its rollout notices, Google and the media, and the research this note builds on.

  27. 9.3Disclosures: Independence, Financial, Intended Use, Methodology, Authoring, And Copyright

    Independence first, then the Financial Disclosure, intended use, research method and its limits, authoring, and copyright terms.

Where To Start, By RoleReader guide · AI drafted · Analyst reviewed

Part 1What Ignite Changed

What Microsoft Announced: Eight Products, Three Release Tracks

Greyhound SpotlightMicrosoft’s chief executive wrote that Copilot is the new OS for work. On stage he went further and said apps are just plugins to Copilot.

Microsoft’s chief executive, Satya Nadella, wrote on November 17 that Copilot is the new OS for work, a description he had used in September and used again in late October. In his Ignite keynote, he also said that apps are just plugins to Copilot. Behind the phrase sit eight products. They reach customers on three tracks: generally available now, in the Frontier program now, and promised for a later date. For a CIO, that means the news is half a product to deploy and half a roadmap to plan for.

What is new is the order of release, not the ambition. Earlier Copilot launches arrived as features inside each application, bought and judged one product at a time. This time the starting page is released first and the agents that justify it follow on a separate track. Greyhound Research expects the doorway to reach most users well before the agents leave Frontier, so it is likely to become the habitual way into Microsoft 365 before anyone has signed for the agents. The effect that is easy to miss is on business cases. One written around the OS claim can borrow its benefits from the preview half while taking its costs from the released half.

Table 1 sets the eight products by status, with what Microsoft has written about each and what it has not. The Frontier program is Microsoft’s opt-in route for customers who want previews before they are released.

Greyhound Research · Table 1 · Status ledger

The doorway is released, and the agents are previews

The eight Copilot products Microsoft named at Ignite 2026, plus Auto, by status, with what Microsoft has and has not written, November 19, 2026.

Fund the released rows as a release. Treat every Frontier row as a pilot until it has a date.

Generally availableFrontier or private previewContext
ProductStatusWhat Microsoft has writtenNot yet written
HomeGenerally available“Home is your new starting point in Copilot”Rolling out worldwide. Deferred release from late November 2026Training guidance for users
Office in CopilotGenerally availableWord, Excel, and PowerPoint inside the Copilot appFiles saved to OneDrive with existing permissions and labelsTraining guidance for users
Copilot Managed RuntimeGenerally available“securely hosts what you build in Cowork, Code and Copilot Studio”Status of Agents and Workflows, a first iteration
CoworkGenerally available since June 16, 2026Multi-step tasks, billed by use in Copilot CreditsDeclarative agents in Cowork: Frontier private previewWhich models carry the work today
Copilot CodeFrontierDashboards, trackers, and apps from plain wordsGeneral availability planned for DecemberA firm date. English only at this release
AutopilotFrontier, rolling outA standing agent with its own identity, memory, and mailboxOff by defaultRelease date, memory retention, complete audit record
WorkspacesFrontierA shared space for people and agentsReplaces Notebooks. Standard release by January 2027Terms at release
TodayPrivate preview in FrontierA daily view in the Copilot app and OutlookDaily brief in the license. Updates through the day use creditsRelease date
AutoGenerally available, with a Frontier partRecommends moving from Chat to CoworkAuto in Cowork uses Microsoft-Decision-1.1, for Frontier customersWhich models it picks for each task
Against this: The released rows already change where every licensed user starts work, so half of the announcement is a deployment, not a roadmap.
Source: Microsoft Book of News (November 17, 2026), Microsoft Copilot Blog (Spataro, November 17, 2026), Microsoft 365 Blog (Lamanna, June 16, 2026), Microsoft 365 message center, Microsoft Learn.

Table 1 lists Microsoft’s Copilot products by status, and shows four generally available and four in the Frontier program. Generally available: Home, Office in Copilot, Copilot Managed Runtime, and Cowork, released on June 16, 2026, whose declarative agents remain a Frontier private preview. In Frontier: Copilot Code, with general availability planned for December, Autopilot, rolling out and off by default, Workspaces, which replaces Notebooks, and Today, in private preview. Context: Auto, generally available for recommending Cowork, with Auto in Cowork for Frontier customers. Each row names what Microsoft has not yet written. Statuses are as Microsoft published them through November 19, 2026.

Table 1. The doorway is released, and the agents are previews. Data as of November 19, 2026. © Greyhound Research.

The doorway is released. Home, Office in Copilot, and Copilot Managed Runtime are generally available, and Cowork, the feature that carries out multi-step tasks, has been since June. The agents are not. Autopilot, Workspaces, and Today are Frontier previews with no release dates, and Copilot Code is in Frontier with general availability planned for December. Budgets and training plans for the next two quarters belong on the released rows.

Greyhound Standpoint:

At Greyhound Research, we believe Ignite 2026 made Copilot the front door to Microsoft 365 in fact and not only in marketing, but the claim to be an operating system for work rests on the part of the announcement that is not yet released. A generally available product arrives with support commitments, service terms, and a predictable change process. A Frontier preview can be modified, suspended, or withdrawn, and may sit outside the service levels a buyer has negotiated. A budget or business case that treats the second as if it were the first carries a risk the buyer has accepted without pricing it.

Anyone who has followed several platform shifts will recognize the shape. Vendors tend to announce the destination and the first step on the same day, and the distance between them is where enterprise plans most often slip. Microsoft deserves credit for publishing three distinct tracks rather than blurring them. The limit of this reading is that Microsoft has given no release dates for Autopilot, Workspaces, or Today, so the length of the gap is unknown, and published dates would shorten the caution. CIOs should separate the two in the next budget cycle: fund the doorway as a release this quarter, and hold any commitment that depends on the agents until a release date and its terms are on paper.

The Deeper Read · About 3 minutes

Select a question to open the full answer

1What exactly did Microsoft announce for Copilot?

In Microsoft’s words. Microsoft’s Copilot marketing chief, Jared Spataro, wrote that Home is now generally available as the new starting point in Copilot. The Book of News says Office in Copilot is generally available and that Copilot Managed Runtime has reached general availability. It places Autopilot, Workspaces, and Today in the Frontier program, and says Copilot Code will be generally available in December. Microsoft’s Source summary lists Autopilot, Code, Workspaces, Office in Copilot, and Today as the parts of the new Copilot.

Two words for one status. Spataro’s post says Home is now generally available. The Book of News says Home is rolling out worldwide. Spataro writes that Code will be generally available in the coming weeks, while the Book of News names December. The note gives both readings.

What the wording tells a buyer. The two documents agree on direction and differ on tense, and the difference matters more for planning than for marketing. A post that says released and a news book that says rolling out can both be accurate while a buyer’s own tenant still lacks the feature. Greyhound Research reads the Book of News and the rollout notices as the planning documents, and the launch posts as statements of intent. Training dates and budgets are safer when they follow the first.

In the source’s own words

  • The Official Microsoft Blog, Nadella on November 17Copilot is the new OS for work.Source
  • Microsoft Copilot Blog, Spataro on November 17Now generally available, Home is your new starting point in Copilot, where Chat and Cowork come together.Source
  • Microsoft’s Book of News, Microsoft CopilotOffice in Copilot is now generally available, bringing the full power of Word, Excel and PowerPointSource
  • Microsoft’s Book of News, Microsoft CopilotCopilot Code will be generally available in December.Source
2Where did the new Copilot start?

September, not November. Microsoft introduced Home, Code, and Autopilot on September 25, 2026, in a post by Spataro. That post placed Home and Code in the Frontier program first, moved Autopilot, previously called Scout, to private preview, and said Managed Runtime was in preview. Ignite moved Home, Office, and Managed Runtime to general availability and moved Autopilot from private preview into the Frontier program.

Cowork came first. Charles Lamanna, Microsoft’s Executive Vice President, Copilot, Agents, and Platform, wrote on June 16, 2026, that Cowork was generally available worldwide that day, billed on a usage basis in Copilot Credits and requiring a Microsoft 365 Copilot user license.

In the source’s own words

  • The Official Microsoft Blog, Spataro on September 25Code runs in a sandboxed environment and can be hosted securely within your tenant.Source
  • Microsoft’s Book of News, Microsoft CopilotAutopilot is rolling out through the Frontier program.Source
3Is this a return to AI everywhere?

An expected destination. Greyhound Research wrote in April 2025 that Copilot is not a feature but a platform shift, and that it expected Microsoft to convert its productivity stack into the default AI operating layer for knowledge work. Ignite is that expectation arriving, and the phrase itself was not new at Ignite.

Not AI on every surface. In March 2026, Greyhound Research said that Microsoft was not stepping away from AI in Windows but correcting how it is positioned and deployed, after an approach that had pushed Copilot across many surfaces without always delivering clear value. Greyhound Research has also expected enterprises to move from general assistants toward narrower agents built for specific work. The OS for work claim fits that view only when it is read as one starting point with task-specific agents behind it, such as Cowork, Code, and Autopilot, and not as Copilot added to every screen. This note reads it that way, so the earlier view stands and the Ignite framing is its next step rather than a reversal.

In the source’s own words

  • Greyhound Research, April 8, 2025 daily briefWe expect Microsoft to convert its productivity stack into the default AI operating layer for knowledge work.Source
  • Greyhound Research, March 24, 2026 commentMicrosoft is not stepping away from AI in Windows. It is correcting how AI is positioned and deployed within the operating system.Source

↑ Back to the section guide

Part 1What Ignite Changed

The Front Door Moves: What Changes For Every User This Winter

Greyhound SpotlightMicrosoft’s notice on Office in Copilot asks admins to take no action. The same notice says the change alters how existing customer data is accessed.

For most employees, the visible change from Ignite is not an agent. It is a new first screen. Home brings Chat and Cowork together, Word, Excel, and PowerPoint open inside the Copilot app, and Copilot Notebooks are renamed Workspaces. The app itself has a new name and a new web address. None of this needs a new purchase, and all of it changes what a help desk will be asked on Monday morning.

For buyers, the starting screen has become something to govern rather than a preference. In earlier office releases, a new start page meant a training note. A first screen that also reads and edits documents on the user’s behalf is closer to a change in how data is reached, which is what Microsoft’s own Office notice says. In Greyhound Research’s view, help desks are likely to feel the change before any dashboard shows it, with the renamed app and address carrying much of the early volume. The cost that tends to be overlooked sits around the software: intranet links, saved bookmarks, help articles, and browser or network rules written for the old address all point somewhere that has moved.

Exhibit 1 sets six front-end changes against three groups who must act on them: users, administrators, and the trainers and help desk staff who support both. A deferred release is the slower update ring some companies choose for stability.

Greyhound Research · Exhibit 1 · Who the front-end change reaches

Users meet every change, and the notices carry no training plan

Six front-end changes from the new Copilot against the three groups who must act on them, read against Microsoft’s rollout notices and documentation, November 19, 2026.

The doorway is the change most companies will feel first. Train every group before its ring.

Acts nowActs with Frontier firstNo action statedUS Users · AD Administrators · TR Trainers and help desk
What changes on the front end
Users
Administrators
Trainers and help desk
1Home becomes the starting point
USActs now
ADNo action stated
TRActs now
2Word, Excel, and PowerPoint open inside Copilot
USActs now
ADNo action stated
TRActs now
3New app name and the copilot.cloud.microsoft address
USActs now
ADActs now
TRActs now
4Cowork access set by a spending policy
USActs now
ADActs now
TRNo action stated
5Notebooks renamed Workspaces
USActs with Frontier
ADNo action stated
TRActs with Frontier
6Autopilot, Today, and Code
USActs with Frontier
ADActs with Frontier
TRActs with Frontier
Against this: Microsoft’s notices ask little of administrators for the doorway itself, which keeps the release light for IT even as it moves work for users.
Source: Greyhound Research analytical model, not measured data. Greyhound Research reading of Microsoft 365 message center notices MC1535647 and MC1530611, Microsoft Learn, and the Book of News.

Exhibit 1 is a matrix of six front-end changes against three groups, users, administrators, and trainers and help desk staff, and shows that users meet every change. Home as the starting point and Office inside Copilot reach users and trainers now, with no administrator action stated. The new app name and address reach all three groups now. Cowork access through a spending policy reaches users and administrators now. Notebooks renamed Workspaces reach users and trainers through Frontier first. Autopilot, Today, and Code reach all three groups through Frontier first. The marks are Greyhound Research analysis, not measured data.

Exhibit 1. Users meet every change, and the notices carry no training plan. Current through November 19, 2026. © Greyhound Research.

Users meet every change, and trainers meet all but one. Administrators have work in three places: the address, the spending policy that grants Cowork, and the Frontier features. They have one more task that no notice lists. A starting page that every user opens makes files shared too widely in the past easier to find, so old sharing settings matter more than they did. Microsoft’s notices set the dates. Home reaches the standard release ring from late October and the deferred ring from late November. Office in Copilot completes by mid-November, with the deferred ring from early December.

Greyhound Standpoint:

The change most companies will feel first from Ignite is, in Greyhound Research’s view, the one least likely to have a plan behind it. It arrives through ordinary update rings, needs no purchase order, and reaches every licensed user within a few weeks, so it does not pass through the budget and approval steps where change is usually noticed. The cost therefore appears outside the licensing line, in help desk volume and in hours spent finding familiar files. Microsoft’s notice is correct that administrators need take no technical action. For the business, that answer is incomplete, because the same notice says the change alters how existing customer data is accessed.

Across several generations of desktop and office software, changes to a familiar start screen or menu have often produced more support calls than larger upgrades, because they touch habits rather than features. Microsoft has helped by publishing dates for each ring, and the deferred ring gives slower companies a few more weeks. This reading has a limit: the note holds no measured data on help desk load, and companies whose users already work in the Copilot app will feel less of it. Change and adoption leads should take the change to the next change advisory board as a release of the suite, with a short guide, help desk scripts for the renamed app and address, and a date before the deferred ring by which every user has seen both.

The Deeper Read · About 3 minutes

Select a question to open the full answer

1What do Microsoft’s rollout notices say?

Home and navigation. Microsoft’s notice MC1535647, published November 2 and updated November 11, sets the standard release from late October 2026 and the deferred release from late November 2026. It adds Projects, a space in Home for related chats, tasks, and files, and converts Notebooks into Workspaces, with standard release by January 2027 and deferred release by February 2027. It asks admins to review who sits in the spending policy that grants Cowork, and it carries no training guidance.

Office in Copilot. Notice MC1530611, published October 29 and updated November 10, says rollout began and should complete by mid-November 2026, with the deferred release from early December. It asks for no admin action. It notes that the change alters how existing customer data is accessed, and that Copilot gains expanded ability to read and edit Office documents.

What the notices tell a buyer. Read together, the two notices describe a change that is light for administrators and heavy for everyone else. They ask for one review, of the spending policy, and otherwise no action, while saying the change alters how existing data is accessed. Greyhound Research reads that as accurate for the technology and incomplete for the business. A notice written for administrators will not tell the training team or the data owners that their work has started, so someone inside the company has to carry it to them.

In the source’s own words

  • Microsoft’s Book of News, Microsoft CopilotFiles are saved to OneDrive and inherit Microsoft 365 permissions, sensitivity labels and compliance controlsSource
  • Microsoft Copilot Blog, Spataro on November 17all this value is already included in your Copilot subscription license.Source
2What is renamed?

A new name and address. Microsoft’s Copilot overview says the Microsoft 365 Copilot Chat app is now called Microsoft Copilot Chat, and that the primary address for the updated app is changing to copilot.cloud.microsoft. The same page says the Home tab provides a unified starting point for Chat and Cowork in the Copilot app.

A familiar problem. Greyhound Research wrote in March 2025, in Microsoft Copilot: The AI Revolution That’s Lost in Branding Chaos, that Copilot had become an overcrowded term with conflicting meanings for different audiences, and called that a strategic weakness. The new names simplify the front end, so that critique is answered in part: one starting page and one app name help, while the Copilot name still covers many products. They also mean one more round of renaming for users to learn.

In the source’s own words

  • Microsoft Learn, What is Microsoft Copilot?The Microsoft 365 Copilot Chat app is now called Microsoft Copilot ChatSource
  • Greyhound Research, Copilot branding note"Copilot" has become an overcrowded term with conflicting meanings for different audiences.Source
3Does the new doorway expose old permissions?

Old sharing, new reach. Microsoft’s deployment guidance, last updated November 13, says Copilot grounds its responses in the data users already have permission to access. It recommends Microsoft Purview and SharePoint Advanced Management to find high-risk sites and files and restrict them, and says SharePoint Advanced Management is included with the Copilot license. Copilot does not widen anyone’s access. A single starting page for every user does make content that was shared too broadly years ago easier to reach, so the cleanup belongs before the deferred ring and not after it.

In the source’s own words

  • Microsoft Learn, Copilot foundational deployment guidanceMicrosoft Copilot can accelerate how people find information, summarize content, and get work done by grounding responses in the data users already have permission to access.Source

↑ Back to the section guide

Part 2The New Front End

Adoption And Training: Teach The Doorway, Then The Delegation

Greyhound SpotlightJoining the Frontier program does not switch Autopilot on. An administrator must also license it, cover the user with a spending policy, and activate it, and it is off by default.

Adoption used to mean teaching people where a button sits in Word. The new Copilot asks for something harder. Users now hand whole tasks to Cowork and, in Frontier, to Autopilot, a standing agent with its own name. They must learn to describe an outcome, set limits, approve actions, and check the result. That is delegation, and most training programs were not built to teach it.

The shift matters because it changes who carries the training. Feature training was largely a task for IT and the help desk, delivered once and refreshed with each release. Delegation training sits closer to management practice: how to brief, how to check, and when to step in. That moves part of the work to line managers and learning teams. Greyhound Research expects the companies that report early value from Cowork and Autopilot to be those that taught scope and checking before they taught features. A less obvious consequence follows. Once a task is delegated, the quality of its result depends on the instruction, so a weak brief can look like a weak product and skew a pilot’s verdict.

Exhibit 2 follows the five steps that put a Frontier feature such as Autopilot in a user’s hands, read against Microsoft’s documentation. A spending policy is the admin setting that lets a user run features billed by use.

Greyhound Research · Exhibit 2 · The path to a Frontier feature

Microsoft has written the gates and left out the training

Five steps that put a Frontier feature such as Autopilot in a user’s hands, read against Microsoft’s documentation and rollout notices, November 19, 2026.

Microsoft has documented the gates well. Teaching people to delegate is the buyer’s work, and it comes first.

Written by MicrosoftPartly writtenNot written
1Enroll WrittenAn admin turns on Frontier for named users or all usersWritten. Frontier is set at the tenant level, for all users or specific users and groups.Open. Which users Microsoft recommends for a first wave.
2License WrittenThe user holds a Copilot licenseWritten. Copilot features in Frontier need a Microsoft Copilot license.Open. None for this step in the documents read.
3Fund WrittenA spending policy covers features billed by useWritten. Autopilot needs a spending policy for billing by use.Open. Costs are the subject of a companion note.
4Activate Partly writtenEach feature is switched on for the userWritten. Autopilot is off by default, and enrollment alone does not enable every preview.Open. Activation steps for Workspaces and Today.
5Train Not writtenUsers learn to delegate, approve, and checkWritten. User pages advise a bounded first task and checking results at their destination.Open. Training guidance in the rollout notices for the new front end.
Against this: Microsoft’s user pages do teach the right first habits: start with a bounded task and check each result where it lands.
Source: Greyhound Research analysis of Microsoft Learn (Frontier program, Get started with Autopilot, Autopilot overview) and Microsoft 365 message center notices MC1535647 and MC1530611. The steps and grades are Greyhound Research’s.

Exhibit 2 sets out five steps to a Frontier feature as a numbered list, and shows that Microsoft has written the first three, partly written the fourth, and not written the fifth. Step one, enroll, is written: Frontier is set for all users or specific users and groups. Step two, license, is written. Step three, fund through a spending policy, is written for Autopilot. Step four, activate, is partly written: Autopilot is off by default, and enrollment alone does not enable every preview. Step five, train, is not written in the rollout notices, though user pages advise a bounded first task. The steps and grades are Greyhound Research analysis.

Exhibit 2. Microsoft has written the gates and left out the training. Current through November 19, 2026. © Greyhound Research.

Microsoft has written the gates in detail: enroll, license, set a spending policy, and activate. The last step is the one adoption leads own. Neither of Microsoft’s two rollout notices for the new front end gives training guidance, and the Office notice suggests only that admins inform users. The documentation does tell users to start small and to check results at their destination.

Greyhound Standpoint:

Greyhound Research holds that adoption of the new Copilot is a delegation skill rather than a feature skill, and that most training budgets are still organized for the second. A user who hands a task to Cowork or Autopilot must decide what the outcome is, what the agent may not do, what to approve, and how to check the result where it lands. Most delegation errors are errors of scope. An agent told too little tends to do too much, and the cost shows up as rework, a message sent too early, or a file changed that should have been left alone.

Enterprises that moved work to outsourcing providers in earlier decades learned the same lesson at the level of the organization: writing the instruction and checking the result proved harder than finding the provider. The new Copilot asks every employee to learn it. Microsoft’s own guidance is sound here, telling users to start with a bounded request that sends nothing and to check results at their destination. Published adoption material from Microsoft would reduce how much a company must build alone. Greyhound Research wrote in July 2025 that every agent output is a draft, not a decision, and that rule belongs in the first lesson. Change and adoption leads, with learning and development, should rebuild training by role around bounded tasks, deliberate approval, and verification, and finish it before the first Frontier pilot group is enrolled.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What must happen before a user sees Autopilot?

Four gates. Microsoft’s Autopilot guide says access requires Frontier enrollment, preview assignment, and participation terms, and that Frontier enrollment alone does not enable every preview feature. It says Autopilot is off by default and that the administrator licenses it, covers the user with a spending policy for billing by use, and activates it. It adds that Frontier enrollment alone does not make Autopilot available.

Frontier itself. Microsoft’s Frontier page says the program is managed at the tenant level, that admins choose all users or specific users and groups, and that features can take three hours to appear. It says the Frontier control does not override the agent settings in the admin center.

What the gates tell a buyer. Four separate gates, each held by an administrator, mean that no user reaches Autopilot by accident, which is a sound default. They also spread the decision to give someone an agent across four settings, none of which records why. Greyhound Research reads this as a reason to keep a short written record for each enrollment: who asked, which data the user holds, and who approved it. The gates control access, and the record explains it.

In the source’s own words

  • Microsoft Learn, Get started with AutopilotAutopilot is off by default.Source
  • Microsoft Learn, Get started with AutopilotStart with a bounded request that doesn't send messages or change shared information.Source
  • Microsoft Learn, Frontier programIT admins have explicit control which users have access to which Frontier features.Source
2What does the evidence say about adoption?

Scale claimed. Spataro wrote that nearly 80% of Fortune 500 companies use Cowork and that more than 5,000 people at Lilly use it every month. Microsoft’s Source says Volkswagen Group is equipping more than 330,000 employees with Copilot. These are Microsoft’s figures and measure use, not outcomes.

Training carries the numbers. Microsoft’s own customer evidence puts skills at the center. In a Microsoft customer story published August 10, 2026, KOHLER’s chief digital officer, Eric Tabor, said that the skilling many companies miss is business skilling, and Sheri Tower, its organizational change manager for AI, said the company focused distinct resources and training at all three levels of the business.

Outcomes are scarcer. Greyhound CIO Pulse 2026, across more than 1,000 technology leaders, found that fewer than one in three can point to measurable outcomes across most of their funded AI portfolio. Greyhound Research argued in March 2025, in AI Meets Productivity: What M365 Copilot Chat Means for Enterprises, that Copilot adoption is an ongoing process rather than a one-time event, and that view holds for the new front end. Measuring Copilot’s value and cost is the subject of a companion Greyhound Research note on Agent 365 economics.

In the source’s own words

  • Microsoft Copilot Blog, Spataro on November 17Today nearly 80% of the Fortune 500 companies use Cowork.Source
  • Microsoft customer story, KOHLER, August 10, 2026The skilling that a lot of companies miss is the business skillingSource
  • Greyhound Research, July 2026 runtime notefinds fewer than one in three can point to measurable outcomes across most of their funded AI portfolio.Source

↑ Back to the section guide

Part 2The New Front End

Copilot Code And Managed Runtime: Every Employee A Builder

Greyhound SpotlightThe runtime that hosts employees’ apps is generally available, while Copilot Code, the tool that builds them, is still in Frontier until December.

Copilot Code lets anyone describe a dashboard, tracker, or small app in plain words and get a working one. Copilot Managed Runtime hosts those apps inside the company’s Microsoft 365 tenant, so they can be shared and connected to live data. The runtime also hosts what employees build in Cowork and Copilot Studio, Microsoft’s agent-building tool. For a CIO, this creates a new estate of small apps, built by people who are not developers.

The order of release is unusual. The hosting layer is generally available now. The builder is in Frontier, and Microsoft’s Code FAQ says it is available in English at this release. A company that switches on the runtime this quarter will host apps built in Cowork and Copilot Studio first, and apps from Code once it is released. Microsoft says every app is visible in the Microsoft 365 admin center. What it does not say is who owns each app once its builder changes jobs.

What is new is the scale, not the idea. Business users have built their own tools for as long as there have been spreadsheets. Copilot Code removes most of the skill that once limited how many such tools a company held, and the runtime gives each one a supported place to run. Greyhound Research expects the number of small apps in an active tenant to grow quickly once Code is released, and expects the first questions to reach the help desk before they reach the security team. When a team comes to rely on an app, the service desk inherits support for software it did not build, test, or document, and few service desks are staffed for that.

Greyhound Standpoint:

Greyhound Research’s reading is that Copilot Code is the most consequential change in the new Copilot for IT operations, because it turns every licensed user into a potential publisher of software that touches live company data. Microsoft’s choice to host those apps inside the tenant, visible in the admin center, is the right one. Visibility, though, is not ownership. The risk in a large estate of small apps sits less in the day an app is built than in the year after, when its builder has changed roles, its data connection still works, and nobody knows who relies on it.

Each wave of end-user computing has followed this course, from spreadsheet macros and departmental databases to low-code tools. Each produced useful work and left estates whose owners had moved on. The evidence here has limits. Code is in Frontier until December, it is available in English at this release, and Microsoft has not said how ownership passes when a builder leaves. A documented ownership transfer or lifecycle control would change this view. The CIO and the Microsoft 365 platform owner should settle two rules at an architecture review before Code reaches general availability in December: every app shared from the runtime carries a named owner and a review date, and Code’s access to work data starts narrow and widens by approval.

The Deeper Read · About 1 minute

Select a question to open the full answer

1What does Microsoft say Code and the runtime do?

Code. The Book of News says Copilot Code is available in the Frontier program on Windows, web, iOS, and Android, with a local sandbox on Windows and coming soon to macOS. Microsoft’s Code FAQ, last updated October 6, says Code can use a user’s documents, emails, meetings, and calendar as context if an administrator enables it, and that apps can be shared within the organization.

The runtime. Microsoft’s runtime documentation describes an IT-governed platform for running code inside the Microsoft 365 tenant. The Book of News says Fabric can provide database, storage, and data services behind those apps, and that Agents and Workflows in the runtime arrive as a first iteration for Copilot Studio agents built locally.

What the documentation tells a buyer. Microsoft has built the runtime as an IT-governed platform, and lets Code use a user’s documents, mail, meetings, and calendar only if an administrator enables it. Both are sound starting positions. Neither page describes what happens to an app when its builder leaves, or how a shared app is retired. Greyhound Research reads the release order as an opportunity rather than a problem: the platform is ready before the builder, so the rules for ownership can be set before the first wave of apps arrives.

In the source’s own words

  • Microsoft Learn, Copilot Managed RuntimeMicrosoft Copilot Managed Runtime is an IT-governed, enterprise-grade platform for running code inside your Microsoft 365 tenantSource
  • Microsoft’s Book of News, Microsoft CopilotCopilot Managed Runtime securely hosts what you build in Cowork, Code and Copilot Studio.Source
  • Microsoft Copilot Blog, Spataro on November 17IT stays in control, with every app visible and managed in the Microsoft 365 admin center.Source
  • Microsoft Learn, Copilot Code FAQIt's available in English at this release.Source

↑ Back to the section guide

Part 3The Frontier Line

Frontier Or General Availability: The Calendar Buyers Must Track

Greyhound SpotlightWorkspaces, which Microsoft showed at Ignite, reaches companies on the slower deferred update ring only by February 2027, three months later.

The new Copilot is not one release. It is a sequence that began with Cowork in June and runs into 2027, and each step reaches companies on two rings. Frontier users see features first, standard release follows, and deferred release, chosen by companies that value stability, comes last. Training and support plans must follow that sequence, or users will meet features their help desk has not seen.

For a buyer, the calendar now does the work that a version number once did. Earlier generations of office software arrived as dated releases that IT could test, approve, and schedule as one event. The new Copilot arrives as a stream, with each feature on its own date and each ring on its own lag, so no single approval covers it. Greyhound Research anticipates that pattern continuing after the agents are released, because software delivered as a service seldom returns to fixed versions. The consequence that receives less attention is that one company can run three calendars at once. Its deferred ring gains weeks to train, while its Frontier users meet the same features months earlier.

Exhibit 3 places the new Copilot on a twelve-month calendar from June 2026 to May 2027, by the dates Microsoft has published. Planned means a date Microsoft has stated for a future release.

Greyhound Research · Exhibit 3 · The release calendar

The new Copilot arrives over nine months and two rings

Releases, rollouts, and planned dates for the new Copilot from June 2026 to May 2027, as Microsoft has published them.

Plan on the dated changes now. Keep the undated agents with pilot groups until Microsoft names a date.

A release or rollout falls in this monthJune 2026 to May 2027
JunReleasedCowork generally available June 16
JulNo date
AugNo date
SepAnnouncedHome, Code, and Autopilot introduced September 25
OctRolloutHome in standard release. Office rollout begins
NovIgniteOffice and Runtime generally available. Autopilot to Frontier. Today begins private preview. Home in deferred release
DecPlannedCode generally available. Office in deferred release
JanPlannedWorkspaces in standard release
FebPlannedWorkspaces in deferred release
MarNo date
AprNo date
MayNo date
Autopilot and Today: no release date publishedDeferred release: the slower update ringPlanned: a date Microsoft has stated
Against this: Microsoft has published more rollout dates for the doorway than most vendors do for a suite change, which makes a training calendar possible.
Source: Microsoft Book of News (November 17, 2026), Official Microsoft Blog (Spataro, September 25, 2026), Microsoft 365 Blog (Lamanna, June 16, 2026), Microsoft 365 message center notices MC1535647 and MC1530611.

Exhibit 3 places the new Copilot on a month grid from June 2026 to May 2027, and shows seven months with a release, rollout, or planned date. June: Cowork generally available on June 16. September: Home, Code, and Autopilot introduced on September 25. October: Home in standard release and Office rollout begins. November: Office in Copilot and Managed Runtime generally available, Autopilot to Frontier, Today begins its private preview rollout, and Home in deferred release. December: Code planned for general availability and Office in deferred release. January: Workspaces in standard release. February: Workspaces in deferred release. Notes beneath say Autopilot and Today have no published release date.

Exhibit 3. The new Copilot arrives over nine months and two rings. Data as of November 19, 2026. © Greyhound Research.

Seven of the twelve months carry a change. The busiest stretch runs from October to December, when the doorway, Office, and the runtime arrive and Code is due. Workspaces reaches the last ring only in February. Autopilot and Today carry no release date at all, so they cannot be placed beyond their Frontier start. A plan built on this calendar can schedule training a month ahead of each ring.

Greyhound Standpoint:

The Frontier program, Greyhound Research judges, has become the main channel for the new Copilot rather than a side door for enthusiasts. The agent features that define the OS claim arrive there first and, at this point, nowhere else. That changes what the Frontier setting is. Choosing who is enrolled is now a release decision, because enrolled users meet features before the help desk, the training team, or the risk owners have seen them, and features in Frontier can change name and scope before release.

This note records two such changes. Scout became Autopilot between preview stages, and Notebooks are becoming Workspaces. Anyone who has run software through several preview cycles will expect more of the same before release. Microsoft has published dates for the doorway, for Office, and for both update rings. The limit is on the other half. Autopilot and Today carry no release date, and Cowork’s status is worded two ways across Microsoft’s pages. Published dates for the agents would turn this from a pilot program into a release plan. The CIO, with the release manager, should run the calendar as part of the quarterly service review, with a training date a month ahead of each ring, an owner for each Frontier feature, and undated features kept with pilot groups until Microsoft publishes a date.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1Which dates has Microsoft published?

Doorway and Office. Microsoft’s notices set Home’s standard release from late October and its deferred release from late November, and set Office in Copilot to complete by mid-November with the deferred release from early December.

Today, two tenses. The September post said Today would enter private preview in October. On November 17, the Book of News said Today will begin rolling out in private preview through Frontier. The calendar places Today’s preview at Ignite, the later and more cautious reading.

Agents. The Book of News says Today will begin rolling out in private preview through the Frontier program, and that Copilot Workspaces is available in the Copilot app through the Frontier program. It gives no release date for Autopilot, Workspaces, or Today.

What the dates tell a buyer. Microsoft has dated what changes the doorway and not what changes who does the work. That split is common in a release of this size, and it gives buyers a clear planning rule. Dated items can go into training calendars and change boards now. Undated items belong in pilot plans, each with an owner and a review point, and are best moved into the release plan only when a date appears in Microsoft’s own notices.

In the source’s own words

  • Microsoft’s Book of News, Microsoft CopilotToday will begin rolling out in private preview through the Frontier program.Source
  • Microsoft’s Book of News, Microsoft CopilotCopilot Workspaces is available in the Copilot app through the Frontier program.Source
2Is Cowork itself released?

Two readings. Lamanna’s June post announced Cowork’s general availability worldwide on June 16, 2026. Microsoft’s Cowork documentation, marked as prerelease, still says customers need to be in the Frontier program for early access. The Book of News adds that declarative agents in Cowork are in private preview through Frontier. Greyhound Research reads Cowork as generally available and its newer additions as previews.

In the source’s own words

  • Microsoft Learn, Copilot Cowork overviewYou need to be part of the Frontier preview program to get early access to Microsoft 365 Copilot Cowork.Source
  • Microsoft’s Book of News, Microsoft CopilotDeclarative agents are available in private preview through the Frontier program.Source

↑ Back to the section guide

Part 3The Frontier Line

Frontier Terms: What The Preview Contract Leaves Out

Greyhound SpotlightMicrosoft’s own Frontier page says Frontier features do not comply with ISO 27001, ISO 27002, or ISO 27018, the security and cloud privacy standards many contracts name.

Enterprise data protection is Microsoft’s name for the contractual commitments that cover Copilot prompts and responses. They include Microsoft acting as processor of the data and not using it to train its foundation models. The question buyers ask is whether those protections reach Frontier features. Microsoft’s answer is yes in part. Frontier runs under the same customer agreements. It also loses protections that regulated companies rely on.

The distinction matters more than its size suggests. In earlier preview programs, the usual risk was a feature that changed or broke. Here the preview is also where the most capable agent features live, so preview terms reach real work sooner than they once did. Greyhound Research expects regulated companies to divide their users into those who may join Frontier and those who may not, and expects that line to follow data classification more than job title. The effect that is harder to see is on certification. A company whose own contracts promise ISO-aligned handling may assume every Microsoft service it uses meets those standards, and a Frontier feature switched on for one team can make that assumption untrue.

Table 2 sets the terms for generally available Copilot beside the terms for Frontier features, as Microsoft’s pages state them. A Business Associate Agreement is the contract United States health care law requires before a vendor handles patient data.

Greyhound Research · Table 2 · Terms ledger

The agreements carry over, and HIPAA and ISO do not

Terms for generally available Copilot beside terms for Frontier features, as Microsoft’s pages state them, November 19, 2026.

The core agreements carry over and the regulated coverage does not. Enroll people for the data they hold, not their enthusiasm.

CoveredWeaker or conditionalExcludedNot addressed
TermGenerally available CopilotFrontier features
Governing agreementsCovered Data Protection Addendum and Product TermsCovered The same agreementsPlus any Frontier-specific preview terms
Personal dataCovered Customer data, under enterprise data protectionAllowed As described in the Data Protection Addendum
HIPAA Business Associate AgreementSupported For properly configured implementationsNot included
ISO 27001, 27002, and 27018In part ISO/IEC 27018 named among privacy commitments27001 and 27002 not addressed on that pageDoes not comply
Support and service levelsNot assessed Outside this note’s evidenceMay not be covered
ContinuityReleased Generally availableMay change or stop May be modified, suspended, or discontinued
PaymentLicense Plus credits for features billed by useMay be paid only For certain Frontier experiences
EU Data BoundarySupported Except web search and Claude modelsNot stated Separately for Frontier
Against this: Microsoft wrote the Frontier exclusions down plainly, on a page updated the day before Ignite, which lets buyers decide with the terms in hand.
Source: Microsoft Learn: Get started with the Microsoft Copilot Frontier Program (updated November 16, 2026), Enterprise data protection (updated November 4, 2026), What is Microsoft Copilot? (updated November 17, 2026). Read November 19, 2026.

Table 2 compares eight terms for generally available Copilot and for Frontier features, and shows that the core agreements carry over while HIPAA and ISO coverage do not. Governing agreements: the Data Protection Addendum and Product Terms cover both. Personal data: covered for released Copilot and allowed in Frontier. HIPAA Business Associate Agreement: supported for properly configured released Copilot, not included for Frontier. ISO 27001, 27002, and 27018: the enterprise data protection page names ISO/IEC 27018 among its privacy commitments and does not address the other two, and Frontier features do not comply with any of the three. Support and service levels may not cover Frontier. Frontier features may change or stop, and some may be paid only. The EU Data Boundary is supported for released Copilot except web search and Claude, and not stated separately for Frontier.

Table 2. The agreements carry over, and HIPAA and ISO do not. Data as of November 19, 2026. © Greyhound Research.

The data protection agreement and product terms carry over to Frontier. HIPAA coverage does not, and Frontier features do not meet three ISO standards. Frontier features may also lack standard support and service levels, and may change or stop. The enterprise data protection page names Microsoft Copilot and Copilot Chat as its scope and does not mention Frontier or previews. For a health care or financial company, that gap decides which users may be enrolled.

Greyhound Standpoint:

Greyhound Research’s position is that enterprise data protection reaches Frontier only in part, and that the parts left out are the ones regulators and auditors ask about first. The core agreements carry over. HIPAA Business Associate Agreement coverage does not, Frontier features do not comply with three ISO standards, and service levels may not apply. The mechanism is contractual rather than technical. A health care company whose staff process patient records in a feature without Business Associate coverage may fall outside its own obligations, and that exposure is the company’s, not Microsoft’s.

Long experience of hosting, outsourcing, and cloud contracts suggests that the gaps which matter are rarely in the technology and usually in the schedules and exclusions. Microsoft deserves credit here. It wrote the exclusions down plainly, on a page updated the day before Ignite, so buyers can decide with the terms in hand. The limits are twofold. This is a reading of published terms, to be confirmed with counsel, and nothing yet says what the terms will be at release. Coverage at release would change this view. Data protection officers should keep patient records and other regulated data out of Frontier groups when the setting is next reviewed, and procurement should ask Microsoft in writing, before the next renewal, which of these terms change when each feature is released.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What does the Frontier page say about terms?

Same agreements. Microsoft’s Frontier page, last updated November 16, 2026, says Frontier experiences are governed by existing customer agreements, including the Product Terms and the Data Protection Addendum, and that they are preview features that allow for personal data processing as described in that addendum.

The exclusions. The same page says HIPAA Business Associate Agreement coverage is not included, that certain Frontier experiences may only be available on a paid basis, and that Frontier features do not comply with ISO 27001, 27002, or 27018. It says previews may be modified, suspended, or discontinued and may not be covered by standard support commitments or service level agreements.

In the source’s own words

  • Microsoft Learn, Frontier programFrontier experiences are governed by your existing customer agreements, including the Product Terms and Microsoft Data Protection Addendum (DPA).Source
  • Microsoft Learn, Frontier programHIPAA Business Associate Agreement coverage is not included for Frontier experiences.Source
  • Microsoft Learn, Frontier programFrontier features do not comply with ISO 27001, ISO 27002, or ISO 27018 requirements.Source
  • Microsoft Learn, Frontier programmay not be covered by standard support commitments or service level agreementsSource
2What does enterprise data protection cover?

Scope. Microsoft’s enterprise data protection page, last updated November 4, defines it as controls and commitments under the Data Protection Addendum and Product Terms for users of Microsoft Copilot and Copilot Chat. It says prompts, responses, and data accessed through Microsoft Graph are not used to train foundation models, and that for agents, users should check each agent’s privacy statement and terms. It does not mention Frontier or preview features. Microsoft’s Copilot overview says the Basic and Premium Copilot experiences are protected when users sign in with Microsoft Entra accounts.

What the two pages tell a buyer. The Frontier page states what is left out, and the enterprise data protection page states what is covered without naming Frontier. Neither contradicts the other, but a buyer who reads only the second could assume more than the first allows. Greyhound Research treats the Frontier page as the safer basis for preview features, because it is the more specific of the two. Counsel should read both together and record which one the company relies on for each enrolled group.

In the source’s own words

  • Microsoft Learn, enterprise data protectionEnterprise data protection (EDP) refers to controls and commitments, under the Data Protection Addendum (DPA) and Product Terms, that apply to customer data for users of Microsoft Copilot and Microsoft Copilot Chat.Source
  • Microsoft Learn, enterprise data protectionWhen you're using agents in Microsoft Copilot, check the privacy statement and terms of use of the agents to determine how they'll handle your organization's data.Source

↑ Back to the section guide

Part 3The Frontier Line

Whose Model: Claude Inside Copilot And The EU Boundary

Greyhound SpotlightCowork ran on Anthropic’s models at general availability. Anthropic’s models are excluded from Microsoft’s EU Data Boundary, its commitment to keep European customers’ data in Europe.

The OS for work runs on more than one company’s models. Auto, Copilot’s router, picks models and effort for each task, and users can also choose models from OpenAI or Anthropic where their company allows. Microsoft said at Cowork’s release in June that it ran on Anthropic models. That matters because where a model runs decides where the data goes.

Microsoft’s pages are clear on the boundary. Anthropic is a Microsoft subprocessor, and Microsoft’s terms apply to Claude models in its services. Claude models are excluded from the EU Data Boundary and from in-country processing commitments. For customers in the European Union, the European Free Trade Association, and the United Kingdom, Claude is off by default. For most other customers in Microsoft’s commercial cloud it is on by default. A European company that turns Claude on for Researcher or other Copilot features sends that work outside the boundary it may have bought Microsoft for.

This departs from how many European buyers chose Microsoft in the first place. For years, a residency commitment was a property of the vendor, settled once at contract time. With several model providers behind one assistant, residency becomes a property of each feature and each setting, and it can change when a setting does. Greyhound Research expects other suite vendors to take the same multi-model route, which is likely to make a list of models and processing locations for each feature a routine procurement request. The consequence that is easy to overlook sits outside Europe. Where Claude is on by default, a company may already be routing some work through a subprocessor that its own customer contracts do not name.

Greyhound Standpoint:

In Greyhound Research’s assessment, model choice inside Copilot is a strength and a data residency decision at the same time. Choice lets Copilot route each task to the model that fits it. The cost sits in where the work goes. Claude models are excluded from the EU Data Boundary and from in-country processing commitments, so a European company that turns them on sends that work outside a boundary it may have bought Microsoft partly to obtain.

Practitioners who have managed cloud contracts will recognize the route. Subprocessor lists have long been where the location of data changes without a new contract being signed. Microsoft has handled this with care. It documented the boundary, kept Claude off by default in the European Union, the European Free Trade Association, and the United Kingdom, and stated that Frontier will not switch AI providers on for a customer. The evidence has a gap, because Microsoft has not restated which models carry Cowork’s work today, and a per-feature list of models and processing locations would settle it. Data protection officers outside those regions should check the default against their own commitments this quarter. Those inside them should treat any request to turn Claude on as a residency decision, approved by name at the data protection review, and not as a model preference set by IT.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What do Microsoft’s pages say about Anthropic?

Subprocessor and boundary. Microsoft’s subprocessor page, last updated November 4, says Anthropic has onboarded as a Microsoft subprocessor, that Claude is on by default for most commercial customers outside the EU, EFTA, and UK, and that Claude models are excluded from the EU Data Boundary and in-country processing commitments. It says the Product Terms and the Data Protection Addendum apply unless models are labeled Anthropic models with Data Retention.

Frontier will not switch it on. The Frontier page says some Frontier features require models from providers such as Anthropic, and that Frontier will never enable AI providers on a customer’s behalf.

In the source’s own words

  • Microsoft Learn, Claude models in Microsoft Online ServicesTo enable this change, Anthropic has onboarded as a Microsoft subprocessor.Source
  • Microsoft Learn, enterprise data protectionClaude models from Anthropic are currently excluded from the EU Data Boundary and when applicable, in-country processing commitments.Source
  • Microsoft Learn, Frontier programEven if a Frontier feature relies on a particular AI provider being turned on, Frontier will never enable AI providers on your behalf.Source
  • Microsoft Copilot Blog, Spataro on November 17Employees can also manually select models from OpenAI or Anthropic, with model access governed by organizational policies.Source
2Which model runs Cowork now?

Not restated at Ignite. Lamanna’s June post said Cowork ran on Anthropic models at general availability, including Opus 4.8 and Sonnet 4.6, and that a model named Cowork 1 would be released in the following weeks. The Book of News says Auto in Cowork will use Microsoft-Decision-1.1, a Microsoft decision model, for Frontier customers. Neither says which models carry Cowork’s work today.

What the gap tells a buyer. Microsoft has said which models Cowork ran on in June, and which decision model Auto in Cowork will use for Frontier customers, but not which models carry the work today. For many buyers that is a detail. For a European buyer that has kept Claude switched off, it bears directly on whether its Cowork work stays inside the boundary. Greyhound Research reads the silence as a gap to close in writing, not as a sign that anything has changed, and the fourth question for Microsoft in this note asks for it.

In the source’s own words

  • Microsoft 365 Blog, Lamanna on June 16At general availability, Copilot Cowork runs on Anthropic models, including Opus 4.8 and Sonnet 4.6.Source
  • Microsoft’s Book of News, Microsoft CopilotAuto in Cowork will use Microsoft-Decision-1.1, a fast, cost-effective decision modelSource

↑ Back to the section guide

Part 4Agents In The Front Door

Autopilot: A Colleague With Its Own Name And Mailbox

Greyhound SpotlightEach employee can have one Autopilot, with its own email address, mailbox, and calendar. Microsoft says it shows up in Teams and Outlook and can be mentioned like a colleague.

Autopilot is the clearest sign of what Microsoft means by an OS for work. It is a cloud agent that keeps working when its owner is away. It has its own name, identity, memory, computer, and workspace, and colleagues can mention it in Teams. It works without asking at each step, and pauses when an action does not match the request and before every payment. It is rolling out to Frontier customers now.

Autopilot changes the unit a security team reviews. Access reviews have long been built around people, with service accounts and bots handled as exceptions. An agent available to every employee turns the exception into a population that could match the size of the workforce. Identity and access teams are likely to feel that change first, on Greyhound Research’s reading, as review lists grow without a single new hire. A less obvious effect touches the employee. When an Autopilot sends a message or changes a file while its owner is away, colleagues will tend to treat the result as the owner’s own work, so accountability for an agent’s mistakes is likely to land on people before any policy says where it belongs.

Exhibit 4 follows one Autopilot task from request to record, and marks what Microsoft documents as a control, what it documents as a limit, and what it does not state. An automated review is Microsoft’s check that compares a planned action with the user’s request.

Greyhound Research · Exhibit 4 · One Autopilot task, end to end

The controls sit in the middle, and the limits at both ends

One Autopilot task from request to record, marked where Microsoft documents a control, a limit, or nothing, November 19, 2026.

The approval controls suit a bounded pilot. Memory retention and a complete record need settling before wider use.

Control documented by MicrosoftLimit documented, or not stated
Request and groundingDocumented controlOnly the owner’s requests authorize actions, and access is no wider than the owner’s.
MemoryRetention not statedThe cloud workspace can keep working context between sessions.
ActionDocumented controlActions that do not match the request wait for approval, and so do all payments.
Files and recordDocumented limitLabels and the audit record are not guaranteed complete.
Against this: Approval before consequential actions, and no access beyond the owner’s, are stronger defaults than many agent products document.
Source: Greyhound Research analysis of Microsoft Learn (Autopilot overview and Get started with Autopilot, both updated November 17, 2026).

Exhibit 4 follows one Autopilot task along a bar from request to record, in six steps: request, grounding in the owner’s access, memory between sessions, automated review and approval, files and labels, and the audit record. A marker labeled approval point sits over the automated review. Request, grounding, and action are documented controls: only the owner’s requests authorize actions, access is no wider than the owner’s, and mismatched actions and all payments wait for approval. Memory has no stated retention period, and files, labels, and the audit record are documented as not guaranteed complete. The mapping is Greyhound Research analysis.

Exhibit 4. The controls sit in the middle, and the limits at both ends. Current through November 19, 2026. © Greyhound Research.

Microsoft has documented real controls. Only the user’s own requests authorize actions, Autopilot cannot see more than its owner can, and actions that do not match the request wait for approval, as do all payments. The limits sit at both ends. Memory is kept between sessions with no stated retention period, and the documentation says neither file labels nor the audit record are guaranteed complete.

Greyhound Standpoint:

Autopilot is an insider by design, and Greyhound Research holds that it should be governed as one. It carries its owner’s access, keeps its own mailbox and memory, and acts on that access while the owner is away. That agrees with a companion Greyhound Research note on Azure agent infrastructure, which found that the authority an agent holds decides what it can do. The buyer’s question shifts from what a user may see to what a standing agent may do with it, at any hour, with no person at the keyboard.

Security teams have met this pattern before, in service accounts, delegated mailboxes, and process automation bots. In each case, a standing identity with broad access and no human present tended to be where access reviews and audit records were weakest. Microsoft has documented controls that compare well with many agent products: only the owner’s requests authorize actions, access is no wider than the owner’s, and mismatched actions and all payments wait for approval. The evidence stops short in two places. No retention period for Autopilot’s memory is stated, and the audit record is not guaranteed complete. A stated retention period and a complete record would justify wider use. CISOs should set the pilot gate now, with bounded routines that send nothing outside the company, no enrolled users who hold regulated data, and Autopilot included in the quarterly access review. A companion Greyhound Research note covers agent identity.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What does Microsoft’s documentation say Autopilot is?

Identity and limits. Microsoft’s Autopilot overview, last updated November 17, says Autopilot has its own workplace identity, memory, computer, and workspace, that each person can have one, and that it has its own mailbox and calendar. It says Autopilot does not expand the data its owner can access, that only the owner’s own requests authorize actions, and that its cloud workspace can keep working context between sessions. It gives no retention period.

Approvals. The same page says an automated review compares any action that sends, shares, deletes, or changes something with the request, and that actions that do not match wait for approval. The getting started guide adds that all payments wait for the user.

What the controls tell a buyer. The documented controls answer what Autopilot may see and when it must ask. They leave open how long it remembers and what record it leaves. Greyhound Research reads that as a sound base for a bounded pilot and an incomplete base for wider use. The automated review is the strongest control on the page, so an early pilot is best judged on how often that step pauses work, and whether the pauses fall where the company would expect them.

In the source’s own words

  • Microsoft Learn, Autopilot overviewAutopilot has its own workplace identity, memory, computer, and workspace. Each person can have one Autopilot.Source
  • Microsoft Learn, Autopilot overviewAutopilot doesn't expand the data you can access.Source
  • Microsoft Learn, Autopilot overviewOnly your own requests authorize actionsSource
  • Microsoft Learn, Autopilot overviewBefore it sends, shares, deletes, or changes something, an automated review compares the action with your request.Source
2Where did Autopilot come from?

From Scout. Microsoft’s September post says Autopilot was previously called Scout. Microsoft’s earlier Scout documentation, last updated August 21, said Scout could route data outside Microsoft 365 to third-party inference paths, such as GitHub, and that admins had to attest and opt in for that reason. No equivalent statement was found in the Autopilot pages read, and Greyhound Research does not assume it carries over.

An evolved view of inherited access. Greyhound Research wrote in July 2025 that Researcher’s use of scoped tokens to respect each user’s permissions was a governance strength. That still holds as a limit, since Autopilot, too, sees no more than its owner. Since then, agents have begun to act on that access with no person present, and Greyhound Research’s November 5, 2026 note on the front door race held that every right a person already holds, within the tools an assistant exposes, can be used by that assistant at once. The view has therefore moved. Inheriting the owner’s permissions bounds what an agent can see, but it is not on its own enough to govern what a standing agent may do.

In the source’s own words

  • Microsoft Learn, Microsoft Scout admin accessBecause Microsoft Scout can route data outside Microsoft 365 to third-party inference paths (for example, GitHub), admins must explicitly attest and opt in for their organization.Source

↑ Back to the section guide

Part 4Agents In The Front Door

The Audit Gap: A Clear Trail In The Launch Post, No Guarantee In The Documentation

Greyhound SpotlightMicrosoft’s launch post promises security teams a clear audit trail for Autopilot. Microsoft’s own Autopilot page, updated the same day, says its activity is not a guarantee of a complete audit record.

An audit record is how a company proves after the fact what happened and who did it. For an agent that acts in its owner’s name while the owner is away, that record is the main evidence a security team has. On November 17, Microsoft said two different things about it. The launch post said Autopilot’s sign-ins and actions are logged under its own name. The product documentation, updated the same day, set limits on what that log proves.

For buyers, a gap between launch messaging and documentation is common in a new product, and it sets the order of work rather than the verdict. Security teams have usually been able to assume that a platform’s activity log records what the platform did. With an agent acting in a person’s name, the log is also the main way to tell the person’s actions from the agent’s. Greyhound Research expects Microsoft to fill in the documentation as Autopilot matures, as vendors typically do. Until then, the place to watch is the incident review. One that cannot separate the owner from the agent may close without a clear finding, and that weakens every control resting on the record.

Exhibit 5 sets the three positions side by side: what Microsoft’s launch post says, what its documentation says, and what neither states. Data loss prevention is the set of rules that stop sensitive data from leaving through the wrong route.

Greyhound Research · Exhibit 5 · The audit gap

A clear trail in the post, no guarantee on the page

What Microsoft’s launch post and its Autopilot documentation each say about the audit record, and what neither states, November 19, 2026.

Plan on the documentation, not the launch post. Test the trail at the pilot gate before relying on it.

Microsoft’s launch postWhat the announcement promisesIdentity. Each Autopilot has its own Entra Agent ID and a named manager.Logging. Sign-ins and actions are logged under its own name.Trail. Security teams have a clear audit trail.November 17 blog post
Microsoft’s documentationWhat the product page saysRecord. Activity is not a guarantee of a complete audit record.Labels. Not every generated file is shown to inherit a label.Data loss rules. Not every operation is shown to be covered.Learn, updated November 17
Neither document statesGaps a buyer must closeContents. What the record captures and leaves out.Location. Where the record is kept, and for how long.Identity timing. The Book of News says Agent ID for Autopilot is in preview.Not stated
Against this: A log under Autopilot’s own name can exist and still be incomplete, so the two documents differ in emphasis more than in fact.
Source: Greyhound Research analysis of the Microsoft Copilot Blog (Spataro, November 17, 2026), Microsoft Learn (Autopilot overview, updated November 17, 2026), and Microsoft’s Book of News. The grouping is Greyhound Research’s.

Exhibit 5 groups three positions on Autopilot’s audit record into cards. Microsoft’s launch post: each Autopilot has its own Entra Agent ID and a named manager, its sign-ins and actions are logged under its own name, and security teams have a clear audit trail. Microsoft’s documentation: activity is not a guarantee of a complete audit record, and label recognition does not show that every generated file inherits a label or that every operation is covered by data loss prevention. Neither states: what the record captures, where it is kept and for how long, and when Agent ID reaches Autopilot, which the Book of News lists as a preview. The grouping is Greyhound Research analysis.

Exhibit 5. A clear trail in the post, no guarantee on the page. Current through November 19, 2026. © Greyhound Research.

The two documents do not contradict each other outright. A log under Autopilot’s own name can exist and still be incomplete. They do set different expectations, and a contract is read against the documentation. The documentation also limits labels and data loss prevention. It says label recognition does not establish that every generated file inherits a label, or that every operation is covered.

Greyhound Standpoint:

The documentation, not the launch post, sets what a buyer can rely on, and in Greyhound Research’s judgment the audit trail for Autopilot is therefore a claim to test rather than a control to assume. The reason is practical. When something goes wrong, a contract is read against the product documentation, and an investigation or a regulator’s inquiry is answered from the record itself. A gap found then costs far more than a gap found in a pilot, because the evidence needed to close it may no longer exist.

Launch messaging and product documentation have often diverged at the start of a product’s life, and in a dispute it is the documentation that tends to carry weight. Microsoft’s candor in its own pages is welcome, and the two statements do not contradict each other outright, since a log kept under Autopilot’s own name can exist and still be incomplete. The limit of this reading should be stated. Greyhound Research has not tested the record, and it may prove more complete in practice than the documentation is willing to promise. Audit documentation from Microsoft that states what is captured would change this view. CISOs should run a known set of Autopilot actions against the record at the pilot gate and hold any wider pilot until the gaps are known. Procurement should carry three questions into the renewal: what the record captures, where it is kept, and for how long.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What exactly does each document say?

The launch post. Spataro wrote that each Autopilot has its own Microsoft Entra Agent ID and a named manager, and that its sign-ins and actions are logged under its own name. The September post said Autopilot works with permissions, audit, and governance behind it.

The documentation. The Autopilot overview says activity is not a guarantee of a complete administrative audit record, and that label recognition does not establish full label inheritance or data loss prevention coverage. It does not mention a named manager.

What the two statements tell a buyer. The launch post describes what is logged. The documentation describes what the log does not prove. Both can be true at once, and the second is the one a buyer should plan around. Greyhound Research reads the documentation’s caution as a reason to test, not as a finding that the record is weak. A test with a known set of actions turns an open question into a measured answer, and the result belongs in the pilot report the CISO signs.

In the source’s own words

  • Microsoft Copilot Blog, Spataro on November 17Its sign-ins and actions are logged under its own name, so security teams have a clear audit trail.Source
  • Microsoft Learn, Autopilot overviewActivity isn't a guarantee of a complete administrative audit record.Source
  • Microsoft Learn, Autopilot overviewSensitivity-label recognition doesn't establish that all generated files inherit labels or that every operation is covered by data loss prevention.Source
2What about Autopilot’s identity?

Two tenses. Spataro’s post says each Autopilot has its own Entra Agent ID. The Book of News says Agent ID for Microsoft cloud agents, in preview, will extend Agent ID to Autopilot agents. Greyhound Research called Entra Agent ID a policy control plane for agent-based computing in May 2025. The substance of agent identity is left to a companion Greyhound Research note on agent identity.

Whose record. The record a buyer tests is kept by the same vendor whose agent it describes. That is a reason for the test to sit with the buyer, and for the record to be exported to storage the buyer controls, so that oversight does not rest entirely inside the system being overseen.

Data protection in preview. The Book of News lists a stronger Copilot data loss prevention rule, which will block Copilot from referencing sensitive files even when they are not labeled, as a preview.

In the source’s own words

  • Microsoft Copilot Blog, Spataro on November 17Each Autopilot has its own Microsoft Entra Agent ID and a named manager.Source
  • Microsoft’s Book of News, Microsoft EntraAgent ID for Microsoft cloud agents, in preview, will extend Agent ID to Microsoft Autopilot agents.Source
  • Microsoft’s Book of News, Microsoft Purviewblock Copilot from referencing files with sensitive information even when those files are not labeled.Source

↑ Back to the section guide

Part 5The Platform Contest

Two Front Doors Compared: Microsoft And Google

Greyhound SpotlightGoogle’s answer to Copilot’s front door, a single Gemini agent for work, also runs jobs on Anthropic’s Claude models as well as Google’s own.

Microsoft is not alone in rebuilding the office suite around an agent. In October 2026, Google Cloud’s chief executive, Thomas Kurian, announced Gemini agent as a single agent for work, reached from the Gemini Enterprise app and by mentioning it inside Gmail, Docs, Sheets, Slides, and Chat. It can run as a personal assistant or as a member of a team, and its coworker agents carry their own identities and email addresses, much as Autopilot does. Like Copilot, it routes each job to the model that fits it.

The convergence is the news here. Two suites that competed for years on documents, mail, and price now describe much the same design: one agent above the applications, coworker agents with their own identities, and work routed across more than one model provider, including the same one. For buyers, that narrows the differences to release status, written terms, and where data is processed. Greyhound Research anticipates the two designs looking more alike with each release, which tends to move competition toward contracts and the cost of switching. A side effect follows. Because both suites draw on Anthropic’s models for part of their work, choosing one over the other does not remove a shared supplier from the buyer’s risk register.

Table 3 compares the two front doors layer by layer, on what each company has announced. Google’s terms for the agent were not found, and cells marked not found were not located in the documents read.

Greyhound Research · Table 3 · Two front doors, layer by layer

Microsoft is ahead on released features and on written terms

Microsoft’s new Copilot and Google’s Gemini agent compared layer by layer, on Microsoft’s documents and on Google’s October 2026 announcement.

Microsoft leads on what is released and written today. Judge the two on status, terms, and data location, not on design.

Generally available or writtenPreviewContextNot found or not assessed
LayerMicrosoftGoogle
One starting pointGenerally available Home in the Copilot appPrivate preview Gemini agent in the Gemini Enterprise app
Office work inside the agentGenerally available Word, Excel, and PowerPoint in CopilotPrivate preview @Gemini in Gmail, Docs, Sheets, Slides, and Chat
A standing agentFrontier Autopilot, one per person, with its own mailboxPrivate preview Coworker agents with their own identity and email
ModelsSeveral Microsoft, OpenAI, and Anthropic, with Auto routingSeveral Gemini and Claude families, routed by job
Apps built by employeesFrontier CodeManaged Runtime generally availableNot assessed Writes and runs code, hosting not read
Preview terms in writingWritten Frontier page names the exclusionsNot found Not in the documents read
Against this: Google’s agent was announced a month earlier as one agent across devices and channels, including Microsoft 365, and its terms may simply be unpublished.
Source: Microsoft Book of News, Copilot Blog, and Learn (November 2026). Google Cloud Blog (Kurian, October 8, 2026), with release status as reported at announcement, as listed in Sources And References.

Table 3 compares Microsoft’s new Copilot and Google’s Gemini agent on six layers, and shows Microsoft ahead on released features and written preview terms. One starting point: Home is generally available, while Gemini agent was in private preview. Office work inside the agent: Word, Excel, and PowerPoint in Copilot are generally available, while @Gemini in Gmail, Docs, Sheets, Slides, and Chat was in private preview. A standing agent: Autopilot in Frontier, one per person with its own mailbox, against Google’s coworker agents with their own identity and email, in private preview. Models: both route across their own and Anthropic’s models. Apps built by employees: Code in Frontier with the runtime released, and Google not assessed. Preview terms: written by Microsoft, not found for Google.

Table 3. Microsoft is ahead on released features and on written terms. Data as of November 19, 2026. © Greyhound Research.

Microsoft is ahead on what customers can use today. Its doorway and Office integration are released, while Google’s agent was in private preview in October. Both route work across their own and Anthropic’s models. Microsoft has written its preview terms down, including the exclusions. Google’s announcement describes strong controls, including an audit trail attributed to each agent and hard spending caps, but its terms for Gemini agent were not found in the documents read, so the table does not rank the two on terms.

Greyhound Standpoint:

Greyhound Research concludes that the contest for the front door of office work is now between two suites, each betting that one agent will sit above its applications, and that Microsoft holds the lead on released features and on written terms. Its doorway and Office integration are released, while Google’s agent was in private preview in October. Both route work across their own and Anthropic’s models, so model choice does not separate them. What separates them today is what a buyer can deploy and what it can read before signing.

Suite contests in enterprise software have usually been settled over several renewal cycles rather than in a season of announcements, because the cost of moving mail, files, identity, and habits is high. Google deserves credit for describing agent identities, an audit trail per agent, and hard spending caps in its announcement. Those are claims in a launch post, the same kind of evidence as Microsoft’s own, and Google’s terms for the agent were not found, so this note does not rank the two on terms. Wide availability of Google’s agent with published terms would reopen the comparison. Greyhound Research’s Microsoft 365 outage note held that consolidation on one suite remains right for most enterprises, and nothing here changes that. Enterprise architects should compare the two at the next architecture review on what is released, what the preview terms exclude, and where each model processes data.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What did Google announce?

Gemini agent. Kurian announced Gemini agent on October 8, 2026, as a single, universal agent for work, reachable from any device and from channels including Google Workspace, Microsoft 365, and Slack. It orchestrates across Google’s Gemini models and Anthropic’s Claude models, and can act as a personal assistant or a team member. Coworker agents have their own identities and email addresses and see only what they are given. The post says every action is written to an audit trail attributed to the agent, and that companies can set hard spending limits by project.

Status. Kurian’s post does not state a release status for the core agent. It was reported at announcement as in private preview, reachable by mentioning @Gemini in Gmail, Docs, Sheets, Slides, and Chat, with wide availability expected soon for select Workspace plans.

Not found. Neither page covers data protection terms or pricing, and Google’s terms for Gemini agent were not found for this note.

What the comparison tells a buyer. Kurian’s post and Spataro’s describe similar controls in similar terms, and both are launch posts. The difference a buyer can check today is status and written terms, not design. Greyhound Research reads Google’s announcement as a credible design that a buyer cannot yet contract on, and Microsoft’s doorway as a release a buyer can. A company weighing the two should ask each vendor for the same three things in writing: release status, preview terms, and processing locations.

In the source’s own words

  • Google Cloud Blog, Kurian on October 8today we are excited to announce the Gemini agent: your new single, universal agent for work.Source
  • Google Cloud Blog, Kurian on October 8every action Gemini takes is written to an audit trail and attributed to the agent rather than to a person.Source
2Does one front door deepen dependence?

Platform gravity. Greyhound Research wrote in July 2025 that Microsoft’s strategy is about platform gravity as much as product breadth, and that the value it creates raises difficult questions about portability, interoperability, and negotiating leverage. An OS for work deepens that gravity, because mail, files, identity, and now the agents that act on them sit behind one door. The Microsoft 365 outage note’s view that consolidation remains right for most enterprises stands alongside it. The two fit together on one condition: consolidate the suite, and keep the evidence of what the agents did, and the plan for leaving, under the buyer’s own control.

In the source’s own words

  • Greyhound Research, Researcher and Analyst agents noteMicrosoft's strategy is not just about product breadth, but platform gravity.Source

↑ Back to the section guide

Part 6The Risks And The Counter-Argument

Risks To Watch: Where The New Front Door Can Go Wrong

Greyhound SpotlightMicrosoft’s Frontier setting offers administrators a single switch that enrolls every user in the company. The risks in this section grow fastest when that switch is used.

Greyhound Research sees five risks in the new Copilot. None of them needs a flaw in Microsoft’s software. Each comes from a company enrolling, training, or trusting faster than the terms allow, and each shows first in a document the company already holds.

These risks look small because each begins as a setting, a list, or a plan, and that is also why they tend to last. Settings chosen in the first week of a program are seldom revisited until something forces a review, and by then they have become the default. Greyhound Research expects the first signs to surface in routine places: an access review that lists Autopilot accounts nobody recognizes, a help desk queue about the new address, or a data protection query about Claude. The second-order effect falls on the program itself. A pilot that goes wrong for avoidable reasons can sour a sound plan and slow the very learning that the objection in the next section rightly values.

Table 4 sets each risk beside its early warning and its owner. Every early warning can be checked without help from Microsoft.

Greyhound Research · Table 4 · Risk register

Every risk starts with an enrollment or a switch

Five risks in the new Copilot, each with its early warning and its owner.

Each risk begins in the buyer’s own settings, and each is cheaper to prevent at enrollment than to unwind later.

RiskEarly warning in the buyer’s own estateOwner
A two-speed workforceFrontier users and everyone else work in different Copilots, with one training plan.A training plan with a single track for all users.Head of change and adoption
Regulated data in FrontierUsers who hold health, financial, or ISO-bound data are enrolled in previews.A Frontier setting of all users.Data protection officer
An app with no ownerApps built in Code or Cowork stay in use after their builder moves on.A runtime inventory with no owner column.CIO
A trail taken on trustAutopilot pilots widen before anyone checks what the record captures.A pilot plan with no test of the audit record.Chief information security officer
A model outside the boundaryClaude is switched on without a residency decision.Anthropic enabled with no named approver.Data protection officer
Against this: This is a judgment about order, not a prediction of harm.
Source: Greyhound Research analytical model, not measured data. Greyhound Research analysis of the evidence in this research note.

Table 4 lists five risks in the new Copilot, each with an early warning in the buyer’s own estate and an owner. A two-speed workforce, warned by a single-track training plan, owned by the head of change and adoption. Regulated data in Frontier, warned by a Frontier setting of all users, owned by the data protection officer. An app with no owner, warned by a runtime inventory with no owner column, owned by the CIO. A trail taken on trust, warned by a pilot plan with no test of the audit record, owned by the CISO. A model outside the boundary, warned by Anthropic enabled with no named approver, owned by the data protection officer. The risks are Greyhound Research analysis.

Table 4. Every risk starts with an enrollment or a switch. Current through November 19, 2026. © Greyhound Research.

The five share a cause: treating the new Copilot as one product when it is two, a released doorway and a set of previews. A Frontier setting of all users, a training plan with one track, an app with no owner, a pilot without a test of the audit record, and Claude switched on without a residency decision are each easy to spot. The table names owners, not likelihoods, and ranks none of the risks above another.

Greyhound Standpoint:

In Greyhound Research’s reading, each of the five risks is cheaper to prevent than to unwind, and that asymmetry, more than any likelihood, sets the order of work. A Frontier enrollment of all users is one setting to choose and months of data to trace once regulated work has flowed through preview features. A training plan with one track costs little to split now and much more to repair after users have formed habits.

The pattern is familiar from earlier waves of technology entering the workplace, from personal devices to unsanctioned cloud services. Controls set at enrollment were cheap, and controls retrofitted after adoption were slow and contested. Microsoft has given buyers the means to do this, since Frontier can be set for specific users and groups and agent settings still apply. The limits are clear. The table names owners and early warnings, not probabilities, and nothing in the evidence shows harm has occurred. This is a judgment about order, not a forecast. Each owner named in Table 4 should check the early warning this quarter, and the Frontier enrollment scope should be placed on the agenda of the next board risk review. The Runbook that follows gives each owner a move.

↑ Back to the section guide

Part 6The Risks And The Counter-Argument

The Strongest Objection: Frontier Is How Leaders Get Ahead

Greyhound SpotlightThe strongest objection to this note is that the companies that learn to delegate first will lead. That part stands.

The objection deserves its full weight. Microsoft built the Frontier program so companies can try features before release and shape them. Delegating work to agents is a skill, and skills take time. Companies that wait for general availability will start a year behind. Administrators already choose who is enrolled, and Microsoft’s data protection agreement still applies. On this view, caution about Frontier costs more than it saves.

The objection reflects a real change in how software is adopted. For much of the history of enterprise software, waiting for general availability cost little, because the released product closely resembled the preview. With agents, the skill that matters is learned by doing, and it cannot be bought later with the license. Greyhound Research expects the gap between early and late adopters to show in how well employees brief and check agents rather than in which features they hold. A further consequence is easy to underrate. Habits formed in an early pilot tend to become company practice, so the first group enrolled effectively writes the first draft of the company’s delegation policy, whether or not anyone asked it to.

Exhibit 6 tests each part of the objection against the evidence. Three parts stand. The claim that regulated work can go into Frontier now does not hold on the terms.

Greyhound Research · Exhibit 6 · The objection held to the evidence

Three parts of the objection stand, and one falls

The fair counter-case to this research note, part by part, against the evidence gathered for each.

The objection holds for learning and not for regulated data. Enroll learners now, and hold regulated work for the terms.

StandsFalls
Early access builds the delegation skillStandsHanding work to agents takes months to learn, and Frontier is where it can start.
Admins already control enrollmentStandsFrontier can be set for specific users and groups, and agent settings still apply.
The core agreements carry overStandsThe Data Protection Addendum and Product Terms govern Frontier features.
Regulated work can go in nowFalls on the termsNo HIPAA coverage, no ISO 27001, 27002, or 27018, and service levels may not apply.
Source: Greyhound Research analytical model, not measured data. Greyhound Research analysis of Microsoft Learn (Frontier program, updated November 16, 2026).

Exhibit 6 holds four parts of the strongest objection to this research note against the evidence, as four cards, and shows that three stand and one falls on the terms. Early access builds the delegation skill: stands. Admins already control enrollment, for specific users and groups: stands. The core agreements carry over, since the Data Protection Addendum and Product Terms govern Frontier: stands. Regulated work can go in now: falls, because Frontier carries no HIPAA coverage, does not comply with ISO 27001, 27002, or 27018, and may lack service levels. The verdicts are Greyhound Research analysis.

Exhibit 6. Three parts of the objection stand, and one falls. Current through November 19, 2026. © Greyhound Research.

Greyhound Standpoint:

Greyhound Research accepts the objection for learning and rejects it for regulated data. Three of its four parts stand on the evidence. Delegating work to agents is a skill that takes months to build, administrators can enroll specific users and groups, and the core agreements carry over. Companies that wait for general availability before anyone learns to delegate will start behind, and that cost is real even if it is hard to measure. The part that does not hold is the claim that regulated work can go into Frontier now, because the terms say otherwise.

Earlier cloud adoption offers a useful precedent. Organizations that ran early pilots on ordinary workloads built skills and operating habits, then moved regulated workloads once the certifications and contract terms arrived. The same sequence fits Frontier. The selection of pilot users should therefore turn on the data they hold, not on seniority or enthusiasm. A pilot group that touches patient records, regulated financial data, or work bound by ISO commitments is not the right group while the Frontier terms stand. If Microsoft extends HIPAA and ISO coverage to features at release, the objection would stand in full. The CIO and the data protection officer should choose the pilot groups together at this quarter’s pilot gate, and enroll real users doing ordinary work now.

The Deeper Read · About 1 minute

Select a question to open the full answer

1Why does the objection not hold for regulated data?

The terms are explicit. Microsoft’s Frontier page excludes HIPAA Business Associate Agreement coverage and says Frontier features do not comply with ISO 27001, 27002, or 27018. Those are not edge cases. They are the terms many health, financial, and public sector contracts name. Learning can happen on ordinary work. Regulated work can wait for the terms.

Learning is real. Greyhound Research wrote in July 2025 that users should be trained not only on functionality but to challenge AI-generated outputs. That skill is what early Frontier pilots build, and it does not need regulated data to build it.

What the evidence tells a buyer. The objection and this note agree more than they differ. Both hold that delegation is a skill worth building now, and both read the Frontier terms as written. The disagreement is narrow and concerns which work goes into a preview. Greyhound Research sees that narrowness as useful, because it lets a CIO say yes to learning and not yet to regulated data in the same decision, without slowing either one.

In the source’s own words

  • Greyhound Research, Researcher and Analyst agents noteestablishing the expectation that every agent output is a draft, not a decision.Source
  • Microsoft Learn, Frontier programFrontier features are preview and subject to change.Source

↑ Back to the section guide

Part 7What To Do, By Role

The Greyhound CXO Runbook: Ten Moves Before The Agents Arrive

Greyhound SpotlightEvery move uses something the buyer already controls: a training plan, a Frontier setting, a data map, a test plan, a contract, an app register, a budget, a usage policy, an architecture review, or a risk register.

Ten moves follow from the evidence, at least one for each leader who will own part of the new Copilot. Each names the assumption it corrects, the evidence behind it, and the executive who decides. None waits for Microsoft, because each uses controls the buyer already holds.

The moves are deliberately ordinary. Each belongs to a process the company already runs, a training plan, a change board, a data map, an access review, a renewal, an app register, a budget cycle, a usage policy, an architecture review, or a risk register, so none needs a new committee or budget line. Earlier platform shifts suggest that controls attached to existing routines outlast programs created for the occasion. The first versions will probably be rough, in Greyhound Research’s estimate, and will change as Microsoft publishes release terms, and that is acceptable. The second-order benefit is an evidence file. If an auditor, a regulator, or the board later asks how the company decided to adopt agents, the ten documents answer it in the company’s own words and with their own dates.

Table 5 sets the ten moves beside the assumption each corrects, its evidence, and its owner. Two of the ten finish only when Microsoft answers.

Greyhound Research · Table 5 · The Greyhound CXO Runbook by owner

Ten moves, and none waits on Microsoft to start

Ten moves for the leaders who will own part of the new Copilot, with the assumption each corrects, its evidence, and its owner.

Start all ten this quarter. Only the audit and contract moves need Microsoft’s answers to finish.

Starts on controls the buyer already holdsCompletes when Microsoft answers

Select a move to open its full text in The Deeper Read below

MoveThe assumption it correctsEvidence anchorThe decision sits with
1/Retrain the doorway now, by roleA new first screen needs no trainingExhibits 1 and 2Head of change and adoption, with learning and development
2/Enroll named pilot groups in Frontier, not all usersFrontier is a switch for the whole companyExhibit 3, Table 1CIO
3/Keep regulated data out of Frontier featuresEnterprise data protection reaches every featureTable 2Data protection officer, with the CISO
4/Test Autopilot’s audit record before a pilot widensA log is complete because it existsExhibits 4 and 5CISO
5/Write the Frontier terms into the renewalTerms at release will match today’sTables 2 and 3Head of procurement, with legal counsel
6/Register every app published to the runtimeVisibility in the admin center is ownershipTable 1CIO, with the Microsoft 365 platform lead
7/Fund the released half as a release, and the Frontier half as a pilotThe OS claim can be funded as one releaseTable 1, Exhibit 2Chief financial officer
8/State in the usage policy who answers for an agent’s workAn agent’s work is plainly its ownExhibit 4Chief people officer, with legal counsel
9/Compare the two front doors on status, terms, and data locationThe two suites differ mainly in designTable 3Chief enterprise architect, with the head of procurement
10/Put the Frontier enrollment scope before the board’s risk reviewA risk that starts as a setting is too small for the boardTable 4Chief risk officer, with the board’s risk committee
Source: Greyhound Research analysis of the evidence in this research note.

Table 5 sets out the ten moves of the Greyhound CXO Runbook, each with the assumption it corrects, the exhibit or table it rests on, and the executive with whom the decision sits, and shows that none waits on Microsoft to start while two complete only when Microsoft answers. The moves are: retrain the doorway now by role, enroll named pilot groups in Frontier and not all users, keep regulated data out of Frontier features, test Autopilot’s audit record before a pilot widens, write the Frontier terms into the renewal, register every app published to the runtime, fund the released half as a release and the Frontier half as a pilot, state in the usage policy who answers for an agent’s work, compare the two front doors on status, terms, and data location, and put the Frontier enrollment scope before the board’s risk review. The moves are Greyhound Research analysis.

Table 5. Ten moves, and none waits on Microsoft to start. Current through November 19, 2026. © Greyhound Research.

The two that finish later, on the audit record and on the contract, wait on answers Microsoft has not yet published. Those answers are what the questions that follow ask for, and each question maps to a move a buyer can make meanwhile. Every other move rests on an exhibit or table in this note and names who decides. Those eight can be finished this quarter with controls the buyer already holds.

The Deeper Read · About 5 minutes

Select a move to open its full text

1Change and adoption leads: retrain the doorway now, by role.

Exhibits 1 and 2 show a front-end change that reaches every licensed user this winter, with no training guidance in Microsoft’s notices. This move corrects the belief that a new first screen needs no training. Its action is to publish a short guide to Home and Office in Copilot before each update ring, give the help desk scripts for the renamed app and address, and build delegation lessons by role. The decision sits with the head of change and adoption, together with learning and development.

2CIOs: enroll named pilot groups in Frontier, not all users.

Exhibit 3 and Table 1 show the agent features arriving only through Frontier, with no release dates. This move corrects the habit of treating Frontier as a switch for the whole company. Its action is to set Frontier to specific users and groups, name an owner for each Frontier feature, and review the groups each quarter. The decision sits with the CIO.

3Data protection officers: keep regulated data out of Frontier features.

Table 2 shows Frontier without HIPAA coverage and outside three ISO standards. This move corrects the belief that enterprise data protection reaches every Copilot feature. Its action is to exclude users who handle patient records, regulated financial data, or ISO-bound work from Frontier groups, to run Microsoft’s oversharing checks on SharePoint and OneDrive before the deferred ring, and to treat any request to turn on Claude models as a residency decision. The decision sits with the data protection officer, together with the CISO.

4CISOs: test Autopilot’s audit record before a pilot widens.

Exhibits 4 and 5 show a launch post that promises a clear trail and documentation that does not guarantee a complete one. This move corrects the assumption that an agent’s log is complete because it exists. Its action is to run a known set of Autopilot actions, compare them with what the record captures, and hold any wider pilot until the gaps are known. The decision sits with the CISO.

5Procurement: write the Frontier terms into the renewal.

Table 2 and Table 3 show preview terms written down by Microsoft and terms not yet published for release. This move corrects the assumption that the terms at release will match today’s. Its action is to ask Microsoft in writing for release dates, the terms each feature carries at release, and the models each feature uses, and to make those answers part of the next renewal. Greyhound Research’s November 15 note on the Microsoft 365 outage held that standard terms around one suite are no longer enough, and the same reasoning applies here. The decision sits with the head of procurement, together with legal counsel.

6Platform owners: register every app published to the runtime.

The section on Copilot Code shows a generally available runtime and a builder due in December. This move corrects the belief that visibility in the admin center is ownership. Its action is to require a named owner, a data connection list, and a review date for every app before it is shared, and to decide before December which work data Code may use by default. The decision sits with the CIO, together with the head of the Microsoft 365 platform.

7Finance leads: fund the released half as a release, and the Frontier half as a pilot.

Table 1 shows four products generally available and four in the Frontier program, and Exhibit 2 shows that features billed by use reach a user only through a spending policy. This move corrects the belief that a business case for the OS claim can be funded as one release. Its action is to split the Copilot business case in the next budget cycle, funding Home, Office in Copilot, and the runtime as a release, and holding any benefit that depends on Autopilot, Workspaces, or Today until each has a release date and terms on paper. The spending policy, which already decides who may run features billed by use, should name its users and be checked against the pilot groups before the next renewal. The decision sits with the chief financial officer. Measuring value and cost in full is the subject of a companion Greyhound Research note on Agent 365 economics.

8Chief people officers: state in the usage policy who answers for an agent’s work.

Exhibit 4 follows one Autopilot task from request to record, and shows an agent with its own name, mailbox, and calendar that keeps working on its owner’s requests while the owner is away. This move corrects the belief that work an agent sends is plainly the agent’s own. Colleagues will tend to read a message or a changed file from an Autopilot as its owner’s work, so accountability is likely to land on people before any policy says where it belongs. Its action is to add three points to the acceptable use policy the company already holds: who answers for what each Autopilot sends or changes, that every agent output is a draft and not a decision until a person checks it, and that line managers review delegated work like any other. The policy should be ready at the pilot gate, before the first Autopilot group is enrolled. The decision sits with the chief people officer, together with legal counsel.

9Enterprise architects: compare the two front doors on status, terms, and data location.

Table 3 shows Microsoft ahead on released features and on written preview terms, with Google’s Gemini agent in private preview in October and its terms not found in the documents read. It also shows both suites routing work across their own and Anthropic’s models. This move corrects the belief that the two front doors differ mainly in design, and that choosing one suite removes a shared supplier from view. Its action is to bring the comparison to the next architecture review on three tests only: what is released, what the preview terms exclude, and where each model processes data. Both vendors should be asked for those three things in writing, and Anthropic belongs on the supplier risk register whichever suite is chosen. The comparison should be run again if Google’s agent becomes widely available with written terms. The decision sits with the chief enterprise architect, together with the head of procurement.

10Chief risk officers: put the Frontier enrollment scope before the board’s risk review.

Table 4 shows five risks, each beginning in a setting, a list, or a plan the buyer already holds, and each cheaper to prevent at enrollment than to unwind later. This move corrects the belief that a risk which starts as a setting is too small for the board. Settings chosen in the first week of a program are seldom revisited until something forces a review, and by then they have become the default. Its action is to enter the five risks in the enterprise risk register with the owners Table 4 names, ask each owner to report its early warning every quarter, and keep a short written record for each Frontier enrollment: who asked, which data the user holds, and who approved it. The Frontier enrollment scope should then sit as a standing item at the board risk review until the agents are released. The decision sits with the chief risk officer, together with the board’s risk committee.

↑ Back to the section guide

Part 7What To Do, By Role

Questions For Microsoft: What Buyers Will Ask Next

Greyhound SpotlightFour of the six questions have no answer at all in what Microsoft has published, including when Autopilot will be released.

Every finding in this note rests on what Microsoft has published, and Microsoft alone can close the gaps it names. Six questions follow, in the order the evidence raises them. Each gives what Microsoft has said so far, what the answer would settle, and the Runbook move it maps to. No move waits on them, and an account team can answer each from documents Microsoft already holds.

Questions of this kind are the normal work of turning an announcement into a contract, and account teams expect them at renewal. What has changed is how many concern previews, where the answer may not yet exist. Greyhound Research expects the release dates and the HIPAA and ISO answers to come first, because Microsoft needs them to move customers out of Frontier, and the memory retention answer to come later. The point worth planning for is that silence is also information. A feature that still has no release date or stated retention period at the next renewal is telling the buyer where it belongs, which is with the pilot group, whatever the announcements suggest.

Table 6 tracks the six questions against what Microsoft has said so far. Two are answered in part, and four not at all.

Greyhound Research · Table 6 · Questions for Microsoft, tracked

Two questions answered in part, four not at all

The six questions only Microsoft can answer, against what it had stated by 00:58 UTC on November 19, 2026.

Ask in writing and act meanwhile. A question still open at renewal is itself a reason to keep a feature in pilot.

Stated in partNot stated

Select a question to open its full text in The Deeper Read below

QuestionWhat Microsoft has said so farThe Runbook move it settles
Q1When will Autopilot, Workspaces, and Today be generally available?Not stated All three are in Frontier, with no release date.Runbook move 2
Q2Will Frontier features carry HIPAA and ISO coverage when they are released?Not stated The Frontier page excludes both for previews.Runbook move 3
Q3What does Autopilot’s audit record capture, and where is it kept?Stated in part Logged under its own name, and not guaranteed complete.Runbook move 4
Q4Which models carry Cowork and Autopilot work today, and where is it processed?Stated in part Anthropic models at Cowork’s June release. Decision-1.1 routes in Frontier.Runbook move 3
Q5How long does Autopilot keep its memory and working context?Not stated Context is kept between sessions, with no period given.Runbook move 5
Q6What training and adoption path does Microsoft provide for the new front end?Not stated Neither rollout notice carries training guidance.Runbook move 1
Against this: Each of the six asks Microsoft to write down what its product does or will do at release.
Source: Greyhound Research analysis of Microsoft’s Book of News, Copilot Blog, Microsoft Learn, and Microsoft 365 message center notices.

Table 6 tracks six questions only Microsoft can answer against what it had stated by 00:58 UTC on November 19, 2026, and shows two answered in part and four not stated at all. Answered in part: what Autopilot’s audit record captures, and which models carry Cowork and Autopilot work. Not stated: release dates for Autopilot, Workspaces, and Today, HIPAA and ISO coverage at release, how long Autopilot keeps its memory, and a training path for the new front end. Each question names the Runbook move it settles. The grading is Greyhound Research analysis.

Table 6. Two questions answered in part, four not at all. Current through November 19, 2026. © Greyhound Research.

Two answers would change this note’s reading most. One is a statement that Frontier features carry HIPAA and ISO coverage when they are released. The other is documentation that Autopilot’s audit record is complete. Either would move the agents from a pilot program toward production. Each of the six asks Microsoft to write down what its product does or will do at release.

The Deeper Read · About 1 minute

Select a question to open its full text

Q1When will Autopilot, Workspaces, and Today be generally available?

Said so far. Not stated. The Book of News places all three in Frontier and gives no release date. The answer settles. When the pilot groups of the second Runbook move can widen. Evidence that would settle it. Published release dates for each feature. Greyhound Research would update. Exhibit 3 and Table 1.

Q2Will Frontier features carry HIPAA and ISO coverage when they are released?

Said so far. Not stated. The Frontier page excludes both for previews. The answer settles. When regulated users can join, under the third Runbook move. Evidence that would settle it. Compliance documentation for each feature at release. Greyhound Research would update. Table 2.

Q3What does Autopilot’s audit record capture, and where is it kept?

Said so far. In part. The launch post says actions are logged under Autopilot’s own name. The documentation says activity is not a guarantee of a complete record. The answer settles. Whether the test of the fourth Runbook move can be passed. Evidence that would settle it. Audit documentation for Autopilot. Greyhound Research would update. Exhibit 5.

Q4Which models carry Cowork and Autopilot work today, and where is it processed?

Said so far. In part. Cowork ran on Anthropic models at release in June, and Auto in Cowork will use Microsoft-Decision-1.1 for Frontier customers. The answer settles. The residency decision of the third Runbook move. Evidence that would settle it. A model and processing location list for each feature. Greyhound Research would update. Table 3.

Q5How long does Autopilot keep its memory and working context?

Said so far. Not stated. The documentation says the cloud workspace can keep working context between sessions. The answer settles. Retention terms for the contract of the fifth Runbook move. Evidence that would settle it. A stated retention period and deletion control. Greyhound Research would update. Exhibit 4.

Q6What training and adoption path does Microsoft provide for the new front end?

Said so far. Not stated. Neither rollout notice carries training guidance. The answer settles. How much of the first Runbook move a company must build alone. Evidence that would settle it. Published adoption material for Home, Office in Copilot, and Autopilot. Greyhound Research would update. Exhibit 2.

↑ Back to the section guide

Part 8The Final Greyhound Standpoint

Copilot As The OS For Work: The Final Greyhound Standpoint

Greyhound SpotlightFour signals within twelve months would move this position, and Microsoft controls all four.

Greyhound Research’s final judgment is that Ignite 2026 moved the front door of Microsoft 365, and that the control which now matters most is who is allowed through its preview side. Home and Office in Copilot are released and reach every licensed user this winter, so the doorway is no longer a plan. The agents that make Copilot an OS for work, Autopilot, Workspaces, Today, and Code until December, are Frontier previews. When the front door moves, Frontier enrollment becomes the control: which users, holding which data, may use features that run under preview terms.

This is a position about sequence, not about the merit of the strategy. Microsoft has done much of the work a buyer could ask on the doorway, with rollout dates written down by ring. On the agents, it has documented substantive controls and stated their limits in its own pages. Its Frontier terms leave out HIPAA coverage and three ISO standards. Its Autopilot documentation does not guarantee a complete audit record. Microsoft is ahead of Google on released features and on written terms. Companies that have lived through earlier platform shifts will recognize the pattern: the interface arrives first and is released, while the capability that justifies it arrives later, under terms that are still settling. Buyers who planned for that gap in past transitions spent less time repairing it afterward.

The evidence has limits, and they bound how firmly this view should be held. Microsoft’s pages word some statuses differently, and the note gives both readings. The Cowork documentation is marked as prerelease. Google’s terms for its agent were not found, and its announcement was read only as a launch post. No company’s outcomes from the agents are yet on the record. Statuses and claims are as each company published them through November 19, 2026.

Four signals would move this position within twelve months, and each would strengthen the case for wider enrollment. They are release dates for Autopilot, Workspaces, and Today, HIPAA and ISO coverage for those features at release, documentation that Autopilot’s audit record is complete, and a stated retention period for Autopilot’s memory.

Exhibit 7 sets those signals side by side with what each would change. All four sit with Microsoft.

Greyhound Research · Exhibit 7 · Signals that would move the position

Four signals in twelve months would move this position

What would move Greyhound Research’s judgment within twelve months, and what each would change.

HIPAA and ISO coverage at release is the signal that would move this view furthest. Watch it first.

Signal Microsoft controlsEvent outside its control
HIPAA and ISO coverage at releaseA statement that Autopilot, Workspaces, and Today carry HIPAA and ISO coverage when released.Would open the agents to regulated users, the change that matters most. Controlled by: Microsoft.Release dates for the agentsGeneral availability dates for Autopilot, Workspaces, and Today.Would turn pilots into a deployment plan. Controlled by: Microsoft.A complete audit recordDocumentation that Autopilot’s record captures every action, and where it is kept.Would let security teams rely on the trail. Controlled by: Microsoft.A memory retention periodA stated retention period and deletion control for Autopilot’s memory.Would let contracts set how long agent context lives. Controlled by: Microsoft.Outside Microsoft’s controlWide availability of Google’s Gemini agent, with written terms, could reset the comparison.
Source: Greyhound Research analytical model, not measured data. Greyhound Research analysis.

Exhibit 7 lists the four signals that would move Greyhound Research’s position within twelve months, each controlled by Microsoft, and one event outside its control. HIPAA and ISO coverage at release would open the agents to regulated users, the change that matters most. Release dates for Autopilot, Workspaces, and Today would turn pilots into a deployment plan. A complete audit record would let security teams rely on the trail. A memory retention period would let contracts set how long agent context lives. Wide availability of Google’s Gemini agent with written terms could reset the comparison. The signals are Greyhound Research analysis.

Exhibit 7. Four signals in twelve months would move this position. Current through November 19, 2026. © Greyhound Research.

One event outside Microsoft’s control could reset the comparison: wide availability of Google’s Gemini agent with written terms. Of the four signals, HIPAA and ISO coverage at release would matter most, because it decides which users may be enrolled at all. Until the signals arrive, the decisions fall to the buyer, at points the buyer already controls. Change and adoption leads should move the doorway now, before the deferred ring. CIOs and data protection officers should enroll the agents slowly and by name at each quarter’s pilot gate. CISOs should test the audit record before any pilot widens. Procurement should carry the open terms into the next renewal, and the board’s risk review should see the Frontier enrollment scope as a standing item until the agents are released.

↑ Back to the section guide

Part 9Appendix, Sources, And Disclosures

Appendix: The Evidence Register, Source By Source

Greyhound Research sets out here the evidence behind every fact, figure, and quotation in this research note, one drop-down for each class of source, so that any sentence can be checked against the words it rests on without leaving the page. Each row gives the source, when it was read, the part of the source the words sit in, what it says, and where in this research note that material is used. Times of reading are in UTC. Every source was read, or read again, on November 19, 2026, between 00:28 and 00:58 UTC. Where a passage was summarized and not quoted, the row says so. A passage quoted in The Deeper Read of a section is not repeated here, and the source’s entry names the section that quotes it.

Microsoft announcements and blogs7 sources, 39 extracts
Source, read, and usedWhere in the sourceWhat it says
KOHLER (2026)Read November 19, 2026, between 00:28 and 00:58 UTCUsed in Adoption And TrainingQuoted in The Deeper Read of Adoption And TrainingStory[quoted in The Deeper Read]
StorySheri Tower, organizational change manager for AI, says the company focused distinct resources and training at all three levels of the business (summarized, not quoted).
Reading noteA Microsoft customer story, published August 10, 2026. Its adoption percentages are not used in this note.
Lamanna, C. (2026)Read November 19, 2026, between 00:28 and 00:58 UTCUsed in What Microsoft Announced, Frontier Or General Availability, Whose Model. Tables 1 and 6. Exhibit 3Quoted in The Deeper Read of Whose ModelPost[quoted in The Deeper Read]
PostCowork is generally available worldwide from June 16, 2026, billed on a usage basis in Copilot Credits, and requires the Microsoft 365 Copilot User Subscription License. A model named Cowork 1 is to be released in the coming weeks (summarized, not quoted).
Reading noteThe English original, published June 16, 2026. It replaces the Japanese edition read on November 18.
Microsoft (2026a)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Copilot Code, What Microsoft Announced, The Front Door Moves, Copilot Code And Managed Runtime, Frontier Or General Availability, Whose Model, The Audit Gap. Tables 1 and 6. Exhibits 3 and 5Quoted in The Deeper Read of What Microsoft Announced, The Front Door Moves, Copilot Code And Managed Runtime, Frontier Or General Availability, Whose Model, The Audit GapMicrosoft Copilot[quoted in The Deeper Read]
Microsoft Copilot[quoted in The Deeper Read]
Microsoft Copilot[quoted in The Deeper Read]
Microsoft Copilot[quoted in The Deeper Read]
Microsoft Copilot[quoted in The Deeper Read]
Microsoft Copilot[quoted in The Deeper Read]
Reading noteThe future tense on November 17 differs from the September post, which planned Today's private preview for October. Exhibit 3 uses the later reading.
Microsoft Copilot[quoted in The Deeper Read]
Microsoft Copilot[quoted in The Deeper Read]
Microsoft Copilot[quoted in The Deeper Read]
Microsoft Copilot"This daily refresh is included with a Microsoft 365 Copilot license." and "Recurring updates throughout the day require Copilot credits." (Today).
Microsoft Copilot"Home, announced in September and now rolling out worldwide, is the new starting point in Copilot"
Microsoft CopilotCopilot Code is available in Frontier on Windows, web, iOS, and Android, with a local sandbox on Windows and coming soon to macOS. Fabric can provide database, storage, and data services for the runtime. Agents and Workflows arrive as a first iteration (summarized, not quoted).
Microsoft Entra[quoted in The Deeper Read]
Microsoft Purview[quoted in The Deeper Read]
Microsoft (2026b)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in What Microsoft Announced, Adoption And TrainingCopilot"New Copilot Workspaces gives people and agents a shared space to work together as a team."
Copilot"Volkswagen Group is equipping more than 330,000 employees with Copilot"
CopilotAutopilot, Code, Workspaces, Office in Copilot, and Today are listed as the parts of the new Copilot (summarized, not quoted).
Nadella, S. (2026)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in What Microsoft AnnouncedQuoted in The Deeper Read of What Microsoft AnnouncedPost[quoted in The Deeper Read]
Post"That is why we have all of Office with its richness built into Copilot."
Spataro, J. (2026a)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in What Microsoft Announced, Frontier Or General Availability, Autopilot, The Audit Gap. Exhibit 3Quoted in The Deeper Read of What Microsoft AnnouncedPost[quoted in The Deeper Read]
Post"with permissions, audit and governance behind it." (Autopilot).
PostAutopilot was previously called Scout and moves to private preview at the end of September. Today enters private preview in October. Managed Runtime is in preview. Billing by use covers Cowork, Code, and Autopilot (summarized, not quoted).
Spataro, J. (2026b)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Copilot Code, What Microsoft Announced, The Front Door Moves, Adoption And Training, Copilot Code And Managed Runtime, Whose Model, The Audit Gap. Exhibit 5Quoted in The Deeper Read of What Microsoft Announced, The Front Door Moves, Adoption And Training, Copilot Code And Managed Runtime, Whose Model, The Audit GapPost[quoted in The Deeper Read]
Post[quoted in The Deeper Read]
Post[quoted in The Deeper Read]
Post"More than 5,000 people at Lilly are using Copilot Cowork every month"
Post[quoted in The Deeper Read]
Post[quoted in The Deeper Read]
Post[quoted in The Deeper Read]
Post[quoted in The Deeper Read]
Post"Code will become generally available in the coming weeks"
Reading noteThe post cites a third-party cost comparison and third-party figures on corporate AI spending. Neither is used in this note.
Microsoft documentation11 sources, 46 extracts
Source, read, and usedWhere in the sourceWhat it says
Microsoft (2026c)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Adoption And Training, Frontier Terms, Whose Model, The Strongest Objection, Copilot As The OS For Work. Table 2. Exhibits 2 and 6Quoted in The Deeper Read of Adoption And Training, Frontier Terms, The Strongest Objection, Whose ModelOverview[quoted in The Deeper Read]
Terms[quoted in The Deeper Read]
Terms[quoted in The Deeper Read]
Terms[quoted in The Deeper Read]
Terms[quoted in The Deeper Read]
Terms[quoted in The Deeper Read]
AI providers[quoted in The Deeper Read]
Terms"Certain Frontier experiences may only be available on a paid basis."
SetupFrontier access can be set for all users or for specific users and groups. Features can take three hours to appear. The Frontier control does not override agent settings in the admin center (summarized, not quoted).
Reading noteLast updated November 16, 2026.
Microsoft (2026d)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Frontier Terms, Whose Model. Table 2Quoted in The Deeper Read of Frontier Terms, Whose ModelDefinition[quoted in The Deeper Read]
Agents[quoted in The Deeper Read]
Exceptions[quoted in The Deeper Read]
CommitmentsPrompts, responses, and data accessed through Microsoft Graph are not used to train foundation models. The EU Data Boundary does not apply to web search queries. HIPAA is supported for properly configured implementations (summarized, not quoted).
PrivacyThe page lists ISO/IEC 27018 among Copilot's privacy commitments. It does not address ISO 27001 or ISO 27002 (summarized, not quoted).
Reading noteLast updated November 4, 2026. The page does not mention Frontier or preview features.
Microsoft (2026e)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in The Front Door Moves, Frontier TermsQuoted in The Deeper Read of The Front Door MovesApps[quoted in The Deeper Read]
HomeThe Home tab provides a unified starting point for Chat and Cowork in the Copilot app. The primary address is changing to copilot.cloud.microsoft (summarized, not quoted).
ProtectionCopilot Chat (Basic), Microsoft 365 Copilot (Basic), and Microsoft 365 Copilot (Premium) are protected by enterprise data protection when users sign in with Microsoft Entra accounts (summarized, not quoted).
Microsoft (2026f)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Final Greyhound Standpoint, Autopilot, The Audit Gap, Copilot As The OS For Work. Exhibits 4 and 5Quoted in The Deeper Read of Autopilot, The Audit GapOverview[quoted in The Deeper Read]
Access[quoted in The Deeper Read]
Access[quoted in The Deeper Read]
Approvals[quoted in The Deeper Read]
Compliance[quoted in The Deeper Read]
Compliance[quoted in The Deeper Read]
MemoryThe cloud workspace can retain working context between sessions. No retention period is given. Autopilot has its own mailbox and calendar (summarized, not quoted).
Reading noteLast updated November 17, 2026. The page does not mention a named manager or Entra Agent ID.
Microsoft (2026g)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Adoption And Training, Autopilot. Exhibits 2 and 4Quoted in The Deeper Read of Adoption And TrainingPrerequisites[quoted in The Deeper Read]
First task[quoted in The Deeper Read]
PrerequisitesThe administrator licenses Autopilot, covers the user with a spending policy for billing by use, and activates it. Frontier enrollment alone does not make Autopilot available. All payments wait for the user to allow or deny (summarized, not quoted).
Microsoft (2026h)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in AutopilotQuoted in The Deeper Read of AutopilotAccess[quoted in The Deeper Read]
Reading noteLast updated August 21, 2026. Describes Scout, the earlier name for Autopilot. Not assumed to apply to Autopilot.
Microsoft (2026i)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Copilot Code, Copilot Code And Managed RuntimeQuoted in The Deeper Read of Copilot Code And Managed RuntimeAvailability[quoted in The Deeper Read]
DataCode can use documents, emails, meetings, and calendar as context if an administrator enables it, and apps can be shared within the organization (summarized, not quoted).
Reading noteLast updated October 6, 2026. The page says Code is a preview provided under Microsoft Product Terms.
Microsoft (2026j)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Copilot Code, Copilot Code And Managed RuntimeQuoted in The Deeper Read of Copilot Code And Managed RuntimeOverview[quoted in The Deeper Read]
Reading noteLast updated November 17, 2026. The landing page does not state a release status.
Microsoft (n.d.)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Frontier Or General AvailabilityQuoted in The Deeper Read of Frontier Or General AvailabilityAvailability[quoted in The Deeper Read]
Reading noteThe page is marked as prerelease documentation and shows no update date.
Microsoft (2026k)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Whose ModelQuoted in The Deeper Read of Whose ModelOverview[quoted in The Deeper Read]
DefaultsClaude models are on by default for most commercial customers, and off by default for customers in the EU, EFTA, and UK (summarized, not quoted).
TermsThe Product Terms and Data Protection Addendum apply unless models are labeled Anthropic models with Data Retention (summarized, not quoted).
Reading noteLast updated November 4, 2026.
Microsoft (2026n)Read November 19, 2026, between 00:28 and 00:58 UTCUsed in The Front Door Moves, The Greyhound CXO RunbookQuoted in The Deeper Read of The Front Door MovesOverview[quoted in The Deeper Read]
ToolsMicrosoft Purview and SharePoint Advanced Management are recommended to find high-risk sites and files, apply interim restrictions, and fix access. SharePoint Advanced Management is included with the Copilot license (summarized, not quoted).
Reading noteLast updated November 13, 2026.
Microsoft 365 message center2 sources, 5 extracts
Source, read, and usedWhere in the sourceWhat it says
Microsoft (2026l)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in The Front Door Moves, Frontier Or General Availability. Exhibits 1 and 3NoticeStandard release from late October 2026, deferred release from late November 2026. Projects added to Home. Notebooks become Workspaces, with standard release by January 2027 and deferred release by February 2027. Admins review who sits in the spending policy that grants Cowork. No training guidance (summarized, not quoted).
Reading noteNotice MC1535647, published November 2 and updated November 11, 2026, read from a public archive of message center notices.
Microsoft (2026m)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in The Front Door Moves, Frontier Or General Availability. Exhibits 1 and 3Notice"We have begun rolling out and expect to complete by mid-November 2026."
NoticeDeferred release from early December 2026. No admin action required. The change alters how existing customer data is accessed, and Copilot gains expanded ability to read and edit Office documents (summarized, not quoted).
Reading noteNotice MC1530611, published October 29 and updated November 10, 2026, read from a public archive of message center notices.
Google and media4 sources, 10 extracts
Source, read, and usedWhere in the sourceWhat it says
Claburn, T. (2026)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in What Microsoft AnnouncedArticle"Apps are just plugins to Copilot," (Nadella, in his Ignite keynote).
Fagan, S. (2026)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in What Microsoft AnnouncedArticleNadella described Copilot as a new OS for work in a LinkedIn post when the new Copilot was introduced in September 2026 (summarized, not quoted).
Reading noteThe article's statement on billing before a spending policy is no longer used. The note now rests that point on Microsoft's Autopilot guide.
Kurian, T. (2026)Read November 19, 2026, between 00:28 and 00:58 UTCUsed in Two Front Doors Compared. Table 3Quoted in The Deeper Read of Two Front Doors ComparedPost[quoted in The Deeper Read]
Post[quoted in The Deeper Read]
PostGemini works across devices and channels including Google Workspace, Microsoft 365, and Slack, orchestrates across Gemini and Claude models, and can act as a personal assistant or team member. Coworker agents have their own identities and email addresses. Companies can set hard spending limits by project (summarized, not quoted).
Reading noteThe post states no release status for the core agent, and no terms or pricing.
Li, A. (2026)Read again November 19, 2026, between 00:28 and 00:58 UTCUsed in Two Front Doors Compared. Table 3Article"It's currently in private preview."
ArticleGemini agent is reached by mentioning @Gemini in Gmail, Docs, Sheets, Slides, and Chat, and wide availability is expected soon for select Workspace Business and Enterprise plans (summarized, not quoted).
Reading noteUsed only for the release status at announcement, which Google's own post does not state.
Greyhound Research10 sources, 20 extracts
Source, read, and usedWhere in the sourceWhat it says
Greyhound Research (2025a)Read again November 19, 2026, before 00:58 UTC, on greyhoundresearch.comUsed in Adoption And TrainingNoteCopilot Chat as a free, web-grounded tier with enterprise data protection, and adoption as an ongoing process (summarized, not quoted).
Greyhound Research (2025b)Read again November 19, 2026, before 00:58 UTC, on greyhoundresearch.comUsed in The Front Door MovesNoteCopilot had become an overcrowded term with conflicting meanings for different audiences (the passage is quoted in The Deeper Read of The Front Door Moves).
Note"This is a strategic weakness, not only a marketing concern."
Greyhound Research (2025c)Read November 19, 2026, before 00:58 UTC, on greyhoundresearch.comUsed in What Microsoft AnnouncedQuoted in The Deeper Read of What Microsoft AnnouncedBriefMicrosoft is proving that Copilot is not a feature but a platform shift (summarized, not quoted).
Brief[quoted in The Deeper Read]
Greyhound Research (2025d)Read again November 19, 2026, before 00:58 UTC, on greyhoundresearch.comUsed in The Audit GapNoteEntra Agent ID as a policy control plane for agent-based computing (summarized, not quoted).
Greyhound Research (2025e)Read again November 19, 2026, before 00:58 UTC, on greyhoundresearch.comUsed in Adoption And Training, Autopilot, Two Front Doors Compared, The Strongest ObjectionQuoted in The Deeper Read of The Strongest Objection, Two Front Doors ComparedNote[quoted in The Deeper Read]
NoteUsers should be trained not only on functionality but empowered to challenge AI-generated outputs (summarized, not quoted).
NoteResearcher uses scoped OAuth 2.0 tokens to respect user-specific permissions and adheres to tenant-wide role-based access control (summarized, not quoted).
Note[quoted in The Deeper Read]
NoteThe value this creates raises difficult questions about portability, interoperability, and negotiating leverage (summarized, not quoted).
Greyhound Research (2026a)Read November 19, 2026, between 00:28 and 00:58 UTCUsed in What Microsoft AnnouncedQuoted in The Deeper Read of What Microsoft AnnouncedComment[quoted in The Deeper Read]
CommentThe earlier approach pushed Copilot across multiple surfaces without always delivering clear, contextual value (summarized, not quoted).
Reading noteA Greyhound Research comment as published on March 24, 2026, read on the publishing page.
Greyhound Research (2026b)Read again November 19, 2026, before 00:58 UTC, on greyhoundresearch.comUsed in Adoption And TrainingQuoted in The Deeper Read of Adoption And TrainingGreyhound CIO Pulse 2026[quoted in The Deeper Read]
Greyhound Research (2026c)Read again November 19, 2026, before 00:58 UTC, on greyhoundresearch.comUsed in What Microsoft Announced, AutopilotNoteNadella described Copilot as the new operating system for work on Microsoft's October 28 call (summarized, not quoted).
NoteEvery right a person already holds, within the tools the door exposes, can be used by an assistant at once (summarized, not quoted).
Greyhound Research (2026d)Read again November 19, 2026, before 00:58 UTC, on greyhoundresearch.comUsed in Two Front Doors Compared, The Greyhound CXO RunbookNote"Consolidation remains the right strategy for most enterprises."
Note"The standard terms around it are no longer enough."
Greyhound Research (2026e)Draft read again November 19, 2026. Not yet publishedUsed in AutopilotDraftThe authority an agent holds, not its machine, decides what it can do (summarized, not quoted).

↑ Back to the section guide

Part 9Appendix, Sources, And Disclosures

Sources And References: Every Document Behind Every Claim

Every fact, figure, and quotation in this research note traces to one of the sources below, presented in Harvard reference format and grouped by class. Each source is also linked in the sentence that carries it. Microsoft’s documents are its account of its own products, terms, and dates, and prove what the company said rather than that the thing is true. The media report what their authors were told. Microsoft 365 message center notices are read from a public archive of the notices. Every source was read, or read again, on November 19, 2026.

Microsoft announcements and blogs

KOHLER (2026) KOHLER achieves 98% Microsoft 365 Copilot adoption with AI change management strategy. Microsoft customer story, August 10. Available at: https://www.microsoft.com/en/customers/story/26948-kohler-company-microsoft-365-copilot

Lamanna, C. (2026) Copilot Cowork is now generally available. Microsoft 365 Blog, June 16. Available at: https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/16/copilot-cowork-is-now-generally-available/

Microsoft (2026a) Microsoft Ignite 2026 | Book of News. Microsoft News, November 17. Available at: https://news.microsoft.com/events/ignite/2026/book-of-news/

Microsoft (2026b) Microsoft Ignite 2026: Empowering human ambition, intelligence and trust. Microsoft Source, November 17. Available at: https://news.microsoft.com/source/2026/11/17/microsoft-ignite-2026-empowering-human-ambition-intelligence-and-trust/

Nadella, S. (2026) Ignite 2026: Building the frontier ecosystem. The Official Microsoft Blog, November 17. Available at: https://blogs.microsoft.com/blog/2026/11/17/ignite-2026-building-the-frontier-ecosystem/

Spataro, J. (2026a) Introducing the new Copilot with Home, Code and Autopilot. The Official Microsoft Blog, September 25. Available at: https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/

Spataro, J. (2026b) Copilot at Microsoft Ignite: Expanding what’s possible with intelligence built for work. Microsoft Copilot Blog, November 17. Available at: https://www.microsoft.com/en-us/copilot/blog/2026/11/17/copilot-at-microsoft-ignite-expanding-whats-possible-with-intelligence-built-for-work/

Microsoft documentation

Microsoft (2026c) Get started with the Microsoft Copilot Frontier Program. Microsoft Learn, updated November 16. Available at: https://learn.microsoft.com/microsoft-365/admin/manage/get-started-frontier

Microsoft (2026d) Enterprise data protection in Microsoft Copilot and Microsoft Copilot Chat. Microsoft Learn, updated November 4. Available at: https://learn.microsoft.com/copilot/microsoft-365/enterprise-data-protection

Microsoft (2026e) What is Microsoft Copilot? Microsoft Learn, updated November 17. Available at: https://learn.microsoft.com/en-us/copilot/plan/copilot-overview

Microsoft (2026f) Autopilot (Frontier) overview. Microsoft Learn, updated November 17. Available at: https://learn.microsoft.com/en-us/copilot/autopilot/overview

Microsoft (2026g) Get started with Autopilot (Frontier). Microsoft Learn, updated November 17. Available at: https://learn.microsoft.com/en-us/copilot/autopilot/get-started

Microsoft (2026h) Admin access overview for Microsoft Scout. Microsoft Learn, updated August 21. Available at: https://learn.microsoft.com/en-us/microsoft-scout/admin-access-overview

Microsoft (2026i) Copilot Code common questions (Frontier). Microsoft Learn, updated October 6. Available at: https://learn.microsoft.com/en-us/copilot/code/code-faq

Microsoft (2026j) Microsoft Copilot Managed Runtime. Microsoft Learn, updated November 17. Available at: https://learn.microsoft.com/microsoft-365/managed-apps/

Microsoft (n.d.) Copilot Cowork overview. Microsoft Learn, prerelease documentation. Available at: https://learn.microsoft.com/en-us/microsoft-365/copilot/cowork/

Microsoft (2026k) Claude models from Anthropic in Microsoft Online Services. Microsoft Learn, updated November 4. Available at: https://learn.microsoft.com/en-us/microsoft-365/copilot/connect-to-ai-subprocessor

Microsoft (2026n) Secure and govern Microsoft Copilot: Foundational deployment guidance. Microsoft Learn, updated November 13. Available at: https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-blueprint-oversharing

Microsoft 365 message center

Microsoft (2026l) Microsoft Copilot app: Updates to Home and navigation. Microsoft 365 message center, MC1535647, November 2, updated November 11. Available at: https://mc.merill.net/message/MC1535647

Microsoft (2026m) Office in Copilot brings the full power of Office into the Microsoft Copilot app. Microsoft 365 message center, MC1530611, October 29, updated November 10. Available at: https://mc.merill.net/message/MC1530611

Google and media

Claburn, T. (2026) Satya sorry for SaaS-y SNAFU - look over there, more AI! The Register, November 17. Available at: https://www.theregister.com/ai-and-ml/2026/11/17/satya-sorry-for-saas-y-snafu-look-over-there-more-ai/5310594

Fagan, S. (2026) Microsoft Rebuilds Copilot as an ‘OS for Work’. Reworked, September 25. Available at: https://www.reworked.co/digital-workplace/microsoft-rebuilds-copilot-as-an-os-for-work/

Kurian, T. (2026) Welcome to Gemini at Work 2026: Introducing the Gemini agent. Google Cloud Blog, October 8. Available at: https://cloud.google.com/blog/products/ai-machine-learning/welcome-to-gemini-at-work-2026

Li, A. (2026) Google Cloud announces ‘Gemini agent’ as ‘universal agent for work’. 9to5Google, October 8. Available at: https://9to5google.com/2026/10/08/gemini-agent-google-cloud/

Research this note builds on

Greyhound Research (2025a) AI Meets Productivity: What M365 Copilot Chat Means for Enterprises. Research note, March 14. Available at: https://greyhoundresearch.com/microsofts-big-ai-play-m365-copilot-chat/

Greyhound Research (2025b) Microsoft Copilot: The AI Revolution That’s Lost in Branding Chaos. Research note, March 20. Available at: https://greyhoundresearch.com/microsoft-copilot-the-ai-revolution-thats-lost-in-branding-chaos/

Greyhound Research (2025c) The Daily Brief by Greyhound Research | April 8, 2025. Daily brief, April 8. Available at: https://greyhoundresearch.com/the-daily-brief-by-greyhound-research-april-8-2025/

Greyhound Research (2025d) Microsoft Build 2025: Making AI Agents More Capable and Secure. Research note, May 22. Available at: https://greyhoundresearch.com/microsoft-build-2025-making-ai-agents-more-capable-and-secure/

Greyhound Research (2025e) How Microsoft’s Researcher And Analyst Copilot Agents Are Transforming Enterprise Workflows With AI Reasoning. Research note, July 14. Available at: https://greyhoundresearch.com/microsofts-copilot-gets-a-brain-what-researchers-and-analysts-mean-for-enterprise-workflows/

Greyhound Research (2026a) Comment on Microsoft’s Windows 11 quality plan. Published comment, March 24. Available at: https://www.computerworld.com/article/4149325/microsoft-maps-windows-11-quality-overhaul-after-acknowledging-gaps.html

Greyhound Research (2026b) Everyone Is Building AI Agents. Oracle Is Moving The Contest Inside The Runtime. Research note, July 20. Available at: https://greyhoundresearch.com/everyone-is-building-ai-agents-oracle-is-moving-the-contest-inside-the-runtime/

Greyhound Research (2026c) The Front Door Race – Oracle, OpenAI And Five Rivals, And Why The Permission Becomes The Control. Research note, November 5. Available at: https://greyhoundresearch.com/oracle-openai-the-front-door-race-the-permission-becomes-the-control/

Greyhound Research (2026d) Microsoft 365 Outage – When The Suite Goes Dark, Restoration Order Becomes The Control. Research note, November 15. Available at: https://greyhoundresearch.com/microsoft-365-outage-when-the-suite-goes-dark-restoration-order-becomes-the-control/

Greyhound Research (2026e) Microsoft Azure Agent Infrastructure – When Agents Get Their Own Machines, Authority Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-azure-agent-infrastructure-when-agents-get-their-own-machines-authority-becomes-the-control/

↑ Back to the section guide

Part 9Appendix, Sources, And Disclosures

The evidence in this research note is current through November 19, 2026, when every source was read again and the last reading closed at 00:58 UTC, two days after Microsoft’s Ignite announcements. Any written response received from an organization named in it after that time is dated where it appears.

Independence Disclosure

Research under the Greyhound Research brand is independent, and no organization holds a right of approval over its content or publication. It is not commissioned, sponsored, or funded by any organization it covers. Greyhound Research may send a research note to companies named in it for factual review before publication. Any such review is confined to the correction of fact, and no viewpoint, conclusion, or recommendation is guided by those companies. All insights and recommendations are Greyhound Research’s alone, and editorial control remains entirely with Greyhound Research. Greyhound Consilium is the B2B thought-leadership arm of The House Of Greyhound and a sister brand to Greyhound Research. It builds on Greyhound Research’s independent research through collaborations that produce thought-leadership content, research, and practical toolkits for decision-makers. Every Greyhound Consilium publication names its partner on the face of the document. This research note is published under the Greyhound Research brand.

Financial Disclosure

Greyhound Research undertakes advisory and consulting engagements with enterprise buyers and technology providers, and no such engagement confers control over its research findings or its decision to publish them. For this research note, Greyhound Research has no financial interest in, and no commercial relationship with, Microsoft, Amazon Web Services, Google, Anthropic, or OpenAI to declare. Oracle is a client of Greyhound Research. Oracle is not a subject of this research note.

Intended Use

This research note is written for chief information officers, change and adoption leads, learning and development leaders, chief information security officers, data protection officers, procurement and vendor management leaders, Microsoft 365 platform owners, board members, and the press. It reads Microsoft’s Copilot announcements at Microsoft Ignite 2026, the documentation and rollout notices beside them, Google’s announced alternative, and earlier Greyhound Research notes, to inform decisions on the Microsoft 365 front end, adoption and training, Frontier enrollment, data protection, and contracts. This research note is not investment advice, a recommendation to buy, sell, or hold any security, or a view on any company’s share price or valuation. It is not legal advice, and its reading of contract and data protection matters is to be confirmed with counsel. Its assessments rest on the documents listed in Sources And References as they stood on November 19, 2026, and can change as the companies named publish more. Product availability, status, features, and terms are described as each company published them through November 19, 2026, so confirm them with the vendor before acting on them.

Research Methodology

Greyhound Research’s analysis combines lived experience with public sources. The lived experience is years of continuously tracking the market, Greyhound Fieldnotes from ongoing advisory engagements with enterprise buyers and with technology providers, and Greyhound Pulse, the firm’s market trackers. Lived experience forms the judgment and never stands in for evidence. The public sources are the thirty-four documents listed in Sources And References, in five classes, and every factual claim is verified against the document that supports it. The passages relied on are quoted in The Deeper Read of the section that uses them, and the other words taken from each source, the passages summarized rather than quoted and the reading notes, are set out in the appendix. A finding that something is not stated or not found is bounded to the documents the text names, as they stood at 00:58 UTC on November 19, 2026. Statuses are given as each company states them, and where two Microsoft documents word the same status differently, both readings are given.

Microsoft 365 message center notices were read from a public archive of the notices. Google’s Gemini agent is described from Google Cloud’s October 8 announcement, with its release status taken from a contemporary account listed in Sources And References, and Google’s terms for the agent were not found. Usage figures for Cowork and Copilot are Microsoft’s own claims and are not used to measure outcomes. The Greyhound CIO Pulse 2026 figure is cited as published in Greyhound Research’s research note of July 20, 2026. No composite figure is computed. No Greyhound Fieldnotes are quoted, and no factual claim in this research note rests on unpublished material.

The reading of who the front-end change reaches, the adoption steps, the release calendar, the terms comparison, the Autopilot task path, the audit comparison, the readings in Exhibits 1 to 7 and Tables 1 to 6, the risks, the Greyhound CXO Runbook, the questions for Microsoft, the signals, and every term proposed for a contract are Greyhound Research’s analysis, not statements by Microsoft or any other company. Quotations are checked against the live source before publication.

Authoring Disclosure

This material reflects the analysis, viewpoint and editorial judgment of Greyhound Research. The position presented is developed from Greyhound Research’s research, advisory work and accumulated institutional knowledge. Depending on the assignment, AI may be used to retrieve relevant material; structure, draft or polish prose from analyst-provided concepts, dictation, notes, rough drafts and source material; support secondary research and factual cross-checking; and assist with editing, condensation and consistency with Greyhound Research’s house style. AI does not independently establish Greyhound Research’s viewpoint, analytical position or conclusions. Material factual claims are verified against source evidence before release. Greyhound Research reviews and approves the final material and retains responsibility for it.

All content in this document and on the Greyhound Research website is protected by copyright law and may not be reproduced, distributed, transmitted, displayed, published, or broadcast without the prior written permission of Greyhound Research or, in the case of third-party materials, the prior written consent of the copyright owner of that content. You may not alter, delete, obscure, or conceal any trademark, copyright, or other notice appearing in any Greyhound Research content. Quotation of up to one hundred words is permitted where it carries attribution to Greyhound Research and a link to the published page. Reproduction, redistribution or republication beyond that extent, in whole or in part, by email or in any medium including websites, newsletters and intranets, requires prior written permission, which may be requested at the address below. The published version of each content piece on the Greyhound Research website carries sharing tools for readers who wish to share it.

For questions arising from these disclosures, including licensing requests, contact the Greyhound Research Community Relations Team at connect@thofgr.com. For media inquiries, write to media@thofgr.com.

↑ Back to the section guide

Analyst In Focus: Sanchit Vir Gogia

Sanchit Vir Gogia, or SVG as he is popularly known, is a globally recognized technology analyst, innovation strategist, digital consultant and board advisor. SVG is the Chief Analyst at Greyhound Research (part of The House Of Greyhound), a Global, Award-Winning Technology Research, Advisory, Consulting & Education firm. Greyhound Research works closely with global organizations, their CxOs and the Board of Directors on Technology & Digital Transformation decisions.


Discover more from Greyhound Research

Subscribe to get the latest posts sent to your email.

Discover more from Greyhound Research

Subscribe now to keep reading and get access to the full archive.

Continue reading