...
| Status |
| ||||||||
| Owner | |||||||||
| Stakeholders |
| Info |
|---|
Decision: xxx OPTION 1: MTR on Windows (MTRoW) Decision made by: ievgen.bezkorovainyi-ext@syensqo.com ; STINCHCOMBE, Sam ; paul.anton@syensqo.com; TRIFFAUX, Eric Date: 04 Jul |
Issue
The decision concerns choosing between the native Microsoft 365 backup and an option extended by a third-party tool.
Recommendation
Option 1: M365 Native backup
Background & Context
During the backup workshops in the first phase of the project (September 2025), the topic of what backup system would be available in M365 after the migration from GWS was discussed.
The decision was to be made during the second phase of the project.
A reassessment was provided by the Hosting/Backup team early 2026, with a comparison of the functionalities of Veeam and the native M365 backup. The results are below.
Assumptions
- If there will be any additional budget for secondary Backup, new project has to be assigned to implement,
Constraints
- No secured budget to implement 3rd party backup tool.
Impacts
- Less configuration flexibility (retention period, target storage)
- Veeam brings more granularity when it comes to restoration (Object level)
Options considered
Option 1: M365 Native Backup
Option 2: 3rd Party Backup (Veeam)
Evaluation
Option 1: M365 Native Backup
...
Option 2: 3rd Party Backup (Veeam)
...
Feature
...
Data stored in your chosen location (on-premises, cloud, or hybrid); supports compliance
requirements
Objective
Deploy a Microsoft Teams Room solution that is fast to implement, fully maintainable, and aligned with a long‑term global standard.
reuse existing meeting room equipment when possible.
- Reliable and easy‑to‑support setup
- Avoid exotic or non-standard hardware
- Ensure full lifecycle control (updates, security, compliance)
Design Recommendation
Given that we have M365 E5, Intune and Logitech equipments already :
OPTION 1 : MTR on Windows (MTRoW)
Why choose the Windows path (Dell + Rally Bar)?
- IT Alignment: Your team already knows how to secure and manage Windows via Entra ID and Intune. There is no "learning curve" for a new OS (Android).
- Performance: The Dell 7000 Micro provides a "future-proof" overhead for high-resolution video processing that built-in Android chips may struggle with in 2-3 years.
- Consistency: In an E5 environment, the ability to push Compliance Policies and Conditional Access rules to a Windows device is much more granular than on Android.
This architecture ensures that the meeting room becomes a first-class citizen in the Microsoft 365 tenant, benefiting from the same security and monitoring tools as the rest of the IT park.
OPTIONS
1. MTR on Windows (MTRoW)
Your current path: Dell OptiPlex 7000 Micro + Logitech Rally Bar (USB Mode)
Pros (Advantages) | Cons (Disadvantages) |
Feature Lead: Receives new Microsoft features first (e.g., advanced Front Row, multi-stream video). | Higher Complexity: More points of failure (PC + Camera + Console + separate cabling). |
Enterprise Management: Fully managed via Intune like any other Windows PC. Full support for Conditional Access and Compliance Policies. | Maintenance: As a Windows device, it requires OS patching, antivirus, and BIOS updates. |
Hardware Flexibility: Can support multiple cameras, external DSPs, and complex audio for large boardrooms. | Setup Time: Requires more manual configuration (Windows IoT image, account login). |
High Performance: The Dell i5/i7 CPU handles 4K content and heavy multitasking better than mobile chips. | Cable Management: Requires a "USB-over-CAT" or long USB cables between the table and the screen. |
Scalability: Modular design allows for independent upgrades of the PC or the Camera. | |
Advanced Features: Native support for "Intelligent Speaker" and complex multi-screen layouts. |
HLD
Lucidchart lcId 989655e7-e104-4770-9c88-0b365dfea604 rich-viewer true autoUpdate false autofit true name HLD - M365 - teams meeting room width 2329 documentToken v2_e2e0b12fecb55a7adf199f9340a811d7cb2ea56f187b7d1d961862db179735be-a=193666448&c=0b53f16d-ce29-4605-b4a7-c6cadf0b7c64&d=b23e2c3c-6304-4482-8d90-08c9c566bcc8&p= id b23e2c3c-6304-4482-8d90-08c9c566bcc8 align Left height 2096
2. MTR on Android (MTRoA)
Alternative: Logitech Rally Bar in "Appliance Mode" (No PC required)
Pros (Advantages) | Cons (Disadvantages) |
Simplicity: All-in-one design. Fewer cables, faster physical installation (Power + HDMI + Network). | Feature Lag: Some Microsoft features arrive 3–6 months later than on Windows. |
Lower TCO: No separate PC to buy or maintain. Reduced power consumption. | Limited Expansion: Harder to add 3rd party mics or extra cameras without proprietary hubs. |
Stability: Custom-built firmware is often more stable than a general-purpose Windows OS, with fewer background processes. | Management Silo: Managed primarily via the Teams Admin Center (TAC) or Logitech Sync, less so via GPO/Intune. |
Instant-On: Faster boot times and recovery after a power outage. | Interoperability: Guest Join (Zoom/Webex) is supported but can be less fluid than the Windows Edge-based version. |
Hardware Locked: If the camera fails or becomes obsolete, the entire compute unit must usually be replaced. |
3. Direct Comparison: MTR on Windows vs. MTR on Android
Feature | MTR on Windows (Selected) | MTR on Android (Appliance) |
Hardware | Modular: Dell PC + Logitech Rally Bar | All-in-One: Integrated Bar |
OS Management | Intune / Entra ID: Full Windows IoT | TAC / Intune: Android AOSP |
Feature Velocity | First: Receives new features first | Delayed: 3-6 month lag typically |
Interoperability | Superior: Direct Guest Join (Zoom/Webex) | Standard: Basic Guest Join |
Flexibility | High: Supports custom DSP & multi-cam | Limited: Closed hardware ecosystem |
Ease of Deployment | Low/Medium | High |
Ease of Management | High (Standardized) | Medium (Siloed) |
Scalability | High (Modular) | Medium (Fixed) |
User Experience | Premium (Full Features) | Standard |
See also
The following section describes relevant documentation:
Description
| Change History | ||
|---|---|---|
|