Microsoft Teams Rooms Migration in Dubai, UAE
Move meeting spaces to a structured Microsoft Teams Rooms environment with a room-by-room migration plan covering identity, licensing, devices, network readiness, management, testing, and cutover.
The service is designed for organizations replacing legacy conferencing, consolidating mixed room technologies, refreshing older meeting-room systems, or standardizing collaboration across multiple sites. FourTeck can help define the migration scope, identify configuration gaps, coordinate room technology, and prepare a practical rollout plan before changes reach production rooms.
A controlled path from mixed meeting rooms to Teams Rooms
Microsoft Teams Rooms migration is not simply a software change. A successful project aligns the physical room, Microsoft 365 tenant, room mailbox, Teams Rooms license, device platform, network access, management policies, audio-video hardware, user workflow, and support model before the room is handed back to employees.
Organizations often begin a migration because meeting rooms have evolved inconsistently. One floor may have a USB camera and television, another may use an older dedicated conferencing appliance, and a third may rely on employees bringing laptops and cables. That variation increases support effort and makes meetings unpredictable. A migration program creates a common operating model: each room has a known identity, a defined license, an appropriate Teams Rooms device, tested audio and video, a calendar workflow, a management path, and a documented support baseline.
Microsoft describes Teams Rooms as a dedicated meeting-room experience available on Windows and Android systems. The platform is intended for Microsoft Teams rather than legacy Skype for Business or Lync room operation. For a business planning change, that means the destination should be treated as a modern room service rather than a direct one-for-one replacement of every legacy component. Existing displays, cameras, microphones, controllers, panels, cabling, compute units, and room scheduling devices need to be reviewed for reuse, replacement, or reconfiguration.
The Microsoft 365 side is equally important. Teams Rooms devices use room resource accounts so the space can appear in calendars, accept bookings, sign into Teams, and expose the expected meeting join experience. The correct Teams Rooms license must be assigned to the resource account. Where organizations use Intune, Microsoft Entra ID, Conditional Access, or the Teams Rooms Pro Management Portal, policies and administrative roles should be reviewed before cutover so a newly migrated room is not blocked by a rule written for normal user computers.
FourTeck supports the migration as a business technology project. The process can begin with discovery of current rooms, user requirements, Microsoft 365 readiness, hardware condition, network dependencies, and support ownership. From there, the business can choose a target standard, build a pilot, test booking and join behavior, validate audio-video quality, document exceptions, and roll out in manageable waves. This approach is useful for a single executive boardroom, a new UAE office, or a multi-site standardization project where downtime and user confusion need to be controlled.
Why organizations migrate meeting rooms as a managed program
The main value is consistency. A planned migration reduces avoidable differences between rooms and gives IT a clearer operating model for identity, devices, policies, room support, and user experience.
Consistent room experience across sites
A defined room standard helps employees know what to expect when they enter a meeting space. Calendar booking, one-touch join, content sharing, camera and microphone behavior, room naming, and support procedures can follow a common design instead of changing from room to room. For multi-floor and multi-site organizations, consistency reduces training overhead and makes service-desk troubleshooting more predictable.
Better migration risk control
Pilot-first deployment lets IT test resource accounts, policies, device enrollment, network access, and room behavior before changing every room. Problems found in one representative room can be corrected in the standard before the next deployment wave.
Clearer device ownership
Teams Rooms environments benefit from defined administrative ownership. The migration can establish who controls room accounts, licenses, device policies, firmware, management portals, AV support, and vendor escalation so a room does not fall between IT, facilities, and audiovisual teams.
Smarter reuse of existing assets
A room assessment can identify which displays, mounts, USB peripherals, speakers, microphones, network ports, cables, and room furniture remain suitable. Reuse decisions should be based on compatibility and supportability rather than age alone, helping procurement avoid unnecessary replacement while still protecting the target experience.
Identity and policy alignment
Room resource accounts are not normal end-user accounts. A migration review can separate room identity requirements from policies built for laptops and interactive user sign-in. That reduces failed sign-ins, policy conflicts, and deployment delays caused by inappropriate authentication or compliance settings.
Predictable project sequencing
Room migrations can be grouped by site, room type, business priority, or technical complexity. This lets the project protect executive rooms, customer-facing spaces, and high-usage training areas while lower-risk rooms are migrated in scheduled waves with clear rollback and support arrangements.
Migration built around the room, tenant, and operating model
A Teams Rooms project succeeds when physical collaboration technology and Microsoft 365 configuration are planned together. The service therefore focuses on dependencies that directly affect whether a room can book, sign in, join meetings, share content, be managed, and remain supportable after handover.
The exact scope can be adjusted for a legacy platform replacement, an office relocation, a hardware refresh, a Surface Hub transition, consolidation of mixed meeting-room brands, or a new standard built for future rooms. Hardware replacement, Microsoft licenses, cabling, installation, room construction, and specialized integration are quoted according to the selected migration design.
Microsoft Teams Rooms migration requirements
The table below defines the normal planning areas. Exact tasks are configuration dependent and should be confirmed against the customer tenant, current rooms, selected Teams Rooms devices, and project scope.
| Area | Migration requirement | Buyer note |
|---|---|---|
| Platform | Microsoft Teams Rooms on Windows or Microsoft Teams Rooms on Android | Select according to room design, certified hardware, management, and required features. |
| Room identity | Dedicated Teams Rooms resource account / room mailbox planning | Each physical meeting room normally needs its own resource account. |
| Licensing | Teams Rooms Basic or Teams Rooms Pro, based on organizational requirements | Pro adds advanced management and additional room capabilities; licensing should be reviewed before cutover. |
| Microsoft 365 | Exchange calendar, Teams, Microsoft Entra ID, and policy readiness | Hybrid configurations may require additional account and mailbox planning. |
| Device management | Teams Rooms Pro Management Portal and/or Intune where applicable | Management design depends on license, platform, tenant, and device type. |
| Network | Corporate network, required Microsoft endpoints, DNS, firewall, VLAN, and internet access review | Network policies should support reliable audio, video, sign-in, updates, and management. |
| Room hardware | Certified room system, displays, camera, microphones, speakers, controller, panels, and accessories | Exact components depend on room size and the selected platform. |
| AV compatibility | Existing HDMI, USB, audio, camera, DSP, and control-path review | Reuse is based on compatibility, supportability, and room performance. |
| Pilot | Representative room migration before broad rollout | Pilot room should reflect common policies, network conditions, and user workflow. |
| Validation | Account sign-in, calendar, one-touch join, audio, video, sharing, controls, management, and reboot recovery | Acceptance criteria should be documented before production rollout. |
| Warranty / support | Based on supplied hardware, vendor terms, service scope, and selected support model | Contact FourTeck for current options and warranty guidance. |
Buyers should avoid treating this table as a fixed package. A ten-room migration from standardized supported hardware is different from a ten-room migration that includes legacy codecs, unsupported cameras, complex AV processors, multiple Microsoft 365 tenants, hybrid identity, meeting-room construction, or strict security policies. The quote should therefore be based on room count, current-state inventory, target platform, Microsoft 365 environment, required hardware, deployment locations, and expected completion window. For a useful assessment, prepare room names, seating capacity, current conferencing platform, device models, account structure, licensing status, network information, and any known meeting issues.
Decisions to make before the migration starts
The highest-risk decision is choosing a target room design before confirming how employees actually use the room. Start with workload, meeting style, room size, current equipment, management requirements, and Microsoft 365 policy constraints.
What is the source environment?
Identify whether rooms use older Teams hardware, Skype-era systems, Zoom or Webex appliances, USB peripherals, Surface Hub devices, unmanaged PCs, analog AV, or a mixture. The source determines what can be migrated, reused, reconfigured, or retired.
Which platform fits the room?
Compare Windows and Android Teams Rooms options against room size, required peripherals, management model, feature expectations, support skills, and standard device family. Do not choose only because another office already uses one platform.
Are identities and policies ready?
Confirm room mailboxes, resource accounts, licenses, password and authentication design, Entra policies, required admin roles, device enrollment, and any Conditional Access exceptions or supported patterns before equipment reaches the room.
Can the network support the target design?
Review wired connectivity, DHCP, DNS, VLAN design, internet egress, firewall rules, Microsoft service endpoints, proxy behavior, QoS strategy where used, and the stability of connections serving high-value rooms.
What hardware can stay?
List displays, cameras, microphones, speakers, DSPs, controllers, room panels, mounts, extenders, cables, and power arrangements. Reuse only where compatibility and supportability are clear for the chosen Teams Rooms architecture.
What should be sent for quotation?
Share room count, locations, room sizes, source systems, target date, current licenses, hardware inventory, network constraints, required integrations, installation expectations, and whether training or post-cutover support is needed.
Where a Teams Rooms migration delivers the most practical value
This service is most useful when a business needs to move from isolated meeting-room fixes to a repeatable collaboration standard. The strongest use cases are environments where room uptime, supportability, and user consistency matter across more than one meeting space.
Multi-room office standardization
Organizations with different room technologies across floors or branches can use migration to define a standard for small, medium, and large rooms. The project can document approved room types, target device families, resource-account naming, license approach, management policy, cabling expectations, and acceptance tests. This gives future offices a reference design rather than restarting the selection process for every new room.
Legacy conferencing replacement
Businesses retiring older conferencing platforms can map each room to an appropriate Teams Rooms design. Migration planning helps separate assets that can be reused from components that depend on the previous platform or are no longer suitable for supported Teams Rooms operation.
Office move or fit-out
A relocation is a good time to modernize meeting rooms because display positions, power, LAN points, camera mounting, acoustic treatment, and cable routes can be planned before furniture and walls are finalized. The migration can be coordinated with facilities and AV contractors to reduce last-minute changes.
Executive and client-facing rooms
High-visibility rooms benefit from a pilot and formal acceptance process. Camera coverage, microphone pickup, display layout, control placement, content sharing, guest workflow, and support escalation can be tested before senior users depend on the room.
Security and management refresh
Some organizations already use Teams Rooms but need to correct resource-account design, licensing, device enrollment, management ownership, outdated hardware, or inconsistent policies. A migration can standardize these operational foundations without necessarily replacing every room device.
Phased enterprise rollout
A large environment can group rooms by building, country, business priority, or technical complexity. Pilot rooms establish the standard, early production waves validate support processes, and later waves benefit from the lessons already learned. This reduces the risk of repeating the same configuration mistake across dozens of rooms.
Microsoft Teams Rooms Migration UAE — Identity and Licensing Readiness
The room account is a core dependency, not an administrative detail. Microsoft Teams Rooms devices need a room resource account so the device can sign in, expose the room calendar, accept meeting bookings, and present the expected join workflow. Each physical room normally receives its own resource account, and the correct Teams Rooms license is assigned to that account.
Before migration, the project should identify existing room mailboxes, room names, aliases, email addresses, licensing assignments, and identity sources. Organizations using cloud-only Microsoft Entra accounts may follow a different operational path from businesses with synchronized identities or Exchange hybrid dependencies. Existing Conditional Access and Intune policies also need review because a policy designed for interactive end users can interrupt automatic room sign-in or device enrollment.
Teams Rooms Basic and Teams Rooms Pro are the current room license families. Basic covers core room meeting capabilities, while Pro adds advanced management and richer room capabilities. The correct choice depends on room count, required features, security, management, and operational expectations. FourTeck can help the customer prepare a licensing and resource-account checklist for quotation and rollout, but final Microsoft subscription availability and commercial terms should be confirmed for the tenant at the time of purchase.
Microsoft Teams Rooms Migration UAE — Device, Network, and Management Readiness
The fastest way to delay a room migration is to discover a network, enrollment, or compatibility problem after the hardware has been mounted. Microsoft’s deployment model includes site readiness, corporate network preparation, resource accounts, management configuration, and physical device deployment as connected phases. A migration plan should reflect the same dependency chain.
Validate address assignment, DNS, firewall and proxy behavior, Microsoft service access, network segmentation, and the stability of the room connection. Where voice and video quality is business critical, include appropriate performance testing rather than assuming an available Ethernet port is sufficient.
Windows and Android room systems have different deployment and management considerations. Intune, Microsoft Entra ID, device compliance, automated deployment, and local administration should be planned according to the selected platform and Microsoft guidance.
Confirm camera coverage, microphone pickup, speaker output, display resolution, controller access, HDMI and USB paths, cable lengths, extenders, room panels, and any digital signal processor or control-system integration before finalizing the bill of materials.
Define how room health, updates, configuration, alerts, incident ownership, and vendor support will be handled after handover. A migrated room without an operating model simply moves the support problem to a newer platform.
For organizations with many rooms, management design can influence the platform and license choice as much as camera or display selection. The migration should therefore involve Microsoft 365 administrators, network teams, endpoint teams, workplace technology, AV specialists, and facilities when those functions are separate.
Microsoft Teams Rooms Migration UAE — Pilot, Cutover, and Validation
A pilot is the point where the design meets the real environment. Microsoft recommends testing migrations in small batches for relevant room-account transition scenarios, and the same principle is sensible for broader Teams Rooms projects. Choose pilot rooms that expose typical policies, network paths, room sizes, peripherals, and user behavior. A laboratory room alone may not reveal the issues that appear in a busy production area.
Before cutover, define acceptance checks. The room should sign in without repeated prompts, display its calendar correctly, accept bookings, expose the expected join control, send and receive audio, show usable camera coverage, share content, recover after restart, and appear in the selected management tools. If third-party meeting join, room panels, direct routing, specialized microphones, dual displays, or AV processors are part of the requirement, include them in the acceptance test rather than assuming they will work because the basic meeting test passed.
After the pilot is accepted, production rooms can be grouped into waves. Higher-risk or business-critical spaces may receive dedicated change windows, while standard rooms can follow a repeatable checklist. The project should retain a migration log showing account, license, device, configuration, test result, exceptions, and support ownership for each room. That record becomes valuable when a later update, hardware replacement, office move, or audit requires the business to understand what was deployed.
What Buyers Should Check Before Purchase
The most important purchase risk is treating migration as a single installation task. Buyers should confirm the source platform, room inventory, target experience, Microsoft 365 readiness, compatibility, licensing, network condition, project quantity, and support expectations before agreeing a room-by-room scope.
Configuration Fit
Confirm the room count, room sizes, user capacity, current conferencing method, desired Teams Rooms platform, required displays, camera coverage, microphone approach, room controllers, panels, and any special AV integration. Similar room names do not guarantee similar technical requirements. A small huddle space can often use a simpler appliance design, while a boardroom may need modular cameras, microphones, dual displays, or control integration. Final design should follow the room, not a generic package.
Compatibility Check
List every component that the business wants to retain and verify whether it is supported or suitable with the target architecture. Displays may be reusable while an old codec is retired; microphones may depend on a DSP; USB cameras may not suit a certified appliance; room booking panels may require their own account and license planning. Also review Microsoft 365 identity, Exchange, Intune, Conditional Access, network segmentation, proxies, and firewall policies. Compatibility problems are often discovered outside the conference device itself.
Availability, Licensing, and Warranty
Migration services are project based. Hardware availability, installation timing, Microsoft subscription terms, warranty handling, and on-site resources can vary by selected device family, quantity, location, and supplier status. Ask which items are included in the quote: assessment, room hardware, licenses, installation, cabling, configuration, Microsoft 365 work, testing, documentation, training, travel, and post-cutover support. Hardware warranty should be confirmed against the selected vendor and regional supply path rather than assumed from a generic room description.
Quote Preparation
For a useful quotation, send the current platform, room count, room sizes, meeting capacity, device inventory, Microsoft 365 tenant type, existing Teams Rooms licenses, preferred migration date, office locations, network constraints, required hardware replacements, installation needs, training expectations, and any integrations such as room panels, direct routing, DSPs, control systems, or third-party meeting join. For multi-site projects, identify which rooms can serve as pilots and which rooms are business critical.
A smaller model or simpler room system may be sufficient where the room only needs dependable Teams meetings, a single display, and integrated audio-video. A more advanced design becomes relevant when the room needs larger coverage, multiple cameras or microphones, dual displays, specialized control, advanced management, or integration with existing AV infrastructure. FourTeck can review the requirement before the buyer selects a device family or commits to a rollout sequence.
Migration support for UAE meeting-room projects
FourTeck supports Microsoft Teams Rooms migration inquiries in Dubai and across the UAE with project scoping, product selection, configuration review, quotation assistance, delivery coordination for selected hardware, and warranty guidance. Availability is not treated as a fixed stock claim because the work may depend on the room count, chosen certified systems, Microsoft licensing, existing infrastructure, site readiness, supplier status, and installation schedule.
Review room sizes, target platform, hardware reuse, license needs, room panels, displays, camera and audio requirements, and management expectations before the bill of materials is finalized.
Coordinate supplied room systems, accessories, mounts, cables, and related equipment according to project quantities and supplier availability. Site dates should be confirmed after technical scope and hardware status are known.
Warranty varies by manufacturer, device, bundle, and supply route. FourTeck can help buyers identify the applicable warranty information for the selected room hardware during quotation.
Dubai, Abu Dhabi, Sharjah, and Ajman project coordination
Businesses in Dubai, Abu Dhabi, Sharjah, and Ajman can contact FourTeck for Teams Rooms migration planning, room technology supply discussions, and project quotation. A UAE rollout may involve a headquarters, branch office, training center, customer briefing facility, education campus, clinic, hotel meeting area, warehouse office, or shared workplace. The practical requirement is to understand each site before committing to a standard.
For multi-emirate projects, send the room count by location, room types, existing platform, access restrictions, target deployment dates, and whether local installation coordination is required. A single design can be used where rooms are similar, but exceptions should be recorded rather than forced into the same configuration. This is especially important when one site has different network security, older displays, unique AV infrastructure, or different room sizes. FourTeck can help organize the quotation around a pilot location and phased deployment plan so procurement, IT, facilities, and room users have a clearer schedule.
GCC and Africa availability for project-based requirements
FourTeck also receives business technology inquiries for selected GCC and Africa markets. Organizations with regional offices in Saudi Arabia, Qatar, Oman, Kuwait, Bahrain, Kenya, Uganda, and other Africa locations can discuss meeting-room standardization, room hardware requirements, and migration planning through the appropriate inquiry channel. The exact service model, delivery route, local installation capability, Microsoft licensing path, warranty handling, and lead time can vary by country and supplier status.
Regional projects benefit from a stronger standardization document because the same room may be delivered through different local supply and installation resources. The project should define approved target platforms, account naming, license requirements, device configuration, network prerequisites, acceptance tests, support escalation, and documentation. When different countries require different hardware variants or procurement paths, those differences should be recorded as approved regional exceptions rather than creating an uncontrolled room estate. Contact FourTeck with the countries, room quantities, target dates, and preferred scope so the team can review suitable options.
Other options buyers may consider
A migration project often leads to hardware decisions. The following FourTeck pages cover meeting-room systems and peripherals that may be relevant when existing equipment cannot be retained or when the business wants a more consistent collaboration standard.
ClickShare Hub Pro + Huddly C1 Room System Bundle
Suitable for buyers reviewing a modern room-system bundle with wireless collaboration, room control, video, and Teams Rooms deployment considerations for small and medium spaces.
Barco ClickShare Hub Core Kit
A related modular meeting-room option for businesses that need a streamlined room control and content-sharing approach.
Yealink Microsoft Teams Panels
Useful when the migration includes door-side room scheduling, room visibility, and a standardized booking experience.
Poly Studio E70 Camera
A meeting-room camera option to review when larger rooms need a dedicated intelligent camera as part of the selected collaboration design.
FourTeck collaboration assistance
If the target room standard is not yet selected, start with the business requirement rather than a model number.
Practical support for a room migration that spans IT and AV
Meeting-room projects sit between multiple teams. Procurement sees products and commercial terms; Microsoft 365 administrators see accounts and policies; network teams see connectivity; facilities teams see power, mounting, and room access; audiovisual specialists see cameras, microphones, displays, and signal paths. FourTeck helps buyers bring these requirements into one purchasing and deployment conversation.
Review suitable Teams Rooms systems, displays, cameras, panels, and accessories according to the target room design and supplier availability.
Translate room size, user experience, platform, network, identity, and management requirements into a clearer bill of materials and migration scope.
Build a project quote around room quantities, selected hardware, installation needs, delivery locations, migration tasks, and support expectations instead of an incomplete per-device figure.
Coordinate technical planning with supply and deployment sequencing so devices, licenses, room accounts, network readiness, and site access are not treated as unrelated workstreams.
Clarify available warranty information for the selected hardware and identify where support responsibility belongs after the room is handed over.
Help identify compatible room panels, cameras, displays, mounts, cabling, switching, power protection, and other supporting products when they are part of the requirement.
FourTeck does not assume every project needs the same hardware or migration path. The useful starting point is the room inventory and business requirement. From there, the buyer can determine whether the project is primarily a Microsoft 365 configuration change, a hardware refresh, a complete room rebuild, or a phased combination of all three.
Microsoft Teams Rooms migration questions
These answers cover the practical decisions that commonly affect room migration scope, compatibility, licensing, timing, and quotation.
What is Microsoft Teams Rooms migration used for?
It is used to move meeting spaces from legacy conferencing, mixed room technologies, older Teams configurations, or laptop-dependent workflows into a structured Microsoft Teams Rooms environment. The migration can include discovery, target room design, resource accounts, Teams Rooms licensing, network and policy readiness, room hardware, installation coordination, pilot deployment, testing, documentation, and phased cutover. The exact scope depends on the source environment and how much existing equipment can be retained.
Can existing meeting-room hardware be reused?
Sometimes. Displays, mounts, cabling, microphones, speakers, cameras, or AV processors may remain useful when they are compatible with the selected Teams Rooms architecture and still meet the room requirement. Other components may be tied to a legacy platform, unsupported by the target system, or unsuitable for the required room size. A room inventory and compatibility review should be completed before the quotation assumes reuse or replacement.
Do Teams Rooms need a separate account and license?
Yes. Microsoft’s deployment guidance uses a dedicated resource account for each physical room so the device can sign into Teams and the room can participate in calendar booking. A Teams Rooms Basic or Teams Rooms Pro license is assigned according to the organization’s requirements. The migration should confirm the account, mailbox behavior, license, identity source, and applicable policies before the room device is expected to sign in.
Should we choose Teams Rooms on Windows or Android?
Both are valid Microsoft Teams Rooms platforms, but the better choice depends on the selected certified hardware, room size, peripheral requirements, feature expectations, management approach, IT skills, and standardization plan. Some businesses prefer appliance-style Android rooms for simplicity, while others select Windows systems for specific integration or management needs. Compare the exact required features and hardware support rather than choosing only by operating system name.
How should a multi-room migration be phased?
Start with representative pilot rooms that reflect normal network, policy, hardware, and user conditions. Define acceptance checks, migrate the pilot, correct issues, and then group production rooms by site, room type, business priority, or technical complexity. High-visibility rooms can receive dedicated change windows. Keep a record of account, device, configuration, test result, and exceptions for every migrated room so later support teams know exactly what was deployed.
Can FourTeck help with Microsoft 365 and room configuration planning?
FourTeck can help review the migration requirement and coordinate the configuration areas that affect the room project, including room resource-account readiness, Teams Rooms licensing, selected hardware, network dependencies, management approach, and installation sequence. The final administrative scope should be confirmed during quotation because customer tenant access, security requirements, hybrid identity, Exchange configuration, and internal change controls can significantly change the amount of work required.
How long does a Teams Rooms migration take?
There is no universal duration. A single room with known supported hardware and a ready Microsoft 365 environment can be much simpler than a multi-site project with legacy AV, hardware procurement, cabling, account remediation, security policy changes, and room construction. The schedule should be estimated after discovery. Buyers should provide room quantities, current systems, target dates, site access restrictions, and hardware needs so the rollout can be planned realistically.
Is Microsoft Teams Rooms migration available in Dubai and the UAE?
FourTeck supports UAE inquiries for Teams Rooms migration planning, room technology selection, quotation, supply coordination, deployment discussion, and warranty guidance for selected hardware. Project availability depends on the required scope, device availability, room locations, supplier status, Microsoft licensing, and installation schedule. Contact FourTeck with the current room environment and target timeline so the team can review suitable options and prepare a project-based response.
What information should we provide before requesting a quote?
Send the number of rooms, locations, seating capacity, current conferencing platform, existing room-device list, Microsoft 365 environment, current Teams Rooms licensing, target Windows or Android preference if known, required integrations, hardware that should be reused, installation or cabling needs, target completion date, and support expectations. For larger projects, include which rooms can be used as pilots and which rooms are business critical or require restricted change windows.
Need Help Planning the Right Migration Scope?
FourTeck can review the existing meeting-room estate, intended Teams Rooms platform, Microsoft 365 readiness, room hardware, quantity, deployment locations, target dates, and support expectations before preparing a quote. A clear discovery summary helps the project separate reusable assets from required changes and gives procurement a more accurate basis for approval.
Share these details for a useful first review:
- Room count and office locations
- Current conferencing platform and device models
- Microsoft 365 and Teams Rooms licensing status
- Target completion date and installation expectations
- Required integrations, reuse goals, and support needs