Microsoft 365 Copilot — SKU Constellation Map

A SKU-anchored view of Microsoft 365 Copilot. What sits underneath (prerequisites), what surrounds it (recommended companions), and the readiness pillars each companion serves. Use this for procurement and bundle conversations rather than executive briefings.

BusinessCapabilityTechnologySource
Compass
  • Businesspersona, use case, outcome
  • Capabilitywhat the org needs to do
  • Technologythe technology choices
  • Sourcewhere the evidence sits
Guided journey · Step 1 of 4

Identity Readiness

Identity companion SKU: Microsoft Entra ID P1 (or P2). Already in M365 E3 — the question is whether it's actually configured. Without it, Copilot inherits a weaker identity perimeter.

~ 4 weeks

Search any SKU, capability, risk, or source on this map.

Filter by type

Narrative intro

Microsoft 365 Copilot sits at the centre of a SKU constellation: M365 E3 or E5 as the licence floor, Entra ID P1 as the identity companion, Purview Information Protection as the data-governance companion. The $30-per-user-per-month price tag is the smallest part of the procurement conversation. This map is for procurement and bundle conversations rather than executive briefings. Use it when comparing total cost of Copilot deployment — the constellation total dwarfs the headline licence. The four pillars below each correspond to a companion SKU or operational investment.

Key takeaways

  • Copilot's headline price isn't the cost. The companion SKU constellation — M365 E3/E5, Entra ID, Purview — carries materially more weight.
  • Two of the four readiness pillars correspond to bundled SKU companions (Entra ID, Purview). Two are operational (tenant hygiene, pilot governance) with no SKU at all.
  • Pilot-scoped Copilot procurement is the right shape for the first phase. Tenant-wide on day one is a procurement pattern, not a deployment strategy.
  • The Copilot constellation overlaps materially with the Modern Workplace stack — most organisations buying Copilot already own the companions but haven't operationalised them.

Programme shape

Estimated duration
16–28 weeks
Estimated FTE
Programme lead, identity SME, information-governance SME, change-management partner. Same shape as the Copilot Readiness executive briefing — different lens.
Spend tier
moderate
Risk level
moderate

SKU-anchored view. The 'cost' question for Copilot is rarely the $30 per user per month — it's the surrounding SKU constellation that determines actual readiness. This map surfaces what surrounds Copilot rather than what's downstream of it.

Back to all maps