Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 10:14 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Upcoming changes to Microsoft Places licensing and feature access

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, safely structured

Introduction

Starting April 1, 2026, Microsoft Places licensing will move from a user-based model to a space-based model. This change will align licensing with how organizations manage physical workspaces and will make core Places experiences more broadly available. Most users will gain access to Places Finder and the Places app, while advanced capabilities such as desk reservations, auto-release policies, and space-based analytics will require a Shared Space license.

Customers with an active Teams Premium subscription will be able to continue using existing Places premium capabilities through the remainder of their current subscription term. After renewal, these capabilities will be included in Shared Space licensing.

When this will happen

  • General availability (Worldwide): April 1, 2026
  • On this date, organizations will be able to acquire space-based licenses for Microsoft Places.

How this will affect your organization

Who is affected

Organizations that use Microsoft Places, including:

  • Users who interact with Places experiences.
  • Admins who will configure or manage Places resources (desks, desk pools, and rooms).

What will happen

  • Places Finder and the Places app will be available across most user licenses; Teams Premium will no longer be required for these capabilities.
  • Licensing for Microsoft Places will transition from a user-based model to a space-based model.
  • Advanced Places functionality will require a Shared Space license, including:
    • Desk reservation support
    • Auto‑release policies for desks and rooms
    • Space‑based analytics
  • Users will be able to reserve individual desks only if those desks are covered by a Shared Space license.
  • Desks that are configured as bookable but not covered by a Shared Space license will appear as unavailable to users.
  • Auto-release policies for desks and rooms will be enforced only when the space is covered by a Shared Space license.
  • Admins will still be able to configure auto-release policies, but these policies will not take effect unless the related spaces are licensed with a Shared Space license.
  • Analytics for desks and rooms will be available only for spaces that are covered by a Shared Space license.
  • Organizations with Teams Premium will be able to continue using existing Places premium capabilities through the current subscription term. After renewal, applicable Places premium capabilities will require Shared Space licensing.

Note: This change will not introduce a new default-on application; it will modify how existing Places capabilities will be licensed and accessed.

What you need to do to prepare

  • Review your organization’s desk, desk-pool, and room configurations and identify which spaces will require a Shared Space license.
  • Ensure that the following spaces are covered by Shared Space licenses:
    • Desks that will need to support reservations.
    • Spaces that will use auto-release policies.
    • Spaces that will require space-based analytics.
  • If your organization has Teams Premium, plan for Places premium capabilities to move to Shared Space licensing after your next renewal date.
  • Update internal documentation and help desk scripts to reflect:
    • That some desks may appear unavailable if they are not covered by a Shared Space license.
    • That auto-release policies and analytics will only apply to licensed spaces.

Learn more:

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 2 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 10:14 UTC · 272 of 272 readable · 271 fully read · documentation 469/469 current