Microsoft Places Is Now Included in Your Microsoft 365 License — But Is Your Organization Ready to Use It?

What the April 2026 licensing change actually means for hybrid work operations — and why access alone is not enough

Starting April 1, 2026, Microsoft is making Microsoft Places available to virtually all Microsoft 365 users at no additional cost. Organizations on E3, E5, Business Basic, Business Standard, and Business Premium — as well as Exchange Online and most Outlook and Teams licenses — now gain access to desk booking, room discovery, and office coordination tools that previously required a Teams Premium license.

On the surface, this looks like a straightforward licensing win. In practice, it raises a more important question: do the organizations now receiving this access have the operational foundations to use it well?

At Impactory, we work with enterprises navigating exactly this gap — between tools that are technically available and operating models that can actually make them work. This article explains what Microsoft Places is, what the licensing change means, and what organizations need to think through before rolling it out.

What Is Microsoft Places?

Microsoft Places is the workplace coordination layer inside Microsoft 365. It connects the digital tools employees use every day — Teams, Outlook, and the calendar — with the physical reality of the office: where desks are, which rooms are available, who is coming in, and when.

Its core capabilities are:

• Places Finder: A rich booking interface replacing the old Room Finder. Users see desk and room options with photos, floor plans, available technology, and real-time availability — enough context to make an informed booking decision rather than guessing which room is on which floor.
• Places Explorer: A map-based view of the entire office — buildings, floors, colleagues’ planned locations, and bookable spaces — all in one place. For employees planning an on-site day, it answers the question “who else is coming in, and is there space near them?” without a single email.
• Intelligent recommendations: Native integration with Teams and Outlook allows Places to suggest presence days based on team patterns and meeting schedules, reducing the coordination overhead of hybrid work.
• Building check-in: Manual, peripheral, and upcoming Wi-Fi-based check-in options allow the system to confirm actual attendance — the foundation for meaningful utilization data.

The intent is clear: make the physical office as discoverable and schedulable as a meeting invite, and give organizations the data to understand how their space is actually being used.

What the Licensing Change Actually Means — and What It Does Not

Before April 2026, advanced Microsoft Places capabilities — including Places Finder, Explorer, desk booking, and analytics — were bundled into Teams Premium at $10 per user per month. The April 2026 change fundamentally restructures this model.

What is now free for all qualifying M365 users:

• Places Finder — rich room and desk discovery with images, floor plans, and attributes
• Places Explorer — map-based office navigation and presence visibility
• Building-level check-in capabilities
• Intelligent scheduling suggestions in Teams and Outlook

What still requires a license — the Teams Shared Space license ($8/month, covers up to 4 spaces):

• Individual desk reservations — desks must be licensed to be bookable
• Auto-release policies for desks and rooms — configured but not enforced without licensing
• Space utilization analytics — inventory and occupancy reports for desks and rooms
• Admin-level space management — booking policies, modes, and directory management

What requires Microsoft 365 Copilot (on top of everything above):

• Managed room booking — Copilot recommends rooms and automatically rebooks on conflicts
• Space analytics with Copilot — AI-generated summaries comparing utilization trends over time

The model shift is significant: Microsoft has moved from per-user pricing to per-space pricing. Organizations with 500 users but only 100 managed desks no longer need to license each person — they license each bookable space. For most enterprises, this is a substantially better economic model.

Why Microsoft Places Changes Operational Decision-Making

Microsoft Places is not just a booking tool. It is a data infrastructure for workplace decisions that most organizations have been making based on assumptions, surveys, or gut instinct.

Once utilization data becomes available at desk and room level, four categories of operational decision change in nature:

1. Capacity Planning

Organizations consistently discover, when they start measuring actual occupancy rather than bookings, that 20 to 40 percent of booked meeting room time has no one in the room. The gap between “booked” and “occupied” is one of the most expensive inefficiencies in corporate real estate. Places surfaces this data directly, enabling facilities and IT teams to identify underutilized spaces, right-size desk allocation per floor or department, evaluate whether a building or floor can be consolidated, and build a defensible, data-backed case for real estate decisions.

2. Booking Policy Design and Enforcement

Desk booking policies are not just a user experience concern — they directly shape employee behavior and space utilization patterns. Questions that need explicit answers before rollout include: Can any employee book any desk, or are neighborhoods assigned by team? What is the maximum advance booking window? How long before an auto-release policy cancels an unchecked booking? Are there desks reserved for specific roles or visitor use? Without deliberate policy design, Places will surface inconsistency rather than solve it. Departments will operate under different rules. Employees will find some desks permanently unavailable without knowing why. The analytics will reflect policies no one agreed on.

3. Real Estate and Facilities Strategy

Once utilization data is visible, real estate decisions become measurable — and accountability follows. If a floor is consistently at 30 percent occupancy on Mondays and Fridays, the data makes consolidation discussions unavoidable. This is often where organizations feel discomfort: not because the data is wrong, but because it makes explicit what was previously easy to defer. CIOs and Heads of IT should proactively align with Facilities and Finance on how this data will be used before rollout — not after the first utilization report lands on a leadership desk.

4. Hybrid Work Policy Operationalization

