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.

feature-teams-panels-check-in-release.mdv1 · history
CurrentApplies to Teams Rooms Pro, Teams Shared DevicesUpdated 3 weeks agoSource Microsoft Learn ↗

What it does

Small touchscreens mounted outside a meeting space that show who has the room, let people book it on the spot, and — with check-in and auto-release turned on — give back rooms that were booked and never used. They're Android devices running the Teams app, signed in as the room's resource account.

Key facts

  • Every panel signs in with a room resource account. If the room has a Teams Rooms system or Surface Hub, the panel uses the same account and needs no extra licence.
  • Licensing: a Teams Rooms Pro licence covers one Teams Rooms system or Surface Hub plus one panel in that room. A room with no room system needs a Teams Shared Device licence for the panel.
  • Pro-licensed panels get extras such as full room alerts and check-in notifications on the front-of-room display; Shared Device panels still get QR code booking and auto-release.
  • Features: Reserve (ad hoc booking), extend and release, QR code booking from a phone, occupancy status, room equipment display, and a "someone's waiting" notification. Busy and free states show on large text and LED lighting.
  • Multiple panels at different doors of the same space share one resource account.
  • Check-in is offered from roughly 20 minutes before start. Joining the meeting on the paired Teams Rooms device also counts as check-in.
  • If nobody checks in, the room declines the meeting, the organiser gets a cancellation, and the room becomes free. The timeout is set under "Release after" and changes can take up to 48 hours to apply.
  • Auto-release is configured on the device (Settings > Device settings > Teams admin settings > Meetings > "Release room if no one checks in") or via a configuration profile.
  • Auto-release needs an Exchange Online room mailbox with the correct time zone; on-premises mailboxes aren't supported. Meetings the room organised itself are never auto-released.
  • Third-party (Zoom etc.) and in-person meetings with no Teams link are auto-checked-in, with an email prompt to the organiser when auto-release is enabled.
  • Panels need PoE+ (check the OEM's spec) and are supported in worldwide, GCC and GCC-High clouds.

When to use / skip

Panels earn their keep in busy offices where people squat in rooms or book them "just in case". Auto-release is the real reason to buy them — it frees capacity without any argument about booking etiquette. In a quiet office with spare rooms, they're a nice-to-have and the money's better spent on room audio.

Pair panels with every Pro room if the budget allows; the licence already covers it. For huddle spaces, focus rooms and other bookable spaces without a room system, a panel on a Shared Device licence is a cheap way to make them visible and bookable. Skip them where the room mailbox is still on-premises — you'll lose auto-release, which is most of the point.

Configuration decisions

  • Whether to enable check-in and auto-release, and the release timeout. Agree this with the workplace team, not just IT; it's a policy change for staff.
  • Which rooms are exempt — boardrooms with assistants managing bookings often are.
  • Office hours, so panels turn off overnight.
  • Admin password, set via configuration profile rather than left at the OEM default.
  • Wallpaper and busy-state colours, within brand guidelines.
  • Panel placement per door, and whether multi-door rooms get more than one panel.
  • Whether to expose QR code booking to staff phones.

Gotchas

  • The 48-hour lag on auto-release changes catches people testing it. Change it, leave it, test later.
  • Wrong mailbox time zone breaks auto-release quietly — rooms release at odd times or not at all.
  • Auto-release cancels the meeting for the organiser. Staff who book a room and turn up five minutes late will complain. Communicate before you switch it on.
  • Mounting surfaces vary (glass, plaster, wood panelling) and need different brackets. Involve facilities early or install day slips.
  • PoE+ is required; plenty of older access switches only offer standard PoE. Check per port.
  • A panel moved to a different service provider may need a factory reset first.

Consultant notes

  • Do a site survey with facilities and AV before ordering: power, network port and mounting surface for each door.
  • Pilot auto-release on one floor with a clear comms note, then roll out. Measure the rooms freed.
  • Create resource accounts and assign licences well ahead of install; signing in panels shouldn't be the first test of the account.
  • Use the same naming convention as the room system so the panel and console are obviously paired in the portal.
  • Management of panels is moving from the Teams admin center into the Teams Rooms Pro Management Portal — set roles and groups there now.

Recheck after the custom background and settings templates for panels finish landing in the Pro Management Portal

Was this accurate?