Core Topics

Supported device types

MDEP platform currently supports six device types:

• MTRA Front of Room
• Touch Console
• USB Connected Touch Console for MTR-A
• Panels (Scheduling device)
• IP Phone (including Sidecar expansion module)
• Convertible (Touch Console/ Panel)

All configurations leverage same MDEP code base and behavior of software stack is configured at build or run-time.

Platform backwards compatibility

MDEP maintains backward compatibility through stable platform contracts, controlled API evolution, and defined migration paths across releases. The objective is to allow device images, partner integrations, and enterprise deployments to evolve across releases with minimal disruption while maintaining consistent security and management behavior across releases.

Backward compatibility in MDEP is governed by the following principles:

• Contract stability first: Backward compatibility in MDEP is achieved through stable platform interfaces and controlled evolution of integration contracts across releases.
• Additive evolution: New capabilities are introduced as additive APIs, feature flags, or optional components whenever possible, instead of replacing existing behavior in-place.
• Migration over breakage: When a breaking change is unavoidable, MDEP favors explicit migration paths and transitional compatibility mechanisms over in-place behavioral replacement.

Component-level versioning and distribution behavior follows the Unified Component Model (UCM), which defines how updates are packaged and consumed while keeping dependent components interoperable across release lines.

Platform integration and customization

In MDEP, integration means connecting partner hardware, services, and application bundles to platform-defined contracts so that provisioning, pairing, policy, security, and lifecycle behaviors remain consistent across device categories. Integration in MDEP is structured around clear platform ownership boundaries, with platform-defined interfaces, configuration points, and onboarding flows serving as the primary integration mechanisms.

Customization allows partners to adapt branding, configuration, and user experience through supported MDEP extension points. Partners may customize or replace reference implementations while preserving required platform behavior, Microsoft-signed components, and MDEP compatibility, security, manageability, and supportability. Detailed integration, customization, and validation requirements are provided to eligible MDEP partners under the applicable commercial agreements.

Platform security

MDEP security is implemented as a layered model that starts at hardware-backed trust anchors and extends through HAL, system services, framework controls, and managed application workflows. The platform enforces identity, integrity, and policy through attestation, key provisioning, secure pairing, controlled provisioning, and runtime restriction mechanisms ensuring consistent trust characteristics throughout the device lifecycle.

Security responsibilities are split across core platform components and partner integrations, with explicit contracts for certificate handling, pairing trust establishment, provisioning policy, diagnostics, and management enforcement. Integration requirements, mandatory security requirements and guidelines are defined in the companion documents released to MDEP partners.

Platform testing and validation

MDEP platform testing and validation assess whether a device implementation meets platform requirements for compatibility, security, manageability, and functional quality before deployment. Validation covers interactions across the HAL, system services, framework, and application layers, as well as supported device types and configurations. Test suites verify defined requirements and key scenarios, including upgrade safety, provisioning, pairing, and policy enforcement. However, passing the applicable tests does not by itself establish compatibility: partners remain responsible for preserving MDEP compatibility, the integrity of Microsoft-signed components, and correct behavior of integrated MDEP services, including where test coverage is silent, ambiguous, incomplete, or does not exercise a specific implementation choice.

Logging

MDEP logging provides a structured diagnostic trail across framework, system services, and partner integration points to support issue triage, operational support, and compliance investigations. Logging is designed to balance observability and security by enforcing controlled access, data minimization, and separation between diagnostic signals and sensitive customer content.

Integration is defined through platform‑provided logging paths and system logging contracts, with implementations operating through these mechanisms rather than introducing independent logging approaches

System health and telemetry

MDEP system health and telemetry capabilities monitor service availability, platform integrity, and runtime quality indicators across supported device types. The goal is to detect degradation early, support reliable incident response, and provide actionable operational insights for both Microsoft and partner-managed deployments.

Telemetry collection and health signaling are implemented through platform services and defined extension points, with policy-driven controls for what is collected, when it is transmitted, and how it is retained.