Most organizations have a hybrid work policy. Far fewer have translated that policy into system rules. Places forces that translation. If your policy says “two anchor days per week,” Places can surface suggested presence days — but only if someone has defined what anchor days look like for each team, which days they apply to, and how they interact with booking availability. The tool does not create the policy. It operationalizes one that already needs to exist.

Where Organizations Commonly Run Into Friction

Across the enterprises we work with, hybrid work initiatives stall not because tools are missing — but because ownership and structure are unclear. Microsoft Places does not create these problems. It reveals them.

The friction points we consistently see:

• Desk booking deployed without agreed policies — leading to inconsistent user behavior and unreliable analytics
• Ownership blurred across Facilities, HR, and IT — with no single team accountable for space data quality or policy enforcement
• Analytics available but not operationalized — reports are run, but no one acts on them or connects them to decisions
• Hybrid rules that differ by department without intent — creating employee confusion and undermining trust in the system
• Floor plan and room data not prepared — Places requires enriched space data to work well; organizations that import empty or incomplete directories lose most of the user experience value immediately

The April 2026 licensing change removes the cost barrier to Places adoption. It does not remove the organizational barriers. Those require deliberate preparation.

The AI Dimension: Why Data Quality Matters Now

Microsoft Places is not positioned as an AI product today, but its trajectory is clear. Usage data from Places feeds optimization models. Utilization analytics inform predictive recommendations. The Copilot license unlocks AI-driven space analytics and managed room booking that automatically resolves conflicts. Over time, Places becomes the data layer for Copilot to surface intelligent hybrid work decisions — suggested presence days, predictive desk allocation, context-aware recommendations delivered directly in Teams or Outlook.

These scenarios only work if the underlying data is sound. Organizations that roll out Places without clean space directories, consistent check-in data, and enforced booking policies will find that their AI recommendations are only as reliable as the inputs feeding them. Getting the foundations right now is not just good operational practice — it is the prerequisite for the AI capabilities coming next.

Impactory’s Lens: Hybrid Work Needs an Operating Model, Not Just a Tool

At Impactory, we approach Microsoft Places not as a feature rollout but as part of a broader digital workplace operating model. The questions that matter are not “which license do we need?” or “how do we turn it on?” — they are:

• Who owns space data and decisions across Facilities, IT, and HR?
• Which booking and presence policies are enforced centrally, and which are managed locally by each site?
• How does utilization data feed real decisions — not just periodic reports that no one acts on?
• Is Teams already the accepted operational interface for work, or will employees need to change habits?
• Are floor plans, room attributes, and desk configurations ready to be populated into the Places Directory?

Without these answers, Places risks becoming another well-intentioned feature that adds complexity rather than clarity — and hinders the adoption it was meant to accelerate.

Questions to Pressure-Test Before Rolling Out Microsoft Places

For CIOs and Heads of IT, a few questions matter more than feature lists:

Policy & Governance

• Do we have a hybrid work policy that is specific enough to translate into system rules?
• Are desk and room booking standards consistent across locations, or does each site operate independently?
• Who owns the decision when policies conflict between Facilities, HR, and IT?

Data & Space Readiness

• Do we have accurate floor plans and room/desk attributes ready to populate the Places Directory?
• Have we inventoried which desks and spaces need Teams Shared Space licensing for booking and analytics?
• Can we explain utilization data to leadership in business terms — not just as occupancy percentages?

Licensing & IT Readiness

• Have we audited our current Teams Premium deployments to understand which features are actually in use?
• Do we have a transition plan for any shared devices currently on the legacy Teams Shared Devices license?
• Is Teams already the accepted primary interface for work coordination among our employees?

If several of these questions feel unclear, Microsoft Places will still technically function — but its strategic value will remain limited, and adoption will be slower than expected.

The Tooling Is Ready. The Question Is Whether the Organization Is.

The April 2026 licensing change removes one of the most common objections to Microsoft Places adoption: cost. For most enterprise users, the core experience is now included in licenses they already own.

But access has never been the bottleneck for hybrid work success. The organizations that extract real value from Places will be the ones that treat it as a strategic capability — with deliberate policy design, clear data ownership, and a commitment to operationalizing what the analytics reveal.

Those that treat it as “just another feature” will see it used inconsistently, generate unreliable data, and wonder why adoption remains low despite broad license availability.

Hybrid work is no longer improvised. It is engineered. The tools are there. The operating model still needs to be built.

Not sure where to start?

We built a structured Copilot & SharePoint Readiness Diagnostic for enterprise IT leaders — and the same principles apply directly to Microsoft Places readiness. If your hybrid work foundations, governance model, and data ownership are unclear, the diagnostic will surface exactly where to focus before you roll out at scale.

→ Download the Readiness Checklist

Fill in your details and get immediate access to the checklist your IT team can use to audit hybrid work and Microsoft 365 readiness across governance, policy, and operational foundations.

→ Book a Consultation with Impactory

If you want to go deeper, our team can walk through your specific Microsoft 365 environment, map the Places readiness gaps, and help you build a rollout plan that is grounded in your actual policy, data, and licensing reality — not a generic checklist.