Publication Record
Evidence current through: Thursday, November 19, 2026, at 12:50 a.m. UTC (7:50 p.m. ET and 4:50 p.m. PT on Wednesday, November 18), which is 12:50 a.m. UTC on Thursday, November 19, 2026.
The Salesforce migration in Dynamics 365 Activate is generally available, while its SAP ECC steps and Salesforce in Copilot are in preview, and the note reads each 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 made two moves on the same day that point in opposite directions. Dynamics 365 Activate, its tool for moving companies off Salesforce onto Microsoft’s own customer software, became generally available, meaning fully released. Microsoft also put the same tool’s first steps for leaving SAP ECC, SAP’s older finance and operations software, into private preview. Then, with Salesforce, it announced Copilotforce, which brings Salesforce data and actions into Microsoft Copilot for companies that stay with Salesforce.
Greyhound Research’s position is that Microsoft is selling the exit and the stay at once, and that both roads end at Copilot. For buyers, the value of Activate is less the migration than the discovery report it produces. A priced, tested plan for leaving changes every renewal conversation with Salesforce and SAP, and with Microsoft, whether or not the company ever moves. Greyhound Research reads this as the familiar economics of switching, changed at one point. The cost of finding out what leaving involves has fallen, while the cost of rebuilding what makes the old system fit the business has not, so the early gain goes to buyers who price the exit rather than those who rush it.
Three findings carry the argument. First, Microsoft has published no price for Activate, and its own words for customized software are “move, simplify, or redesign,” so much of the work is rebuilding, not moving. Second, the SAP tool is in private preview while SAP’s mainstream maintenance for ECC ends at the end of 2027, so it is a planning aid, not yet a path. Third, the speed figures behind the launch are partner forecasts and company claims, and none comes with a method.
The note sets out a ten-move Greyhound CXO Runbook, with seven exhibits, seven tables, and six questions for Microsoft. None of the moves waits on Microsoft. The first three are simple to state. Commission the discovery before the next renewal. Put the exit plan on the renewal table. Test a sample of records and processes before trusting any timeline.
The evidence has limits. Activate has no public documentation beyond Microsoft’s announcements and a partner page. Microsoft’s pages disagree on the SAP tool’s status, and Salesforce and SAP are read here only through their own announcements. Greyhound Research names the signals that would change its view within twelve months. Until they arrive, the advice holds: run the discovery, price the exit, and keep press-release timelines out of contracts.
In This Research NoteSection guide · AI drafted · Analyst reviewed
Seventeen sections in eight 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 twelve 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.
- Part 1What Ignite Changed
- 1.1What Microsoft Announced: One Exit Released, One In Private Preview, One Way To Stay
The Salesforce migration tool is generally available, the SAP ECC tool is in private preview, and Salesforce in Copilot is in preview. None has a published price.
- 1.2Two Signals At Once: Microsoft Sells The Exit And The Stay In The Same Week
Activate moves customers off Salesforce and SAP. Copilotforce keeps Salesforce in place. Both put Copilot in front of the work, and neither has a published price.
- Part 2The Exit
- 2.1Activate For CRM: Leaving Salesforce Now Starts With A Report
Activate reads a Salesforce estate, recommends what to keep or change, and runs the move, with people checking the result. Microsoft has written the first steps, not the price or the proof that nothing was lost.
- 2.2The SAP ECC Clock: A Private Preview Against A 2027 Deadline
SAP’s mainstream maintenance for ECC ends at the end of 2027, with paid extended maintenance to 2030 and a narrow option to 2033. Microsoft’s ECC tool is in private preview.
- 2.3Data And Process Fidelity: Records Move, Logic Is Rebuilt
Data records move. Custom code, workflows, and business processes are decided case by case and often rebuilt. Microsoft does not say how history and audit trails are carried.
- Part 3The Stay
- 3.1Copilotforce: Staying With Salesforce, Inside Microsoft’s Front Door
Salesforce in Copilot lets sellers use Salesforce from Copilot under Salesforce’s own permissions. Who pays for what, and who answers for a wrong update, is not written.
- 3.2The Front Door: Both Doors Lead To Copilot
Whether a company leaves Salesforce or stays, Microsoft’s plan puts Copilot where work starts. The incumbent keeps the record, or Microsoft takes it.
- Part 4The Money
- 4.1Renewal Leverage: The Discovery Report Is The Bargaining Chip
A priced, tested exit plan changes renewals with Salesforce, SAP, and Microsoft alike, whether or not the company moves. Each vendor has its own counter-claim.
- 4.2The Speed Claims: Five Months Is One Customer’s Forecast
The launch rests on five speed and scale claims from Microsoft, two partners, and SAP. None has a published method, and the largest is a forecast for a project still running.
- Part 5The Risks And The Counter-Argument
- 5.1Risks To Watch: Where A Cheaper Exit Can Still Go Wrong
Five risks, from rules lost in the move to paying twice to stay, each with an early warning in the buyer’s own documents and an owner.
- 5.2The Strongest Objection: Most Companies Stay
The fair counter-case: large CRM and ERP moves are rare, Microsoft needs Salesforce, and a vendor-built assessment favors its maker. All three hold. The conclusion that the exit plan has little value does not.
- Part 6What To Do, By Role
- 6.1The Greyhound CXO Runbook: Ten Moves Before The Next Renewal
Ten moves for the CIO, business applications leads, procurement, the CFO, the chief data officer, enterprise architects, and the board, each naming the assumption it corrects and who decides.
- 6.2Questions For Microsoft: What Buyers Will Ask Next
Six questions only Microsoft can answer, on price, the SAP timeline, what moves, where data sits during a move, coexistence licensing, and accountability. Each is tied to a Runbook move.
- Part 7The Final Greyhound Standpoint
- 7.1Dynamics 365 Activate: The Final Greyhound Standpoint
Microsoft sells the exit and the stay, and both end at Copilot. The exit plan is the buyer’s control. The limits of the evidence, and the signals that would change the view within twelve months.
- Part 8Appendix, Sources, And Disclosures
- 8.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.
- 8.2Sources And References: Every Document Behind Every Claim
Twenty-two sources in four classes, from Microsoft’s announcements to Salesforce’s, SAP’s, and other companies’ own statements, the media, and the research this note builds on.
- 8.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
Find your role and read its sections in the order shown. Each line takes you straight to the section.
Chief information officer
Head of business applications
Chief financial officer
Head of procurement
Enterprise architect
Chief data officer
Part Of A Larger SeriesSeries guide · AI drafted · Analyst reviewed
This research note is one of nine in Greyhound Research’s Microsoft Ignite 2026 series. The flagship note brings the series together, and each companion takes one part of what Microsoft announced. Select a title to open it in a new tab.
- FlagshipThe series in one read
- 1/Microsoft Ignite 2026 – When Agents Join The Workforce, Written Authority Becomes The Control
The series in one read. Microsoft has shipped what agents need to run, and the deciding control in every area is the authority the buyer writes down.
- CompanionsOne part of Ignite each
- 2/Microsoft Copilot As The OS For Work – When The Front Door Moves, Frontier Enrollment Becomes The Control
Copilot becomes the front door to daily work while its agents stay in Frontier, so enroll people by the data they handle.
- 3/Microsoft Agent Economics – When Work Is Billed By The Task, The Spending Policy Becomes The Control
When work is billed by the task, the bill follows behavior, and the written policy on pooling, caps and unused credits decides the cost.
- 4/Microsoft Agent Identity – When Rivals’ Agents Get A Microsoft Name, Enforcement Becomes The Control
Agent 365 can list agents built on rival platforms, but listing is not stopping, so the duty to enforce belongs in each contract.
- 5/Microsoft Azure Agent Infrastructure – When Agents Get Their Own Machines, Authority Becomes The Control
The machinery for running agents on Azure is ready to pilot. What each agent may touch, and under whose name, is still to be written.
- 6/Microsoft Confidential Computing – When Agents Work Inside The Seal, Attestation Becomes The Control
The seal keeps the cloud operator out but not the customer’s own agent, so judge offers by who checks the proof.
- 7/Microsoft Perception – When Agents Close The Alerts, The Audit Becomes The Control
Security agents that close alerts can take real load off teams, and a weekly sample of their closures is the safeguard.
- 8/Microsoft MAI Models – When The Platform Owner Ships Its Own Models, Model Choice Becomes The Control
With Microsoft now supplier, router and rival at once, keep the right to pick and pin the model, and budget on list price.
- 9/Microsoft Dynamics 365 Activate – When Leaving Gets Cheaper, The Exit Plan Becomes The Control (you are reading this note)
Activate makes it cheaper to learn what leaving involves, and a priced exit plan strengthens the hand even of companies that stay.
Part 1What Ignite Changed
What Microsoft Announced: One Exit Released, One In Private Preview, One Way To Stay
Greyhound SpotlightMicrosoft’s own partner page still called the Salesforce migration tool a limited public preview after the Book of News called it generally available.
Microsoft’s Ignite summary lists two business application moves that face in opposite directions. The first is Dynamics 365 Activate, which Microsoft calls an implementation and migration platform. Its Salesforce migration is now generally available, and its first SAP ECC steps are in private preview, a test release open only to invited customers. The second is a set of Salesforce links into Copilot, Teams, and Microsoft’s data platform, announced jointly with Salesforce.
Greyhound Research reads the release as the moment a long courtship became a product. Microsoft has pursued Salesforce and SAP customers for years with offers and partner programs, and what is different now is that the pitch comes with a released tool a buyer can run on its own estate. Greyhound Research expects a price, and possibly migration funding, to be published once the SAP steps are ready to sell, since vendors tend to set terms when a scenario is complete. The effect that is easy to miss is on paperwork. When two Microsoft pages describe one tool differently, the contract, not the web page, should record the status the buyer is paying for.
Table 1 sets each item beside its status and what Microsoft has not yet written. A pilot is a trial with a few selected customers.
Greyhound Research · Table 1 · Status ledger
One exit released, the other in private preview, and no price for either
Microsoft’s Ignite 2026 items for leaving Salesforce and SAP ECC and for staying with Salesforce, by status, November 19, 2026.
Greyhound Research’s judgment: sign only on the two released rows, and treat every preview as a roadmap until it has a price.
| Offering | Status | What Microsoft has written | Not yet written |
|---|---|---|---|
| Dynamics 365 Activate for CRM, Salesforce to Dynamics 365 | Generally available | “For CRM, the Salesforce migration experience is now generally available.”Public preview from September 9, 2026 | Price, and what converts versus what is redesigned |
| Activate for ERP, SAP ECC discovery | Private preview | Analyzes processes, configurations, customizations, and dependenciesThe Book of News says rolling out over the coming weeks | Release date, price, ECC releases and modules in scope |
| Activate for ERP, requirements, configuration, and data migration | Private preview | Carries project context from assessment through implementation | Release date, price |
| Salesforce in Copilot | Public preview | Plugin with 38+ prebuilt sales skills, under Salesforce permissions | Licensing on each side, release date |
| Sales Cloud in Teams | Pilot | Pipeline, quota, deal alerts, and briefings in TeamsOpen beta later this year | Licensing, release date |
| Data federation, OneLake into Salesforce Data 360 | Generally available | Query OneLake data from Data 360 without copying itThe reverse direction is in public preview | Licensing for queries across both platforms |
| Dynamics 365 Sales, Customer Service, and ERP apps plugins for Copilot | Generally available | More than 57 customer experience and more than 39 finance and operations skills | Context: the front door after a move |
| Entra Agent ID for agents on connected platforms | Rolling out | Agents on eleven platforms, Salesforce Agentforce and SAP among them, receive a Microsoft identityMicrosoft says the rollout completes in December | Context: Microsoft’s directory across vendors |
Table 1 lists Microsoft’s Ignite 2026 items for leaving and staying with incumbent CRM and ERP vendors by status, and shows two generally available rows that can be signed, four previews or pilots, and no published price. Generally available: Dynamics 365 Activate for CRM, which moves customers from Salesforce, and data federation from OneLake into Salesforce Data 360. Private preview: Activate for ERP, SAP ECC discovery, and requirements, configuration, and data migration, which the Book of News says is rolling out. Public preview: Salesforce in Copilot. Pilot: Sales Cloud in Teams. Context: the Dynamics 365 Sales, Customer Service, and ERP apps plugins for Copilot, generally available, and Entra Agent ID for agents on connected platforms, rolling out to December. Statuses are as Microsoft published them through November 19, 2026.
Only two rows can be signed with full terms today: the Salesforce migration and the data link from Microsoft’s data platform into Salesforce. The SAP tool, Salesforce in Copilot, and Sales Cloud in Teams are previews or pilots. Microsoft’s own pages also disagree on the SAP tool, which one calls private preview and another says is rolling out. Budgets should rest on the generally available rows until Microsoft publishes terms for the rest.
Greyhound Standpoint:
Greyhound Research judges that Ignite turned Microsoft’s long-running interest in Salesforce and SAP customers into a released product on one side and a promise on the other, and that buyers should plan on the two halves differently. The CRM tool is generally available, which means Microsoft stands behind it on its standard terms. The ERP tool is a private preview, which means its scope, timing, and price can still change before anyone should rely on it. Anyone who has followed enterprise software through several release cycles has seen previews narrow, slip, or change their licensing on the way to release, and that pattern is the reason to keep the two apart in a plan.
Microsoft deserves credit for releasing the Salesforce tool rather than announcing it again, and for labeling the SAP steps plainly as a preview. The limit is that Activate has no public documentation beyond announcements and a partner page, and two Microsoft pages disagree on the SAP tool’s status. A published price, a scope list, and one consistent status would move this reading toward full confidence.
Until then, business applications leads should treat the Salesforce tool as available and the SAP tool as a roadmap, and procurement should ask for the price, the status of each step, and the scope of what moves, in writing, at the first planning review that budgets for either.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What exactly did Microsoft announce for Activate?
The CRM half. Microsoft opened a public preview of Activate for companies moving from Salesforce on September 9, 2026. At Ignite, the Book of News says the Salesforce migration experience is generally available, and Jeff Teper, Executive Vice President of Microsoft Apps and Agents, writes the same.
The ERP half. The same post says requirements analysis, configuration, and data migration for SAP ECC are in private preview. The Book of News describes the ERP capabilities as starting to roll out on November 17 and continuing over the coming weeks. Microsoft’s partner page, read on November 18 and again on November 19, still describes a limited public preview of the Salesforce tool. In September, Teper wrote that Salesforce was the first migration scenario, with further CRM and ERP scenarios to follow.
What the partner page tells a buyer. A partner page that still says limited public preview after the Book of News says generally available is most likely a page not yet updated, not a change of plan. It still matters, because partners scope and price work from their own pages. A buyer should confirm with Microsoft and with the partner that the statement of work rests on the released product and its standard terms.
In the source’s own words
- Microsoft’s Book of News, Dynamics 365 ActivateFor CRM, the Salesforce migration experience is now generally available.Source
- Microsoft’s Book of News, Dynamics 365 Activatewhich start rolling out today and continue over the coming weeksSource
- Dynamics 365 Blog, Teper on November 17Requirements analysis, configuration, and data migration are also available in private previewSource
- Microsoft partner tools pagePartners can sign up to the limited public previewSource
- Dynamics 365 Blog, Teper on September 9Salesforce is our first migration scenario, with additional CRM and ERP migration scenarios to follow.Source
2What exactly did Microsoft and Salesforce announce together?
Three links. The joint release describes Salesforce in Copilot as a plugin in public preview with more than 38 prebuilt sales skills, says Sales Cloud in Teams is in pilot with open beta later this year, and says data federation from Microsoft OneLake into Salesforce Data 360 is generally available. Data sharing in the other direction, from Data 360 into OneLake, is in public preview.
The name. The release calls the partnership Copilotforce. Salesforce used the same pattern in August, when it announced Claudeforce with Anthropic.
In the source’s own words
- Microsoft Source, joint release, November 17Salesforce in Copilot is available in public preview (beta) beginning today.Source
- Microsoft Source, joint release, November 17Sales Cloud in Teams is in pilot with enterprise customers, with open beta coming later this year.Source
- Microsoft Source, joint release, November 17Data federation from Microsoft OneLake into Salesforce Data 360 is generally availableSource
Part 1What Ignite Changed
Two Signals At Once: Microsoft Sells The Exit And The Stay In The Same Week
Greyhound SpotlightOn the same day, Microsoft issued a joint release with Salesforce and promoted a tool for moving customers off Salesforce.
A buyer reading Ignite could take away two opposite messages. One says leave Salesforce and SAP for Microsoft’s own business software. The other says keep Salesforce and reach it through Microsoft Copilot. Both are true at once, and they are not a contradiction. Microsoft wins something either way, and the buyer’s job is to see what.
For buyers, the practical meaning is that the vendor across the table now sells both outcomes, so its account team gains whichever way the decision goes. That is a change from the classic CRM contest, in which a rival’s pitch was simply to win the record. Competing and partnering at once is old in enterprise software, from databases that ran on rivals’ hardware to applications sold through rivals’ clouds. The likely next step, in Greyhound Research’s view, is for similar pairings to appear between other assistants and other systems of record. The consequence that gets less attention is internal. Two roads invite two sponsors inside the buyer, and without one owner a company can end up funding both.
Exhibit 1 sets the three offerings against what each does to the software a company already runs. The incumbent is the vendor a company uses today. A system of record is the software that holds the official version of the data.
Greyhound Research · Exhibit 1 · Two signals, one front door
Every road keeps Copilot in front of the work
What each of Microsoft’s three Ignite 2026 business application offerings does to the CRM or ERP software a company already runs.
Greyhound Research’s judgment: the real choice is who holds the record, because Copilot takes the front door on every road.
Exhibit 1 is a matrix of five effects against three offerings, Activate for CRM, Activate for ERP, and Copilotforce, and shows that all three keep Copilot in front of the work while none has a published price. Reads and maps the incumbent estate: yes for Activate for CRM, in preview for Activate for ERP, no for Copilotforce. Moves data off the incumbent: the same. Keeps the incumbent as the system of record: only Copilotforce. Puts Copilot in front of the work: yes for both Activate offerings, through the Dynamics 365 plugins, and in preview for Copilotforce. Has a published price: not published for any of the three, shown as a tinted row. The marks are Greyhound Research analysis, not measured data.
Each road keeps Copilot in front of the work. Activate replaces the system of record with Microsoft’s, while Copilotforce leaves Salesforce’s in place and puts Copilot in front of it. None of the three has a published price. The exhibit is Greyhound Research’s reading of each company’s announcements, not a vendor claim. It shows that the choice is less between Microsoft and Salesforce than over who owns the record behind the front door.
Greyhound Standpoint:
At Greyhound Research, we believe the two signals are one strategy, and that reading them as a contradiction would lead buyers to the wrong question. Microsoft wants Copilot to be where work starts. It can get there by replacing the incumbent’s record with Dynamics 365, or by sitting in front of Salesforce’s record through Copilotforce, and it gains on either road. That is not unusual. Large platform vendors have long competed with a rival in one product line while partnering with it in another, and customers have done best when they handled each relationship on its own terms. The arrangement also reflects well on Salesforce, which keeps its record and its permissions in place while reaching users where they already work.
The consequence for buyers is that two decisions which used to travel together now come apart: which system holds the record, and which tool is the front door. Each carries its own price, its own contract, and its own exit. The reading rests on the companies’ announcements, and neither company has published prices that would show how the two roads compare in cost. The view would change if published terms tied the front door to the record, because the two choices would then travel together again.
CIOs should take the record decision and the front door decision as two separate items at the next architecture review, rather than letting one renewal settle both.
The Deeper Read · About 1 minute
Select a question to open the full answer
1How does each offering treat the incumbent?
Replace it. Microsoft describes Activate for CRM as helping customers migrate from Salesforce to Dynamics 365, and Activate for ERP as starting with SAP ECC. Both end with Dynamics 365 as the system of record, and Microsoft calls Copilot the new front door to Dynamics 365.
Sit in front of it. Under Copilotforce, Salesforce stays the system of record. The joint release says Salesforce continues to govern access and business actions, and the Book of News says sellers work within their existing Salesforce permissions.
In the source’s own words
- Dynamics 365 Blog, Teper on November 17We began with Dynamics 365 Activate for CRM (generally available), helping customers migrate from Salesforce to Dynamics 365.Source
- Dynamics 365 Blog, Teper on November 17Copilot is the new front door to Dynamics 365 and plugins make Copilot work for your business.Source
- Microsoft Source, joint release, November 17Salesforce continues to govern access and business actionsSource
2Does Microsoft also help customers keep SAP?
Yes, on Azure. The Book of News lists Azure Workload Center, in preview, to extend agentic operations to Oracle and SAP. SAP names Microsoft among the partners for agent-to-agent links between Joule, SAP’s assistant, and outside agent frameworks. Microsoft offers agentic operations for SAP on Azure to some customers and a way off SAP to others.
What the hedge tells a buyer. Microsoft offers SAP customers a way to run on Azure and a way to leave, and offers Salesforce customers a way to stay and a way out. A vendor that sells every road is signaling that the road itself is open to negotiation. The buyer’s leverage lies in deciding which road it is on before the account team proposes one.
Part 2The Exit
Activate For CRM: Leaving Salesforce Now Starts With A Report
Greyhound SpotlightMicrosoft has not published a price for Activate in any document read for this note.
Moving a company off one CRM onto another has usually started with months of discovery. Consultants list every data object, custom field, workflow, and connection before anyone can say what the move will cost. Activate does that first pass with AI agents and hands the result to the project team. The output is a report on the company’s own estate, and that report has value of its own.
What is new is who pays for the first look. Discovery has usually been sold as the opening phase of a migration contract, so a company had to half commit before it could see the cost. A tool from the destination vendor moves that look earlier, to the point where a buyer is still deciding. Greyhound Research anticipates that other application vendors will answer with assessment tools of their own, since none will want a rival to hold the only map of its customers’ estates. A less obvious effect falls on partners. If the first pass is automated, partner value shifts toward judgment and redesign, and statements of work should be priced that way.
Exhibit 2 follows Activate’s steps from reading the Salesforce estate to proving the move worked, and marks which ones Microsoft has written down. Configuration means setting up the new system’s options and rules.
Greyhound Research · Exhibit 2 · The path of a Salesforce move
Microsoft has written the first steps and left out the proof
Five steps of a move from Salesforce to Dynamics 365 with Activate, read against Microsoft’s announcements, November 19, 2026.
Use the discovery now. Do not sign off a move until the buyer holds its own proof that nothing was lost.
Exhibit 2 sets out five steps of a move from Salesforce to Dynamics 365 with Activate as a numbered list, and shows that Microsoft has written the first three, part of the fourth, and not the fifth. Step one, discover, is written: Activate profiles data, maps dependencies, and flags customizations. Step two, recommend, is written. Step three, configure and move, is written as automated migration with built-in guardrails in a Microsoft-hosted experience. Step four, validate, is partly written, as validation by implementation project teams without stated criteria. Step five, reconcile and price, is not written in any document read. The steps and grades are Greyhound Research analysis.
Microsoft has written the first steps clearly. The tool reads the estate, recommends what to keep or change, and runs the move with what it calls built-in guardrails. People on the project check the work. The last step is missing from every document read. No Microsoft page says how a buyer proves that records, rules, and history arrived intact, or what the tool costs.
Greyhound Standpoint:
Greyhound Research holds that the discovery report is the most valuable thing Activate produces, and that buyers should commission one whether or not they intend to move. The reason is economic. The first months of a CRM project have usually gone to consultants listing objects, fields, workflows, and integrations, and that cost has kept many companies from pricing an alternative at all. A tool that does the first pass at lower cost turns an expensive question into an affordable one. The migration itself deserves more caution. A familiar pattern from the move of customer software to the cloud is that record counts reconciled at go-live while reports, approvals, and integrations revealed gaps weeks later.
Microsoft deserves credit for writing the early steps clearly and for keeping people on the project in the review. What its documents do not yet show is how a buyer proves that records, rules, and history arrived intact, or what the tool costs. A vendor-built assessment also reflects its maker’s view of the destination, so a second reviewer who does not sell Dynamics 365 is a sensible check. A published reconciliation method would strengthen the case for the move itself.
Business applications leads should require a written reconciliation of every record and rule before signing off any move, and should treat the stated guardrails as a claim to test at the pilot gate.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What does Activate do, step by step?
Discovery and recommendations. Microsoft’s September post says Activate analyzes an existing Salesforce CRM environment, profiles data and entities, maps relationships and dependencies, and flags customizations that need attention. It then helps teams decide what to preserve, simplify, or redesign.
The move. The same post describes automated migration execution with built-in guardrails in a Microsoft-hosted experience. The Book of News says Activate is built on Success by Design, Microsoft’s implementation method, and that project context carries forward from assessment through implementation.
In the source’s own words
- Dynamics 365 Blog, Teper on September 9It will analyze an existing Salesforce CRM environmentSource
- Dynamics 365 Blog, Teper on September 9automated migration execution with built-in guardrailsSource
- Microsoft’s Book of News, Dynamics 365 ActivateDynamics 365 Activate is built on Success by Design, Microsoft's implementation methodology.Source
2What does a named customer credit?
The discovery. Microsoft’s September post says Comcast wanted to accelerate its migration assessment and gain a clearer view of its Salesforce landscape. Sathish Arumugam, Manager, Software Dev and Engineering at Comcast, credits the discovery capabilities with greater visibility into that landscape and with more informed planning decisions. The quote speaks to the assessment and the plan, not to a completed move, which is the part of Activate this note values most.
What a discovery quote tells a buyer. The named customer credits visibility and planning, which is the part of Activate a buyer can test without committing to a move. The quote says nothing yet about cost, duration, or what arrived intact. A buyer should read the reference the same way, as evidence that the discovery is in use at a large company, and ask for a reference that has completed a move before relying on the migration itself.
In the source’s own words
3Who checks the work?
People, by Microsoft’s account. Teper’s Ignite post says Activate brings agentic capabilities to the work, with validation by implementation project teams. A partner quoted in September says its approach is human-led and AI-accelerated. Greyhound Research’s October note on Oracle’s agentic implementation held that the person who signs off agent-drafted configuration is signing off authority, and the same applies here.
In the source’s own words
- Dynamics 365 Blog, Teper on November 17Activate brings agentic capabilities to that work, with validation by implementation project teams.Source
- Dynamics 365 Blog, partner quote, September 9Human-led, AI-accelerated is core to how we operate at congruentX.Source
- Greyhound Research, Oracle agentic implementation notethe person who signs off the configuration is signing off the authoritySource
Part 2The Exit
The SAP ECC Clock: A Private Preview Against A 2027 Deadline
Greyhound SpotlightSAP’s option to run ECC until 2033 is not a later deadline for everyone. SAP calls it not a prolongation, and ties it to a move under RISE with SAP.
SAP ECC runs finance, supply chain, and manufacturing for many of the world’s large companies. SAP has said since 2020 that mainstream maintenance, its standard support and updates, ends for ECC’s current releases at the end of 2027. After that, customers can pay for extended maintenance to the end of 2030. SAP wants them to move to S/4HANA, its newer system, and offers its own tools to help.
For most ECC customers the clock matters more than the tool. End-of-support dates have long shaped ERP spending, and the familiar pattern is a late rush in which partner capacity, not software, sets the pace and the price. A second destination with an agent-assisted path could ease some of that pressure, though only once it leaves preview. Greyhound Research expects demand for experienced ECC teams to tighten as 2027 approaches, whichever destination companies choose. The point that tends to be overlooked is that the decision and the move are separate events. A company can settle its destination this year and still need the paid years after 2027 to finish the work.
Exhibit 3 sets SAP’s dates and Microsoft’s Activate steps on one calendar, from SAP’s 2020 decision to the end of its narrow 2033 option. Extended maintenance is paid support after standard support ends.
Greyhound Research · Exhibit 3 · The SAP ECC clock
Microsoft’s ECC tool arrives a year before the first deadline
SAP’s maintenance dates for SAP ECC and Microsoft’s Activate steps, on one calendar, 2020 to 2033.
Too late to finish a move before 2027, early enough to price the choice. Use it to decide, not yet to migrate.
Exhibit 3 places SAP’s ECC dates and Microsoft’s Activate steps on a grid of years from 2020 to 2033, and shows Microsoft’s ECC tool reaching private preview in November 2026, a year before the end of 2027. In 2020 SAP set the end of 2027 for mainstream maintenance and the end of 2030 for extended maintenance. In 2024 SAP committed to S/4HANA until 2040. In 2025 it added a transition option for 2031 to 2033 for RISE with SAP customers. In 2026 SAP introduced agent-led migration tooling in May, Microsoft opened Activate for CRM in September, and Activate for SAP ECC reached private preview in November. Mainstream maintenance ends in 2027, extended maintenance in 2030, and the transition option runs from 2031 to 2033 on conditions. Years without an event are marked quiet.
The calendar is tight for anyone moving off ECC to Microsoft. Microsoft’s tool reached private preview in November 2026, a little over a year before mainstream maintenance ends. Microsoft’s own partner puts a typical CRM move at 12 to 18 months, and a large finance system is rarely simpler, so the tool cannot carry a full move before the 2027 date. It can help a company decide where to go, and price the choice. The dates after 2027 give more time, at a price and on SAP’s conditions. Greyhound Research said in January 2026, of an earlier short SAP extension, that “This is a transition period, not a reprieve,” and that reading holds for ECC’s later dates too.
Greyhound Standpoint:
Greyhound Research’s reading is that Activate for ERP arrives too close to the end of 2027 to carry a full move off ECC before that date, and early enough to shape the decision about where to go. Large ERP moves take years rather than quarters, and a preview opened a little over a year before mainstream maintenance ends does not change that. SAP deserves a fair hearing. It has stated its ECC dates in public since 2020, offers paid extended maintenance to the end of 2030, has committed to S/4HANA until 2040, and offers its own migration tooling. Those are real options, and for many companies staying with SAP will be the sound choice.
The 2031 to 2033 option is narrower, tied to RISE with SAP and a move to SAP ERP, private edition, and SAP itself says it is not a prolongation. The longer view is that end-of-support dates in enterprise software have tended to arrive with paid extensions and a range of support options rather than a single cliff, and buyers who priced every path early have negotiated from a stronger position. The evidence limit is that Microsoft’s ECC scope is unpublished. A dated general availability and a module list would raise the tool’s weight.
CFOs and CIOs should price three paths side by side before the 2027 budget is set: extended maintenance on ECC, S/4HANA with SAP, and Dynamics 365, with any preview date in writing.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What exactly has SAP said about ECC dates?
2027 and 2030. SAP’s October 2024 post gives the end of 2027 for mainstream maintenance of the latest three enhancement packages of the Business Suite 7 core applications and 2030 for the extended maintenance option, and commits to S/4HANA until 2040. SAP said in January 2025 that the dates are the end of 2027 for SAP Business Suite 7 and the end of 2030 for extended maintenance.
2031 to 2033. SAP’s February 2025 post, updated in March 2025, describes a transition option active from 2031 to 2033, designed for large customers with complex installations on a RISE with SAP journey. Systems must be moved to SAP ERP, private edition, before the end of 2030, and SAP HANA is the only supported database. The post says this is not a maintenance prolongation of SAP ERP, and SAP said in January 2025 that the option is not a prolongation of the 2020 deadlines.
What the wording tells a buyer. SAP has said in two places that the later option is not a prolongation. That is a careful choice of words, and a buyer should take it at face value. The option is a conversion path with conditions, a move under RISE with SAP and a single supported database, not extra time on today’s system. A plan that counts on 2033 should start from those conditions.
In the source’s own words
- SAP News Center, October 30, 20242030 for the extended maintenance optionSource
- SAP spokesperson, January 28, 2025the end of 2027 for SAP Business Suite 7 and the end of 2030 for extended maintenance.Source
- SAP spokesperson, January 28, 2025not a prolongation of the mainstream maintenance deadlines communicated in 2020.Source
- SAP News Center, February 4, 2025, updated March 7, 2025need to be moved to SAP ERP, private edition prior to the end of 2030Source
- SAP News Center, February 4, 2025, updated March 7, 2025this is not a maintenance prolongation of SAP ERPSource
- SAP News Center, October 30, 2024SAP also announced a commitment to SAP S/4HANA until 2040.Source
2What do Microsoft and SAP each offer ECC customers?
Microsoft’s tool. The Book of News says SAP ECC discovery will identify migration complexity, potential gaps, and areas that need further evaluation. Teper ties the launch to SAP ECC approaching the end of mainstream maintenance.
SAP’s own tool. In May 2026 SAP introduced agent-led transformation tooling that it says can reduce ERP migration effort by more than 35 percent, and said ECC customers are not excluded from select AI scenarios if they commit to moving most of their landscape to SAP Cloud ERP. Both claims are SAP’s own, without a published method.
In the source’s own words
- Microsoft’s Book of News, Dynamics 365 ActivateIt will identify migration complexity, potential gaps and areas that need further evaluationSource
- SAP News Center, May 12, 2026SAP also introduced new agent-led transformation tooling that can reduce ERP migration efforts by more than 35 percentSource
- SAP News Center, May 12, 2026transitioning the majority of their current landscape to SAP Cloud ERPSource
Part 2The Exit
Data And Process Fidelity: Records Move, Logic Is Rebuilt
Greyhound SpotlightMicrosoft’s own words for customized software are “move, simplify, or redesign.” Only the first of the three is a migration.
Fidelity is whether the new system does what the old one did, with the same data. Records such as accounts, contacts, and invoices can be copied. The rules around them cannot. Custom fields, automated workflows, approval chains, and code written for one vendor’s platform have to be rebuilt in the other’s. That is where migrations run late and where business users notice what went missing.
This is where the budget is decided. A migration plan that counts records looks complete well before the work is understood, because records are the easiest layer to measure. Earlier waves of consolidation, from mainframes to client-server and from on-premises software to the cloud, each showed that the rules hidden in workflows and custom code took longest to surface. Greyhound Research’s expectation is that migration tools will grow better at reading that logic before they grow better at rebuilding it. The second-order effect concerns knowledge. Many custom rules were written by people who have since moved on, so a migration is also the moment a company learns which of its own rules it no longer understands.
Exhibit 4 follows the layers of a CRM or ERP estate, from data records to history and audit trails, and marks where Microsoft’s announcements place Activate. An audit trail is the record of who changed what, and when.
Greyhound Research · Exhibit 4 · What moves and what is rebuilt
Records move, and the logic around them is rebuilt
The layers of a CRM or ERP estate, marked by what Microsoft’s announcements say Activate moves, November 19, 2026.
Budget for the logic, not the records. The rebuild, not the data load, decides what a move costs.
Exhibit 4 follows the layers of a CRM or ERP estate along a bar from data to logic and history, in six layers: data records, objects and configuration, customizations and code, integrations, workflows and business processes, and history and audit trail. A marker labeled what moves sits at the end of the first two layers, which Microsoft says Activate moves. Customizations, integrations, and workflows are marked as decided case by case, since Microsoft says organizations must decide what to move, simplify, or redesign. History and audit trail are marked not stated. A strip beneath groups the layers into four. Not stated is not the same as not handled. The mapping is Greyhound Research analysis.
Microsoft says Activate reads the whole estate and moves data. For customizations, integrations, and business processes, its own Ignite post leaves the choice to the project: move, simplify, or redesign. History and audit trails are not mentioned in any document read. Not stated is not the same as not handled. A buyer should still assume that the logic of the old system will be rebuilt, and test it.
Greyhound Standpoint:
Greyhound Research’s position is that a migration’s speed is set by its data and its cost by its logic. Activate will make the first faster. The second remains a design project, and Microsoft’s own wording, move, simplify, or redesign, says as much. The mechanism is plain. Records are standard objects that a tool can map and copy. Workflows, approval chains, and custom code record how one company chose to work on one vendor’s platform, and each rule has to be understood before it can be rebuilt or retired. That is where budgets drift, because the rebuild can be sized only after the discovery has been read.
Consolidation cycles over three decades show a consistent shape, in which the data moves in weeks and the business logic takes most of the year. There is also an upside. A forced review of customizations is a rare chance to retire rules that no longer earn their cost, and a cleaner estate is worth having on any platform, including the one the company already runs. The limit is that Microsoft has not said how history and audit trails are carried, and not stated is not the same as not handled. Published conversion scope would change the estimate.
Business applications leads should classify every customization as move, simplify, redesign, or retire, and reconcile a sample of records, workflows, and history on real data at the pilot gate, before any timeline is committed.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What does Microsoft say moves, and what is decided?
Moves. The Book of News says data migration will help move data from existing systems into Dynamics 365. Microsoft’s September post says Activate processed over six billion data records in early customer engagements, a company figure without a stated accuracy rate.
Decided. For ERP, Teper’s Ignite post says that as SAP ECC approaches the end of mainstream maintenance, organizations must decide which customizations, integrations, and business processes to move, simplify, or redesign. The image description on the September post names Salesforce objects, workflows, code, and integrations among the things Activate assesses.
What volume without accuracy tells a buyer. Six billion records shows the tool has run on large estates. It does not show how many records arrived unchanged, or how many rules came with them. The wording that follows, move, simplify, or redesign, is the more useful line for a budget, because it says where the decisions and the cost will sit.
In the source’s own words
- Microsoft’s Book of News, Dynamics 365 ActivateData migration will help move data from existing systems into Dynamics 365.Source
- Dynamics 365 Blog, Teper on September 9processed over six billion data recordsSource
- Dynamics 365 Blog, Teper on November 17As SAP ECC approaches the end of mainstream maintenance, organizations must decide which customizations, integrations, and business processes to move, simplify, or redesign.Source
2Why does the governance of data matter in a move?
Concentration risk. Greyhound Research’s May 2025 note on Salesforce’s Informatica deal cited Greyhound CIO Pulse 2025, in which 58% of enterprise technology leaders globally classify vendor concentration of data governance capabilities as a Tier-1 architectural risk when building their AI platforms. A migration moves that concentration from one vendor to another unless the buyer keeps the data rules in its own hands.
Lock-in, measured. Greyhound Research said in December 2025 that Salesforce customers face “behavioral lock in created by layered dependency over time,” not technical lock-in where migration is impossible. That view stands. What has changed since is the cost of measuring the dependency: Activate lowers the cost of mapping it, while the rebuild the map reveals is as large as before. The title of this note means exactly that, and no more. Leaving gets cheaper to price, not cheap to do.
In the source’s own words
- Greyhound Research, Salesforce and Informatica note58% of enterprise technology leaders globally now classify ‘vendor concentration of data governance capabilities’ as a Tier-1 architectural risk when building their AI platformsSource
Part 3The Stay
Copilotforce: Staying With Salesforce, Inside Microsoft’s Front Door
Greyhound SpotlightSalesforce built the same arrangement with Anthropic in August, as Salesforce in Claude. Greyhound Research reads that as a plan to sit inside every assistant.
For companies that stay with Salesforce, Copilotforce brings Salesforce into the tools staff already use. A seller can ask Copilot about an account, see Salesforce data beside their email and meetings, and update a record without opening Salesforce. Data can also be read across Microsoft’s and Salesforce’s data platforms without copying it, which the companies call zero copy.
The arrangement reflects a change in how integrations reach the buyer. Connecting two vendors’ products used to be a customer project, built by a partner and owned by the buyer. Here the two vendors have built the link themselves and announced it jointly, which shortens the work and also places part of the governance with them. In Greyhound Research’s view, the commercial terms, more than the technology, are likely to decide how widely it is used once it leaves preview. Less visible is the effect on data agreements. Reading data across two platforms without copying it is cleaner, but each query then crosses two sets of terms, and the buyer’s agreements should name both.
Table 2 sets out who governs each part of the arrangement, according to the companies’ own announcements. Writeback means an action that changes a record in Salesforce.
Greyhound Research · Table 2 · Coexistence ledger
The access rules are written, and the money and the blame are not
Who governs each part of Salesforce in Copilot and the Microsoft and Salesforce links, as the two companies announced them, November 19, 2026.
Sound access design, with the money and the blame unwritten. Settle who pays and who answers before the pilot widens.
| Part of the arrangement | Who governs it | What is written | Status |
|---|---|---|---|
| What a seller can see in Salesforce | Salesforce | “within their existing Salesforce permissions” | Written |
| Updates made from Copilot | Salesforce, with the user | Salesforce governs actions, and each update needs explicit user confirmation | Written |
| Context from Teams, Outlook, and documents | Microsoft | Work IQ adds context under Microsoft’s compliance controls | Written |
| Regions and customer access | Each customer’s agreements | Governed by applicable customer agreements | Partly written |
| Identity of agents on connected platforms | Microsoft Entra | Agents on eleven platforms, Salesforce Agentforce and SAP among them, receive an Entra Agent ID, rolling out to December | Rolling out |
| Licenses needed on each side | Not stated | Neither company says what a seller needs | Not written |
| Who answers for a wrong update | Not stated | No joint term on writeback errors | Not written |
Table 2 lists seven parts of the Copilotforce arrangement, who governs each, and what is written, and shows that access rules are written while licensing and accountability for a wrong update are not. Salesforce governs what a seller can see, under existing Salesforce permissions. Updates made from Copilot are governed by Salesforce and need explicit user confirmation. Context from Teams, Outlook, and documents is governed by Microsoft. Regions and customer access are left to each customer’s agreements. Identity for agents on connected platforms comes from Microsoft Entra, rolling out to December. The licenses needed on each side and who answers for a wrong update are not written. The grading is Greyhound Research’s reading of the two companies’ announcements.
The access rules are clear. Salesforce decides what each user can see and do, and every update needs the user to confirm it. What is missing is commercial and legal. Neither company says which licenses a seller needs on each side, or who is accountable when an update goes wrong. The arrangement also sits inside preview terms, and regional access is left to each customer’s agreements.
Greyhound Standpoint:
Greyhound Research’s judgment is that Copilotforce is good news for Salesforce customers whose staff work mainly in Microsoft’s tools, and that its full cost is not yet visible. The design deserves credit on both sides. Salesforce keeps its own permissions and remains the system of record, every update needs a person to confirm it, and data can be read across the two platforms without being copied. That is what buyers have asked of integrations for decades: reach without a second copy of the truth. The open question is commercial. When two vendors share a user, each has a license to sell, and experience with suite integrations suggests the combined price is often settled after the pilot, once use has already grown.
A seller who carries Copilot and Salesforce licenses for the same work could be paid for twice, and neither company has yet said what a seller needs on each side or who answers when an update goes wrong. Salesforce’s parallel arrangement with Anthropic is a fair sign that it intends to give customers a choice of assistant rather than tie them to one. The arrangement is in preview, so its terms may change, and published licensing at general availability would settle the main question.
Procurement should ask both companies, in writing, for the combined price per seller at general availability, and business applications leads should pilot with a defined group and measure use before the rollout decision.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What exactly does Copilotforce do?
In Copilot. The Book of News says users can retrieve customer information and take supported actions within their existing Salesforce permissions, with Work IQ adding relevant context from Teams meetings, Outlook emails, and documents. The joint release says supported writeback actions require explicit user confirmation.
In Teams and the data platforms. Sales Cloud in Teams shows pipeline and quota progress, deal notifications, and briefing materials. Data federation lets joint customers query OneLake data from Data 360 while leaving the source data in Fabric, Microsoft’s data platform.
The first large user. The joint release names Accenture as design and implementation partner and as pilot customer, deploying the integrations in its own global sales organization. The release describes Accenture as one of the largest Salesforce users, with 55,000 users, and says it has scaled Copilot to more than 740,000 people. Julie Sweet, Chair and Chief Executive Officer of Accenture, said the company will serve as customer zero for Copilotforce. A firm that already pays for both products at that scale is the natural first test of what a seller needs on each side.
What customer zero tells a buyer. A pilot inside a firm that is the design partner, a large Salesforce user, and a large Copilot user is a strong test of the technology and a limited guide to what a typical buyer will pay. Few buyers will have its terms. The lessons worth asking for are about writeback, permissions, and seat use, more than about price.
In the source’s own words
- Microsoft’s Book of News, Salesforce in Copilotwithin their existing Salesforce permissionsSource
- Microsoft’s Book of News, Salesforce in CopilotWork IQ adding relevant context from Teams meetings, Outlook emails and documentsSource
- Microsoft Source, joint release, November 17require explicit user confirmationSource
- Microsoft Source, joint release, November 17Regional availability and customer access are governed by applicable customer agreements.Source
- Microsoft Source, joint release, November 17and as one of the largest Salesforce users globally with 55,000 usersSource
2What does each company say it gets?
In their own words. Judson Althoff, Chief Executive Officer of Microsoft’s commercial business, said AI is only as powerful as the data and context that grounds it. Miguel Milano, President and Chief Operating Officer of Salesforce, said the companies are turning AI from a standalone tool into a driver of productivity. Each statement is its company’s claim.
Salesforce’s pattern. In August 2026 Salesforce and Anthropic announced Claudeforce, with Salesforce in Claude open to select pilot customers and Claude available in Agentforce, Salesforce’s agent platform. Marc Benioff, Salesforce’s Chair and Chief Executive Officer, said: “This is how every business will run.” On September 15, Anthropic released Salesforce in Claude in beta on all paid Claude plans, so the Claude road is a step further along than the Copilot road, which opened in public preview at Ignite.
In the source’s own words
- Microsoft Source, joint release, Althoff of MicrosoftAI is only as powerful as the data and context that grounds itSource
- Microsoft Source, joint release, Milano of Salesforcewe're transforming AI from a standalone tool into a powerful driver of productivitySource
- Salesforce Newsroom, August 26, 2026Claude is available in AgentforceSource
- Anthropic, September 15, 2026Salesforce in Claude is available in beta on all paid Claude plansSource
Part 3The Stay
The Front Door: Both Doors Lead To Copilot
Greyhound SpotlightMicrosoft calls Copilot “the new front door to Dynamics 365.” Copilotforce puts the same door in front of Salesforce.
The front door is the screen where a person starts their work. For years, the CRM was its own front door: sellers logged into Salesforce or Dynamics to see their accounts. Assistants change that. If a seller asks Copilot, Claude, or Agentforce, the assistant becomes the front door and the CRM becomes the record behind it. Ignite shows Microsoft taking that door on both roads.
In practice, the screen staff open first may soon matter as much in a renewal as the system that holds the data. Seat counts, training, and support have tended to follow the application people log into, and an assistant in front of the CRM moves that center of gravity. Greyhound Research would expect vendors to compete harder on the entry point over the next renewal cycles, with bundles that pair the assistant and the record. One knock-on effect is on measurement. When work starts in an assistant, the CRM’s own usage reports may undercount what sellers do, and license reviews built on those reports could cut or keep the wrong seats.
Exhibit 5 sets the two roads side by side, with what stays the same either way. An agent identity is the account an AI agent uses to sign in and act.
Greyhound Research · Exhibit 5 · Two roads to one front door
Leave or stay, Copilot is where work starts
The exit road and the stay road offered at Ignite 2026, set side by side with what stays the same on both, November 19, 2026.
Microsoft takes the door either way. Choose the record on its merits, and license the door once.
Exhibit 5 sets the two roads offered at Ignite 2026 side by side in three cards. If the company leaves, through Activate, Dynamics 365 replaces Salesforce or SAP ECC as the record, Copilot is the front door through the Dynamics 365 plugins, and no price is published. If the company stays, through Copilotforce, Salesforce keeps the record under its own permissions, Copilot and Teams become the front door with Salesforce inside, and licensing on each side is not stated. Either way, Copilot is where work starts, Microsoft Entra issues identities to agents on connected platforms, and the rules and processes still need owners. The grouping is Greyhound Research analysis.
On the exit road, Microsoft holds both the front door and the record. On the stay road, it holds the front door and Salesforce keeps the record. Either way, Microsoft’s directory is starting to issue identities to agents built on other vendors’ platforms, Salesforce’s and SAP’s among them. A companion Greyhound Research note on Azure agent infrastructure holds that what each agent may read, change, and spend is the control, and that identity is where it is enforced. The buyer’s choice is about the record, the price, and the rules. The front door goes to Microsoft either way.
Greyhound Standpoint:
Greyhound Research concludes that the contest in business applications has widened from the record to the front door, and that Microsoft starts ahead on the door because most office staff work in its tools. The shift is familiar. The browser, the portal, and the mobile app each changed where work started, and each time the vendors behind the screen had to decide whether to own the entry point or be reached through someone else’s. Salesforce’s answer serves its customers well: sit inside every assistant, Copilot and Claude alike, and keep the record and the permissions. That keeps a Salesforce customer’s choice of assistant open.
Microsoft’s answer is to make Copilot the entry point on both roads and to issue identities to agents built on other platforms. The consequence for the buyer is that control now sits in two places, the assistant that frames the request and the system of record that enforces the answer, and the companion note on Azure agent infrastructure places that enforcement in identity. The limit is that no company has published usage data for these assistants in sales work, so Microsoft’s lead is a reading of reach, not of results. Evidence that sellers keep starting their day in the CRM would weaken this view.
CIOs should choose the front door on purpose at the next architecture review: decide which assistant staff start from, license it once, and keep each system of record’s permissions behind it.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1How does Microsoft describe Copilot’s role?
The front door. Teper writes that Copilot is the new front door to Dynamics 365. Microsoft’s Sales, Customer Service, and ERP apps plugins for Copilot are generally available, with more than 57 business skills for customer experience and more than 39 for finance and operations, by Microsoft’s count. On the stay road, Salesforce in Copilot starts in preview with more than 38 prebuilt sales skills, so at launch Microsoft’s own door is the more complete of the two.
A customer at the door. Manish Mittal, Senior Vice President and Global Technology Head for Value-Added Services at Visa, is quoted by Microsoft on building on Dynamics 365 in customer service as Visa expands into sales with Copilot. Visa is not described as an Activate customer. Its quote shows the door in use on Microsoft’s own record.
Agents from other vendors. Microsoft’s Agent 365 post says connected agents now automatically receive a Microsoft Entra Agent ID, with support rolling out across eleven platforms, Salesforce Agentforce and SAP among them, to complete in December.
What the skill counts tell a buyer. By Microsoft’s count, its own plugins carry more skills at launch than the Salesforce plugin, which suggests the door is more finished on Microsoft’s own record. Skill counts measure breadth, not depth or use. A pilot that times common seller tasks on each road would tell a buyer more than the counts do.
In the source’s own words
- Microsoft Community Hub, Agent 365 at Ignite 2026Connected agents now automatically receive a Microsoft Entra Agent IDSource
- Microsoft Community Hub, Agent 365 at Ignite 2026Support is rolling out across Salesforce Agentforce, Amazon AgentCore, Google Vertex AISource
- Dynamics 365 Blog, Mittal of Visa, November 17At Visa, we're building on our success with Dynamics 365 in customer service as we expand into sales with Copilot.Source
2Has Greyhound Research seen this pattern before?
Oracle’s version. Greyhound Research’s November 5 note on the front door race read OpenAI’s ChatGPT becoming a front door to Oracle Fusion, and advised buyers to plan on what is live and get the status, price, and region of the rest in writing. The same rule applies to Copilotforce.
The record still matters. In July 2025 Greyhound Research wrote that the rhetoric of AI agents replacing apps is premature, because core systems such as ERP and CRM still perform irreplaceable data integrity and compliance functions. This note keeps that view. The front door moves to the assistant, and the system of record still decides what each user may see and change.
Part 4The Money
Renewal Leverage: The Discovery Report Is The Bargaining Chip
Greyhound SpotlightThe discovery report is worth having even if the company does not move.
Renewals are negotiations about the cost of leaving. A vendor that knows a customer cannot leave has little reason to move on price. A customer with a documented, priced plan for leaving has a credible alternative, which is a strong card in any renewal. Until now, building that plan cost months of consulting. Activate lowers that cost for Salesforce customers today, and for SAP ECC customers once its preview opens.
What changes is the cost of credibility. Buyers have long known that a real alternative improves a renewal, but building one cost enough that many companies negotiated on assumption instead. A cheaper discovery lets more companies bring evidence to the table, and Greyhound Research expects incumbents to answer with earlier renewal offers and longer price holds, as they tend to when switching becomes easier to cost. The effect most coverage misses is timing. A report run a few weeks before a renewal deadline arrives too late to change the terms, so the value lies in running it a renewal cycle ahead and refreshing it before each negotiation.
Table 3 sets out each renewal a buyer faces, what Ignite gives the buyer, what the vendor is likely to answer with, and what to get in writing. Each vendor’s position is its own claim.
Greyhound Research · Table 3 · Renewal leverage ledger
One discovery report strengthens four negotiations
The renewals and contracts a buyer faces after Ignite 2026, with what the buyer gains, each vendor’s likely answer, and the terms to secure.
One report, four negotiations. Commission it a renewal cycle ahead, and keep it in the company’s hands.
| Negotiation | What Ignite gives the buyer | What the vendor will say (its claim) | What to get in writing |
|---|---|---|---|
| Salesforce CRM renewal | A released, Microsoft-hosted map of the Salesforce estate, and a priced alternative | Staying is easier: Salesforce now sits inside Copilot and Claude | Data export terms, a price hold, exit support, and seat counts matched to use through Copilot |
| SAP ECC decision | A second destination to price, once the ECC preview opens | S/4HANA until 2040, its own agent-led tooling, and the 2033 option for RISE customers | Each path’s dates and costs in SAP’s own words |
| Microsoft renewal | Two roads, both ending at Copilot | Speed claims: five months for 20,000 users, 25% faster finance setup | Activate’s price, migration funding, data handling, and Copilotforce licensing |
| Implementation partner contract | A discovery that once took months, produced faster | Partner speed claims, and the partner’s method | Who owns the discovery output, and who keeps the time saved |
Table 3 lists four negotiations a buyer faces after Ignite 2026 and shows that one discovery report strengthens all four. In the Salesforce renewal, the buyer gains a map of the estate and a priced alternative, Salesforce will say staying is easier now that it sits inside Copilot and Claude, and the buyer should get data export terms, a price hold, exit support, and seat counts matched to use through Copilot in writing. In the SAP ECC decision, the buyer gains a second destination, SAP will point to S/4HANA until 2040, its own tooling, and the 2033 option, and the buyer should get each path’s dates and costs in writing. In the Microsoft renewal, the buyer gains two roads, Microsoft will cite speed claims, and the buyer should get Activate’s price, funding, data handling, and Copilotforce licensing in writing. In the partner contract, the buyer should settle ownership of the discovery output and of the time saved. The reading is Greyhound Research analysis.
The same report helps in every row. It gives the Salesforce renewal a priced alternative and the SAP decision a second destination. In the Microsoft renewal, it gives the buyer a basis for asking what Microsoft will fund. Each vendor has an answer. Salesforce now sits inside Copilot, SAP has its own migration tools and dates, and Microsoft has speed claims. The buyer who holds the report can test each answer against its own estate. Copilotforce adds one more item to the Salesforce renewal: where sellers do most of their work through Copilot, the number and tier of Salesforce seats are worth checking against actual use.
Greyhound Standpoint:
Greyhound Research’s position is that when leaving gets cheaper, the exit plan becomes the control. Renewals are priced against the cost of leaving, and for most CRM and ERP customers that cost has been large, unknown, and therefore easy for an incumbent to discount. A plan with a scope, a price, and a tested sample turns an assumed cost into a measured one, and that changes the terms of every renewal, whichever way the decision goes. The outsourcing waves taught the same lesson, when buyers who had written and priced an exit could renegotiate and buyers who held only an exit clause found it much harder. Each incumbent also has a fair answer.
Salesforce can point to Copilotforce and Claudeforce as evidence that staying no longer limits the choice of assistant. SAP can point to its published dates, its 2040 commitment, and its own tooling. Microsoft can point to its speed claims. A buyer holding its own discovery can test each answer against its own estate. The limit is that no vendor publishes how it prices renewals, so the effect of a plan on a given offer cannot be measured in advance. An exit plan held only by a partner or a vendor is weaker leverage, because the other side knows who controls it.
Procurement and CFOs should commission the discovery before the next Salesforce renewal or SAP decision, and write ownership of the output into the partner contract.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What will each vendor say?
Salesforce. Salesforce’s answer is to make staying easier. It sits inside Copilot through Copilotforce and inside Claude through Claudeforce, so a customer can change its front door without changing its CRM.
SAP. SAP’s answer is time and tools. It has committed to S/4HANA until 2040, offers extended maintenance to 2030 and a transition option to 2033 for RISE customers, and claims its own agent-led tooling cuts migration effort by more than 35 percent. Christian Klein, SAP’s CEO, said in January 2025: “We don’t want to leave the customers behind.”
What the incumbents’ answers tell a buyer. Each answer is a reason to stay, and each has a price. Salesforce’s place inside two assistants may change which seats a seller needs, and SAP’s later dates come with paid maintenance or a move under RISE with SAP. A buyer who maps each answer to a line in the renewal offer can see which reasons cost money and which do not.
2What has Greyhound Research said about leverage before?
Bundles reduce it. In July 2025 Greyhound Research wrote that folding agents into higher-tier Copilot plans makes each feature’s value hard to judge, and that renegotiation leverage is then materially diminished.
Exit ramps restore it. In May 2025, on Salesforce’s Informatica deal, Greyhound Research advised customers to write exit ramps into multi-year deals, with pricing freezes, migration assistance, and clear licensing transition paths. This note takes the same position one step further: a priced exit plan is what gives those clauses weight. The companion note on Azure agent infrastructure held that committing to one platform is defensible when the way out is in the contract.
In the source’s own words
- Greyhound Research, Copilot agents note, July 14, 2025At that point, renegotiation leverage is materially diminished.Source
- Greyhound Research, Salesforce and Informatica note, May 28, 2025writing exit ramps into multi-year deals: pricing freezes, migration assistance, and clear licensing transition pathsSource
Part 4The Money
The Speed Claims: Five Months Is One Customer’s Forecast
Greyhound SpotlightThe five-month figure is one partner’s forecast for one customer still on track, not a finished project.
Every migration tool launches with speed claims, and Activate follows that pattern. A partner says one large customer is on track to move 20,000 users off Salesforce in about five months. Another says core finance setup was 25 percent faster in a side-by-side test. SAP, for its own tools, claims more than 35 percent less migration effort. These figures will appear in business cases unless someone checks them first.
Launch figures are a fixture of enterprise software, and seasoned buyers discount them by habit. What is different here is where they will land. Activate’s own discovery output can produce a timeline that looks as authoritative as a partner’s forecast, and the two can reinforce each other in a business case without either being tested. Greyhound Research thinks it likely that more customer timelines will be published over the coming year, which would make the claims easier to judge. A quieter effect concerns the partner market. Once a fast figure is public, partners may be asked to match it in fixed-price bids, and the risk then moves into the scope clauses of the contract.
Table 4 lists each claim with who made it, the basis it gives, and what it lacks. A company claim is a figure the company states about its own product.
Greyhound Research · Table 4 · Speed claims ledger
Five claims, and none comes with a method
The speed and scale claims behind Activate and SAP’s rival tooling, with who made each and the basis it gives, November 19, 2026.
Read every figure as a forecast. Budget from the company’s own discovery and a timed pilot, not from a press release.
| Claim | Kind | Who made it | Basis given | What it lacks |
|---|---|---|---|---|
| 20,000 users off Salesforce in about five months, against a typical 12 to 18 | Partner claim | congruentX, quoted by Microsoft | One customer, still on track | A finished result and the scope moved |
| Core finance setup 25% faster | Partner claim | Alithya, quoted by Microsoft | Side-by-side testing | Production results, and the share of a project it covers |
| Over six billion data records processed | Company claim | Microsoft | Early customer engagements | An accuracy or reconciliation rate |
| Strong momentum with Comcast and Fusion5 | Company claim | Microsoft | Two names. Fusion5 is a Microsoft partner | Outcomes for either |
| ERP migration effort cut by more than 35 percent | Rival claim | SAP, for its own tooling | None given | A method, and the tool’s name |
Table 4 lists five speed and scale claims and shows that none comes with a published method. congruentX, quoted by Microsoft, says one customer is on track to move 20,000 users off Salesforce in about five months, against a typical 12 to 18 months, which is a forecast for one project still running. Alithya, quoted by Microsoft, says side-by-side testing showed core finance setup 25 percent faster. Microsoft says Activate processed over six billion records in early engagements, without an accuracy rate, and names Comcast and Fusion5, a Microsoft partner, among its customers, without outcomes. SAP says its own agent-led tooling cuts ERP migration effort by more than 35 percent, with no method given. The claims are each party’s own.
None of the five comes with a method. The largest is a forecast, not a result. The test figure covers one part of a finance setup. Microsoft’s six billion records describes volume, not accuracy. SAP’s figure is SAP’s, for SAP’s own tools. The claims are not false. They are not yet evidence a CFO should budget on.
Greyhound Standpoint:
In Greyhound Research’s assessment, the speed claims show what is possible on a well-prepared estate with a capable partner, and they do not show what a given company should expect. A launch figure is chosen because it is the best example a vendor or partner can cite, which is normal practice and no fault. The issue is how it travels. A five-month forecast for one customer, a 25 percent gain on one part of a finance setup, six billion records without an accuracy rate, and SAP’s 35 percent for its own tools each measure something different, and none comes with a method.
Once one of them sits in a business case, it becomes the baseline the project is judged against, and the project team inherits a target it did not set. Three decades of implementation timelines suggest that the difference between one estate and another is larger than the difference between one tool and another. Microsoft deserves credit for naming customers and quoting partners on the record, and the figures may prove right. A finished project with a stated scope and method would change this reading.
CFOs should budget from the company’s own discovery report and a timed pilot on its own data, place any press-release timeline in the risk register rather than the business case, and ask at the pilot gate whether the pilot’s pace held.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What exactly did each party claim?
Microsoft’s partners. Marty Priest, Chief Executive Officer of congruentX, is quoted by Microsoft saying one large enterprise customer is on track to move 20,000 users from Salesforce in about five months, against the 12 to 18 months such projects typically take. John Scandar of Alithya is quoted saying side-by-side testing showed core finance setup could be delivered 25 percent faster.
Microsoft and SAP. Microsoft says Activate processed over six billion data records in early engagements, and names Comcast and Fusion5 among its customers. Fusion5 is a Microsoft business applications partner, and its New Zealand chief executive’s September quote speaks of delivering Activate with Microsoft for “our customers”, so the second name is better read as a partner’s endorsement than as a customer result. SAP claims more than 35 percent lower ERP migration effort for its own agent-led tooling.
What the sources of the claims tell a buyer. Every figure comes from a party with an interest in the result: two partners that sell the work, a vendor that sells the tool, and a rival that sells its own. That is normal at launch and does not make the figures wrong. It does mean a buyer should ask each party for the scope, the starting state of the estate, and what was left out.
In the source’s own words
- Dynamics 365 Blog, congruentX quoteOne large enterprise customer is on track to move 20,000 users from Salesforce to Microsoft in about five monthsSource
- Dynamics 365 Blog, congruentX quotemore than twice as fast as the 12 to 18 months these projects typically take.Source
- Dynamics 365 Blog, Alithya quoteIn side-by-side testing, Dynamics 365 Activate helped us see how we could deliver core finance setup 25% fasterSource
- Dynamics 365 Blog, Teper on November 17We're seeing strong momentum with customers including Comcast and Fusion5.Source
- Microsoft partner Fusion5, Dynamics 365 Blog, September 9the true partnership between Microsoft, Fusion5 and our customersSource
2How should a buyer read them?
As drafts. Greyhound Research wrote in July 2025 that every agent output is a draft, not a decision. A migration estimate produced by an agent, or quoted by a vendor, is the same. Buyers already read launch figures this way. Greyhound CIO Pulse 2026, across more than 1,000 enterprise technology leaders, finds 82 percent dismissing mega-announcements as more optics than delivery. A migration business case is where that caution should be applied.
In the source’s own words
- Greyhound Research, Oracle AI security note, October 29, 2026finds 82 percent dismissing mega-announcements as more optics than deliverySource
Part 5The Risks And The Counter-Argument
Risks To Watch: Where A Cheaper Exit Can Still Go Wrong
Greyhound SpotlightNone of the five risks is caused by the tool. Each comes from treating its output as a decision.
Greyhound Research sees five risks in Ignite’s two roads. Two sit on the exit road, one on the SAP clock, one on the stay road, and one on both. Each shows first in a document the buyer already holds, where it can be caught early.
These risks differ from the ones most migration risk logs were built for. Such logs have tended to track technical faults, such as a data load that breaks or an integration that will not connect, each with a fix and a date. The five here are gaps in judgment, where a document is accepted as more final than it is. Greyhound Research expects the first signs to appear in steering committee papers and budget reviews rather than in test results. The second-order effect is on accountability. If a timeline came from a vendor tool and was adopted without review, the company will find it hard to say who owned the decision, and internal audit will ask.
Table 5 sets each risk beside its early warning and its owner. Every early warning can be checked without help from Microsoft, Salesforce, or SAP.
Greyhound Research · Table 5 · Risk register
Every risk comes from treating a vendor’s output as the decision
Five risks on the exit road, the SAP clock, and the stay road, each with its early warning and its owner.
Every risk is cheapest to catch in the buyer’s own documents. Check all five this quarter, without waiting on a vendor.
| Risk | Early warning in the buyer’s own documents | Owner |
|---|---|---|
| Rules lost in the moveRecords arrive, and the workflows, approvals, or history that gave them meaning do not. | A migration plan with no sample reconciliation of records and processes. | Head of business applications |
| A budget set by a press releaseA business case adopts a partner’s five-month forecast as its own timeline. | A budget that cites a vendor or partner claim as its basis. | Chief financial officer |
| A deadline that forces the wrong pathAn ECC plan relies on a private preview reaching general availability by a set date. | An ECC roadmap with no dated alternative for 2027. | Chief information officer |
| Paying twice to staySellers carry Copilot and Salesforce licenses for the same work, with no test of use. | A license plan that adds Salesforce in Copilot without retiring anything. | Head of procurement |
| Data copies with no ownerData sits in a hosted migration copy or a federated query path with no retention rule. | A migration or data agreement without retention and deletion terms. | Chief data officer |
Table 5 lists five risks, each with an early warning in the buyer’s own documents and an owner. Rules lost in the move, warned by a plan with no sample reconciliation, owned by the head of business applications. A budget set by a press release, warned by a budget that cites a vendor claim, owned by the CFO. A deadline that forces the wrong path, warned by an ECC roadmap with no dated alternative for 2027, owned by the CIO. Paying twice to stay, warned by a license plan that retires nothing, owned by procurement. Data copies with no owner, warned by an agreement without retention and deletion terms, owned by the chief data officer. The risks are Greyhound Research analysis.
The five share a cause: a vendor’s output read as the buyer’s decision. A discovery report is a starting point, a speed claim is a forecast, and a preview is a roadmap. Each warning sits in a plan, a budget, or a contract the buyer controls. The table names owners, not likelihoods, and ranks none of the risks above another.
Greyhound Standpoint:
In Greyhound Research’s reading, none of the five risks is new to business application projects, and what has changed is how quickly a tool can produce a plan that looks finished. A discovery report with clean tables and a confident timeline carries an authority that a consultant’s draft spreadsheet did not, and that authority can carry it past the review it needs. The mechanism behind every risk in the table is the same: a vendor’s output read as the buyer’s decision. Rules lost in the move, a budget set by a press release, a deadline that forces the wrong path, paying twice to stay, and data copies with no owner each begin as a reasonable shortcut.
Program leaders will recognize the pattern from earlier waves of automated tooling, when faster drafting moved the risk from the work to the review of the work. The encouraging part is that each risk shows early, in a plan, a budget, a roadmap, a license plan, or a data agreement the buyer already controls. This is a judgment about order, not a prediction of harm, and the table ranks no risk above another because the evidence does not support a ranking.
A published Microsoft reconciliation method would ease the first risk. Each risk has an owner in the Runbook that follows, and each early warning can be checked this quarter, before the first statement of work is signed.
Part 5The Risks And The Counter-Argument
The Strongest Objection: Most Companies Stay
Greyhound SpotlightThe strongest objection to this note is that Microsoft’s own Ignite shows coexistence beats migration. Much of that is right.
The objection deserves its full weight. Large companies rarely leave Salesforce or SAP, because the cost and risk are high and the business gains are uncertain. Microsoft itself chose to partner with Salesforce on the same day it launched an exit tool, which suggests it expects most customers to stay. And a migration assessment built by the destination vendor will tend to make the destination look easy. On this view, Activate is mainly a sales tool and Copilotforce is the larger story.
The objection has history on its side. Enterprise application estates have proved durable for decades, and many announced migrations have ended as partial moves or renegotiated renewals. Microsoft’s own choice to partner on the same day suggests it reads the market the same way, and Greyhound Research expects the coexistence road to carry more customers than the exit road over the next few years. What the objection leaves out is the buyer’s position during those years. A company that stays without a priced alternative renews on the incumbent’s assumptions. One that stays with a priced alternative renews on its own, which makes for a different contract even when the vendor is the same.
Exhibit 6 tests each part of the objection against the evidence. Three parts stand. The conclusion that a buyer gains little from an exit plan does not hold.
Greyhound Research · Exhibit 6 · The objection held to the evidence
Three parts of the objection stand, and its conclusion does not
The fair counter-case to this research note, part by part, against the evidence gathered for each.
Greyhound Research’s judgment: most companies will stay, and those holding a priced exit plan are likely to stay on better terms.
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 the conclusion does not. Large CRM and ERP moves are rare and slow: stands, since Microsoft’s own partner puts a typical CRM move at 12 to 18 months. Microsoft expects most customers to stay: stands, since it launched Copilotforce with Salesforce the same day. A vendor-built assessment favors its maker: stands. So an exit plan adds little: falls, because leverage needs a credible alternative rather than a move, and the plan prices that alternative. The verdicts are Greyhound Research analysis.
Greyhound Standpoint:
Greyhound Research accepts the objection’s facts and does not accept its conclusion. Most companies will not move. Large CRM and ERP migrations are slow and costly, Microsoft partnered with Salesforce on the same day it released a tool for leaving Salesforce, and an assessment built by the destination vendor will tend to favor the destination. Each of those points is fair, and the coexistence road may well prove the larger business for all three companies. The objection goes too far in treating a move as the only return on an exit plan. A renewal changes when the incumbent believes the customer could leave, and a documented estate with a priced alternative is the evidence for that belief.
The plan also lists the customizations the buyer is paying to keep, which is useful whether the company moves or not. Long experience of enterprise contracts points the same way: an option to leave is valuable mainly because it is credible, and it is seldom exercised. The fair limit is that leverage is hard to measure, and some incumbents will hold price regardless. Evidence that priced exit plans made no difference to renewal terms would weaken this view.
Buyers who stay should still own an exit plan, reviewed by people who do not sell the destination, and procurement should table it at the next renewal.
The Deeper Read · About 1 minute
Select a question to open the full answer
1Why does the conclusion not hold?
Leverage needs credibility, not a move. A renewal changes when the vendor believes the customer could leave, and a documented estate with a priced alternative is the evidence for that. Activate lowers the cost of producing it. Greyhound Research’s October note on Oracle’s agentic implementation proposed that the drafter never approves its own output, which here means a vendor-built assessment should be reviewed by people who do not sell the destination.
Microsoft hedges too. Microsoft offers agentic operations for SAP on Azure and partners with Salesforce while selling a way off both. The buyer can hedge the same way, by holding an exit plan while renewing.
What Microsoft’s own hedge tells a buyer. If the destination vendor keeps both roads open, the buyer gains little by closing either one early. Holding a priced exit plan while renewing is the buyer’s version of the same position, and it costs far less than a move.
In the source’s own words
- Greyhound Research, Oracle agentic implementation notethe drafter never approves its own outputSource
Part 6What To Do, By Role
The Greyhound CXO Runbook: Ten Moves Before The Next Renewal
Greyhound SpotlightEvery move uses a document the buyer already controls: a renewal calendar, an estate map, a contract, a budget, a data agreement, a license plan, an access review, or a risk register.
Ten moves follow from the evidence, at least one for each leader who owns part of the decision. Each names the assumption it corrects, the evidence behind it, and the executive who decides. None waits for Microsoft, Salesforce, or SAP, because each uses controls the buyer already holds.
Each move is tied to a document for a practical reason. Migration programs have often been governed by steering committees whose decisions were hard to trace later, while a renewal calendar, an estate map, or a license plan can be dated, read, and checked. The first versions will be incomplete and should be revised as the vendors publish terms. In Greyhound Research’s judgment, the estate map is likely to need the most revision, because it changes with every release of the incumbent’s product. What is easy to overlook is that none of these documents favors a destination. An estate map, a customization register, or a data agreement serves a company that stays as well as one that moves.
Table 6 sets the ten moves beside the assumption each corrects, its evidence, and its owner. Two of the ten finish only when Microsoft publishes its terms.
Greyhound Research · Table 6 · The Greyhound CXO Runbook by owner
Ten moves, and none waits on a vendor to start
Ten moves for the leaders who own part of the CRM and ERP decision, with the assumption each corrects, its evidence, and its owner.
Start all ten this quarter. Only the price of the move and coexistence licensing wait on published terms.
Select a move to open its full text in The Deeper Read below
| Move | The assumption it corrects | Evidence anchor | The decision sits with |
|---|---|---|---|
| 1/Commission the discovery before the next renewal | A discovery is only worth doing once a move is decided | Exhibit 2 | CIO, with the head of business applications |
| 2/Put the exit plan on the renewal table | Leverage requires an intent to leave | Table 3 | Head of procurement, with the CFO |
| 3/Classify every customization and test a sample | A migration tool moves the logic | Exhibit 4 | Head of business applications |
| 4/Price three paths for SAP ECC | 2027 is the only date that matters | Exhibit 3, Table 4 | CFO, with the CIO |
| 5/Write the rules for coexistence | A joint release settles who answers for what | Table 2 | Chief data officer, with the CISO |
| 6/Choose the front door once | The CRM decision settles the assistant decision | Exhibit 5 | CIO, with the CFO |
| 7/Write each item’s release status into the contract | A Microsoft web page records the status the buyer pays for | Table 1 | Head of procurement, with the head of business applications |
| 8/Bring agents on other platforms into one identity review | An agent built on Salesforce or SAP is only that vendor’s to govern | Table 2, Exhibit 5 | Enterprise architect, with the CISO |
| 9/Have the discovery reviewed by someone who does not sell the destination | A vendor-built assessment is a neutral one | Exhibit 6 | Head of business applications, with the CIO |
| 10/Ask for the five early warnings at the board risk review | Migration risk is a technical matter for the project log | Table 5 | Board risk committee, with internal audit |
Table 6 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 a vendor to start while two complete only when Microsoft and Salesforce publish terms. The moves are: commission the discovery before the next renewal, put the exit plan on the renewal table, classify every customization and test a sample, price three paths for SAP ECC, write the rules for coexistence, choose the front door once, write each item’s release status into the contract, bring agents on other platforms into one identity review, have the discovery reviewed by someone who does not sell the destination, and ask for the five early warnings at the board risk review. The moves are Greyhound Research analysis.
The two that finish later, on the price of the move and on coexistence licensing, wait on terms Microsoft and Salesforce have not yet published. Those terms 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. The remaining eight can be finished with controls the buyer already holds.
The Deeper Read · About 5 minutes
Select a move to open its full text
1CIOs: commission the discovery before the next renewal.
Exhibit 2 shows that Activate’s first steps, reading the estate and recommending what to change, are written and released for Salesforce. This move corrects the belief that a discovery is only worth doing once a move is decided. Its action is to run a discovery on the Salesforce estate, with Activate or an independent partner, before the next renewal date, and to keep the output in the company’s hands. For SAP ECC, the action is to request access to the private preview or run an equivalent review. The decision sits with the CIO, together with the head of business applications.
Why this move comes first. Every other move draws on its output. Without a discovery, the exit plan has no price, the customization register has no list, and the SAP comparison has no baseline. Buyers who start from the renewal letter rather than the estate map tend to negotiate on the vendor’s numbers.
2Procurement: put the exit plan on the renewal table.
Table 3 shows that a priced exit plan changes the Salesforce, SAP, and Microsoft renewals alike. This move corrects the assumption that leverage requires an intent to leave. Its action is to price the alternative, set it beside the renewal offer, and ask each incumbent for data export terms, price holds, and exit support in writing. From Microsoft, ask for Activate’s price and any migration funding. The decision sits with the head of procurement, together with the CFO.
3Business applications leads: classify every customization and test a sample.
Exhibit 4 shows that records move while customizations, integrations, and processes are moved, simplified, or redesigned case by case. This move corrects the belief that a migration tool moves the logic. Its action is to classify every customization as move, simplify, redesign, or retire, and to reconcile a sample of records, workflows, and history on real data before any timeline is committed. The decision sits with the head of business applications.
4CFOs: price three paths for SAP ECC.
Exhibit 3 shows mainstream maintenance ending at the end of 2027, paid extended maintenance to 2030, and a narrow option to 2033, with Microsoft’s tool in private preview. This move corrects the habit of treating 2027 as the only date. Its action is to price staying under extended maintenance, moving to S/4HANA with SAP, and moving to Dynamics 365, using each vendor’s dates in its own words and a budget built from the company’s discovery, not from a speed claim. The decision sits with the CFO, together with the CIO.
5Chief data officers: write the rules for coexistence.
Table 2 shows that Salesforce governs access and every update needs a user’s confirmation, while licensing and accountability for a wrong update are not written. This move corrects the assumption that a joint release settles who answers for what. Its action is to agree which Salesforce actions Copilot may take, how federated data is kept and deleted, and who answers when an update goes wrong, and to write those into the data and service agreements. The decision sits with the chief data officer, together with the CISO.
6CIOs: choose the front door once.
Exhibit 5 shows that both roads put Copilot where work starts. This move corrects the belief that the CRM decision settles the assistant decision. Its action is to decide which assistant staff start from, license it once, and keep each system of record’s permissions behind it, so that sellers are not paid for twice. The decision sits with the CIO, together with the CFO.
7Procurement: write each item’s release status into the contract.
Table 1 shows two rows that can be signed with full terms today, beside four previews or pilots and no published price. It also shows that Microsoft’s pages disagree. The partner page still described a limited public preview of the Salesforce tool after the Book of News called it generally available, and one page calls the SAP ECC steps private preview while another says they are rolling out. This move corrects the assumption that a Microsoft web page records the status the buyer pays for. Its action is to list every Ignite item an order form or statement of work relies on, write each item’s release status into the contract, and commit no spend to a preview. Partners scope and price work from their own pages, so the partner’s statement of work should carry the same list. The decision sits with the head of procurement, together with the head of business applications, before the first statement of work is signed.
8Enterprise architects: bring agents on other platforms into one identity review.
Table 2 and Exhibit 5 show Microsoft Entra issuing an Entra Agent ID to agents on eleven connected platforms, Salesforce Agentforce and SAP among them, with the rollout due to complete in December, while Salesforce continues to govern what each user may see and change. This move corrects the assumption that an agent built on Salesforce or SAP is only that vendor’s to govern. Such an agent then sits with two vendors. Its action is to use the access review the company already runs to list every agent on a connected platform, name an owner for each, and record which system grants its rights and which can withdraw them. The companion Greyhound Research note on Azure agent infrastructure holds that identity is where control is enforced, so this list is where the work starts. The decision sits with the enterprise architect, together with the CISO, at the architecture review that falls before the December rollout completes.
9Business applications leads: have the discovery reviewed by someone who does not sell the destination.
Exhibit 6 finds that one part of the strongest objection stands: Activate is built by the destination vendor and runs in a Microsoft-hosted experience, so its assessment will tend to favor its maker. This move corrects the assumption that a vendor-built assessment is a neutral one. Its action is to have the discovery report reviewed, before it reaches a renewal or a budget, by people who do not sell Dynamics 365, an internal team or an independent partner. The reviewers should check the recommendations on what to keep, simplify, or redesign, and how those recommendations weigh staying on Salesforce, which Exhibit 2 marks as open. Greyhound Research’s October note on Oracle’s agentic implementation proposed that the drafter never approves its own output, and the same rule applies to a migration assessment. The decision sits with the head of business applications, together with the CIO, at the pilot gate where the report is first used.
10Board risk committees: ask for the five early warnings at the board risk review.
Table 5 sets out five risks, from rules lost in the move to data copies with no owner, each with an early warning in a plan, a budget, a roadmap, a license plan, or a data agreement the buyer already holds. This move corrects the assumption that migration risk is a technical matter for the project log. Such logs track faults with a fix and a date, while these five are gaps in judgment. Its action is to put the five early warnings on the agenda of the next board risk review, ask each named owner whether the warning is present, and record who approved any timeline or budget that came from a vendor tool. If a timeline was adopted without review, internal audit will ask who owned the decision, and the board is better placed to ask first. The decision sits with the board risk committee, together with internal audit.
Part 6What To Do, By Role
Questions For Microsoft: What Buyers Will Ask Next
Greyhound SpotlightNot one of the six questions has a full answer in what Microsoft has published, including what Activate costs.
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 tend to be answered in the order that suits the seller. Price and release dates usually arrive first, because a vendor needs them to close business, while terms on data handling and accountability arrive later, often only when customers ask in writing. Greyhound Research expects Activate’s price and the SAP timetable to be published before the questions on retention and writeback errors are answered. Buyers who ask together, through user groups or in the same renewal season, have tended to get earlier answers. A written reply can also be appended to the statement of work for a migration, so the answer travels with the contract rather than staying in a slide.
Table 7 tracks the six questions against what Microsoft has said so far. Three are answered in part, and three not at all.
Greyhound Research · Table 7 · Questions for Microsoft, tracked
Three questions answered in part, three not at all
The six questions only Microsoft can answer, against what it had stated by 00:50 UTC on November 19, 2026.
Ask in writing now. A price and a conversion scope would change this reading most, and no move waits on either.
Select a question to open its full text in The Deeper Read below
| Question | What Microsoft has said so far | The Runbook move it settles |
|---|---|---|
| Q1What does Activate cost, and does migration funding or credit come with it? | Not stated No price in Microsoft’s announcements or its partner page. | Runbook move 2 |
| Q2When will Activate for ERP be generally available, and for which ECC releases and modules? | Not stated One page says private preview, another says rolling out. | Runbook move 4 |
| Q3What does Activate move unchanged, convert, or leave for redesign? | Stated in part Items assessed are named. Customizations are moved, simplified, or redesigned. | Runbook move 3 |
| Q4Where does customer data sit during a move, and for how long? | Stated in part A Microsoft-hosted experience, with no retention terms. | Runbook moves 2 and 5 |
| Q5Which licenses does Salesforce in Copilot need on each side, and when does it leave preview? | Not stated Access is left to customer agreements. | Runbook move 6 |
| Q6Who answers when an update made through Copilot goes wrong in Salesforce? | Stated in part Salesforce governs actions, and each update needs user confirmation. | Runbook move 5 |
Table 7 tracks six questions only Microsoft can answer against what it had stated by 00:50 UTC on November 19, 2026, and shows three answered in part and three not stated at all. Not stated: what Activate costs and whether funding comes with it, when Activate for ERP will be generally available and for which ECC releases, and which licenses Salesforce in Copilot needs. Answered in part: what Activate moves, converts, or leaves for redesign, where customer data sits during a move, and who answers for a wrong update made through Copilot. Each question names the Runbook move it settles. The grading is Greyhound Research analysis.
Two answers would change this note’s reading most. One is a published price for Activate, with any migration funding attached. The other is a documented list of what Activate moves unchanged, what it converts, and what it leaves for redesign. Either would move Activate from a promising tool to one a CFO could budget on. None of the six is a trick question. Each asks Microsoft to write down what its product does, costs, or will do at release.
The Deeper Read · About 2 minutes
Select a question to open its full text
Q1What does Activate cost, and does migration funding or credit come with it?
Said so far. Not stated. Microsoft’s announcements and its partner page give no price for Activate. The answer settles. Whether the exit plan of the second Runbook move can carry a full price. Evidence that would settle it. A published price or licensing note. Greyhound Research would update. Table 1.
Q2When will Activate for ERP be generally available, and for which SAP ECC releases and modules?
Said so far. Not stated. One Microsoft page says private preview, and the Book of News says rolling out over the coming weeks. The answer settles. Whether Microsoft is a real third path in the fourth Runbook move before SAP’s dates. Evidence that would settle it. A release date and a scope list. Greyhound Research would update. Exhibit 3.
Q3What does Activate move unchanged, what does it convert, and what does it leave for redesign?
Said so far. In part. Microsoft names objects, workflows, code, and integrations among the things assessed, and leaves customizations to be moved, simplified, or redesigned. The answer settles. How much of the third Runbook move’s classification the tool can do. Evidence that would settle it. Documentation of conversion scope, including history and audit trails. Greyhound Research would update. Exhibit 4.
Q4Where does customer data sit during a move, and for how long?
Said so far. In part. Microsoft describes a Microsoft-hosted experience. The answer settles. What the data terms of the second and fifth Runbook moves must cover. Evidence that would settle it. A data handling and retention statement for Activate. Greyhound Research would update. Exhibit 2.
Q5Which licenses does Salesforce in Copilot need on each side, and when does it leave preview?
Said so far. Not stated. The joint release leaves access to customer agreements. The answer settles. The license plan of the sixth Runbook move. Evidence that would settle it. Published licensing for Salesforce in Copilot and Sales Cloud in Teams. Greyhound Research would update. Table 2.
Q6Who answers when an update made through Copilot goes wrong in Salesforce?
Said so far. In part. Salesforce governs access and actions, and each update needs the user’s confirmation. The answer settles. The accountability terms of the fifth Runbook move. Evidence that would settle it. Joint terms naming who is responsible for writeback errors. Greyhound Research would update. Table 2.
Why user confirmation matters. A confirmation step answers part of the question, because a person approved each update. It leaves open what happens when the person approves an update built on wrong context from the assistant. That gap sits between two vendors’ terms, which is why it needs a joint answer in writing.
Part 7The Final Greyhound Standpoint
Dynamics 365 Activate: 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 put a released tool behind Microsoft’s long-standing bid for Salesforce and SAP customers, and on the same day offered Salesforce customers a way to stay. Both roads end at Copilot. When leaving gets cheaper, the exit plan becomes the control: a scoped, priced, tested plan the buyer owns, used at every renewal whether or not the company moves. The judgment is not that companies should leave. For most, staying with Salesforce or SAP will remain the sound choice, and both vendors have given them reasons to stay. Salesforce keeps its record and its permissions behind each assistant it joins, and SAP has committed to S/4HANA until 2040, offers paid maintenance beyond 2027, and has built its own migration tooling.
On the exit road, the Salesforce tool is generally available and its discovery is the part to use now. The SAP tool is a private preview against SAP’s end-2027 date, useful for deciding and too new to carry a full move. On the stay road, Copilotforce keeps Salesforce’s own permissions, and its licensing is not written. On both roads, the hardest work is still rebuilding the rules that made the old system fit the business.
The mechanism is the price of information. For decades the cost of finding out what leaving would involve has protected incumbents more than most contract terms, because a buyer that cannot price the alternative cannot use it. Earlier platform shifts, from client-server software to the cloud, often brought destination vendors willing to fund that discovery to win share, and the buyers who gained most kept the findings and used them at the table, whatever they decided. Activate lowers that cost for Salesforce customers today, and may do the same for SAP ECC customers once its preview opens. Microsoft deserves credit for that, and buyers should remember that the tool comes from the vendor that gains if they move.
The evidence has limits. Activate has no public documentation beyond Microsoft’s announcements and a partner page. Microsoft’s pages disagree on the SAP tool’s status. The speed claims come from partners and vendors without a method. Salesforce’s and SAP’s positions are read only through their own announcements and statements. Statuses and claims are as each company published them through November 19, 2026.
Four signals would move this position within twelve months. Each would make Activate easier to budget on. They are a published price for Activate with any migration funding, general availability of Activate for ERP with a scope list, documentation of what Activate converts and what it leaves for redesign, and published licensing for Salesforce in Copilot at general availability.
Exhibit 7 sets those signals side by side with what each would change. All four sit with Microsoft, and one of them also with Salesforce.
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.
A documented conversion scope would move this view furthest. Watch for it first.
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. A documented conversion scope would show how much of a move is migration and how much is rebuilding. A published price for Activate would let CFOs cost the exit plan in full. General availability of Activate for ERP, with a scope list, would make Microsoft a dated third path before SAP’s deadlines. Published Copilotforce licensing would show the cost of staying. A change by Salesforce or SAP to data export or access terms, or a new migration offer, could reset the comparison. The signals are Greyhound Research analysis.
One event outside Microsoft’s control could reset the comparison: a change by Salesforce or SAP to data export or access terms, or a new migration offer from either. Of the four signals, a documented conversion scope would matter most, because it decides how much of a move is migration and how much is rebuilding. Until the signals arrive, CIOs, CFOs, and procurement leaders have a clear order of work for the next renewal or SAP decision. Run the discovery, keep it in the company’s hands, price the exit beside the renewal offer, and treat any press-release timeline as a forecast to test in a pilot rather than a basis for a contract.
Part 8Appendix, 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 first read on November 18, 2026, between 11:55 and 12:05 UTC, and read again on November 19, 2026, between 00:28 and 00:50 UTC, when every quotation was checked against the live page. Four sources were added on November 19. 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, blogs, and partner pages6 sources, 60 extracts
| Source, read, and used | Where in the source | What it says |
|---|---|---|
| Microsoft (2026a)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Two Signals At Once, Activate For CRM, The SAP ECC Clock, Data And Process Fidelity, Copilotforce, The Strongest Objection, Dynamics 365 Activate. Tables 1 and 2. Exhibits 1, 2, 3, and 4Quoted in The Deeper Read of What Microsoft Announced, Activate For CRM, The SAP ECC Clock, Data And Process Fidelity, Copilotforce, Two Signals At Once | Dynamics 365 Activate | [quoted in The Deeper Read] |
| Same section | [quoted in The Deeper Read] | |
| Same section | "Dynamics 365 Activate is an implementation and migration platform" | |
| Same section | [quoted in The Deeper Read] | |
| Same section | [quoted in The Deeper Read] | |
| Same section | "Project context will carry forward from assessment through implementation" | |
| Same section | [quoted in The Deeper Read] | |
| Salesforce in Copilot, Teams and Fabric | [quoted in The Deeper Read] | |
| Same section | [quoted in The Deeper Read] | |
| Same section | "allowing sellers to get a real-time view of pipeline and quota progress" | |
| Same section | "while leaving the source data in Fabric." | |
| Azure agentic operations | [quoted in The Deeper Read] | |
| Same section | "now available in preview with more than 38+ prebuilt sales skills" | |
| Reading note | Azure Workload Center is listed as "in preview", without a private or public qualifier (corrected on November 19 from [quoted in The Deeper Read]). The Book of News does not use the name Copilotforce. The page was read in two passes, from the start and from character 100,000. No passage mentions Agentforce. | |
| Microsoft (2026b)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Two Signals At Once, Copilotforce, Renewal Leverage, The Strongest Objection, Dynamics 365 Activate. Tables 1 and 2. Exhibits 1 and 5Quoted in The Deeper Read of What Microsoft Announced, Two Signals At Once, Copilotforce | Release | "a plugin available in public preview with 38+ prebuilt sales skills" |
| Availability | [quoted in The Deeper Read] | |
| Availability | [quoted in The Deeper Read] | |
| Availability | [quoted in The Deeper Read] | |
| Availability | Data sharing from Salesforce Data 360 into OneLake is in public preview (summarized, not quoted). | |
| Trust | [quoted in The Deeper Read] | |
| Trust | [quoted in The Deeper Read] | |
| Trust | "Microsoft applies its existing enterprise compliance controls to communications and documents." | |
| Accenture | "Accenture is serving as design and implementation partner and pilot customer," | |
| Accenture | "having scaled Copilot to more than 740,000 people" | |
| Sweet of Accenture | "We are also excited to serve as customer zero for Copilotforce" (Julie Sweet, Chair and CEO, Accenture). | |
| Terms | [quoted in The Deeper Read] | |
| Althoff of Microsoft | [quoted in The Deeper Read] | |
| Milano of Salesforce | [quoted in The Deeper Read] | |
| Reading note | The release does not address licensing, pricing, or who pays, and does not mention Slack. Several sentences quoted in The Deeper Read end with a comma in the release and are quoted without closing punctuation. Dateline: Redmond and San Francisco, November 17, 2026. | |
| Teper, J. (2026a)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Activate For CRM, Data And Process Fidelity, The Speed Claims. Exhibits 2 and 4. Table 4Quoted in The Deeper Read of Activate For CRM, Data And Process Fidelity, What Microsoft Announced | Status | "We are starting with a public preview for organizations moving from Salesforce to Dynamics 365" |
| Discovery | [quoted in The Deeper Read] | |
| Execution | [quoted in The Deeper Read] | |
| Execution | The migration runs in a "Microsoft-hosted experience" (phrase quoted, sentence summarized). | |
| Scale | [quoted in The Deeper Read] | |
| Scope | [quoted in The Deeper Read] | |
| Partner quote | [quoted in The Deeper Read] | |
| Image description | "analysis results for Salesforce objects, workflows, code, integrations, and related components" | |
| Comcast | "For example, Comcast was looking for ways to accelerate its migration assessment" | |
| Comcast quote | "greater visibility into our Salesforce landscape and key migration considerations" (Sathish Arumugam, Manager, Software Dev and Engineering, Comcast). | |
| Fusion5 quote | "Dynamics 365 Activate represents a significant step forward in how Dynamics 365 solutions can be delivered." (Kristy Brown, Chief Executive, New Zealand, Fusion5). | |
| Reading note | No price, licensing, or data retention terms are given. No formal human-review step is described beyond the partner quote. | |
| Teper, J. (2026b)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Two Signals At Once, Activate For CRM, The SAP ECC Clock, Data And Process Fidelity, The Front Door, The Speed Claims. Tables 1 and 4. Exhibits 3 and 5Quoted in The Deeper Read of Two Signals At Once, What Microsoft Announced, Data And Process Fidelity, Activate For CRM, The Speed Claims | Modernize with Dynamics 365 Activate | [quoted in The Deeper Read] |
| Same section | "extending Dynamics 365 Activate for ERP, starting with SAP ECC (private preview)" | |
| Same section | [quoted in The Deeper Read] | |
| Same section | [quoted in The Deeper Read] | |
| Same section | [quoted in The Deeper Read] | |
| Same section | [quoted in The Deeper Read] | |
| congruentX quote | [quoted in The Deeper Read] | |
| congruentX quote | [quoted in The Deeper Read] | |
| Alithya quote | [quoted in The Deeper Read] | |
| Copilot | [quoted in The Deeper Read] | |
| Plugins | The Sales, Customer Service, and ERP apps plugins are each marked [quoted in The Deeper Read], with "more than 57 business skills" across the customer experience plugins and more than 39 finance and operations skills. | |
| Visa quote | Manish Mittal, Senior Vice President and Global Technology Head for Value-Added Services, Visa (title as printed). | |
| Reading note | The post does not mention Salesforce in Copilot, Copilotforce, pricing, or credits for Activate. Fusion5 and Comcast appear only in the momentum sentence. | |
| Stanford, C. (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in The Front Door. Exhibit 5Quoted in The Deeper Read of The Front Door | Connected platforms | [quoted in The Deeper Read] |
| Connected platforms | "A sales team might build in Salesforce Agentforce, a data team in Databricks Genie, and developers in Amazon Bedrock." | |
| Rollout | "Anthropic Claude Managed Agents, OpenAI, Oracle, SAP, ServiceNow, and UiPath, and will complete in December." | |
| Reading note | Re-read November 19: the rollout sentence lists eleven platforms, Salesforce Agentforce first. The earlier reading that the post named Agentforce only as an example is corrected. The post is signed carolinestanford, with no job title. | |
| Microsoft (n.d.)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced. Table 1Quoted in The Deeper Read of What Microsoft Announced | Activate | [quoted in The Deeper Read] |
| Reading note | The page describes Activate for project discovery and Activate for migration for Salesforce only, states no cost to partners or customers, and has no SAP content. It still said limited public preview when read again on November 19. |
Salesforce, SAP, and other companies6 sources, 22 extracts
| Source, read, and used | Where in the source | What it says |
|---|---|---|
| Anthropic (2026)Read November 19, 2026, between 00:28 and 00:50 UTCUsed in Copilotforce | Article | "Today we are releasing Salesforce in Claude in beta." |
| Reading note | Dated September 15, 2026. Admins request access through AgentExchange. | |
| Fusion5 (n.d.)Read November 19, 2026, between 00:28 and 00:50 UTCUsed in The Speed Claims | News | "won the prestigious Microsoft ANZ Business Applications Partner of the Year Award for 2024" |
| Reading note | The page carries no publication date. It is cited only for Fusion5's status as a Microsoft partner. | |
| Salesforce (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Copilotforce, Renewal Leverage. Table 3Quoted in The Deeper Read of Copilotforce | Release | [quoted in The Deeper Read] |
| Benioff of Salesforce | "This is how every business will run." | |
| Availability | "Salesforce in Claude is available to select pilot customers now and expects to launch in open beta in September 2026." | |
| Reading note | The release does not mention Microsoft or Copilot in its body. [quoted in The Deeper Read] is followed by more text and is quoted without closing punctuation. | |
| Gilg, J. (2024)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in The SAP ECC Clock, Renewal Leverage. Exhibit 3. Table 3Quoted in The Deeper Read of The SAP ECC Clock | Post | [quoted in The Deeper Read] |
| Post | "end maintenance for the latest three enhancement packages of core applications" | |
| Post | [quoted in The Deeper Read] | |
| Reading note | The post, by Jan Gilg, gives the end of 2027 for mainstream maintenance of the latest three enhancement packages of SAP Business Suite 7, and states no fee. | |
| SAP (2025)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in The SAP ECC Clock, Renewal Leverage. Exhibit 3. Table 3Quoted in The Deeper Read of Renewal Leverage, The SAP ECC Clock | Transition option | [quoted in The Deeper Read] |
| Transition option | "available for active usage from 2031 to 2033" | |
| Conditions | [quoted in The Deeper Read] | |
| Conditions | "SAP HANA is the only supported database for the new subscription offering." | |
| Reading note | The page was published on February 4, 2025, and updated on March 7, 2025, under the headline New Offering to Help Navigate Complex RISE with SAP Transformations. The note earlier gave its title as the RISE with SAP landing title and no publication date, corrected on November 19. | |
| SAP (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in Two Signals At Once, The SAP ECC Clock, Renewal Leverage, The Speed Claims. Tables 3 and 4Quoted in The Deeper Read of The SAP ECC Clock, Two Signals At Once | Release | [quoted in The Deeper Read] |
| Release | "SAP S/4HANA on-premises and SAP ERP Central Component (SAP ECC) customers are not excluded" | |
| Release | [quoted in The Deeper Read] | |
| Partnerships | [quoted in The Deeper Read] | |
| Reading note | The tooling is not named. Google Cloud and Microsoft are named as partners for agent interoperability. |
Media3 sources, 11 extracts
| Source, read, and used | Where in the source | What it says |
|---|---|---|
| Clark, L. (2025)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in The SAP ECC Clock, Renewal Leverage. Exhibit 3. Table 3Quoted in The Deeper Read of The SAP ECC Clock, Renewal Leverage | SAP spokesperson | [quoted in The Deeper Read] |
| SAP spokesperson | [quoted in The Deeper Read] | |
| Transition option | "The option will be offered for the period from 2031 until the end of 2033," | |
| Conditions | Customers must "sign up for a cloud migration deal" (phrase quoted, sentence summarized). | |
| Klein of SAP | [quoted in The Deeper Read] | |
| Reading note | The article attributes the Klein line to a recent call, linked to SAP's fourth-quarter 2024 earnings call transcript. | |
| Ghoshal, A. (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, as corroboration only | Report | Activate was "currently in public preview" on September 10, 2026 (phrase quoted, sentence summarized). |
| Report | Microsoft planned "ERP capabilities expected later this year" (phrase quoted, sentence summarized). | |
| Reading note | Commentary from third-party analysts in the article is not used. The article carries no Salesforce comment. | |
| Zwets, B. (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, as corroboration only | Report | "Organizations can now sign up for the public preview of the Salesforce migration." |
| Report | "The ERP capabilities will be released later this year." |
Research this note builds on7 sources, 13 extracts
| Source, read, and used | Where in the source | What it says |
|---|---|---|
| Greyhound Research (2025a)Read November 18, 2026, before 12:05 UTC, and again November 19, 2026, before 00:50 UTC, on greyhoundresearch.comUsed in Data And Process Fidelity, Renewal LeverageQuoted in The Deeper Read of Data And Process Fidelity | What This Deal Signals | "According to Greyhound CIO Pulse 2025, 58% of enterprise technology leaders globally now classify" |
| Reading note | The figure is in the main body under What This Deal Signals for the Broader Enterprise Technology Ecosystem, not in the page's separate AI-generated summary notice. The sentence ends [quoted in The Deeper Read], which the note now includes. The exit-ramps advice is point 5 of the Post-Acquisition Toolkit. | |
| Greyhound Research (2025b)Read November 18, 2026, before 12:05 UTC, and again November 19, 2026, before 00:50 UTC, on greyhoundresearch.comUsed in Renewal Leverage, The Speed ClaimsQuoted in The Deeper Read of Renewal Leverage | Note | [quoted in The Deeper Read] |
| Note | "every agent output is a draft, not a decision" | |
| Greyhound Research (2025c)Read November 19, 2026, between 00:28 and 00:50 UTC, on greyhoundresearch.comUsed in The Front Door | Standpoint | "According to Greyhound Research, the rhetoric of AI agents replacing apps is premature." |
| Standpoint | "still perform irreplaceable data integrity and compliance functions" | |
| Greyhound Research (2026a)Read November 18, 2026, before 12:05 UTC, and again November 19, 2026, before 00:50 UTC, on greyhoundresearch.comUsed in Activate For CRM, The Speed Claims, The Strongest ObjectionQuoted in The Deeper Read of Activate For CRM, The Strongest Objection | Standpoint | [quoted in The Deeper Read] |
| Note | [quoted in The Deeper Read] | |
| Reading note | The shorter wording used before November 19, whoever signs off agent-drafted configuration is signing off authority, sits in that note's AI-drafted synopsis, so the Standpoint wording is now quoted. The note's disclosures state that Oracle is a client of Greyhound Research. | |
| Greyhound Research (2026b)Read November 19, 2026, between 00:28 and 00:50 UTC, on greyhoundresearch.comUsed in The Speed Claims | Reading note | The figure sits in Questions For Oracle, Q1, and is given as Greyhound CIO Pulse 2026, across more than 1,000 enterprise technology leaders. The note's disclosures state that Oracle is a client of Greyhound Research. |
| Greyhound Research (2026c)Read November 18, 2026, before 12:05 UTC, and again November 19, 2026, before 00:50 UTC, on greyhoundresearch.comUsed in The Front DoorQuoted in The Deeper Read of The Front Door | Note | [quoted in The Deeper Read] |
| Greyhound Research (2026d)Read November 18, 2026, from the draft of the same date, and checked again November 19, 2026Used in The Front Door, Renewal Leverage | Lock-In And Exit | Committing to one agent platform is defensible when the way out is in the contract (summarized, not quoted). |
| Agent Grid And Identity | What each agent may read, change, and spend becomes the control (summarized, not quoted). |
Part 8Appendix, 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, Salesforce’s, SAP’s, and the other companies’ documents are each company’s account of its own products, dates, and terms, and prove what the company said rather than that the thing is true. Partner figures quoted by Microsoft are the partners’ claims. The news reports what its authors were told. Standing pages that carry no publication date are marked n.d. All sources were first read on November 18, 2026, and every source was read again on November 19, 2026.
Microsoft announcements and blogs
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 and Salesforce Announce Copilotforce, Bringing Trusted Customer Context and Action into Microsoft AI Experiences. Microsoft Source, November 17. Available at: https://news.microsoft.com/source/2026/11/17/microsoft-and-salesforce-announce-copilotforce-bringing-trusted-customer-context-and-action-into-microsoft-ai-experiences/
Teper, J. (2026a) Accelerate your move to agentic business applications with Dynamics 365 Activate. Microsoft Dynamics 365 Blog, September 9. Available at: https://www.microsoft.com/en-us/dynamics-365/blog/business-leader/2026/09/09/accelerate-your-move-to-agentic-business-applications-with-dynamics-365-activate/
Teper, J. (2026b) Microsoft Ignite 2026: Introducing Dynamics 365 in Copilot. Microsoft Dynamics 365 Blog, November 17. Available at: https://www.microsoft.com/en-us/dynamics-365/blog/business-leader/2026/11/17/microsoft-ignite-2026-introducing-dynamics-365-in-copilot/
Stanford, C. (2026) What’s new in Microsoft Agent 365: Ignite 2026. Microsoft Community Hub, November 17. Available at: https://techcommunity.microsoft.com/blog/agent-365-blog/whats-new-in-microsoft-agent-365-ignite-2026/4571753
Microsoft (n.d.) Dynamics 365 Partner Tools. Microsoft Partner. Available at: https://microsoftpartners.microsoft.com/abs/d365-partner-tools/
Salesforce, SAP, and other companies
Anthropic (2026) Bringing Salesforce into Claude. Claude, September 15. Available at: https://claude.com/resources/articles/salesforce-in-claude
Fusion5 (n.d.) Fusion5 Secures 2024 Microsoft ANZ Business Applications Partner of the Year Award. Fusion5 News. Available at: https://www.fusion5.com/nz/news/fusion5-secures-2024-microsoft-anz-business-applications-partner-of-the-year-award
Gilg, J. (2024) Embracing the Future: A Strategic Shift to Cloud ERP Solutions. SAP News Center, October 30. Available at: https://news.sap.com/2024/10/embracing-strategic-shift-cloud-erp/
Salesforce (2026) Salesforce and Anthropic Announce Claudeforce. Salesforce Newsroom, August 26. Available at: https://www.salesforce.com/news/?p=94766
SAP (2025) New Offering to Help Navigate Complex RISE with SAP Transformations. SAP News Center, February 4, updated March 7. Available at: https://news.sap.com/2025/02/sap-erp-private-edition-transition-option-navigate-complex-rise-with-sap-transformations/
SAP (2026) SAP Unveils the Autonomous Enterprise. SAP News Center, May 12. Available at: https://news.sap.com/?p=242256
Media
Clark, L. (2025) SAP extends support deadline for getting off legacy software – in very special circumstances. The Register, January 28. Available at: https://www.theregister.com/2025/01/28/sap_extends_support_deadline/
Ghoshal, A. (2026) Microsoft targets Salesforce customers with AI-powered Dynamics 365 migration tool. CIO, September 10. Available at: https://www.cio.com/article/4220712/microsoft-targets-salesforce-customers-with-ai-powered-dynamics-365-migration-tool.html
Zwets, B. (2026) Microsoft aims to attract Salesforce customers to Dynamics 365 using AI. Techzine Global, September 10. Available at: https://www.techzine.eu/news/applications/144215/microsoft-aims-to-attract-salesforce-customers-to-dynamics-365-using-ai/
Research this note builds on
Greyhound Research (2025a) Salesforce Acquires Informatica: What This Means for AI Trust. Research note, May 28. Available at: https://greyhoundresearch.com/salesforce-acquires-informatica-what-this-means-for-ai-trust/
Greyhound Research (2025b) 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 (2025c) Dismantling SaaS Silos: The Role of AI In Integration. Research note, July 26. Available at: https://greyhoundresearch.com/dismantling-saas-silos-the-role-of-ai-in-integration/
Greyhound Research (2026a) Oracle Agentic Implementation – When Agents Draft The Setup, Review Becomes The Control. Research note, October 29. Available at: https://greyhoundresearch.com/oracle-agentic-implementation-when-agents-draft-the-setup-review-becomes-the-control/
Greyhound Research (2026b) Oracle AI Security – When AI Finds The Flaws Faster, Fixing Becomes The Control. Research note, October 29. Available at: https://greyhoundresearch.com/oracle-ai-security-when-ai-finds-the-flaws-faster-fixing-becomes-the-control/
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 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/
Part 8Appendix, Sources, And Disclosures
Disclosures: Independence, Financial, Intended Use, Methodology, Authoring, And Copyright
The evidence in this research note is current through November 19, 2026, with an evidence cutoff of 00:50 UTC that day. Every source was first read on November 18, 2026, the day after Microsoft’s Ignite announcements, and was read again between 00:28 and 00:50 UTC on November 19, 2026. No Microsoft Learn documentation for Dynamics 365 Activate was found by that time. 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, heads of business applications and enterprise architects, chief financial officers, procurement and vendor management leaders, chief data officers, board members, and the press. It reads Microsoft’s Dynamics 365 Activate and Copilotforce announcements at Microsoft Ignite 2026, the announcements beside them, and Salesforce’s and SAP’s own published statements, to inform decisions on CRM and ERP renewals, migration, coexistence, 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 maintenance terms is to be confirmed with counsel and with each vendor. 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, dates, features, and prices 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 twenty-two documents listed in Sources And References, in four 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 documented is bounded to the documents the text names, as they stood at 00:50 UTC on November 19, 2026. Statuses are given as each company states them, and where two Microsoft pages disagree, both are reported.
Salesforce’s and SAP’s positions are taken from their own announcements and, for SAP, also from statements made in January 2025 by an SAP spokesperson and by Christian Klein, SAP’s CEO. Speed and scale figures from Microsoft, its partners, and SAP are company or partner claims and are not used to compute any estimate. The Greyhound CIO Pulse figures are cited as published in Greyhound Research’s research notes of May 28, 2025, and October 29, 2026. Earlier Greyhound Research comments published in the press, in December 2025 and January 2026, are quoted word for word and attributed to Greyhound Research with their date. 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 the two signals, the Activate steps, the fidelity layers, the coexistence terms, the renewal positions, the readings in Exhibits 1 to 7 and Tables 1 to 7, 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, Salesforce, SAP, 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.
Copyright Policy
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.

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.













Microsoft Ignite 2026 – When Agents Join The Workforce, Written Authority Becomes The Control
Publication Record
Evidence current through: Thursday, November 19, 2026, at 1:20 a.m. UTC (8:20 p.m. ET and 5:20 p.m. PT on Wednesday, November 18).
This note summarizes the eight companion notes of the Greyhound Research Microsoft Ignite 2026 series and reads each product at the status Microsoft gave it by the time above. The sources were checked again for this edition, after the companion notes completed their own pre-launch audit. Most agent features announced on November 17, 2026, are in preview or Microsoft’s Frontier program. 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 treated AI agents as part of the workforce rather than a feature of its software. Agents now get a name in Microsoft’s directory, a sealed-off machine of their own, a budget drawn from a shared meter, and a choice of Microsoft’s own models. Copilot became the front door to Microsoft 365, security agents began closing alerts on their own, and a released tool now helps companies leave Salesforce. Much of what decides cost and risk is still in preview or Microsoft’s early-access Frontier program.
Greyhound Research’s position is that Ignite 2026 changed who holds the control. In every area its eight-note series examines, Microsoft shipped a capable tool and left the rule that tool enforces for the buyer to write. When agents join the workforce, written authority becomes the control: who may enroll, spend, act, and leave, set down by the buyer before the agent starts work. Greyhound Research reads this as a normal stage of a platform shift. The capability has arrived ahead of the terms, as it did with software as a service and public cloud, and the buyers who fare best tend to adopt what is released and write their own rules for the rest.
Three findings carry the argument. First, Microsoft has written the first steps of an agent’s authority, its name and its machine, and not yet the rule at each tool call or the power to stop a rival’s agent. Second, the meter now sits beside every seat price, and several of its rates are unpublished. Third, Microsoft now meters the spend, scores the value, grades its own security agents, and sells its own models, so buyers need records Microsoft does not mark.
The note sets out a ten-move Greyhound CXO Runbook for the whole series, with six exhibits, five tables, and six questions for Microsoft. None of the moves waits on Microsoft. The first three are simple to state. Sign on general availability terms and enroll named groups only. Write the spending policy before the meter runs. Register every agent as a privileged account and map where it can be stopped.
The evidence has limits. This note summarizes eight companion notes and does not repeat their evidence, which each one sets out in full. Most agent features are previews, and Microsoft’s pages word some statuses differently. Greyhound Research names the signals that would change its view within twelve months. Until they arrive, the advice holds: use what Microsoft has released, and write down the rules for everything an agent may do.
In This Research NoteSection guide · AI drafted · Analyst reviewed
Sixteen sections in seven 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 eleven 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.
Microsoft gave agents names, machines, budgets, and models of their own. Most of what decides cost and risk is still in preview or the Frontier program.
Greyhound Research’s top ten by consequence for buyers, with each one’s status. Copilot as the front door ranks first. Most of what decides cost is in preview.
At Ignite 2025 Agent 365 was in the Frontier program and agents were being named. A year later they have prices, budgets, and a count of 50 million.
In each area the series examines, Microsoft shipped a tool and left the rule it enforces to the buyer. Eight notes name eight controls, and each is a written document.
The eight companion notes, each with its control and its readers, and the order in which to read them by role.
Copilot’s new front door reaches every user this winter while its agents stay in Frontier. Copilot Credits are one currency but not one bill, and the spending policy decides the cost.
Three notes follow an agent from its directory name to its own machine and its sealed data. Microsoft has written the name and the machine, and not yet the limit or the stop.
Security agents now close alerts on their own, Microsoft sells its own models beside its partners’, and a released tool prices the way out of Salesforce. Each needs a record Microsoft does not keep.
Five risks that run across the eight notes, from previews drifting into production to the seller marking its own work, each with an early warning and an owner.
The fair counter-case: Microsoft ships more control tooling than its rivals, and one suite simplifies buying it. Both hold. The claim that the tools are the control does not.
Ten series-level moves for the CIO, CFO, CISO, data protection officer, procurement, general counsel, change and adoption leads, and the chief risk officer, each naming the assumption it corrects and who decides.
Six series-level questions only Microsoft can answer, on release terms, rates, enforcement, data, exit, and audit. Each is tied to a Runbook move.
Agents joined the workforce, and written authority is the control. The limits of the evidence, and the signals that would change the view within twelve months.
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.
Twenty-three sources in five classes: Microsoft’s announcements, a partner announcement, media, the eight companion notes, and earlier Greyhound Research notes.
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
Find your role and read its sections in the order shown. Each line takes you straight to the section.
Chief information officer
Chief financial officer
Chief information security officer
Data protection officer
Head of procurement
Chief risk officer
Change and adoption lead
General counsel
Board member
Part Of A Larger SeriesSeries guide · AI drafted · Analyst reviewed
This research note is the flagship of Greyhound Research’s nine-note Microsoft Ignite 2026 series, and brings the eight companion notes together. Each companion takes one part of what Microsoft announced. Select a title to open it in a new tab.
The series in one read. Microsoft has shipped what agents need to run, and the deciding control in every area is the authority the buyer writes down.
Copilot becomes the front door to daily work while its agents stay in Frontier, so enroll people by the data they handle.
When work is billed by the task, the bill follows behavior, and the written policy on pooling, caps and unused credits decides the cost.
Agent 365 can list agents built on rival platforms, but listing is not stopping, so the duty to enforce belongs in each contract.
The machinery for running agents on Azure is ready to pilot. What each agent may touch, and under whose name, is still to be written.
The seal keeps the cloud operator out but not the customer’s own agent, so judge offers by who checks the proof.
Security agents that close alerts can take real load off teams, and a weekly sample of their closures is the safeguard.
With Microsoft now supplier, router and rival at once, keep the right to pick and pin the model, and budget on list price.
Activate makes it cheaper to learn what leaving involves, and a priced exit plan strengthens the hand even of companies that stay.
Part 1What Ignite Changed
What Ignite Changed: Agents Moved From Feature To Workforce
Greyhound SpotlightMicrosoft’s chief executive said the week was about two things. The second was building the capability to deal with the consequences of fast-growing AI, and every note in this series is about that second thing.
At Ignite in San Francisco on November 17, 2026, Satya Nadella, Microsoft’s chief executive, called Copilot “the new OS for work.” The phrase carried the week. Copilot, Microsoft’s AI assistant, became the starting point for work in Microsoft 365, with Word, Excel, and PowerPoint inside it. Around it, Microsoft treated agents, AI programs that carry out tasks on a person’s behalf, less like features and more like staff.
Agents now get most of what a new employee gets. They get a name in Entra, Microsoft’s directory of people and systems. They get a sealed-off machine for each task, a budget drawn from Copilot Credits, Microsoft’s usage-based currency, and a choice of Microsoft’s own AI models beside those of OpenAI and Anthropic. Security agents in Microsoft Perception now close alerts without asking anyone first. Microsoft’s own summary put the stakes this way: as agents move from answering questions to taking action, trust becomes the deciding factor.
The workforce comparison is about governance, not about what an agent is. Greyhound Research said in January 2026 that service agents should be monitored “like they’re privileged employees,” and the comparison here borrows the same discipline: a name, a sponsor, narrow rights, and a way to remove them. It does not make an agent an employee, and agents should not be bought, priced, or credited as if they were.
The keynote also opened with an apology. Days after a Microsoft 365 outage, Nadella said that Microsoft takes the trust customers place in its services extremely seriously and has work to do on resilience. By Greyhound Research’s count, that outage was the fourth multi-service Microsoft 365 incident of 2026. Greyhound Research said on November 13, and repeated in its November 15 note on that outage, that enterprises have priced Microsoft 365 as a license rather than as a single point of failure. Agents raise the same question one level up.
What this changes is the unit a buyer governs. For three decades, enterprise software has been governed product by product, through a license count and the settings that switch features on. Ignite moves part of that work down to the individual agent, each with its own name, machine, and budget, so the familiar joiner, mover, and leaver routine of human resources now needs a software counterpart. Agent numbers are likely to grow faster than any review cycle built for staff. The effect most coverage misses is the leaver. When the employee who sponsored an agent changes role or leaves, the agent stays, and its rights stay with it unless someone has written down who removes them.
Exhibit 1 groups the week’s news by what a buyer can sign now, what is still on test terms, and what is not yet written. Generally available means fully released, with support and service terms. Frontier is Microsoft’s early-access route for previews.
Greyhound Research · Exhibit 1 · What Ignite 2026 released, and what it left open
The products shipped. The rules for agents did not
Microsoft’s Ignite 2026 announcements grouped by what a buyer can sign today, what is still on test terms, and what is not yet written, November 19, 2026.
Greyhound Research’s judgment: commit only on the first card, pilot the second, and treat the third as the buyer’s to write.
Exhibit 1 groups Microsoft’s Ignite 2026 announcements into three cards. Generally available: Home and Office in Copilot, Microsoft Perception, Microsoft-Decision-1.1 with MAI Code 2 live in GitHub Copilot, and the Salesforce migration in Dynamics 365 Activate. In preview or the Frontier program: Autopilot, Workspaces, and Today, Agent 365 Cost Management, connected platforms for rivals’ agents, and Agent Grid, the AKS sandbox extension, and the Confidential Clean Room in limited preview. Not yet written: several Copilot Credits rates and a Perception rate card, prices for Licensed Weights and Activate, HIPAA coverage and three ISO standards for Frontier features, whether agent memory sits inside the seal or controls are enforced on rivals’ platforms, and the confidential computing items Microsoft describes as still in development. The grouping is Greyhound Research analysis.
The first card is real and usable today. The second holds most of the agent features that justify the week’s claims, and they sit on preview terms. The third card matters most, because it lists what no one has written yet: rates, prices, coverage, and the boundaries of what an agent can reach. Those gaps do not wait for Microsoft to close them. Each one is a place where the buyer’s own written rule decides the risk.
Greyhound Standpoint:
At Greyhound Research, we believe Ignite 2026 marks the point at which Microsoft began to sell agents as a workforce rather than as a feature, and that the first question it raises is about mandate, not technology. The reason lies in what Microsoft attached to each agent. A directory name, a machine, a budget, and a choice of model resemble what a company gives a new member of staff, and each one opens a cost line, a risk line, or both. A feature is governed by the setting that switches it on. A worker is governed by a written mandate that says what it may touch, spend, and decide, and who answers when it gets something wrong.
Practitioners have seen this before. When personal computers, email, and then cloud services reached employees, use spread well ahead of the policies that later governed it, and catching up cost more with each month of delay. Microsoft deserves credit for putting trust at the center of its message and for opening the keynote by addressing the outage. Much of the agent estate is still in preview, so the mandate may change as terms are published. CIOs should table a one-page agent mandate at the next architecture review, naming who may deploy an agent, what it may reach, what it may spend, and who can stop it, before any agent moves past pilot.
The Deeper Read · About 3 minutes
Select a question to open the full answer
1What did Microsoft say the week was about?
Two things. The keynote, posted by Microsoft as an edited transcript, says the week was about capitalizing on capabilities growing exponentially, and building the capability to deal with their consequences. The same text calls Copilot “the new OS for work.” On stage, Nadella added that apps are “just plugins to Copilot.”
Trust as the deciding factor. Microsoft’s Source summary of the event names four themes: human ambition, intelligence, trust, and infrastructure. Its trust section says that trust becomes the deciding factor as agents move from answering questions to taking action.
What the two framings tell a buyer. The keynote and the Source summary put the same week in two ways. One speaks of capability and its consequences, the other of trust as the deciding factor. Read together, they show Microsoft asking to be judged on trust, which is welcome, and they give buyers a simple test for each announcement: does it add capability, or does it help deal with the consequences? On Greyhound Research’s reading, most of the released items add capability, and most of the consequence work, the rules, rates, and terms, is still to come.
In the source’s own words
2How did the outage shape the keynote?
An apology first. Nadella acknowledged the previous week’s outage. He said Microsoft knows the trust customers place in its services and takes that responsibility extremely seriously, and that it has work to do on resilience. Greyhound Research’s outage note, which counts the incident as the fourth multi-service Microsoft 365 incident of 2026, found that consolidating on one suite remains right for most enterprises while the standard terms around it no longer suffice.
Consolidate, and keep the record independent. Greyhound Research has also warned, in its July 2025 note on Copilot’s Researcher and Analyst agents, that as agents become embedded in business-critical workflows the enterprise becomes progressively dependent on them, and “renegotiation leverage is materially diminished.” The two views fit together, and this series carries both. Consolidating the suite remains sensible for most enterprises, on the condition that the evidence of what agents did, the approval of what they may do, and the means to recover sit outside the suite being governed. The same condition explains why Copilot as the new OS for work is treated here as a dependency to govern as well as a convenience.
How the outage advice has moved. In its June 2025 outage note, Greyhound Research wrote that no single vendor can serve as the sole source of continuity, and advised failover messaging tools that integrate with Microsoft’s identity service. The November 2026 note keeps the first point and narrows the second. It advises against a second suite held in reserve, and asks instead for a rehearsed fallback for the few processes that cannot stop, one that shares nothing with the suite, including its sign-in. A fallback that signs in through the suite shares its outage, which is why the advice changed.
In the source’s own words
↑ Back to the section guide
Part 1What Ignite Changed
What Microsoft Announced: Ten Announcements, Ranked By What They Change
Greyhound SpotlightFour of the ten announcements that matter most to buyers are generally available at their core. The other six, including every item that sets cost or identity, are mostly in preview or Frontier.
Microsoft’s Book of News, its official list of Ignite announcements, covers every product line the company sells. Greyhound Research ranked them by one test: how much each changes a buyer’s budget, contracts, or risk in the next twelve months. Status matters as much as substance. A preview is a test release without full service terms, so a preview cannot carry a production commitment however large the keynote made it. By Greyhound Research’s count of the 59 announcement headings in the Book of News, 10 cover only generally available items, 19 cover only previews or Frontier items, and 28 mix the two. The other two give no status for some or all of their items.
Greyhound Research reads the heading count as more telling than any single launch. With 28 headings mixing released and preview items, one product name can now cover both, and a purchase approved by name can carry a preview inside it. In earlier cycles a product was usually either shipping or not, and the release note settled the question. Here status sits at the level of the feature, and it is likely to keep moving month by month as the December dates arrive. The second-order effect is administrative. Internal approvals, risk registers, and contract schedules that list products by name will need to list features, or they will record a status the vendor has already changed.
Table 1 sets out the ten, in order, with the status Microsoft gave each and the companion note that covers it. Nine of the ten are covered by a companion note in this series.
Greyhound Research · Table 1 · The top ten, by buyer consequence
Ten announcements, and most of what decides cost is in preview
Greyhound Research’s ranking of Microsoft’s Ignite 2026 announcements by consequence for enterprise buyers, with status as Microsoft gave it, November 19, 2026.
Judge each row by its status, not its rank. Only the four released rows are ready for a contract.
Table 1 ranks ten Ignite 2026 announcements by consequence for buyers, with each one’s status and the companion note that covers it. First, Copilot as the new OS for work, partly generally available and partly in Frontier. Second, Agent 365 Cost Management and Business Analytics, in preview and Frontier. Third, Copilot Credits across more services, with several rates unpublished. Fourth, connected platforms for rivals’ agents, completing in December. Fifth, Microsoft Perception, generally available. Sixth, Dynamics 365 Activate and Copilotforce. Seventh, MAI models and Licensed Weights. Eighth, local and shadow agent governance. Ninth, Azure agent infrastructure and Cobalt 200. Tenth, Microsoft IQ and Azure HorizonDB, not covered by a companion note. The ranking is Greyhound Research analysis.
Copilot as the front door ranks first because it reaches every licensed user this winter, whatever a company decides about agents. The economics items rank next because the meter now touches every product. The four rows released at their core are the ones a buyer can sign today: Perception, the MAI coding models live in GitHub Copilot with the generally available Decision-1.1, Activate’s Salesforce migration, and Microsoft IQ. The rest belong in a plan, not a contract.
Greyhound Standpoint:
Greyhound Research’s reading is that Ignite 2026 released the parts of the agent story a buyer can see and kept in preview most of the parts a buyer will rely on. That gap should set the order of work. Four of the ten items that matter most are released at their core: Perception, the MAI models live in GitHub Copilot with the Decision-1.1 routing model, the Salesforce migration in Activate, and Microsoft IQ. The spending controls, the reach into rivals’ agents, and the machinery for running agents remain on test terms. A preview carries no full service terms, so a commitment built on one rests on terms that do not yet exist.
The pattern is a familiar one. Platform vendors have long announced the whole vision at a flagship event and released it in stages, and buyers who signed on the vision ahead of the release could end up paying for what they could not yet use. Microsoft labels its previews clearly, which is to its credit, and several open items carry December dates. If those dates hold with full terms attached, the gap will narrow quickly. CIOs and procurement leads should hold each item in Table 1 to its status at the next pilot gate, adopting the released rows on their merits, budgeting the previews as plans, and accepting no production commitment that rests on a keynote status.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1How was the ranking made?
By buyer consequence. Greyhound Research read Microsoft’s Book of News, the keynote, and the product blogs, and ranked each announcement by its effect on a buyer’s budget, contracts, or risk within twelve months. The statuses are as Microsoft gave them. Where Microsoft’s pages disagree, the companion notes record both readings.
What the statuses say. The Book of News lists Perception, Microsoft IQ, and Azure HorizonDB as generally available, and calls the Salesforce migration in Dynamics 365 Activate generally available. Microsoft IQ comes, in Microsoft’s words, with no new SKU or subscription. Cobalt 200 virtual machines, Microsoft’s own Arm-based servers, are generally available too.
In the source’s own words
2What did not make the ten?
Confidential computing. The Book of News lists three confidential computing offerings as in preview, under a heading on protecting highly sensitive data. Microsoft’s more detailed confidential computing post, by Vikas Bhatia, reads more narrowly: one limited preview and two items still in development. It describes the multi-GPU item as a technology showcase whose confidential VMs and containers remain in development, and the enclaves as planned for a future release. Only the clean room, first previewed in June, is in limited preview. This note follows the detailed post, as the companion notes do. None of the three has a price or release date, so the news ranks below the ten for most buyers. For banks, insurers, and health groups it may matter more than anything on the list, and it has its own companion note.
What the gap between the two pages tells a buyer. The Book of News is a summary written for the whole event, and the product team’s post is written for the people who will build on the product. When the two differ, the more detailed page is usually the safer guide, and the difference is itself a sign of how early the product is. A buyer’s status check should cite the most specific Microsoft page available, with the date it was read, rather than the event summary.
Silicon and Windows. Maia 300, Microsoft’s next AI chip, was highlighted with a claim of 40 percent more tokens per watt than leading GPU systems, a company figure this note does not use. Windows security changes, including a Windows Endpoint Security Platform, now generally available, that gives approved security products a safer way to protect devices, matter to endpoint teams and sit outside this series.
In the source’s own words
↑ Back to the section guide
Part 1What Ignite Changed
A Year On: From Ignite 2025’s Previews To Ignite 2026’s Price List
Greyhound SpotlightAt Ignite 2025, Agent 365 was an early-access preview. By May 2026 it had a price of USD 15 per user, and Microsoft now says more than 50 million agents have been registered in it.
A year ago, Microsoft’s Ignite was about naming agents. Agent 365, its tool for keeping track of a company’s agents, arrived through the Frontier program, and agents built in Copilot Studio began to get an Entra Agent ID. Microsoft’s post that week spoke of organizations becoming Frontier Firms. Two of its new context services, Fabric IQ and Foundry IQ, were in preview, and Azure HorizonDB, a new database, was in private preview.
Twelve months on, the same products have prices and general availability. Microsoft announced in March that Agent 365 and Microsoft 365 E7, its top suite, would be generally available on May 1, at USD 15 and USD 99 per user. At Ignite 2026, Microsoft IQ, the umbrella over its context services, and Azure HorizonDB became generally available. Microsoft says organizations have registered more than 50 million agents in Agent 365 since its May launch.
The pace is the news here. Microsoft took Agent 365 from an early-access preview to a priced, generally available product in less than a year, between Ignite 2025 and May 1, and buyers should plan for the next steps to move at a similar speed. Most enterprise governance runs on an annual cycle of budgets, audits, and renewals, so the vendor’s calendar now runs quicker than the buyer’s. The consequence most coverage misses is the estate already built. Agents created during the preview year, under test terms, now sit inside paid products, and the first governance task is to find and classify them before planning new ones.
Exhibit 2 places the steps between the two events on a month grid, from the first prices to the security agents.
Greyhound Research · Exhibit 2 · The year between two Ignites
In twelve months, agents went from preview to price list
Microsoft’s steps from Ignite 2025 to Ignite 2026, by month, from the first price for agent management to the general availability of its security agents.
Microsoft delivered on its year. Buyer governance now has to keep the same pace.
Exhibit 2 places Microsoft’s steps between Ignite 2025 and Ignite 2026 on a month grid from December 2025 to November 2026, and shows six months with a step from preview to product. On March 9, Microsoft set prices for Microsoft 365 E7 and Agent 365. On May 1, both became generally available, at USD 99 and USD 15 per user. On June 16, Cowork became generally available. On July 27, Project Perception was introduced. In September, Microsoft announced Home in Copilot. On November 17, Ignite opened days after a Microsoft 365 outage. A note beneath records the starting point: at Ignite 2025, Agent 365 was in the Frontier program and Fabric IQ and Foundry IQ were in preview.
The pattern is a move from naming to billing. In 2025 the question was whether an agent could be found and listed. In 2026 it is what an agent costs, what it may do, and who answers for it. Microsoft’s own summary now describes last year’s theme as Frontier Transformation, and this year’s news as its next milestone. The buyer’s work has moved with it, from inventory to policy.
Greyhound Standpoint:
Greyhound Research’s view is that Microsoft used the year well, and that the move from preview to price list changes the buyer’s job from watching to governing. Products that were early-access previews at Ignite 2025 now carry prices and general availability, and Microsoft reports more than 50 million agent registrations in Agent 365 since May. Greyhound Research called Entra Agent ID a policy control plane for agent computing in its Build 2025 note, and Microsoft has since extended it to rivals’ agents. That is steady delivery.
The mechanism behind the shift is the meter. A preview costs little to watch. A released product with a per-user price and a usage meter creates a commitment that grows each month whether or not anyone has decided what it is for. The same arc ran through the early years of software as a service, when trial seats became enterprise contracts and ownership stayed with IT long after the spending had spread across departments. Fifty million registrations measures reach rather than governed use, and a published definition would make it more useful. CFOs, CISOs, and general counsel should each take written ownership of a part of the agent estate at the next budget cycle, so that the meter, the access, and the terms do not rest with the IT team alone.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What did Ignite 2025 announce?
Agents named, not yet billed. The Ignite 2025 Book of News says Agent 365 was available in the Microsoft 365 admin center with the Frontier program, and that agents built in Copilot Studio would get a Microsoft Entra Agent ID. It lists Fabric IQ and Foundry IQ in preview and Azure HorizonDB in private preview. Frank X. Shaw’s post that week described Agent 365 as a way to observe, manage, and secure agents.
In the source’s own words
2What changed by Ignite 2026?
Prices, then volume. Judson Althoff, CEO of Microsoft’s commercial business, set general availability for Agent 365 and Microsoft 365 E7 on May 1, 2026, and E7 bundles Microsoft 365 E5, Microsoft 365 Copilot, and Agent 365. Microsoft’s Agent 365 blog gives the 50 million as registrations since the May launch. The companion note on agent identity finds three wordings of the figure and no published definition, so it counts registrations, not governed agents.
How the view has moved. Greyhound Research said in March 2026 that “there is no mature control plane that governs how agents act,” what they access, or how their actions can be reversed or contained. Since then, Agent 365 and E7 have reached general availability, and Microsoft has extended Entra Agent ID to rivals’ agents and to agents on employees’ computers. The view has moved in part. For Microsoft’s own agents and for managed devices, a control plane now exists. For agents on rivals’ platforms, the rule at each tool call and the power to stop an agent are not yet written, which is where this series places the remaining gap.
What three wordings of one figure tell a buyer. A registration count measures how many agents have been listed, not how many are in use or governed. That the 50 million is worded three ways, with no published definition, does not make it wrong. It means the figure cannot yet serve as a benchmark, either for a buyer’s own estate or against a rival’s. A company that wants a number it can compare over time will need to define its own, for example agents active in the past month with a named sponsor.
In the source’s own words
↑ Back to the section guide
Part 2The Through-Line
The Through-Line: The Control Moves To What The Buyer Writes
Greyhound SpotlightEvery one of the eight controls this series names is a document the buyer writes: a list, a policy, a map, a rule, a test, an audit, a contract term, or a plan.
Greyhound Research read Ignite 2026 in eight companion notes, one for each area where a buyer’s decisions change. Each note ends with the same kind of finding. Microsoft has built a capable tool. The tool enforces a rule. The rule is not in Microsoft’s product, its price list, or its terms. It has to be written by the customer, and it is now the thing that decides the risk.
The pattern holds from the front door to the exit. Copilot’s agents reach only the users a company enrolls in Frontier, so the enrollment list is the control. Copilot Credits are predictable only under a spending policy. A rival’s agent can be stopped only where its credentials are issued, so the map of those places matters more than the directory. The same is true of authority, proof, audit, model choice, and the plan to leave. Greyhound CIO Pulse 2026, across more than 1,000 enterprise technology leaders, found that 84% have shifted their focus from AI adoption to AI accountability. Accountability needs a written rule to account against.
What is new is the kind of rule being asked for. Earlier enterprise controls mostly governed access: who could open a system, see a record, or approve a payment. Agent controls govern action, what software may do on its own once inside, and most governance frameworks were written before that question arose. The 84% figure suggests the demand for accountability is already ahead of the documents that would support it, and Greyhound Research expects that gap to surface first in audit committees and internal audit plans. The second-order effect is that a written rule is also a record. Once it exists, auditors and regulators can ask for it, and the company can be measured against what it wrote.
Exhibit 3 holds the eight notes against three tests: whether the product is released today, whether its price and terms are written, and whether Microsoft’s tool settles the control on its own.
Greyhound Research · Exhibit 3 · One through-line, eight controls
In every area, the control is something the buyer writes
The eight companion notes of Greyhound Research’s Microsoft Ignite 2026 series, each with the control it names, against three tests, November 19, 2026.
This is not a gap in Microsoft’s tools. It is work only the buyer can do, and it should be staffed now.
Exhibit 3 is a matrix of the eight companion notes against three tests, and shows that in no area does Microsoft’s tool settle the control alone. Released today: yes for Perception, in part for Copilot, economics, identity, infrastructure, MAI models, and Activate, and not yet for confidential computing, where only the clean room is in limited preview. Price and terms written: in part for economics, where seat prices are published and several credit rates are not, and not yet for the other seven. Microsoft’s tool settles it alone: no for all eight, whose controls are Frontier enrollment, the spending policy, enforcement, authority, attestation, the audit, model choice, and the exit plan. The marks are Greyhound Research analysis.
Only one area, Perception, is generally available at its core, and only one, agent economics, has price and terms written in part. In none does the tool settle the control alone. That is not a charge against Microsoft. A spending limit, a directory, or an attestation service can only enforce a rule someone has written. The finding is that the rule-writing has moved to the buyer, and many buyers are only beginning to staff it.
Greyhound Standpoint:
Greyhound Research’s position is that Ignite 2026 has a single through-line. When agents join the workforce, written authority becomes the control, and that authority is a set of documents the buyer writes and owns: who may enroll, spend, act, and leave, set down before the agent starts work. Every Microsoft tool read for the series enforces a setting, whether a spending limit, a Conditional Access policy, or an attestation check, and a setting is only as sound as the rule behind it. Where no rule is written, the default decides, and defaults are designed for the vendor’s general case rather than the buyer’s particular risk.
Experienced buyers will recognize the lesson from the outsourcing era. Contracts moved the work to a provider, and the retained team that wrote and policed the service terms came to matter as much as the contract itself. Microsoft deserves credit for building tools that can enforce such rules and for its stated commitment to transparency. This note relies on the evidence of eight companion notes, and a documented rule at the tool call from Microsoft would move part of the control back into the product. Boards should ask, at their next risk review, to see six documents by name: the Frontier enrollment list, the spending policy, the agent register with its stop points, the audit sample, the model policy, and the exit plan.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1Why written, and why the buyer?
A rule needs an author. Each Microsoft tool read for the series enforces a setting: a spending limit, a Conditional Access policy, an attestation check, or a review queue. The companion note on agent economics finds that a spending limit is a ceiling, not a budget. The note on Azure agent infrastructure finds that the layer deciding what an agent may do was left to be written. In both, the setting is only as good as the rule behind it.
Accountability. Greyhound Research’s November 5 note on agent front doors cited the Greyhound CIO Pulse 2026 finding that 84 percent of more than 1,000 enterprise technology leaders have shifted their focus from AI adoption to AI accountability. A written rule is what accountability is measured against.
In the source’s own words
2How does this square with Microsoft’s message on trust?
Microsoft agrees on transparency. The keynote said that nested black boxes are unacceptable, announced an AI Transparency Initiative with 40 organizations, and described an end-to-end trust platform. Those are welcome commitments. They describe how Microsoft will show what its systems do. They do not write the customer’s rules for what its agents may do, which is the gap the series finds.
Why the trust quotes matter. Calling nested black boxes unacceptable is a strong line for a platform vendor to use on its own stage, and it gives buyers a standard to quote back in negotiation. Transparency of the platform and authority of the agent are different layers, though. The first lets a company see what happened. The second decides what may happen. Microsoft’s commitments address the first, and the series’ finding concerns the second, so the two positions fit together rather than conflict.
In the source’s own words
↑ Back to the section guide
Part 2The Through-Line
The Series: Eight Notes, Eight Controls
Greyhound SpotlightThe series names eight controls, and only one of them, the spending policy, belongs to finance. The rest fall to security, data, legal, procurement, and the CIO.
The series has seven numbered notes and one extra on confidential computing. Each follows the same plan: what Microsoft announced, what it means for a buyer, the risks, the strongest case against the note’s view, a ten-move Greyhound CXO Runbook, and six questions for Microsoft. Each title follows one pattern. It names the change, and the control that change creates.
The series is built around controls rather than products for a reason. Microsoft’s product names and bundles change often, and features move between suites and licenses, while the questions a buyer must answer about authority, spend, and exit stay stable. Reading by control is likely to outlast this year’s packaging. The larger change is to the vendor relationship. Most enterprises run Microsoft through one account owner and one renewal. Once finance, security, legal, and data protection each own a control, each will bring its own questions to Microsoft, and a company that does not gather them in one place will negotiate in several voices at once, which tends to favor the seller.
Table 2 maps the eight notes, with the control each names, what the buyer writes, and the readers each is written for.
Greyhound Research · Table 2 · The Series
Eight notes, eight controls, one direction
Greyhound Research’s Microsoft Ignite 2026 series, note by note, with the control each names and the readers it is written for.
Every control needs a named owner. Read first the note whose control your role will own.
Table 2 maps the eight companion notes of the Microsoft Ignite 2026 series, each with its control and main readers. Note 1, Copilot as the OS for work: Frontier enrollment, for CIOs and change leads. Note 2, agent economics: the spending policy, for CFOs and FinOps leads. Note 3, agent identity: enforcement, for CISOs and identity leads. Note 4, Azure agent infrastructure: authority, for platform engineering and CISOs. The confidential computing note, a series extra: attestation, for CISOs and data protection officers. Note 5, Perception: the audit, for CISOs and SOC leads. Note 6, MAI models: model choice, for CTOs and general counsel. Note 7, Dynamics 365 Activate: the exit plan, for CIOs and business applications leads.
The notes can be read in any order, though they build on each other. The note on Copilot as the front door and the one on agent economics cover what every user and every budget will meet first. The notes on agent identity, Azure agent infrastructure, and confidential computing follow an agent from its name to its machine and its sealed data. The notes on Perception, MAI models, and Dynamics 365 Activate cover the security agents, Microsoft’s own models, and the way out of rivals’ software.
Greyhound Standpoint:
Greyhound Research’s reading is that the most practical lesson of the series concerns ownership. The eight controls belong to at least six different functions, and no single team can write the rules for a workforce of agents on its own. Enrollment touches change management, the spending policy belongs with finance, enforcement and the audit sit with security, the data map with data protection, and model choice and the exit plan with procurement and legal. When ownership stays with whoever bought the license, the controls outside that team’s expertise tend to go unwritten, less because anyone decided against them than because no one was asked.
Consolidation cycles have taught this before. When enterprises standardized on large suites, the savings showed up in procurement while the governance work spread across functions that had not budgeted for it. Each note names its readers, so a leader can read the two or three that touch their remit. The assignment suggested here is a starting point, and a company with a central AI office may group the controls differently, which is reasonable. CIOs should assign each of the eight controls to a named executive at the next steering committee, set a date for a first draft, and record any control without an owner as an open risk.
The Deeper Read · About 1 minute
Select a question to open the full answer
1How do the notes relate to each other?
They agree by design. Where two notes meet, they reach the same verdict and say so. The note on agent identity and the note on Azure agent infrastructure both find AWS ahead today on written rules at the tool call. The notes on Perception and infrastructure both treat agents as insiders that need the narrow rights of a privileged account. The note on agent economics agrees with the infrastructure and confidential computing notes on the same week’s news.
Each keeps its own evidence. Every companion note sets out its own sources, evidence register, and limits. This overview summarizes their positions and does not restate their evidence. A reader checking a claim about a single product should go to the note that covers it.
Why agreement across notes matters. Where two notes reach the same verdict from different evidence, as with AWS’s lead on written rules at the tool call, the finding is sturdier than either note alone. Where a note records that Microsoft’s own pages disagree, the disagreement is information too. It usually marks a feature whose status or terms are still settling, and those are the features a buyer should hold at the pilot gate.
↑ Back to the section guide
Part 3The Eight Notes In Brief
The Front Door And The Bill: Copilot And Agent Economics
Greyhound SpotlightThe front door moves for every licensed user this winter. The agents behind it stay under Frontier terms that leave out HIPAA coverage and three ISO standards.
The first thing most employees will notice from Ignite is a new starting page. Home, in the Copilot app, is where work now begins, with Word, Excel, and PowerPoint inside Copilot. Both are generally available. The agents that do work on a person’s behalf, Autopilot, Workspaces, and Today, are in the Frontier program. The companion note on Copilot as the front door finds that Frontier terms do not include HIPAA coverage and do not meet ISO 27001, 27002, or 27018. It also finds that Microsoft’s launch post says Autopilot leaves a clear audit trail while its documentation says Autopilot activity is not a guarantee of a complete audit record.
The second thing most companies will notice is the bill. Microsoft kept Microsoft 365 Copilot at USD 30 per user a month, Agent 365 at USD 15, and E7 at USD 99. Beside those seat prices it widened Copilot Credits, which now also pay for Windows 365 for Agents, a billing option in Fabric, and the Today Feed. The companion note on agent economics finds that credits are one currency but not yet one bill, because services are set up in three different consoles. It finds that a spending limit reserves nothing, stops the user’s work for the rest of the month when reached, and by default covers every new metered service. For new Copilot Business subscriptions bought through Microsoft’s partners, Microsoft plans to switch usage-based billing on by default between January and March 2027, moved from December 1, 2026, with a default limit of 4,000 credits per user a month that administrators can adjust.
Together the two notes describe the employee’s side of Ignite. One changes where people work, the other how the work is paid for. Both put a control in the buyer’s hands. The first is an enrollment list for the Frontier side of the front door. The second is a spending policy that says who may spend, how much, on which services, and what happens when the money runs out.
The shift beneath both notes is from a fixed bill to a variable one. For most of the history of Office licensing, the seat price was close to the whole cost, and finance could forecast it from headcount. A second line now moves with use, and it sits behind the very front door Microsoft is designing to be used more. Greyhound Research expects the first surprises to come through partner-billed Copilot Business subscriptions once usage billing switches on by default in early 2027. The effect most coverage misses is that adoption and cost now pull in the same direction. A rollout that succeeds in getting people to use agents will, by design, raise the bill.
Greyhound Standpoint:
Greyhound Research holds that the front door and the bill should be governed as one program, because the same employees will meet both in the same months. When the front door moves, Frontier enrollment becomes the control. When work is billed by the task, the spending policy becomes the control. Each user enrolled in a Frontier agent feature is also a new point of spend, and a spending limit, as the economics note finds, reserves nothing and stops the user’s work for the rest of the month once reached. Enrollment without a policy invites unplanned cost, and a policy without enrollment discipline invites stalled work.
Interface changes and pricing changes have usually been run by different teams, and the friction between them has tended to surface at the help desk and in the budget review. Microsoft deserves credit for holding seat prices steady and for publishing more about the cost of a task than its rivals. The limits are that several credit rates are unpublished and that Frontier terms do not yet include HIPAA coverage or three ISO standards, so the right scope for enrollment may widen once release terms appear. Change leaders should retrain users by role this quarter and enroll only named pilot groups. Finance leaders should switch off automatic coverage of new metered services and write a spending policy for each business unit before the next renewal.
The Deeper Read · About 2 minutes
Select a question to open the full answer
1What does the note on Copilot as the OS for work find?
The doorway now, the agents slowly. The companion note finds that Home and Office in Copilot change where every user starts work, and that Microsoft’s rollout notices carry no training guidance. Its ten moves begin with retraining by role, enrolling named groups in Frontier, and keeping regulated data out of Frontier features. Its advice is to move the doorway now and enroll the agents slowly. It finds Microsoft ahead of Google on released features and on written terms.
Signals. Release dates for Autopilot, Workspaces, and Today, HIPAA and ISO coverage at release, a complete Autopilot audit record, and a stated retention period for Autopilot’s memory would each strengthen the case for wider enrollment.
What the gap between the launch post and the documentation tells a buyer. The launch post says Autopilot leaves a clear audit trail, and the documentation says its activity is not a guarantee of a complete audit record. Both can be true. A launch post describes intent, and documentation describes what Microsoft commits to. For audit and legal purposes the documentation is the page that counts, so a company relying on Autopilot for compliance should treat its trail as useful evidence, not as a complete record.
2What does the note on agent economics find?
The policy, not the price list. The companion note finds that predictability has moved from Microsoft’s price list to the spending policy the customer writes. It finds Microsoft ahead of its rivals in publishing what a task costs, level with them in pairing seats with a meter, and behind Google on what happens at the cap, where Google pauses an agent’s calls and Microsoft stops the user’s access for the month. It also finds that Microsoft now meters the spend and scores the value, so the business should keep its own measure of what the work was worth.
How the view on credits has moved. Greyhound Research said in November 2025 that new units such as credits were “deliberately designed to obscure value exchange.” The economics note finds that Copilot Credits answer much of that charge, because Microsoft now publishes more of what a task costs than its rivals do, and keeps the earlier caution where rates are still unwritten.
What is missing. Several credit rates are unpublished, including those for the Today Feed, Fabric, and Windows 365 for Agents. Its advice is to buy prepaid credits from measured use and to negotiate the terms for credits at renewal as hard as the price of seats. Microsoft’s Source summary says Business Analytics shows leaders what their AI is costing.
In the source’s own words
↑ Back to the section guide
Part 3The Eight Notes In Brief
The Name, The Machine, And The Seal: Identity, Infrastructure, And Confidential Computing
Greyhound SpotlightMicrosoft can now give a Salesforce or AWS agent a Microsoft name. Its own documentation describes that link as read-only, so stopping the agent stays with the platform that runs it.
Three companion notes follow an agent through the infrastructure that runs it. The first is its name. Microsoft’s connected platforms feature copies agents from Salesforce, AWS, Google, Anthropic, and other vendors into Agent 365 and gives each an Entra Agent ID. The companion note on agent identity finds that Microsoft’s documentation calls the link to rivals’ platforms read-only. Agent 365 can name and watch a rival’s agent. It cannot stop one, so enforcement stays wherever each agent’s credentials are issued.
The second is its machine. The note on Azure agent infrastructure finds that Microsoft gave agents sealed-off machines, network rules that refuse by default, and a cache of work already done, and brought Foundry onto customers’ own clusters. Running agents is level with AWS and Google, AWS is ahead on written rules for each tool call, and Microsoft is ahead on the identity, security, and Microsoft 365 estate around the agent. The third is its data. The note on confidential computing finds the seal keeps the cloud operator out but not the customer’s own agent, which is the one reading the data.
The detail that matters most in these three notes is the read-only link. For human staff, the directory has long been the master record: disable an account there and access ends almost everywhere. For agents on rivals’ platforms, Microsoft’s directory is a mirror of a record held elsewhere. With AWS also accepting outside agents in its registry, many large buyers are likely to hold more than one list of the same agents. The second-order effect falls on incident response. A responder’s first move will be to disable the agent in Entra, and for a rival’s agent that will not stop it, so the incident runbook must say where to go next and who answers there.
Exhibit 4 follows an agent through five steps, from being named to being stopped, and grades how much of each Microsoft has written.
Greyhound Research · Exhibit 4 · The path of an agent’s authority
Microsoft has written the name and the machine, not the limit
Five steps from giving an agent a name to being able to stop it, read against what Microsoft had documented by November 19, 2026.
The unwritten steps decide what an agent can do. That is where the buyer’s own rule has to go first.
Exhibit 4 sets out five steps of an agent’s authority as a numbered list, and shows Microsoft has written the first two and not the last two. Step one, name: written, as Entra Agent ID reaches rivals’ agents through connected platforms, though the link to rivals’ platforms is read-only. Step two, house: written, with Container Apps Sandboxes generally available, while the AKS sandbox extension had no documentation. Step three, seal: partly written, with the Confidential Clean Room in limited preview, the other confidential computing items still in development, and no statement on agent memory. Step four, limit: not written, as Agent Grid had no documentation. Step five, stop: not written for rivals’ platforms, though Microsoft enforces on Windows devices. The grades are Greyhound Research analysis.
Microsoft has written the first two steps and part of the third. The limit at each tool call and the power to stop a rival’s agent are the parts not yet written, and they are the parts that decide what an agent can do. The three notes reach one finding from three directions. Isolation and sealing keep others out. Neither decides what the agent itself may do with the access it holds.
Greyhound Standpoint:
Greyhound Research’s view is that Microsoft has built the most complete directory and surrounding estate for agents of any vendor read for the series, and has left the layer that decides what an agent may do unwritten. When rivals’ agents get a Microsoft name, enforcement becomes the control. When agents get their own machines, authority becomes the control. When agents work inside the seal, attestation becomes the control. A name lets a company find an agent, isolation keeps other workloads out, and the seal keeps the cloud operator out. None of them limits what the agent does with the access it holds, which is where the exposure for data and money sits.
Identity programs have followed this arc before. Directories came first, and the discipline of limiting what powerful accounts may do followed later, at greater cost. Credit is due on several counts. Running agents on Azure is level with AWS and Google, and Microsoft leads on the identity, security, and Microsoft 365 estate around the agent, while AWS is ahead today on written rules at each tool call. A documented rule at the tool call would change this view. Before the next architecture review, CISOs should register every agent as a privileged account with a named sponsor and map where its credentials are issued. Regulated buyers should commit sensitive data only once the proof, its checker, and the agent’s memory are documented.
The Deeper Read · About 3 minutes
Select a question to open the full answer
1What does the note on agent identity find?
A directory entry is not a control. The companion note finds that Microsoft names eleven connected platforms while its documentation lists seven, syncs only when an administrator asks, and does not promise to remove agents deleted at the source. On employees’ computers Microsoft does enforce, through Defender, Intune, and Windows containers, with a warning that a block can arrive after a tool has run. Its advice is to use Agent 365 as the inventory of record and keep the power to stop each agent with the platform that issues its credentials. Microsoft is not alone in bidding for the cross-vendor list: AWS’s agent registry, generally available since August 31, 2026, also accepts agents running outside AWS. The note finds Microsoft ahead on reach, AWS ahead on rules at each tool call, and no vendor documenting enforcement on a rival’s platform.
Microsoft’s own description agrees. Ray Smith, Microsoft’s corporate vice president for the Agent 365 product, described Agent 365 in a partner’s launch release as the observability platform for AI, helping organizations turn shared visibility into management, governance, and security decisions. Security partners announced the same week that they would add runtime evidence and enforcement alongside it. Observability is a real and useful layer. The decisions it informs still have to be written by the customer.
Why the word observability matters. Ray Smith’s choice of word is precise, and it matches the documentation’s read-only label. An observability platform shows what agents do. By that description, it does not decide what they may do. Buyers should take Microsoft at its word here. The security partners’ announcements the same week point the same way: enforcement is expected to come from a mix of Microsoft and other vendors, which means the buyer will be the one assembling it.
In the source’s own words
2What does the note on Azure agent infrastructure find?
Ready to pilot. The companion note finds that Ignite made running agents on Azure ready to pilot. Almost all of it is in preview, with Cobalt 200 and Container Apps Sandboxes generally available. It finds that Context Cache saves money only where agents reread the same long text and is a new store of data to govern, since it keeps processed text for 1 to 30 days counted from last use, so a cache in steady use does not expire. Its section on confidential computing agrees with the companion note: one limited preview and two items still in development. It places lock-in in an agent’s identity, memory, and records, not in the model it calls, and sets out ten moves.
3What does the note on confidential computing find?
The proof matters more than the lock. The companion note finds three announced items without prices or release dates: one limited preview, the clean room, which restates a June preview, and two items still in development. Microsoft has not said whether agent memory and cached context sit inside the seal, and its Ignite demonstration checked the hardware’s proof with a local verifier, with remote attestation described as an architectural direction, while Google already offers a verifier it does not own. Its advice is to pilot on what is generally available and commit regulated data only when the proof, its checker, and the agent’s memory are documented.
In the source’s own words
↑ Back to the section guide
Part 3The Eight Notes In Brief
The Defender, The Model, And The Exit: Perception, MAI, And Activate
Greyhound SpotlightIn three areas Microsoft now plays two roles at once. It supplies the security agents and their price, sells its own models beside its partners’, and sells both the way out of Salesforce and a way to stay.
Microsoft Perception, a team of AI security agents inside Microsoft Defender, became generally available, though three of Microsoft’s own pages still call it a preview. The companion note on Perception finds that its Triage Agent closes alerts it judges to be false alarms without asking anyone first, and Microsoft says it covers about 80% of alerts in a typical Defender queue. The note reads that figure as coverage, not accuracy. Its price has a meter and a calculator but no published rate card, and Microsoft’s own pages give three versions of the Sentinel offer for E5 and E7 customers.
Microsoft also put its own MAI models on sale beside the OpenAI and Anthropic models it resells. The companion note on MAI models finds that MAI grows first inside Microsoft’s own products, starting with the Copilot model picker. It is a credible option for everyday coding, routing, and classification, likely to become a firm price anchor once list prices are published and others can test it, with cost claims measured at a promotional price and contract terms still catching up with fast product progress. Microsoft’s copyright protection page does not yet name MAI models. MAI Licensed Weights, which would let a company run a tuned MAI model in its own Azure account, has no price or date. The note on Dynamics 365 Activate finds Microsoft selling the exit from Salesforce and the stay with it in the same week, with both roads ending at Copilot.
In each of the three areas, the buyer needs a record Microsoft does not mark. For Perception, it is a regular check of what the agents closed. For MAI, it is the company’s own test of a model on its own code, and its own rule for which model serves which task. For Activate, it is a priced, tested plan for leaving that the buyer owns whether or not it moves.
The new element is how far Microsoft now competes with the companies it works beside. It resells OpenAI and Anthropic models while selling its own, and in the same week it sells a road out of Salesforce and a way to stay with it. Rivals are likely to answer at renewal time, which gives buyers more room to negotiate than they had a year ago. The second-order effect most coverage misses sits in the security team. When agents close alerts without asking, analysts review fewer cases, and over time the skill to judge a closure can thin. A regular sample of agent decisions keeps that skill in practice as well as checking the agents.
Greyhound Standpoint:
Greyhound Research holds that when a vendor plays two roles at once, the buyer’s own record becomes the control. When agents close the alerts, the audit becomes the control. When the platform owner ships its own models, model choice becomes the control. When leaving gets cheaper, the exit plan becomes the control. Two roles are not a problem in themselves, but the party reporting on the work also has an interest in the result, so an independent measure belongs beside the vendor’s own.
Each area also shows real progress. Perception brings red, blue, and green team agents into one console. MAI is a credible option for everyday coding and routing, and is likely to become a firm price anchor once list prices are published, the models are sold beyond Microsoft’s own tools, and others can test them. Earlier consolidation cycles taught the discipline this calls for: use the vendor’s tooling, and check its claims against the company’s own data. The limits are that Perception has no published rate card, MAI’s cost claims rest on a promotional price, and Activate’s speed figures are partner forecasts and company claims. SOC leads should audit a weekly sample of agent-closed alerts. AI platform leads should pilot MAI on the company’s own work and pin the model for each task. CIOs should commission Activate’s discovery before the next Salesforce or SAP renewal.
The Deeper Read · About 3 minutes
Select a question to open the full answer
1What does the note on Perception find?
Let the agents work, and check their work. The companion note records that the Book of News calls Perception generally available while three of Microsoft’s own pages still say preview: the older product page calls it a preview, and two documentation pages an invitation-only limited preview. Its status therefore rests on the Ignite announcements. It finds Microsoft ahead on breadth, with red, blue, and green team agents in one console, and on bundling a cheaper SIEM for E5 and E7. The agents that defend the company are insiders too, and need narrow rights and reviews. It finds Perception priced separately from Security Copilot, whose capacity units many E5 customers already hold. Among rivals, CrowdStrike lists approval gates, under which an agent pauses for an analyst before a sensitive tool call, as available today, while Perception’s Triage Agent has no approval step before a closure.
Why the status label matters. A status label is more than a formality. It decides which service terms, support commitments, and compliance coverage apply. When the Book of News says generally available and three Microsoft pages still say preview, a buyer cannot tell from the pages alone which terms govern its use. The practical answer is to ask Microsoft to confirm the status in writing for the buyer’s own contract, and to file that confirmation with the pilot decision.
In the source’s own words
2What does the note on MAI models find?
Supplier, reseller, router, and rival. The companion note finds that MAI Code 2 is first an expansion inside Microsoft’s own products, with a wider contest in the open market likely to follow, and that by Microsoft’s own account it is not a replacement for OpenAI or Anthropic models on the hardest work. Microsoft disclosed its test conditions more fully than most launches do. Its headline cost ratios use a promotional price with no list price yet published, an earlier MAI coding model was replaced about eleven weeks after reaching business customers, and the smaller coding model was trained in part on prompts from individual GitHub Copilot users who had not opted out. Microsoft corrected its own blind preference figure on November 18, and both of its pages now give 64%, an evaluation that has not been independently reproduced. Licensed Weights also has a precursor: on October 15, 2026, Microsoft AI said its MAI-Base-2 base model would let it license model weights to trusted partners through Foundry. Its advice is to pilot MAI on the company’s own work, budget on the cost of each change that ships, keep the right to pick and pin the model, and explore licensed weights with Microsoft while price, export, indemnity, and update terms are agreed.
In the source’s own words
3What does the note on Dynamics 365 Activate find?
The discovery report is the value. The companion note finds no published price for Activate, a SAP tool in private preview while SAP’s mainstream maintenance for ECC ends at the end of 2027, and speed figures that are partner forecasts and company claims without a method. Microsoft’s own pages disagree on the SAP tool’s status, and a Microsoft partner page still describes the Salesforce tool as a limited public preview. It records that Microsoft names Comcast and Fusion5 among Activate’s customers, though Fusion5 is a Microsoft partner, and that Comcast’s Sathish Arumugam credits the discovery step with more informed planning, which speaks to the assessment rather than a completed move. Accenture, the design and implementation partner for Copilotforce, calls itself customer zero. It finds that Copilotforce keeps Salesforce’s own permissions and that its licensing is not written, so a seller could be paid for twice. Its advice is to run the discovery, price the exit, and keep press-release timelines out of contracts.
↑ Back to the section guide
Part 4The Risks And The Counter-Argument
Risks To Watch: Where The Series’ Controls Can Fall Short
Greyhound SpotlightNone of the five risks needs Microsoft to get anything wrong. Each starts when a buyer’s own rule is missing.
Greyhound Research sees five risks that run across the series. Each appears in more than one companion note, and each shows first inside the buyer’s own organization, in a pilot list, a policy, a register, or a board report. That makes them cheap to catch early and slow to unwind later.
These risks differ from the ones most technology risk registers were built for. Registers have tended to list vendor failures, such as an outage, a breach, or a missed service level, each with a contract remedy attached. The five here are gaps in the buyer’s own records, and no service credit covers them. Greyhound Research expects the first signs to appear in expense reviews and internal audit findings rather than in security incidents. The second-order effect is on accountability. When a loss traces back to a rule nobody wrote, the company has no supplier to hold to account, and the board will ask who inside the firm owned the gap.
Table 3 sets each risk beside its early warning and its owner. Every early warning can be checked without help from Microsoft.
Greyhound Research · Table 3 · Risk register for the series
Five risks, and each starts in the buyer’s own paperwork
Five risks that run across the Microsoft Ignite 2026 series, each with its early warning and its owner.
None of the five needs a Microsoft error. Each is cheapest to catch in the buyer’s own records this quarter.
Table 3 lists five risks that run across the Microsoft Ignite 2026 series, each with an early warning in the buyer’s own estate and an owner. Preview drifts into production, warned by a pilot group that grows without a new decision, owned by the CIO. A meter without a policy, warned by a new metered service joining existing policies by default, owned by the CFO and FinOps lead. A name without a stop, warned by an agent inventory with no column for where credentials are issued, owned by the CISO. Unwritten data stores, warned by a data register with no entry for agent memory or caches, owned by the data protection officer. The seller reports on its own work, warned by a board report built only from Microsoft’s dashboards, owned by the chief risk officer. The risks are Greyhound Research analysis.
The five share a cause: a belief that a released or bundled tool comes with the rule it enforces. Preview drift and unwritten data stores come from treating test terms as contract terms. A meter without a policy and a name without a stop come from treating a tool as a control. The last risk is the newest. Microsoft now meters the spend, scores the value, grades its own security agents, and sells its own models, so a board that reads only Microsoft’s dashboards is reading the seller’s own account of its work.
Greyhound Standpoint:
In Greyhound Research’s reading, the five risks share one cause and one remedy. Each begins when a company treats a released or bundled tool as if it came with the rule it enforces, and each is cheaper to prevent with a written rule than to repair after an incident. None requires Microsoft to make an error. A pilot group that grows without a new decision, a metered service that joins a budget by default, or a register with no column for where an agent can be stopped is a gap in the buyer’s own paperwork, and the early warning sits there too.
Operational risk has tended to build this way in earlier technology shifts. Many of the incidents that reach boards begin as small, unowned exceptions that persist for months before anyone measures them. None of the five reflects a fault in Microsoft’s products, and none should be read as a forecast that harm will occur. General availability terms for the agent features and a published rate card would take two of the risks partly off the buyer’s desk, and would ease this view. Chief risk officers should test all five warnings this quarter, name an owner for each, and report the result at the next board risk review.
↑ Back to the section guide
Part 4The Risks And The Counter-Argument
The Strongest Objection: Microsoft Will Write The Controls Itself
Greyhound SpotlightThe strongest objection to this note is that Microsoft already sells the controls, in Agent 365, Entra, Purview, Defender, and E7. That part is right.
The objection deserves its full weight. Microsoft ships more control tooling for agents than any rival read for the series. It leads on the reach of its directory, on the breadth of its security agents, and on publishing what a task costs. E7 bundles Microsoft 365 E5, Copilot, and Agent 365 in one license. On this view, a company that buys the suite and switches on its controls has done the work, and a written rule from the buyer adds paperwork, not protection.
The objection has force because the controls are already paid for. A company on E7 holds Entra Suite and advanced Defender, Intune, and Purview capabilities in the same license, and switching them on can feel like the end of the work. Greyhound Research expects Microsoft to narrow part of the gap over time with templates and defaults, as vendors usually do once a product matures. The second-order effect is easy to miss. When a company’s controls live inside a license tier, its control framework becomes part of the renewal. Moving down a tier, or moving a workload elsewhere, then removes controls as well as features, and that belongs in the renewal analysis.
Exhibit 5 tests each part of the objection against the evidence in the series. Two parts stand, and two do not hold.
Greyhound Research · Exhibit 5 · The objection held to the evidence
Two parts of the objection stand, and two do not hold
The fair counter-case to this research note, that Microsoft will write the controls itself, part by part against the evidence in the series.
The objection holds for the tools, not for the rules. Switch the tools on and own the rules they enforce.
Exhibit 5 holds four parts of the strongest objection to this research note against the evidence, as four cards, and shows two stand and two do not hold. Microsoft ships more control tooling than its rivals: stands, as it leads on directory reach, bundled security agents, and publishing what a task costs. One suite simplifies buying the controls: stands, as E7 bundles Microsoft 365 E5, Copilot, and Agent 365 at USD 99 per user. The tools are the control: does not hold, because a spending limit is a ceiling, the link to rivals’ agents is read-only, and Autopilot’s audit record is not guaranteed complete. Buyers can wait for general availability: does not hold on timing, because the new front door reaches every licensed user this winter. The verdicts are Greyhound Research analysis.
The tooling and the bundle are real, and buyers should use both. The claim that the tools are the control does not hold on the series’ own evidence. A spending limit is a ceiling that stops work, not a budget. The link to rivals’ agents is read-only. Autopilot’s audit record is not guaranteed complete. The claim that buyers can wait does not hold on timing, because the doorway reaches every user before the agent terms are written.
Greyhound Standpoint:
Greyhound Research accepts the objection for the tools and does not accept it for the rules. Microsoft ships the strongest set of agent controls of any vendor read for this series, across Agent 365, Entra, Purview, and Defender, and E7 brings many of them into one license. Buying them and switching them on is sensible. The objection weakens at one step. A control enforces a rule, and the rule has to come from someone who knows the business. A spending limit cannot know which workflow must keep running at month end, and a directory cannot know which rival’s agent should be stopped first.
Seasoned buyers have heard versions of this argument in earlier consolidation cycles, from integrated enterprise application suites to bundled security platforms. Each time the bundle simplified purchasing, and the policy work stayed with the customer. That is the normal division of labor between the vendor, who builds the mechanism, and the customer, who decides its use. The view would shift if Microsoft published a documented rule at the tool call and a per-platform list of what it can enforce. Until then, the two together are the control, and either alone is not. Leaders should switch Microsoft’s tools on at the next pilot gate and, in the same decision, approve the written limits those tools will apply, each with a named owner.
The Deeper Read · About 1 minute
Select a question to open the full answer
1Why do the tools not settle the control?
Three findings from three notes. The note on agent economics finds that a spending limit reserves nothing and stops the user’s work for the rest of the month when reached. The note on agent identity finds the link to rivals’ platforms read-only. The note on Copilot as the front door finds that Autopilot activity is not a guarantee of a complete audit record. In each case Microsoft’s tool works as designed. The rule it needs is the buyer’s.
The bundle is real. Microsoft says E7 unifies Microsoft 365 E5, Microsoft 365 Copilot, and Agent 365, and adds Entra Suite and advanced Defender, Intune, and Purview capabilities. That simplifies buying the tools. It does not decide who in the company may use them for what.
What “unifies” tells a buyer. Microsoft’s word for E7 is accurate for buying. One contract and one price replace several. Unifying the purchase does not unify the decisions. Each tool in the bundle still asks a different team a different question, from Purview’s data labels to Defender’s response rules, and the bundle makes those questions arrive together rather than one product at a time.
In the source’s own words
↑ Back to the section guide
Part 5What To Do, By Role
The Greyhound CXO Runbook: Ten Moves Across The Series
Greyhound SpotlightEvery move produces a document the buyer owns, from an enrollment list, a spending policy, and an agent register to a status record, a renewal analysis, and a rehearsed fallback.
Ten moves follow from the series as a whole. Each companion note sets out its own ten moves for its own area. These ten sit above them, at least one for each leader who will own part of a company’s agent workforce. None waits for Microsoft, because each uses controls the buyer already holds.
Greyhound Research has kept the moves to documents on purpose. Earlier platform shifts often produced programs and committees whose output was hard to inspect. A list, a policy, a register, or a clause can be read, dated, and checked, which makes each move easy to audit and hard to defer quietly. The first versions will be imperfect and should be revised as Microsoft publishes terms. The benefit most coverage misses is portability. None of the ten documents is specific to Microsoft. A spending policy, an agent register, or an exit clause written now will serve as well for agents from AWS, Google, or Salesforce, so the work reduces dependence on any one vendor rather than adding to it.
Table 4 sets the ten moves beside the assumption each corrects, its evidence, and its owner. Two of the ten finish only when Microsoft publishes its terms.
Greyhound Research · Table 4 · The Greyhound CXO Runbook by owner
Ten moves across the series, and none waits on Microsoft to start
Ten series-level moves for the leaders who will own a part of Microsoft’s agent estate, with the assumption each corrects, its evidence, and its owner.
Treat all ten as this quarter’s work, not next year’s. Only two need Microsoft’s published terms to finish.
↓Select a move to open its full text in The Deeper Read below
Table 4 sets out the ten moves of the series-level 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 publishes terms. The moves are: sign on general availability terms and enroll named groups only, write the spending policy before the meter runs, register every agent as a privileged account and map where it can be stopped, map where agent data rests, write model choice and the exit into every renewal, keep an audit of agent work that Microsoft does not mark, retrain users by role before the front door moves, approve features rather than product names and get each status in writing, price the controls inside the license tier before any renewal, and rehearse a fallback for the agent work that cannot stop. The moves are Greyhound Research analysis.
The two that finish later, the first move on signing terms and the fifth on renewals, wait on terms Microsoft has not yet published. The questions that follow ask for those terms, and each maps to a move a buyer can make meanwhile. The other eight can be finished this quarter with documents and tools the buyer already holds. Each move points to the companion notes whose own Runbooks carry the detail.
The Deeper Read · About 5 minutes
Select a move to open its full text
1CIOs: sign on general availability terms, and enroll named groups only.
Exhibit 1 and Table 1 show the released products beside agent features still on preview terms. This move corrects the belief that a keynote status is a contract status. Its action is to sign production commitments only on general availability terms, to enroll named pilot groups, not all users, in Frontier and previews, and to record each enrollment as a decision with an owner. The companion notes on Copilot as the front door and Azure agent infrastructure carry the detail. The decision sits with the CIO, together with procurement.
The order of the moves matters as much as the moves. Signing on released terms and enrolling named groups come first because every later document depends on knowing which agents are in use and under which terms. A spending policy, a register, or an audit sample written before that list exists will describe an estate that has already changed.
2CFOs: write the spending policy before the meter runs.
Table 3 shows a meter without a policy as a risk that starts by default. This move corrects the belief that a price list makes AI spend predictable. Its action is to switch off automatic coverage of new metered services, write one spending policy per business unit, budget the credit line as a range, and decide what happens at the limit for each critical workflow. The companion notes on agent economics and Perception carry the detail. The decision sits with the CFO, together with the FinOps lead.
3CISOs: register every agent as a privileged account, and map where it can be stopped.
Exhibit 4 shows Microsoft has written an agent’s name and machine but not the limit or the stop. This move corrects the belief that a directory entry is a control. Its action is to register every agent, security agents included, as a privileged account with a named sponsor, and to record for each one where its credentials are issued and who can halt it. The companion notes on agent identity, infrastructure, and Perception carry the detail. The decision sits with the CISO, together with identity leads.
4Data protection officers: map where agent data rests, and keep regulated data in written places.
Exhibit 4 and Table 3 show agent memory, cached context, and Frontier features holding data outside written terms. This move corrects the belief that a sealed or licensed service covers everything the agent touches. Its action is to list every place an agent’s data rests during a task, mark which places have written terms, and keep regulated data out of the rest. The companion notes on Copilot as the front door, Azure agent infrastructure, and confidential computing carry the detail. The decision sits with the data protection officer.
5Procurement: write model choice and the exit into every renewal.
Exhibit 3 shows price and terms unwritten in seven of the eight areas. This move corrects the belief that model and platform are settled at signing. Its action is to write the right to pick and pin a model, copyright cover for each route, and the export of agent identity, state, and records into every Microsoft renewal, and to bring a priced exit plan to every Salesforce and SAP renewal. The companion notes on MAI models and Dynamics 365 Activate carry the detail. The decision sits with procurement, together with general counsel.
6Chief risk officers: keep an audit of agent work that Microsoft does not mark.
Exhibit 5 and Table 3 show the seller metering the spend, scoring the value, and grading its own agents. This move corrects the belief that the vendor’s dashboard is the record. Its action is to keep a regular, independent sample of agent decisions, from closed alerts to Autopilot actions, and a value measure drawn from the business’s own records, and to report both to the board. The companion notes on Perception, agent economics, and Copilot as the front door carry the detail. The decision sits with the chief risk officer, together with the CIO.
7Change and adoption leads: retrain users by role before the front door moves.
Table 1 ranks the new front door first because it reaches every licensed user this winter, and Exhibit 5 shows it arriving before the agent terms. This move corrects the belief that a new starting page needs no change program. Microsoft’s rollout notices carry no training guidance, so the control is the buyer’s own training plan. Its action is to retrain users by role this quarter, starting with the named groups enrolled under the first move, to brief the help desk before Home arrives, and to tell each group which features are released and which are still on test terms. The companion note on Copilot as the front door carries the detail.
Training also shapes the bill. A rollout that gets people to use agents will, by design, raise it, so each training wave should be agreed with the owner of the spending policy in the second move. The decision sits with change and adoption leads, at each pilot gate.
8General counsel: approve features, not product names, and get each status in writing.
Table 1 shows status set by feature, with released and preview items under one product name. Of the 59 announcement headings in the Book of News, by Greyhound Research’s count, 28 mix the two. This move corrects the belief that one product name carries one status. Microsoft’s pages also differ. The Book of News calls Perception generally available, while three Microsoft pages still say preview. Its action is to list features, not product names, in the approvals, risk registers, and contract schedules it already keeps, to cite for each feature the most specific Microsoft page with the date it was read, and to ask Microsoft to confirm the status in writing for the buyer’s contract. The companion notes on Perception and Dynamics 365 Activate record where the pages disagree.
The confirmation is filed with the pilot decision and checked again at renewal, since statuses are likely to keep moving. The decision sits with general counsel, at each pilot gate and renewal.
9CFOs: price the controls inside the license tier before any renewal.
Exhibit 5 shows that one suite simplifies buying the controls, with E7 bundling Microsoft 365 E5, Copilot, and Agent 365 at USD 99 per user. This move corrects the belief that a license tier is a price decision alone. A company on E7 also holds Entra Suite and advanced Defender, Intune, and Purview capabilities in the same license, so its control framework becomes part of the renewal. Moving down a tier, or moving a workload elsewhere, then removes controls as well as features. Its action is to list, from the license records the buyer already holds, which agent controls depend on which tier, to name what would replace each one if the tier changed, and to put both in the renewal analysis beside the seat price. The companion note on agent economics carries the detail on the meter beside the seats.
The decision sits with the CFO, together with the CISO, before each Microsoft renewal.
10Chief risk officers: rehearse a fallback for the agent work that cannot stop.
Exhibit 2 ends with Ignite opening days after a Microsoft 365 outage, which Greyhound Research counts as the fourth multi-service Microsoft 365 incident of 2026. This move corrects the belief that the suite’s resilience covers the agents inside it. Enterprises have priced Microsoft 365 as a license rather than as a single point of failure, and agents raise the same question one level up. Work can also stop without an outage, because a spending limit, once reached, stops the user’s work for the rest of the month. Its action is to start from the company’s existing continuity plan, name the agent-supported processes that cannot stop, and rehearse for each a fallback that shares nothing with the suite, including its sign-in. A fallback that signs in through the suite shares its outage. The note on that outage carries the detail.
The decision sits with the chief risk officer, who reports the results of each rehearsal at the next board risk review.
↑ Back to the section guide
Part 5What 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 what leaves with the customer.
Every finding in the series rests on what Microsoft has published, and Microsoft alone can close the gaps the series names. Each companion note asks six questions of its own, and the note on Azure agent infrastructure asks ten. The six below sit above 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.
Questions like these carry more weight when they are put in writing and asked by several buyers at once. In past licensing transitions, the terms that many customers asked for tended to arrive sooner. Greyhound Research expects release terms and rates to be answered first, because Microsoft needs them to sell, and the export question last, because vendors seldom lead with the terms of leaving. The second-order effect is contractual. A written answer from an account team can be attached to an order form or a renewal schedule, which turns a briefing into a commitment the buyer can rely on. Asked only in a meeting, the same answer leaves no record.
Table 5 tracks the six questions against what Microsoft has said so far. Two are answered in part, and four not at all.
Greyhound Research · Table 5 · Questions for Microsoft, tracked
Two questions answered in part, four not at all
Six series-level questions only Microsoft can answer, against what it had stated by 1:20 a.m. UTC on November 19, 2026.
Ask in writing, and act meanwhile. A written answer can become a contract term, and no move waits on it.
↓Select a question to open its full text in The Deeper Read below
Table 5 tracks six series-level questions only Microsoft can answer against what it had stated by 1:20 a.m. UTC on November 19, 2026, and shows two answered in part and four not at all. Answered in part: whether every credit-using service and Perception will have a published rate, and what the 50 million agents count and what audit record each leaves. Not stated: when the agent features reach general availability and on which terms, which controls are enforced on each platform, where agent memory and Frontier data rest, and what leaves with the customer. Each question names the Runbook move it settles. The grading is Greyhound Research analysis.
Two answers would change this note’s reading most. One is a documented rule at the tool call, with a list of what Agent 365 can stop on each platform. The other is general availability terms for the agent features, with their coverage. Either would move part of the control back toward Microsoft’s product. None of the six is a trick question. Each asks Microsoft to write down what its products do or will do at release.
The Deeper Read · About 2 minutes
Select a question to open its full text
Q1When will the agent features reach general availability, and on which terms?
Said so far. In part for a few items. Copilot Code is due in December, and connected platforms complete in December. Autopilot, Workspaces, Today, Agent Grid, the AKS sandbox extension, the confidential computing items, and Licensed Weights have no date. The answer settles. When a pilot can become a production commitment, under the first Runbook move. Evidence that would settle it. Release dates with service levels and compliance coverage. Greyhound Research would update. Exhibit 1 and Table 1.
Q2Will every credit-using service, and Perception, have a published rate?
Said so far. In part. Seat prices are held and published. Several credit rates and a Perception rate card are not. The answer settles. Whether the spending policy of the second Runbook move can be a forecast. Evidence that would settle it. One published rate card with caps by unit. Greyhound Research would update. Exhibit 3.
Q3For each platform, which controls are enforced and which are only observed?
Said so far. Not stated as a list. Microsoft’s documentation calls the link to rivals’ platforms read-only. The answer settles. Where an agent can be stopped, under the third Runbook move. Evidence that would settle it. A per-platform enforcement matrix and a documented rule at the tool call. Greyhound Research would update. Exhibit 4.
Why read-only matters. The phrase is short and easy to pass over, but it already answers half of the question. A read-only link means Agent 365 can report on a rival’s agent and cannot change or halt it. The open half is whether that will change, and on which platforms first.
Q4Where do agent memory, cached context, and Frontier data rest, and under which terms?
Said so far. Not stated. Frontier terms leave out HIPAA coverage and three ISO standards, and Microsoft has not said whether agent memory sits inside the confidential seal. The answer settles. Which data places the fourth Runbook move can mark as written. Evidence that would settle it. A data boundary and retention statement for each agent feature. Greyhound Research would update. Exhibit 4 and Table 3.
Q5What leaves with the customer: identity, memory, records, and tuned models?
Said so far. Not stated. The answer settles. What the exit and model terms of the fifth Runbook move can rely on. Evidence that would settle it. A documented export path for agent identity, state, and audit records, and terms for licensed weights. Greyhound Research would update. Exhibit 3.
Q6What do the 50 million agents count, and what audit record does each leave?
Said so far. In part. Microsoft says the agents were registered since the May 2026 launch, and its Autopilot documentation does not guarantee a complete audit record. The answer settles. What the independent audit of the sixth Runbook move can sample. Evidence that would settle it. A defined count of active agents and a documented audit record for each agent type. Greyhound Research would update. Exhibit 5.
↑ Back to the section guide
Part 6The Final Greyhound Standpoint
Microsoft Ignite 2026: The Final Greyhound Standpoint
Greyhound SpotlightFour signals within twelve months would move this position, and Microsoft controls all four.
Greyhound Research’s position is that Ignite 2026 made AI agents part of the enterprise workforce, and that this changes where control sits. Microsoft gave agents names, machines, budgets, sealed data, and models of its own, and made Copilot the door every employee walks through. When agents join the workforce, written authority becomes the control: who may enroll, spend, act, and leave, set down by the buyer before the agent starts work. That is not a criticism of the products. It describes what any capable tool needs before it can be trusted with real work.
The judgment rests on a gap between product and terms. On products, Microsoft leads on the breadth of what it ships and on the identity, security, and Microsoft 365 estate around the agent, as the companion notes find area by area. On terms, it trails its own products. The agent features sit in Frontier and preview, several rates are unpublished, and the rule at each tool call is not yet written. The tools are ready to enforce rules that many companies have not yet drafted, and the cost of that gap lands with the buyer, as unplanned spend, unclear accountability, or data held outside written terms.
Earlier platform shifts suggest the gap is normal and, in time, temporary. Client-server computing, software as a service, and the first wave of public cloud each shipped capability ahead of the contracts, rate cards, and controls that later made it routine. In each, the buyers who fared better tended to be those who adopted what was released and wrote their own rules for the rest, rather than those who waited or those who signed on the vision. Microsoft’s record over the past year supports that approach. It turned the previews of Ignite 2025 into priced, released products, which justifies planning on its stated dates while still contracting only on released terms.
The evidence has limits. This note summarizes eight companion notes and relies on their reading of Microsoft’s documentation, which each sets out in full. Most agent features are previews, and Microsoft’s pages word some statuses differently. Company figures, including the 50 million agents and the cost claims for MAI models, are Microsoft’s own. Statuses and claims are as each company published them through 1:20 a.m. UTC on November 19, 2026.
Four signals would move this position within twelve months. Each would move part of the control back into Microsoft’s product. They are general availability terms for the agent features, one published rate card, documented enforcement where the agent runs, and written boundaries for agent data with an export path. Exhibit 6 sets those signals side by side with what each would change, and all four sit with Microsoft.
Greyhound Research · Exhibit 6 · Signals that would move the position
Four signals in twelve months would move this position
What would move Greyhound Research’s series-level judgment within twelve months, and what each would change.
Enforcement where the agent runs is the signal that would move this view furthest. Watch it first.
Exhibit 6 lists four signals that would move Greyhound Research’s series-level position within twelve months, each controlled by Microsoft, and one event outside its control. General availability terms for the agents would let buyers widen enrollment. One rate card for credits and Perception would make the spending policy a forecast. Enforcement where the agent runs, at the tool call and on each platform, would turn the directory into a control. Written boundaries for agent memory and an export path would settle where agent data rests and what leaves with the customer. A rival’s announcement could reset the comparison. The signals are Greyhound Research analysis.
One event outside Microsoft’s control could reset the comparison: a rival’s announcement on agent identity, pricing, or enforcement at its own conference. Of the four signals, enforcement where the agent runs would matter most, because it decides whether a name in Microsoft’s directory carries the power to stop. Until the signals arrive, the balanced course is to use what Microsoft has released on its merits and to write down the rules for everything an agent may do. CIOs and boards should make both decisions at the next annual planning cycle, approving the released products for use and the written documents of the ten Runbook moves, which set an agent’s authority, before any agent moves beyond pilot.
↑ Back to the section guide
Part 7Appendix, 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 on November 18, 2026, and read again on November 19, 2026, between 01:05 and 01:20 UTC, and the companion notes in their final text after their pre-launch audit the same night. 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 blogs8 sources, 47 extracts
Partner announcements1 sources, 2 extracts
Media1 sources, 5 extracts
The Microsoft Ignite 2026 series8 sources, 16 extracts
Research this note builds on5 sources, 8 extracts
↑ Back to the section guide
Part 7Appendix, 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, prices, and terms, and prove what Microsoft said rather than that the thing is true. The media report what their authors saw and were told. The companion notes set out their own sources in full. All sources were read on November 18, 2026, and read again on November 19, 2026, between 1:05 and 1:20 a.m. UTC.
Microsoft announcements and blogs
Microsoft (2025a) Microsoft Ignite 2025 | Book of News. Microsoft News, November 18. Available at: https://news.microsoft.com/ignite-2025-book-of-news/
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) 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/
Microsoft (2026c) 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/
Microsoft (2026d) What’s new in Microsoft Agent 365: Ignite 2026. Microsoft Agent 365 Blog, Microsoft Community Hub, November 17. Available at: https://techcommunity.microsoft.com/blog/agent-365-blog/whats-new-in-microsoft-agent-365-ignite-2026/4571753
Althoff, J. (2026) Introducing the First Frontier Suite built on Intelligence + Trust. The Official Microsoft Blog, March 9. Available at: https://blogs.microsoft.com/blog/2026/03/09/introducing-the-first-frontier-suite-built-on-intelligence-trust/
Bhatia, V. (2026) What’s New in Azure Confidential Computing, Ignite 2026. Microsoft Azure Confidential Computing Blog, Microsoft Community Hub, November 17. Available at: https://techcommunity.microsoft.com/blog/azureconfidentialcomputingblog/what%E2%80%99s-new-in-azure-confidential-computing-%E2%80%94-ignite-2026/4573909
Shaw, F. X. (2025) From idea to deployment: The complete lifecycle of AI on display at Ignite 2025. The Official Microsoft Blog, November 18. Available at: https://blogs.microsoft.com/blog/2025/11/18/from-idea-to-deployment-the-complete-lifecycle-of-ai-on-display-at-ignite-2025/
Partner announcements
Zenity (2026) Zenity expands AI agent security coverage across the Microsoft ecosystem. Business Wire, November 17. Available at: https://www.financialcontent.com/article/bizwire-2026-11-17-zenity-expands-ai-agent-security-coverage-across-the-microsoft-ecosystem
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
The Microsoft Ignite 2026 series
Greyhound Research (2026a) Microsoft Copilot As The OS For Work – When The Front Door Moves, Frontier Enrollment Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-copilot-as-the-os-for-work-when-the-front-door-moves-frontier-enrollment-becomes-the-control/
Greyhound Research (2026b) Microsoft Agent Economics – When Work Is Billed By The Task, The Spending Policy Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-agent-economics-when-work-is-billed-by-the-task-the-spending-policy-becomes-the-control/
Greyhound Research (2026c) Microsoft Agent Identity – When Rivals’ Agents Get A Microsoft Name, Enforcement Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-agent-identity-when-rivals-agents-get-a-microsoft-name-enforcement-becomes-the-control/
Greyhound Research (2026d) 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/
Greyhound Research (2026e) Microsoft Confidential Computing – When Agents Work Inside The Seal, Attestation Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-confidential-computing-when-agents-work-inside-the-seal-attestation-becomes-the-control/
Greyhound Research (2026f) Microsoft Perception – When Agents Close The Alerts, The Audit Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-perception-when-agents-close-the-alerts-the-audit-becomes-the-control/
Greyhound Research (2026g) Microsoft MAI Models – When The Platform Owner Ships Its Own Models, Model Choice Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-mai-models-when-the-platform-owner-ships-its-own-models-model-choice-becomes-the-control/
Greyhound Research (2026h) Microsoft Dynamics 365 Activate – When Leaving Gets Cheaper, The Exit Plan Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-dynamics-365-activate-when-leaving-gets-cheaper-the-exit-plan-becomes-the-control/
Research this note builds on
Greyhound Research (2025a) 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 (2025b) Microsoft 365 Outage on June 17, 2025: What Happened? Research note, June 18. Available at: https://greyhoundresearch.com/microsoft-365-outage-on-june-17-2025-what-happened/
Greyhound Research (2025c) 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 (2026i) 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 (2026j) 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/
↑ Back to the section guide
Part 7Appendix, Sources, And Disclosures
Disclosures: Independence, Financial, Intended Use, Methodology, Authoring, And Copyright
The evidence in this research note is current through November 19, 2026, with an evidence cutoff of 1:20 a.m. UTC that day (8:20 p.m. ET on November 18), after a pre-launch re-verification of every source. The companion notes it summarizes each state their own cutoff. 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, chief financial officers, chief information security officers, data protection officers, chief risk officers, procurement and vendor management leaders, general counsel, board members, and the press. It summarizes Greyhound Research’s eight-note series on Microsoft Ignite 2026 and reads Microsoft’s Ignite announcements, keynote, and product blogs, with Ignite 2025 as the baseline, to inform decisions on agents, Copilot, spending, identity, security operations, models, 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 at 1:20 a.m. UTC on November 19, 2026, and can change as the companies named publish more. Product availability, status, features, and prices are described as each company published them through 1:20 a.m. UTC on 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 twenty-three documents listed in Sources And References, in five classes, and every factual claim is verified against the document that supports it. The positions of the eight companion notes are summarized from their final texts, and their evidence is set out in each note. The passages relied on are quoted in The Deeper Read of the section that uses them, and the other words taken from each source are set out in the appendix. A finding that something is not stated or not documented is bounded to the documents the companion notes name, as they stood when each was last read on November 19, 2026. Statuses are given as each company states them.
The ranking of announcements in Table 1 is Greyhound Research’s judgment of buyer consequence. Two dates in Exhibit 2, Cowork’s general availability on June 16, 2026, and the introduction of Project Perception on July 27, 2026, are carried from the companion notes that verified them. Company figures, including the 50 million registered agents and Microsoft’s performance and cost claims, are Microsoft’s own and are not used as measures. The Greyhound CIO Pulse 2026 figure is cited as published in Greyhound Research’s research note of November 5, 2026. The count of Book of News headings in What Microsoft Announced is Greyhound Research’s own, made from the Book of News as read on November 19, 2026. No composite figure is computed. No Greyhound Fieldnotes are quoted, and no factual claim in this research note rests on unpublished material.
The through-line, the readings in Exhibits 1 to 6 and Tables 1 to 5, the risks, the Greyhound CXO Runbook, the questions for Microsoft, and the signals 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.
Copyright Policy
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.
Research Note In Two Minutes
Note synopsis · AI drafted · Analyst reviewedAt Microsoft Ignite on November 17, 2026, Microsoft treated AI agents as part of the workforce rather than a feature of its software. Agents now get a name in Microsoft’s directory, a sealed-off machine of their own, a budget drawn from a shared meter, and a choice of Microsoft’s own models. Copilot became the front door to Microsoft 365, security agents began closing alerts on their own, and a released tool now helps companies leave Salesforce. Much of what decides cost and risk is still in preview or Microsoft’s early-access Frontier program.
Greyhound Research’s position is that Ignite 2026 changed who holds the control. In every area its eight-note series examines, Microsoft shipped a capable tool and left the rule that tool enforces for the buyer to write. When agents join the workforce, written authority becomes the control: who may enroll, spend, act, and leave, set down by the buyer before the agent starts work. Greyhound Research reads this as a normal stage of a platform shift. The capability has arrived ahead of the terms, as it did with software as a service and public cloud, and the buyers who fare best tend to adopt what is released and write their own rules for the rest.
Three findings carry the argument. First, Microsoft has written the first steps of an agent’s authority, its name and its machine, and not yet the rule at each tool call or the power to stop a rival’s agent. Second, the meter now sits beside every seat price, and several of its rates are unpublished. Third, Microsoft now meters the spend, scores the value, grades its own security agents, and sells its own models, so buyers need records Microsoft does not mark.
The evidence has limits. This note summarizes eight companion notes and does not repeat their evidence, which each one sets out in full. Most agent features are previews, and Microsoft’s pages word some statuses differently. Greyhound Research names the signals that would change its view within twelve months. Until they arrive, the advice holds: use what Microsoft has released, and write down the rules for everything an agent may do.
This research note is available to read in full only on greyhoundresearch.com, at https://greyhoundresearch.com/microsoft-ignite-2026-when-agents-join-the-workforce-written-authority-becomes-the-control/ . Greyhound Research permits quotation of up to one hundred words with attribution and a link to the published page. For licensing requests, contact the Greyhound Research Community Relations Team at connect@thofgr.com.
In This Research Note
Section guide · AI drafted · Analyst reviewed