Share via

MTR on Android — License Class Mismatch & Service-Side Token Revocation (MTR Basic)

Jhon Alvarez 0 Reputation points
2026-03-26T14:26:16.49+00:00

Description:

We are documenting a reproducible authentication failure within the Microsoft Teams Rooms (MTR) on Android ecosystem, specifically affecting the RoomPanel Plus E2 hardware class.

Technical Analysis:

Initial Handshake Success: The device initially achieves a "Healthy" status via the standard /devicelogin flow. All telemetry in the Teams Admin Center (TAC) confirms the Teams Admin Agent, OEM Agent, and Intune Compliance are "Up to Date."

Licensing Context: The resource account is provisioned with a Microsoft Teams Rooms Basic license.

Failure Mode (Token Revocation): Within a 24-hour cycle, the Microsoft Identity Provider (IdP) revokes the session during a background token refresh. The client-side application returns the error: "Your current licence is not supported on this device."

Hardware Classification Issue: The failure appears to be a backend misclassification. We suspect the RoomPanel (Meeting Room Accessory) is being identified as a "Primary MTR Console," which may be causing the MTR Basic license to be rejected during the entitlement handshake.

Objective: Confirm if there has been a recent Service Policy Regression or a User Agent mismatch in the Microsoft Licensing Service that is now gating MTR-A accessories from the Basic license tier.

Summary of the Photographic Evidence (to show with this brief):

Step 1: Shows the device fully updated and "Healthy."

Step 2: Confirms the MTR Basic license is active on the account.

Step 3: Shows the device initially worked ("Available" state).

Step 4: Shows the final "Licence not supported" error after the refresh.

Would you like me to create a version of the sequential photo log with the client's name blurred out so you can safely attach it to this Microsoft ticket?

Description:

We are documenting a reproducible authentication failure within the Microsoft Teams Rooms (MTR) on Android ecosystem, specifically affecting the RoomPanel Plus E2 hardware class.

Technical Analysis:

Initial Handshake Success: The device initially achieves a "Healthy" status via the standard /devicelogin flow. All telemetry in the Teams Admin Center (TAC) confirms the Teams Admin Agent, OEM Agent, and Intune Compliance are "Up to Date."

Licensing Context: The resource account is provisioned with a Microsoft Teams Rooms Basic license.

Failure Mode (Token Revocation): Within a 24-hour cycle, the Microsoft Identity Provider (IdP) revokes the session during a background token refresh. The client-side application returns the error: "Your current licence is not supported on this device."

Hardware Classification Issue: The failure appears to be a backend misclassification. We suspect the RoomPanel (Meeting Room Accessory) is being identified as a "Primary MTR Console," which may be causing the MTR Basic license to be rejected during the entitlement handshake.

Objective: Confirm if there has been a recent Service Policy Regression or a User Agent mismatch in the Microsoft Licensing Service that is now gating MTR-A accessories from the Basic license tier.

Technical Evidence Log: The Knight School (Sequential Workflow)

We have attached a clean, sequential log  documenting the precise steps taken to activate the RoomPanel Plus E2 and the resulting failure states.

1. Full Environmental Health Checks and Updates (Software Health is 'Up to date' and 'Healthy').

2. Verification of the MTR Basic License as Checked and Active on the account.

3. Initial Successful Initialization and Synchronization State (Panel functional with Boardroom Calendar).

4. The subsequent re-authentication prompt flow ([Moderator note: personal info removed] pairing code).

