What changes: Teams Rooms on Android will gain a modernized Gallery that prioritizes participants sending video by default, offers an equal audio/video participant layout, uses consistent aspect ratios, minimizes tile movement, and lets users hide the room’s self-preview.
Who controls it: Users can choose between the video-first and equal-participant layouts and can hide self-preview. Administrators can configure the default through local device settings or the Pro Management portal.
What admins should do now: Identify affected Android rooms, choose a provisional default based on common meeting types, and prepare to validate both layouts and the hidden-preview behavior after release.
Target availability: Microsoft 365 Roadmap ID 567468 lists General Availability for July 2026. The item remains marked In development, so the date should be treated as a target rather than confirmation that the feature is already available.
Microsoft’s planned Gallery update gives organizations a practical choice: emphasize visible remote participants or give audio and video participants equal treatment on the meeting stage. The best default will depend on how each room is used. Collaborative rooms may benefit from larger or more prominent video feeds, while briefing, attendance-focused, or audio-led meetings may need a more balanced representation of everyone in the call.
The central change in Roadmap ID 567468 is a video-first Gallery layout for Teams Rooms on Android. Participants who are sending video will receive priority on the meeting stage instead of automatically sharing equal stage treatment with audio-only attendees.
For many everyday meetings, that can make the front-of-room display more useful. Facial expressions, gestures, reactions, and other visual cues help people in the room follow a remote conversation. Giving video participants priority can also prevent static profile images and initials from consuming space that could otherwise display larger live feeds.
That approach will not fit every meeting. Camera status does not necessarily indicate a participant’s importance or level of engagement. A presenter, executive, subject-matter expert, or caller with limited connectivity may participate by audio only. Some meetings also use the room display partly to maintain broad awareness of attendance rather than to maximize the size of live video.
Microsoft therefore plans to provide an alternative that displays audio and video participants equally on the stage. The two choices allow organizations to select a default based on their most common meeting patterns without eliminating the other option.
Administrators should base the provisional default on meeting type rather than treating either option as universally superior.
A collaboration room used for interviews, workshops, design reviews, or customer discussions may benefit from video priority. A briefing room, operations center, training space, or room used for structured proceedings may favor equal treatment when awareness of the full participant set matters more than maximizing live video.
The roadmap confirms that users can choose the alternative layout during a meeting. It does not yet explain where that control will appear, how it will be labeled, or how quickly an unfamiliar user will be able to find it. Those details will matter when organizations prepare room instructions and help-desk guidance.
That is a useful change for a shared display. People in a meeting room often watch the front-of-room screen from several feet away while also looking at colleagues, shared content, and notes. When participant tiles repeatedly change size or position, viewers must spend time finding the same remote attendee again.
A more consistent layout should make it easier to build and retain a mental map of the meeting. If a customer appears in one part of the Gallery and a specialist appears in another, limiting unnecessary movement helps in-room viewers return their attention to those participants without rescanning the entire display.
Consistent aspect ratios should also give the stage a more deliberate appearance when it contains a mixture of camera feeds, profile images, and initials. The roadmap does not define the exact aspect ratio, cropping behavior, or layout rules, so administrators should not assume that all sources will be framed identically in every situation.
Microsoft’s wording is also appropriately limited: the update will minimize tile movement, not eliminate it. A Gallery must still react as people join, leave, enable video, or disable video. Shared content and other meeting actions may also alter what the room needs to display.
The practical question is whether the modernized Gallery avoids unnecessary disruption while still responding clearly to meaningful changes in the meeting. That can only be judged after the feature is available on representative room hardware.
Administrators should include participant transitions in their validation rather than evaluating the feature from a single screenshot. A static Gallery may look orderly while still becoming difficult to follow as attendee states change.
Self-preview serves an important purpose: it allows room occupants to check whether the camera is active and whether everyone is framed appropriately. It can reveal an obstructed lens, poor seating position, or a camera view that excludes part of the table.
After occupants verify the framing, however, the local preview may no longer be the best use of the front-of-room display. People in the room can already see one another directly. Hiding the preview can leave more stage space for remote participants and reduce the temptation to watch the room’s own image instead of the person speaking remotely.
This control introduces a simple but important training requirement. A hidden self-preview does not necessarily mean that the room camera is off. Users may hide the local representation while the outgoing room video remains visible to remote participants.
Room guidance should therefore distinguish among three conditions:
A remote participant should be included in validation. The person in the room can hide self-preview while the remote tester confirms whether the room video remains visible. That test will help support teams explain the difference using the actual controls and indicators presented by the released software.
The local option provides a way to configure an individual room. The portal option provides a central administrative control. Roadmap ID 567468 does not document the exact navigation paths, configuration workflow, assignment model, reporting behavior, or prerequisites for either method.
Administrators should therefore treat central configuration as a confirmed capability but not yet as a documented deployment procedure. It would be premature to write instructions based on assumptions about how the setting will be named, grouped, assigned, or displayed.
The ability to choose a default remains the most important enterprise element of the update. Most people entering a meeting room will use the layout presented to them. Although users can select the alternative, the administrator’s choice will shape the normal experience in that room.
Organizations should make that decision provisionally before release:
This mixture is necessary to expose the main difference between the new Gallery options. A meeting in which everyone has a camera enabled will not adequately demonstrate how the video-first default changes the treatment of audio-only attendees.
The goal is not simply to decide which layout looks more modern. Administrators should determine which one supports the room’s usual meetings and whether users can find the alternative when the default is unsuitable.
Because Microsoft promises to minimize tile movement rather than eliminate it, administrators should evaluate whether the amount of movement is reasonable and understandable. They should not use “no tile ever changes position” as the acceptance criterion.
Next, disable the room’s outgoing video and compare the controls and indicators. Document how a user can distinguish hidden self-preview from a disabled or unavailable camera based on the released interface.
This recommendation does not assume that particular models, screen counts, or firmware versions will produce different results. It recognizes only that organizations should verify an important front-of-room change on the equipment they actually operate rather than extrapolating from a single test room.
This can expose confusing terminology or state indicators before the update becomes part of normal room use. It also gives the help desk realistic language to incorporate into support guidance.
The roadmap establishes product intent, not the complete operating model. It supports planning around the two layouts, self-preview, and configurable defaults, but it does not support conclusions about update channels, staged deployment, firmware prerequisites, tenant sequencing, or different arrival patterns among rooms.
Those fields should be read together. July 2026 is Microsoft’s stated target month, while “In development” indicates that the roadmap item has not yet been presented as fully released. The record does not establish that deployment has started, that availability is being staged during July, or that any customer has already received the feature.
It also does not establish when each tenant, device, or cloud environment will receive it. Administrators should not infer daily rollout timing or room-level availability from the General Availability month alone.
The listed platform is Teams Rooms on Android. The listed cloud environments include Worldwide Standard Multi-Tenant, GCC, GCC High, and DoD. That identifies Microsoft’s stated availability scope, but it does not provide separate release dates or deployment mechanics for those environments.
A concise planning timeline is therefore more appropriate than a speculative rollout analysis:
Organizations should monitor Microsoft’s roadmap and future product documentation for changes to the target date or status. They should also verify the feature directly before telling users that it is available.
Support teams do not need an extensive new troubleshooting framework before release. They need a short decision path based on what the user and a remote participant can observe.
For a participant-visibility question, support should first determine which Gallery behavior is active. If the room is prioritizing video, switching to equal audio/video treatment may better fit a meeting in which the complete roster needs stage visibility.
For a camera question, support should determine whether only the local preview is absent or whether remote attendees have also lost the room feed. A remote confirmation is more reliable than assuming that the front-of-room display always represents outgoing camera state.
Final support instructions should use the actual names and indicators in the released interface. Until those are documented, organizations can prepare the concepts without guessing the exact taps, menu locations, or reset behavior.
This focused guidance avoids turning every layout difference into an incident. It also prevents the opposite mistake: dismissing a genuine camera problem merely because the new Gallery includes a hide-preview option.
The immediate administrative value is concrete: select the default that best matches the meeting, validate how mixed audio and video participation appears, and teach users that hiding self-preview is not the same as turning off the camera.
Microsoft has supplied the broad outline through Roadmap ID 567468: video-first Gallery behavior, an equal-participant alternative, consistent aspect ratios, minimized tile movement, optional self-preview, local and portal-based default configuration, and a target of July 2026.
Important implementation details remain undocumented. Exact UI paths, version requirements, hardware exceptions, rollout mechanics, and persistence behavior should remain open questions rather than become assumptions in deployment plans.
That makes the next step straightforward. Administrators can make provisional policy decisions now, but final procedures should wait for the released controls and supporting Microsoft documentation. Once those arrive, a short representative-room validation should provide the evidence needed to choose the default, train users, and support the new Gallery without overstating what the roadmap currently guarantees.
Who controls it: Users can choose between the video-first and equal-participant layouts and can hide self-preview. Administrators can configure the default through local device settings or the Pro Management portal.
What admins should do now: Identify affected Android rooms, choose a provisional default based on common meeting types, and prepare to validate both layouts and the hidden-preview behavior after release.
Target availability: Microsoft 365 Roadmap ID 567468 lists General Availability for July 2026. The item remains marked In development, so the date should be treated as a target rather than confirmation that the feature is already available.
Microsoft’s planned Gallery update gives organizations a practical choice: emphasize visible remote participants or give audio and video participants equal treatment on the meeting stage. The best default will depend on how each room is used. Collaborative rooms may benefit from larger or more prominent video feeds, while briefing, attendance-focused, or audio-led meetings may need a more balanced representation of everyone in the call.
Modernized Gallery Gives Admins a Meaningful Default
The central change in Roadmap ID 567468 is a video-first Gallery layout for Teams Rooms on Android. Participants who are sending video will receive priority on the meeting stage instead of automatically sharing equal stage treatment with audio-only attendees.For many everyday meetings, that can make the front-of-room display more useful. Facial expressions, gestures, reactions, and other visual cues help people in the room follow a remote conversation. Giving video participants priority can also prevent static profile images and initials from consuming space that could otherwise display larger live feeds.
That approach will not fit every meeting. Camera status does not necessarily indicate a participant’s importance or level of engagement. A presenter, executive, subject-matter expert, or caller with limited connectivity may participate by audio only. Some meetings also use the room display partly to maintain broad awareness of attendance rather than to maximize the size of live video.
Microsoft therefore plans to provide an alternative that displays audio and video participants equally on the stage. The two choices allow organizations to select a default based on their most common meeting patterns without eliminating the other option.
| Gallery behavior | Stage emphasis | Likely advantage | Likely trade-off | Confirmed control |
|---|---|---|---|---|
| Prioritize video participants | Participants sending video receive priority | Makes visible faces and nonverbal communication more prominent | Audio-only attendees may receive less stage emphasis | Users can select it; admins can configure the default |
| Show audio and video participants equally | Audio and video participants receive equal treatment | Maintains broader visual representation of the participant roster | Static participant tiles may use space that could enlarge video feeds | Users can select it; admins can configure the default |
A collaboration room used for interviews, workshops, design reviews, or customer discussions may benefit from video priority. A briefing room, operations center, training space, or room used for structured proceedings may favor equal treatment when awareness of the full participant set matters more than maximizing live video.
The roadmap confirms that users can choose the alternative layout during a meeting. It does not yet explain where that control will appear, how it will be labeled, or how quickly an unfamiliar user will be able to find it. Those details will matter when organizations prepare room instructions and help-desk guidance.
Consistent Tiles Should Make the Stage Easier to Follow
Microsoft also says the modernized Gallery will use consistent aspect ratios and minimize movement of participant tiles on the stage.That is a useful change for a shared display. People in a meeting room often watch the front-of-room screen from several feet away while also looking at colleagues, shared content, and notes. When participant tiles repeatedly change size or position, viewers must spend time finding the same remote attendee again.
A more consistent layout should make it easier to build and retain a mental map of the meeting. If a customer appears in one part of the Gallery and a specialist appears in another, limiting unnecessary movement helps in-room viewers return their attention to those participants without rescanning the entire display.
Consistent aspect ratios should also give the stage a more deliberate appearance when it contains a mixture of camera feeds, profile images, and initials. The roadmap does not define the exact aspect ratio, cropping behavior, or layout rules, so administrators should not assume that all sources will be framed identically in every situation.
Microsoft’s wording is also appropriately limited: the update will minimize tile movement, not eliminate it. A Gallery must still react as people join, leave, enable video, or disable video. Shared content and other meeting actions may also alter what the room needs to display.
The practical question is whether the modernized Gallery avoids unnecessary disruption while still responding clearly to meaningful changes in the meeting. That can only be judged after the feature is available on representative room hardware.
Administrators should include participant transitions in their validation rather than evaluating the feature from a single screenshot. A static Gallery may look orderly while still becoming difficult to follow as attendee states change.
Hiding Self-Preview Can Reclaim Useful Display Space
The update will also let users hide the room’s self-preview.Self-preview serves an important purpose: it allows room occupants to check whether the camera is active and whether everyone is framed appropriately. It can reveal an obstructed lens, poor seating position, or a camera view that excludes part of the table.
After occupants verify the framing, however, the local preview may no longer be the best use of the front-of-room display. People in the room can already see one another directly. Hiding the preview can leave more stage space for remote participants and reduce the temptation to watch the room’s own image instead of the person speaking remotely.
This control introduces a simple but important training requirement. A hidden self-preview does not necessarily mean that the room camera is off. Users may hide the local representation while the outgoing room video remains visible to remote participants.
Room guidance should therefore distinguish among three conditions:
- The room preview is hidden locally.
- The room’s outgoing video is turned off.
- The camera or video feed is not working as expected.
A remote participant should be included in validation. The person in the room can hide self-preview while the remote tester confirms whether the room video remains visible. That test will help support teams explain the difference using the actual controls and indicators presented by the released software.
Local and Central Defaults Support Different Room Needs
Microsoft says administrators will be able to configure the default experience through local device settings and through the Pro Management portal.The local option provides a way to configure an individual room. The portal option provides a central administrative control. Roadmap ID 567468 does not document the exact navigation paths, configuration workflow, assignment model, reporting behavior, or prerequisites for either method.
Administrators should therefore treat central configuration as a confirmed capability but not yet as a documented deployment procedure. It would be premature to write instructions based on assumptions about how the setting will be named, grouped, assigned, or displayed.
The ability to choose a default remains the most important enterprise element of the update. Most people entering a meeting room will use the layout presented to them. Although users can select the alternative, the administrator’s choice will shape the normal experience in that room.
Organizations should make that decision provisionally before release:
- Choose video priority when rooms are primarily used for interactive meetings in which facial expressions and visual participation are important.
- Choose equal audio and video treatment when meetings depend on broad participant awareness, include many camera-off attendees, or follow procedures in which camera state should not affect stage emphasis.
- Consider room-specific defaults when specialized spaces have clearly different meeting patterns, while avoiding unnecessary variation that would make rooms harder for users to understand.
Recommended Validation Plan
The following is a recommended organizational validation plan, not a Microsoft-prescribed testing procedure. Its purpose is to help administrators compare the two layouts and prepare accurate user guidance after the feature is released.1. Establish a mixed-participant meeting
Use at least one Teams Room on Android, several remote participants sending video, and several remote participants joining without video.This mixture is necessary to expose the main difference between the new Gallery options. A meeting in which everyone has a camera enabled will not adequately demonstrate how the video-first default changes the treatment of audio-only attendees.
2. Compare both Gallery behaviors
Observe the video-first layout and then select the equal audio/video alternative. Record which participants remain visible, how prominently each participant is represented, and whether room occupants can understand the difference without technical explanation.The goal is not simply to decide which layout looks more modern. Administrators should determine which one supports the room’s usual meetings and whether users can find the alternative when the default is unsuitable.
3. Change participant states
Ask remote participants to join, leave, enable video, and disable video. Observe how the Gallery responds and whether occupants can continue following the meeting without repeatedly searching for the same people.Because Microsoft promises to minimize tile movement rather than eliminate it, administrators should evaluate whether the amount of movement is reasonable and understandable. They should not use “no tile ever changes position” as the acceptance criterion.
4. Test hidden self-preview with a remote participant
Hide the room’s self-preview while keeping the room camera active. Ask a remote participant to confirm whether the outgoing room video remains visible.Next, disable the room’s outgoing video and compare the controls and indicators. Document how a user can distinguish hidden self-preview from a disabled or unavailable camera based on the released interface.
5. Repeat testing in representative rooms
If the organization operates more than one Android room model or room configuration, repeat the essential tests in representative spaces.This recommendation does not assume that particular models, screen counts, or firmware versions will produce different results. It recognizes only that organizations should verify an important front-of-room change on the equipment they actually operate rather than extrapolating from a single test room.
6. Use nontechnical participants
Invite ordinary room users to complete a meeting without being told where each layout control is located. Ask them to explain what happened when self-preview was hidden and how they would restore equal participant treatment.This can expose confusing terminology or state indicators before the update becomes part of normal room use. It also gives the help desk realistic language to incorporate into support guidance.
Limitations: What Microsoft Has Not Yet Documented
These gaps are the main reason administrators should avoid creating a detailed deployment procedure before Microsoft publishes additional documentation or the controls become visible on released room software.
The roadmap establishes product intent, not the complete operating model. It supports planning around the two layouts, self-preview, and configurable defaults, but it does not support conclusions about update channels, staged deployment, firmware prerequisites, tenant sequencing, or different arrival patterns among rooms.
July 2026 Is a Target, Not a Live Rollout Report
The roadmap record lists General Availability as July 2026 and the status as In development.Those fields should be read together. July 2026 is Microsoft’s stated target month, while “In development” indicates that the roadmap item has not yet been presented as fully released. The record does not establish that deployment has started, that availability is being staged during July, or that any customer has already received the feature.
It also does not establish when each tenant, device, or cloud environment will receive it. Administrators should not infer daily rollout timing or room-level availability from the General Availability month alone.
The listed platform is Teams Rooms on Android. The listed cloud environments include Worldwide Standard Multi-Tenant, GCC, GCC High, and DoD. That identifies Microsoft’s stated availability scope, but it does not provide separate release dates or deployment mechanics for those environments.
A concise planning timeline is therefore more appropriate than a speculative rollout analysis:
| Phase | Evidence-safe action |
|---|---|
| Before release | Identify Android rooms and choose a provisional layout default based on meeting type |
| When the feature appears | Confirm the released controls and compare both Gallery layouts |
| During validation | Test mixed audio/video participation and hidden self-preview with a remote attendee |
| After Microsoft publishes control details | Update configuration, room-use, and support documentation |
| After organizational approval | Apply the selected default using the documented local or portal control |
Support Guidance Should Focus on Observable States
The modernized Gallery may generate questions that sound like technical faults but are actually layout choices. An audio-only attendee may appear less prominent because the room is using video priority. The room’s own image may disappear because self-preview was hidden rather than because the camera stopped sending video.Support teams do not need an extensive new troubleshooting framework before release. They need a short decision path based on what the user and a remote participant can observe.
For a participant-visibility question, support should first determine which Gallery behavior is active. If the room is prioritizing video, switching to equal audio/video treatment may better fit a meeting in which the complete roster needs stage visibility.
For a camera question, support should determine whether only the local preview is absent or whether remote attendees have also lost the room feed. A remote confirmation is more reliable than assuming that the front-of-room display always represents outgoing camera state.
Final support instructions should use the actual names and indicators in the released interface. Until those are documented, organizations can prepare the concepts without guessing the exact taps, menu locations, or reset behavior.
This focused guidance avoids turning every layout difference into an incident. It also prevents the opposite mistake: dismissing a genuine camera problem merely because the new Gallery includes a hide-preview option.
Action Checklist for Admins
- [ ] Identify Teams Rooms on Android. Build or verify a list of the rooms that fall within the platform scope of Roadmap ID 567468.
- [ ] Decide a provisional default. Choose video priority or equal audio/video treatment based on the predominant meeting type in each room or room category.
- [ ] Test both layouts after release. Use a meeting containing both camera-on and camera-off remote participants, then compare the two Gallery behaviors.
- [ ] Test hidden self-preview with a remote participant. Hide the local preview while a remote attendee confirms whether the room’s outgoing video remains visible.
- [ ] Update room-support guidance when Microsoft publishes the controls. Document the verified UI paths, labels, indicators, prerequisites, and selection behavior only after they are available from Microsoft or confirmed in the released product.
A Small Control With Practical Room-Level Impact
The modernized Gallery is not a reason to redesign an entire Teams Rooms operating model. It is a focused change that gives administrators and users better control over what receives attention on the front-of-room display.The immediate administrative value is concrete: select the default that best matches the meeting, validate how mixed audio and video participation appears, and teach users that hiding self-preview is not the same as turning off the camera.
Microsoft has supplied the broad outline through Roadmap ID 567468: video-first Gallery behavior, an equal-participant alternative, consistent aspect ratios, minimized tile movement, optional self-preview, local and portal-based default configuration, and a target of July 2026.
Important implementation details remain undocumented. Exact UI paths, version requirements, hardware exceptions, rollout mechanics, and persistence behavior should remain open questions rather than become assumptions in deployment plans.
That makes the next step straightforward. Administrators can make provisional policy decisions now, but final procedures should wait for the released controls and supporting Microsoft documentation. Once those arrive, a short representative-room validation should provide the evidence needed to choose the default, train users, and support the new Gallery without overstating what the roadmap currently guarantees.
References
- Primary source: Microsoft 365 Roadmap
Published: 2026-07-10T21:58:35.1674832Z
Loading…
www.microsoft.com - Official source: learn.microsoft.com
Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal - Microsoft Teams | Microsoft Learn
Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portallearn.microsoft.com - Official source: techcommunity.microsoft.com
Loading…
techcommunity.microsoft.com - Official source: support.microsoft.com
Loading…
support.microsoft.com - Official source: partner.rooms.microsoft.com
Loading…
partner.rooms.microsoft.com - Related coverage: yealink.com
Loading…
www.yealink.com
- Related coverage: futureisnow.logitech.com
Loading…
futureisnow.logitech.com - Related coverage: logicool.co.jp
Loading…
www.logicool.co.jp - Related coverage: websites.uta.edu
Loading…
websites.uta.edu - Related coverage: m365admin.handsontek.net
Loading…
m365admin.handsontek.net - Related coverage: pexip.com