Yealink MP5X E2 Teams phones upgraded to Android 15 devices may be marked inactive and noncompliant and signed out

Yealink MP5X E2 Teams phones upgraded to Android 15 may become noncompliant in Intune due to invalid enrollment certificates, causing sign-outs after a 30-day grace period. Admins should inform users, advise re-sign-in to renew certificates, and review Conditional Access policies to mitigate impact.

[Introduction]

We’re aware of a known issue affecting Yealink MP52 E2, MP54 E2, MP55 E2, MP56 E2, and MP58 E2 Teams phone devices after upgrading to Android 15. On impacted devices, enrollment certificates used for secure communication with Microsoft Intune may become invalid, preventing the devices from communicating with Intune. As a result, affected devices may be reported as noncompliant.

For organizations that enforce compliance-based Conditional Access policies with a 30-day grace period, users may be signed out when that grace period expires. We are actively investigating this issue and will share updates as they become available.

[How this affects your organization:]

Who is affected:

• Organizations using Yealink MP5X E2 Teams phones (MP52/MP54/MP55/MP56/MP58 E2) upgraded to Android 15
• Admins managing devices with Microsoft Intune and compliance-based Conditional Access policies

What will happen:

• Devices running Android 15 (firmware version 176.15.0.191) may appear as noncompliant in Intune.
• Devices may be marked inactive due to failed certificate-based communication.
• Users may be signed out after the Conditional Access grace period expires.
• Users may lose access to corporate resources if policies require compliant devices.
• This issue is not configurable by admins and occurs after the OS upgrade.

[What you can do to prepare:]

• Inform your helpdesk and users about potential sign-out behavior.
• Advise affected users to sign in again on the device to re-establish enrollment and generate a new certificate.
• Review Conditional Access policies that require compliant devices.

Admins may also wish to review their compliance-based Conditional Access configuration as a temporary mitigation to reduce the immediate risk of user sign-outs. However, we do not recommend broadly disabling Conditional Access, as this may introduce security risk. If you choose to make temporary policy changes, carefully evaluate the security implications and limit changes as much as possible.

[Compliance considerations:]

Devices may fall out of compliance, which can trigger Conditional Access enforcement (sign-outs and access loss).