Almanac
Microsoft/teamsMicrosoft 365

Consultant-focused KB for Microsoft Teams: implementation notes, gotchas and configuration decisions beyond the official docs — across chat and collaboration, meetings, webinars and town halls, Teams Phone, PSTN connectivity (Direct Routing, Operator Connect, Calling Plans, Teams Phone Mobile), auto attendants, call queues and contact centre integration, Teams Rooms and devices, apps and extensibility, Copilot in Teams, administration and governance, security and compliance, network and call quality, and licensing — plus cross-cutting decision guides.

teams/12-licensing/feature-licensing-teams-unbundling-base-skus.md
feature-licensing-teams-unbundling-base-skus.mdv1 · history
CurrentApplies to Teams Enterprise · Teams EssentialsUpdated 3 weeks agoSource Microsoft Learn ↗

What it does

The base Teams licence is what lets a user sign in to Teams at all. Since unbundling, how a user gets it depends on which suite family they're on and when the tenant first bought it: a suite that still includes Teams, a "no Teams" suite plus a standalone Teams SKU, or Teams Essentials on its own.

Key facts

  • From 1 April 2024, new Enterprise customers who want Teams plus the E1/E3/E5 suite value buy two SKUs: an E1/E3/E5 (no Teams) suite and a standalone Teams SKU (Microsoft Teams Enterprise or Microsoft Teams EEA).
  • In the EEA and Switzerland the same change landed earlier, on 1 October 2023.
  • Enterprise customers already subscribed to suites that include Teams before 1 April 2024 can keep using, renewing, upgrading and adjusting those subscriptions as before. Learn's footnote is explicit that Microsoft 365 E3/E5 and Office 365 E1/E3/E5 suites with Teams are no longer sold to new customers.
  • Microsoft 365 Business suites (up to 300 users) and Frontline suites are offered both with and without Teams.
  • Except for anonymous meeting join, every user needs a Teams licence to use Teams.
  • The Teams service plan identifiers are TEAMS1 (commercial), TEAMS_GOV (GCC) and TEAMS_DOD (DoD). Disabling the plan takes about 24 hours to take effect.
  • Licence management needs at least the User Administrator role; the Microsoft 365 admin center Licenses page handles up to 20 users at a time, and bulk work goes through PowerShell (Set-MgUserLicense) or Entra group-based licensing.
  • Teams Essentials is a standalone Teams subscription for small businesses, sold direct and through Microsoft Cloud Partners, using Microsoft Entra identity. It can sit alongside an existing mail system (Google Workspace, for example) with calendar sync.
  • Teams Essentials (AAD Identity) is a valid prerequisite for Teams Phone Standard and Teams Phone with Calling Plan, so a small business on Essentials can still have a phone system.
  • Business plans and Teams Essentials cap meetings at 300 people; Enterprise, Frontline and Teams EEA plans go to 1,000.
  • Add-ons (Teams Premium, Teams Phone, Audio Conferencing) all sit on top of a base Teams licence. None of them replaces it.

When to use / skip

You don't really choose unbundling — it chooses you, based on the tenant's purchase history. The real work is establishing which side of the line a client is on before anyone builds a bill of materials. A tenant that has been on Microsoft 365 E3 with Teams since 2022 can carry on renewing that; a newly created tenant, or a business that's moved from Business Premium up to Enterprise, may not have the same right. That's a question for the client's licensing partner and the agreement itself, not something Learn will answer for a specific customer.

Teams Essentials is worth suggesting for genuinely small organisations that already live in Google Workspace or another mail platform and just want meetings and chat. Once they want SharePoint, Exchange mailboxes, Intune or anything resembling governance, it's the wrong starting point and you're better on a Business suite.

Configuration decisions

  • Bundled-suite customer or "no Teams" plus Teams Enterprise? Confirm from the agreement and the tenant's Licenses page, not from memory.
  • On migration or tenant consolidation, does the destination tenant's agreement carry the bundled right, or does it need to move to the split model?
  • Licence assignment method: direct assignment, PowerShell, or Entra group-based licensing. For anything beyond a pilot, group-based is the sane option.
  • Do you disable the Teams service plan for any population (kiosk users, service accounts), and how will that be audited?
  • For small businesses: Teams Essentials versus a Business suite with Teams, based on whether they need Microsoft mail and file storage.
  • EEA customers: Teams EEA versus Teams Enterprise, which follows the customer's location and agreement.

Gotchas

  • "Microsoft 365 E5" in a client conversation can mean two different things now: the legacy bundled SKU or E5 (no Teams). The no-Teams version doesn't give anyone Teams on its own. Check the actual SKU part names in Get-MgSubscribedSku.
  • Removing Teams via Set-MgUserLicense with -DisabledPlans re-enables any other plans you didn't list. Script the full list of disabled plans every time.
  • Disabling the Teams plan isn't instant. Allow a day before you call it broken.
  • Teams Essentials requires all users in the same domain. Multi-brand small businesses trip over this.
  • Feature parity isn't the issue after unbundling — Teams Enterprise is still Teams. The issue is purchase sequencing: a renewal that drops the bundled SKU by accident can't simply be reversed.

Consultant notes

  • Put a licensing line in every discovery questionnaire: "Which Teams base SKU, and when was it first bought?" It saves a re-quote later.
  • Where Learn defers to the Microsoft Product Terms or the licensing announcement (aka.ms/MSTeamsLicensingROW), say so in the design document and point the client's licensing partner at it. Don't paraphrase entitlement terms as fact.
  • Map the licence groups in Entra early. Teams Phone, Premium and Audio Conferencing assignments are all far easier to manage once the base groups exist.
  • For Essentials customers, set expectations on admin depth: it's managed through the Microsoft admin center, but it isn't an Enterprise tenant.

Recheck if Microsoft changes the existing-customer rights or the Business/Frontline "with and without Teams" line-up — that's the bit most likely to move

Was this accurate?
Related
Teams Premium entitlements: who needs the licence and for what12-licensingTeams Phone licence SKUs and how PSTN choice changes them12-licensingLicensing shared devices: Teams Rooms Basic, Teams Rooms Pro and Teams Shared Space12-licensingPower Apps and Dataverse for Teams07-apps-and-extensibilityThe new Teams client — classic retirement, deployment and multiple accounts01-chat-and-collaborationTeam Creation Governance: Who Can Create, Naming Policy and Expiration09-administration-and-governance