You create a room resource in Exchange Online. Maybe it’s just a single meeting room for a small office, but you want bookings managed properly rather than relying on calendar etiquette and guesswork. Everything appears to be set up correctly, yet users report they cannot find the room in Outlook’s Room Finder. They can add it by manually typing the room name, but the automated search is an empty void.

When a user clicks “Add room” and selects “Browse all rooms”, Room Finder prompts them to select a building, only to return zero results.

This behavior shows up consistently across Outlook desktop, Outlook on the web, and Teams. In most cases, nothing is actually broken—Microsoft’s default configurations simply assume you are a multinational corporation.

The Missing Metadata Trap

Microsoft’s official troubleshooting guidance tells you to create a Room List using PowerShell and add the rooms to it (documented in Microsoft’s Troubleshooting Guide).

You can follow those instructions exactly, create the list, add the room, and wait 48 hours for replication, only to find the Room Finder is still completely empty.

The reason is that modern Room Finder is driven by Microsoft’s Places service. If a room is missing basic location metadata—specifically street, city, postcode, and country—it will fail to appear even when the building field is populated. The UI doesn’t throw an error or warn you; it just silently fails to display the resource.

This design makes sense if you assume every tenant has dozens of offices spread across regions, each managed by a dedicated facilities team. For a small office with one meeting room and a kettle in the corner, it is absurd. There is no fallback, no “show all rooms” button, and no hint explaining that missing metadata is the blocker.

The Fix

The fix requires PowerShell. You cannot configure these location attributes in the Microsoft 365 Admin Center or the Exchange Admin Center UI.

First, connect to Exchange Online PowerShell and run this to inspect what Exchange actually sees:

Get-Place | Where-Object { $_.Type -eq "Room" } | Format-Table Identity,Building,City,Street,PostalCode

If your rooms show empty location fields, Room Finder will ignore them. To fix it, assign both the building and the core location metadata:

Set-Place `
  -Identity "Meeting Room 1" `
  -Building "ABC Company HQ" `
  -Street "Alphabet Street" `
  -City "London" `
  -PostalCode "ABC DEF" `
  -CountryOrRegion "United Kingdom" `
  -Floor 1 `
  -Capacity 8

After running Set-Place and ensuring the room is in a valid Room List, wait a few hours for the directory changes to propagate.

Microsoft’s choice to require enterprise-grade metadata before displaying a single office meeting room is a classic example of corporate over-engineering. But once you populate the Place fields, the Room Finder finally works.