Teams unbundling changes how new Microsoft 365 tenants license Teams

Licensing in Microsoft 365 and Office 365 has kept shifting over the past few months. I support a lot of tenants, and I keep seeing how small changes catch admins and CSP partners off guard. Microsoft introduced the "no Teams" suites in the EU/EEA in October 2023. Since April 2024, the Teams unbundling has applied globally. New commercial customers now receive Microsoft 365 and Office 365 suites without Teams, and there's a new standalone Teams Enterprise SKU alongside them. This is more than a regulatory side note. In every new tenant, licences are assigned and priced differently, and I've already watched that cause confusion on real projects.

New tenants now get Microsoft 365 suites without Teams

If you set up a new commercial tenant today, the familiar "Microsoft 365 E3" and "Office 365 E1/E3/E5" only show up as "no Teams" versions. Teams is not included by default. You have to assign the new "Microsoft Teams Enterprise" add-on as well. Microsoft says the price difference between the "no Teams" suites and Teams Enterprise is meant to match the previous bundles. Still, check the official announcement and the licensing documentation yourself, because regional prices and taxes can vary. Frontline plans (F1, F3) are the exception. They still include Teams by default and aren't affected by the unbundling. In CSP environments these differences are easy to miss, particularly when plans get mixed or customers move between regions.

Practical tip: Check the exact product name in both the admin center and the CSP portal every time. The "no Teams" suites and the Teams Enterprise add-on look very similar at a glance. I've had cases where users ended up without Teams, or with both assigned by mistake, mostly in larger tenants or in the middle of migrations.

Existing customers keep their current Teams licences for now

If you already own suites with Teams, nothing changes for you. Renewals, upgrades and additional seats are still available with the existing "with Teams" licences. The new model only applies to new commercial tenants and customers after the April 2024 switch. Some IT teams have told me they're worried about being forced to migrate or split their licences. For now, there's no such requirement. I'd still review your current licence mix, especially if you're planning a tenant split, a merger or new locations outside your current region. There's no reason to panic. Just keep an eye on it when you plan changes.

The split licences add cost checks and room for admin mistakes

The unbundled model gives admins and partners more pieces to manage. Where one SKU used to be enough, you may now have to assign a "no Teams" suite and the Teams Enterprise licence together. That makes assignment more granular, but it also makes errors more likely, particularly with large user bases or hybrid licensing strategies. Microsoft's announcement says overall costs are meant to stay close to the old bundles. Even so, calculate the total price for your actual combination of suites and add-ons before you decide. New products in the admin center are labelled "(no Teams)", which helps, but in real deployments people overlook that label all the time. The result is users who suddenly can't find Teams in their apps, or duplicate assignments nobody intended.

This is the PowerShell one-liner I use to get an overview of all assigned licences and find mismatches:

Get-MsolUser | Select DisplayName, Licenses | Export-Csv teams-licensing-overview.csv -NoTypeInformation

It won't solve everything, but it's a low-effort way to audit licence assignments and spot problems before users do.

The unbundled model reshapes licensing across the Microsoft 365 ecosystem

New organizations and international customers feel the change most, since they now get the same model everywhere in the world. CSPs and IT partners have to adjust their quoting and onboarding processes, sometimes at short notice. Microsoft's Teams licensing overview has been updated to reflect the current situation. Existing tenants won't see anything change overnight. Over time, though, the licence lineup gets more uniform, and you'll find "with Teams" and "no Teams" plans side by side in the same admin center, depending on when and where they were bought.

The following diagram shows how these plan types relate to each other:

flowchart TD
    SuiteNoTeams["M365/O365 Suite (no Teams)"] --> TeamsEnterprise["Teams Enterprise"]
    SuiteWithTeams["M365/O365 Suite with Teams (existing)"]
    FrontlineSKU["F1/F3 Suite (with Teams)"]
    SuiteNoTeams -- "new customers only" --> TeamsEnterprise
    SuiteWithTeams -- "existing, renewals" --> SuiteWithTeams
    FrontlineSKU -- "includes Teams" --> FrontlineSKU

Figure: How the licensing structure looks after the Teams unbundling.

Teams unbundling calls for vigilance rather than panic

For admins and consultants, the Teams unbundling isn't a major disruption, but licence management now needs more care. If you're planning new rollouts or tenant migrations, or you advise clients on Microsoft 365, check every SKU name and price before you assign or quote anything. Microsoft licensing has always had a few traps hidden in it, such as licence names that are almost identical or Teams being delivered differently in old and new tenants. Teams itself works exactly as before. What changed is the licensing logic, and that's where careful attention now will save you trouble later.