5. Re-validating the resource account (([Moderator note: personal info removed]).

6. The definitive rejection: "Signing out... licence is not supported."

This chronological sequence proves that all prerequisites were met and that the standard deployment path was followed before the backend failure occurred.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian-Ng 11,715 Reputation points Microsoft External Staff Moderator
    2026-03-26T16:58:20.86+00:00

    Hi @Jhon Alvarez, 

    Thank you for providing such a comprehensive and high-quality technical breakdown regarding the authentication failures on the RoomPanel Plus E2 hardware class. Documentation of this caliber is invaluable to the community. 

    Based on your analysis, the device successfully completes the initial /devicelogin handshake and maintains a healthy status in the Teams Admin Center (TAC). However, within a 24-hour cycle, the Microsoft Identity Provider (IdP) revokes the session during a background token refresh, resulting in the error: "Your current license is not supported on this device." Your hypothesis suggests a backend misclassification where the RoomPanel accessory is being incorrectly identified as a primary MTR console, leading to an entitlement rejection under the MTR Basic license. 

    This issue likely stems from a service-side logic error that requires escalation to Microsoft engineers, who maintain exclusive access to the internal identity and licensing logs necessary to diagnose the token refresh failure. Furthermore, only an official support engagement can address potential hardware entitlement regressions or perform the specialized tenant-level diagnostics required to rectify hardware classification mismatches within Microsoft’s backend database. 

    To ensure this is handled by the appropriate Teams Rooms Engineering department, please follow these steps: 

    1. Log in to the Microsoft 365 Admin Center. 
    2. Navigate to Support > Help & support. 
    3. Enter a brief summary and select Contact Support. 
    4. Use the categorization you identified: Microsoft Teams > Meetings and calls > Other. 
    5. Attach your technical evidence log. 

    For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin. 

    By opening a support ticket, you ensure that this reproducible failure is tracked officially, which often leads to a broader service-side fix if other organizations are experiencing the same regression. 

    Thank you for your diligence in documenting this for the community, and I appreciate your cooperation. 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Q&A Assist
    2026-03-26T14:27:00.5633333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The described behavior can be explained and validated using existing guidance for Teams Rooms licensing, Conditional Access, and Android device sign-in; there is no documented evidence in the provided material of a known service-side regression specific to RoomPanel Plus E2 or a Basic/Pro “hardware class” mismatch.

    Key points from the available guidance:

    1. License type and device role
    • Teams Rooms devices that are centrally IT-managed are expected to use Teams Rooms Pro or Teams Rooms Basic licenses, plus any required calling/security add-ons. No other licenses should be applied to the resource account.
    • Teams Rooms Pro/Basic licenses are per room and must not be shared across multiple devices that are not part of the same room.
    • The documentation does not differentiate licensing entitlements between “primary console” and “accessory” (panel) within the Basic vs Pro SKUs; it only states that the resource account must have a valid Teams Rooms license and meet authentication requirements.
    1. “License not supported” after successful initial sign-in The pattern of:
    • Initial successful sign-in and “Healthy” state, followed by
    • Token revocation and forced sign-out within a short period is consistent with Conditional Access / compliance or sign-in policy issues rather than a pure SKU entitlement failure.

    From the Conditional Access and Android troubleshooting guidance:

    • If a device is marked noncompliant or blocked by an unsupported Conditional Access policy, Microsoft Entra stops renewing tokens or revokes them, which causes:
      • Devices signing out randomly
      • Sign-in loops
      • Teams freezing or failing to sign in
    • The Sign-in frequency setting can force periodic reauthentication; each reauth can create new device objects until device limits are hit, at which point sign-in fails.
    • Terms of Use + MFA policies can also cause sign-in failures on Teams Android devices.
    1. Recommended checks for this scenario Given the symptoms, the following checks are explicitly recommended in the documentation for Teams Rooms on Android / panels:
    1. Verify sign-in failures and token revocation
    • In Microsoft Entra admin center → Monitoring & health → Sign-in logs, review the User sign-ins (non-interactive) tab for the resource account.
    • Look for entries where:
      • Application = Microsoft Authentication Broker
      • Status = Failure
      • Resource = Device Registration Service
    • These entries indicate the device is being blocked at the token/device registration level, which aligns with token revocation behavior.
    1. Run the Microsoft Teams Rooms Sign-in connectivity test
    • Use the Microsoft Remote Connectivity Analyzer → Microsoft Teams Rooms Sign in test.
    • Sign in with a Global Administrator account, then specify the resource account used on the RoomPanel Plus E2 and select the appropriate device type.
    • Review the test output for failures or warnings; follow the linked remediation guidance for each failing check.
    1. Review Conditional Access and compliance policies
    • Check for Conditional Access policies applied to the resource account and/or device that:
      • Enforce Sign-in frequency on shared resource accounts. Best practice is to exclude resource accounts from sign-in frequency conditions; otherwise, devices will sign out until an admin re-signs them in.
      • Require device compliance in ways that are not supported or not yet met by the Teams Rooms on Android / panel device.
    • For Intune compliance:
      • Confirm the device meets the supported compliance policies for Teams Rooms on Android (for example: minimum OS version > Android 10, no rooted devices, encryption required).
      • Ensure the compliance policy is correctly assigned to both the device and the resource account.
    1. Use device filters and proper scoping
    • Use filters for devices in Conditional Access to:
      • Exclude shared Teams Rooms Android devices (including panels) from policies intended for personal devices.
      • Apply only the minimal, supported policies to these shared devices.
    • Where possible, use attributes such as device.displayName or extension attributes to reliably identify the RoomPanel Plus E2 devices and scope policies appropriately.
    1. Licensing-specific notes
    • Teams Rooms Pro/Basic licenses are intended for a single room; using the same resource account across multiple devices in different rooms violates terms of use and can cause unexpected behavior.
    • Avoid assigning OneDrive for Business to IT-managed Teams Rooms resource accounts to prevent user content from being stored on the room’s OneDrive.
    • There is no statement in the provided material that a Teams Rooms Basic license is invalid for Android-based panels; the guidance treats Teams Rooms on Android and Teams panels as supported device types under the Teams Rooms licensing model, subject to Conditional Access and compliance requirements.
    1. Next steps for the described case Based on the documented behavior and tools:
    2. Confirm in Entra sign-in logs whether the resource account’s non-interactive sign-ins show failures for Microsoft Authentication Broker against Device Registration Service around the time the device signs out.
    3. Run the Microsoft Teams Rooms Sign in connectivity test for the resource account to validate licensing, permissions, and policy impact from the service side.
    4. Review and, if necessary, adjust Conditional Access:
      • Exclude the resource account from Sign-in frequency policies.
      • Ensure only supported CA and compliance policies are applied to Teams Rooms on Android / panels.
    5. Verify Intune compliance status for the RoomPanel Plus E2 device and ensure it meets the documented minimum requirements.

    If, after these checks, the device still shows “Your current licence is not supported on this device” and the connectivity test confirms licensing and policies are correct, the evidence set (sign-in logs, Remote Connectivity Analyzer output, and the sequential photo log with identifiers redacted) should be attached to a support ticket for escalation, as the next step is formal service-side investigation rather than a documented configuration fix.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.