Microsoft will introduce a single enterprise subscription SKU that includes both GitHub Copilot and Microsoft 365 Copilot, by May 18, 2028.
Bottom line
Microsoft has built meaningful commercial and technical bridges between the two Copilots, but the evidence still stops short of a single enterprise subscription SKU including both.
The evidence and what would settle it
Where it stands
On September 11, 2025, Microsoft announced plans to absorb three role-based Copilots into its $30-per-user-per-month Microsoft 365 Copilot package. Microsoft 365 E7 became generally available on May 1, 2026; its listed suite components combine E5, Microsoft Copilot, Entra Suite and Agent 365, without GitHub Copilot. On June 16, Microsoft announced Agent Factory’s single consumption model spanning Microsoft 365 Copilot and GitHub Copilot, with user subscription licenses as the foundation.
On September 25, Microsoft announced Home, Code and Autopilot, with Code using GitHub Copilot’s underlying technology and pricing combining subscriptions with consumption. On October 28, Microsoft announced its company-wide adoption of the harness built by GitHub’s engineering team. That day, GitHub also included Copilot access for every licensed GitHub Enterprise user at enterprises served by a GitHub or Microsoft account team, with AI usage metered against the enterprise budget rather than included monthly credits.
The case against
The case is weaker than the unified-app language suggests: a September LinkedIn post claimed both products were bundled, whereas Microsoft’s official announcement described shared technology, previews and subscription-plus-consumption pricing—not a GitHub Copilot entitlement. Microsoft’s October 16 Azure guide still requires a separate GitHub-managed subscription, and November 9 licensing coverage reports separate licenses and bills. Microsoft’s November 12 documentation explicitly says harness-agent consumption is excluded from the Microsoft 365 Copilot license.
August reporting described expanded FTC bundling scrutiny, a potential obstacle rather than a prohibition. The European Commission’s June 2024 preliminary objections to Teams tying provide an older regulatory precedent, not a decision on this proposed bundle.
Evidence for
- 16 Jun 2026 Microsoft's June 16, 2026 strategy announcement describes Agent Factory as offering a single consumption model spanning Microsoft 365 Copilot and GitHub Copilot, with user subscription licenses as the foundation. This is a specific commercial bridge between the products, although it does not announce one subscription SKU including both. blogs.microsoft.com
- 28 Oct 2026 On October 28, 2026, Microsoft announced that GitHub's engineering-built harness had been adopted company-wide and powers Copilot Code, Copilot Studio, the GitHub Copilot app, CLI and VS Code, with availability through Foundry. Sharing this core platform makes joint subscription packaging more practical, but technical integration does not establish joint licensing. linkedin.com
- 25 Sept 2026 Microsoft's September 25, 2026 announcement brings Home, Code and Autopilot into one Copilot experience, with Office integration and Code powered by the same underlying technology as GitHub Copilot. This moves the user experience toward convergence, but the official announcement describes preview rollouts and subscription-plus-consumption pricing, not a GitHub Copilot subscription entitlement; item 472's stronger bundling interpretation is not corroborated by those terms. blogs.microsoft.com
- 28 Oct 2026 On October 28, 2026, GitHub announced Copilot access for every licensed GitHub Enterprise user served by a GitHub or Microsoft account team, replacing separate seat management with enterprise-budget usage metering. This demonstrates willingness to bundle Copilot into an existing enterprise subscription, although it bundles with GitHub Enterprise rather than Microsoft 365 Copilot. github.blog
Evidence against
- 17 Nov 2026 Microsoft's October 16, 2026 Azure setup guide explicitly requires a separate GitHub-managed Copilot subscription; November licensing coverage likewise reports separate licenses, admin centers and bills, with GitHub Copilot seats not bundled with Microsoft 365 Copilot. This is the strongest evidence that commercial convergence has not yet reached the predicted SKU, though it does not rule out a launch by May 2028. aipricing.guru
- 1 Jun 2026 June 2026 reporting describes FTC scrutiny of Microsoft's licensing, interoperability and bundling, and August reporting says the investigation expanded to cloud, AI and software bundling, including Copilot. This creates a directly relevant regulatory obstacle to adding another AI service to a Microsoft enterprise suite. cio.com
- 12 Nov 2026 Microsoft's November 12, 2026 documentation states that agents powered by the Microsoft Copilot harness use consumption-based billing not included with a Microsoft 365 Copilot license. Copilot Studio documentation and a September billing discussion also distinguish harness use from users' Microsoft 365 Copilot entitlements, limiting how far shared technology can be treated as a subscription bundle. learn.microsoft.com
- 26 Jun 2024 The European Commission's June 2024 preliminary findings objected to Microsoft's tying of Teams to Office 365 and Microsoft 365 and considered Microsoft's initial unbundling changes insufficient. This provides a concrete regulatory precedent against using the productivity suite to distribute another product, though an optional Copilot bundle could be structured differently. courthousenews.com
What would settle it
Microsoft would make the prediction true by introducing, by May 18, 2028, one enterprise subscription SKU whose terms grant both GitHub Copilot and Microsoft 365 Copilot entitlements. A binding decision prohibiting that packaging through the deadline would rule it out; otherwise, the deadline passing without introduction would settle it negatively.
What to watch
A shared-entitlement purchasing pilot would show commercial integration beyond a common interface. Product terms or ordering documentation assigning both paid entitlements through one SKU would signal an approaching launch. A regulatory proceeding specifically targeting developer-AI tying to productivity subscriptions would create a more direct obstacle than today’s broader scrutiny.