Teams Rooms renders idle-time signage itself, from one web URL you set in its management portal. If your CMS serves no URL, connect a standalone player to the display's spare HDMI input instead, and give screens that are never in a meeting a dedicated signage display.
Teams Rooms units can show your signage between meetings, but only their way: the room system loads one web URL that you configure in its management portal. If your CMS plays only through installed apps, that setting has nothing to load, and the fix is a platform decision, not a wiring change. You have two working paths. Point the signage setting at a URL your signage platform serves, or leave the room system alone and connect a standalone player to the display's spare HDMI input. This comparison covers what each path needs, what each one shows and when, and which rooms each wins. For screens that are never in a meeting, a third answer, a dedicated signage display, usually beats both.
Why won't your signage CMS run on a Teams Rooms screen?
Because the signage feature on the room system loads a web URL; a CMS whose players install as apps, with no URL player, has nothing you can point the setting at. That is the whole problem, and it catches IT teams after they have already filled their rooms with conferencing screens. The room system's signage feature renders web pages. It does not run your CMS's Windows player, its Android player or any other installed app, and the setting has no field for a local file.
So ask your vendor one exact question: can each screen's layout be served as an HTTPS page that loads with no login? If the answer is no, the built-in path is closed with that CMS today. Vendors add these integrations when enough customers ask, and several signage platforms already publish a setup flow for this setting. Until yours does, the choice is between a platform that serves URLs and the hardware path further down.
What does the Teams Rooms digital signage setting actually show?
A web URL source: you add a source on the Digital signage tenant management page, name it, and the room system renders that address between meetings. Microsoft documents the flow: select Add source, enter a unique name and description, and assign the web URL signage source to rooms. Each screen can receive its own URL, so the reception room can show visitor welcomes while a workshop room shows a shift board. Signage platforms that built an integration appear as a source you pick by name, which saves you hosting the page yourself.
Turning the feature on happens in the Teams Rooms Pro Management portal: sign in with an admin account, open Settings > Digital Signage and toggle Digital Signage on, then assign your sources to rooms. Configuration needs the Microsoft 365 Global Admin role or the Teams Rooms Pro Manager role, so arrange that access before rollout day.
What are the limits of the signage URL?
One HTTPS page per screen that loads with no login prompt; the setting takes a URL and nothing else, so local files and installed apps are out. The two documented limits are the scheme and the sign-in: the page must be HTTPS, and it must render for an anonymous visitor. Anything behind a login stays blank.
Dashboards are the classic casualty, because most of them ask you to sign in. Publish a snapshot or a share view that loads with no credentials, the approach covered in displaying a live dashboard on a signage screen. Before you commit a floor to URL playback, read what a web page signage player can and cannot render: whatever the room system's web view supports is what your page gets, so test one room with your real content first.
When does signage show, and when does a meeting take over?
Signage runs only while the room is idle: a meeting takes the screen the moment it starts, and signage returns when the room frees up, with nothing for you to switch. Nothing in the signage setting overrides a meeting, and none is needed. Before you count screens, count idle time: export a month of bookings per room, because a room booked nearly all day is weak signage real estate on either path, and a room empty half the day is where the feature pays. Match the loop to the gap as well: the minutes between meetings suit short slides, not long videos.
Can you use the display's spare HDMI input instead?
Yes: leave the room system on its input and connect a standalone signage player to a second HDMI input; you keep your CMS, and the display shows the player whenever you select that input. Room displays typically carry two or three HDMI inputs, and the room system occupies one. Any player your platform supports works here, and choosing a digital signage player covers the box itself.
How the display changes inputs is the display's own setting: manual selection, a timed schedule, or automatic switching when the display detects a signal, the options compared in scheduling HDMI input switching on a lobby screen. Use HDMI-CEC display control to bring the display up and down with the workday. The trade is physical: one more box, one more outlet and one more cable per screen, and every meeting starts with the display on the correct input. This path also fits displays that are not room systems at all, like a reception screen with a free input.
Which path wins in which room?
The URL path wins wherever the room system already owns the screen and the content is part-time; the HDMI input path wins where you must keep an app-based CMS or the screen is not a Teams Rooms unit at all. Put the two side by side:
| URL in the signage setting | Player on a spare HDMI input | |
|---|---|---|
| What renders the content | The room system, from a web URL | A standalone player on its own input |
| What your platform must provide | Every screen as an HTTPS page, no login | Any player it supports, app or otherwise |
| During a meeting | The meeting takes the screen | You switch the display to the room system's input |
| After the meeting | Signage resumes when the room frees | The display returns when its input is reselected |
| Hardware per screen | None | One player, one HDMI cable, one outlet |
| Works with an app-only CMS | No | Yes |
| Fits displays that are not room systems | No | Yes |
The URL path wins for fleet management: one portal, no hardware, a per-screen URL, and a content change that reaches every room at once. The input path wins for platform freedom and for mixed estates, where some screens are conferencing displays and some are plain displays with a spare input. Neither path wins on a screen that is never in a meeting; that screen should be a signage display first.
Recommendation: put every Teams Rooms screen you cover on the built-in URL path, on one condition: your platform serves each screen as an HTTPS page that loads with no login. Keep an app-only CMS off the room systems and give it the screens it can actually drive: reception and open areas, through a player on a spare input or a dedicated signage display. Where the platform serves no URL today, wait for its integration instead of fitting a player to every booked room.
How does one worked example decide a whole floor?
Take 15 screens: 12 meeting rooms plus a reception display and two open-area displays; the rooms average 6 hours of bookings in an 8-hour day, so each room offers about 2 hours of signage a day. Run the arithmetic. Each room gives 8 h − 6 h = 2 h of idle signage, so 12 rooms × 2 h = 24 signage-hours across the floor. The reception and open-area displays are on from 8:00 to 17:00, 9 h, with no meetings competing: 3 displays × 9 h = 27 signage-hours. Three screens out-earn twelve, which sets your priorities before any technology choice.
Text size next. The far seat in these rooms sits about 15 ft from the screen. At the fast-reading figure of 20 ft of viewing distance per inch of capital height, the page needs 15 ft ÷ 20 ft per inch = 0.75 in capitals, with line spacing at 1.7 × 0.75 in ≈ 1.3 in. Viewers at 10 ft read 10 ft ÷ 20 ft per inch = 0.5 in, so keep body text at 0.5 in and headlines at 0.75 in.
Decision for this floor: the 12 rooms take the URL path, because two hours of signage each is worth one setting and nothing in hardware; a player per room would add 12 boxes and an input switch before every meeting. Reception and the open areas take dedicated signage displays, because 9 h a day of signage is the screen's whole job and no meeting ever takes it. If the CMS in place serves no URL, the rooms keep showing the clock between meetings until the platform side changes; the numbers rule out buying 12 players to force it.
What about reception and corridors that are never in a meeting?
Put a dedicated signage screen there: our lobby displays play images and video from a card with no subscription, which suits a screen whose whole job is signage for 9 hours a day. They mount portrait or landscape, flush in a cut-out or on the wall, and playback runs offline from the card, so no meeting system and no anonymous URL sits in the chain. See lobby displays for the current range. They are signage screens, not room systems, which is exactly what a corridor wants.
Questions
Can you install the CMS player on the Teams Rooms console itself?
The documented signage route is a URL source, and the setting accepts a URL. There is no documented way to point it at an installed application, so an app-only CMS stays off the room system until its vendor ships an integration. The spare-input path avoids the question entirely.
Does the digital signage feature work on Teams Rooms on Android?
Yes. Signage for Teams Rooms on Android is configured in the same management portal and takes a web URL under the same limits, HTTPS and no authentication. Signage platforms can also register an integration ID, so their service appears by name when you add a source instead of you pasting a URL.
How big should the text be on a meeting-room signage page?
Use 20 ft of viewing distance per inch of capital height when the page must be read fast; the 30 ft per inch planning figure is the minimum legible. From 15 ft that means 0.5 in capitals as a floor and 0.75 in as the working size, and viewers 10 ft away read 0.5 in easily.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.