Teams Phones Major Updates Have Begun

Picture of John Miller
John Miller

Cloud Solutions Architect

Introduction

This is a follow up to our earlier article about the major upgrades to native Teams phones taking place this year:

  1. The operating system on the phones will be upgraded to Android 12.
  2. Management of Native Teams phones in Intune will switch to the Android Open Source Project (AOSP) from the Android Device Administrator.

As of late June, the Android 12 firmware update from AudioCodes has become available through the Teams Admin Center (TAC) and AudioCodes One Voice Operations Center (OVOC). Poly is providing the update through the Poly LENS management platform. It is expected that it will become available through the TAC. Read below for some additional guidance for these upgrades.

Microsoft recently published Migrating Teams Android Devices to AOSP Device Management from Device Administrator. This article describes:

  1. How to configure Intune to enroll and manage Native Teams phones that use the AOSP management platform.
  2. Some organizations have added enrollment, compliance and conditional access policies to Intune to manage native Teams phones. This article tells you what to do to prepare to move these managed phones from the Android Device Administrator platform to the AOSP platform. This must be setup before upgrading these managed devices to Android 12.

If You Currently Manage Native Teams Phones in Intune – READ THIS!

Two (2) years ago I summarized the information from Microsoft about how to enroll native Teams phones in Intune:


Native Teams phones running the Android 9 operating system have run under the Android Device Administrator (ADA) platform. Intune is ending support for ADA beginning December 31, 2024.

If you have setup Intune to enroll and manage native Teams phones based on the ADA platform, you must prepare your organization before the support ends.

You should complete these steps before upgrading any enrolled phones to the Android 12 operating system. If the AOSP enrollment policy is implemented in Intune, Microsoft states that when you upgrade an enrolled native Teams phone, Intune will automatically re-enroll the phone using the AOSP enrollment.

The steps to setup AOSP managed native Teams phones are very similar to those in the original articles, mentioned previously. Rather than completely reproduce those blogs, I will just provide the required changes here.

Create an AOSP Enrollment Profile

  1. Sign into the “Microsoft Intune Admin Center.”
  2. If you don’t have an Intune filter defined for native Teams phones, please refer to the “Create an Intune filter for Teams Phones” section in the first blog article.
  3. Click on “Devices.”
  4. Click on “Enrollment.”
  5. Under “Android Open Source Project (AOSP),” click “Corporate-owned, user-associated devices.”
  •  

6. Click “Create profile.”

7. Type in a name for the profile.
8. Optionally, add a description.
9. An expiration date ninety (90) days in the future will be provided. You can change this at your discretion, but it cannot be longer than ninety (90) days from today’s date.
10. Set “Wi-Fi” to “Not configured.”
11. Select “Enabled” for “For Microsoft Teams devices.”
11. Click the “Next” button.

13. Click the “Create” button on the next screen.

Create an AOSP Management Configuration Policy

  1. Click on “Devices.”
  2. Click “Configuration.”
  3. Under the “Policies” tab, click the “Create” drop-down menu.
  4. Click “New Policy.”

5. In the “Create Profile” window, select “Android (AOSP)” from the “Platform” drop-down menu.
6. From the “Profile type” drop-down menu, select “Device restrictions.”
7. Click the “Create” button.

8. Provide a name for the policy.
9. Optionally, add a description.
10. Click the “Next” button.

11. Click on “General.”
12. Click “Yes” for “Block Screen Capture.” This is the only setting that Microsoft recommends currently.
13. Click the “Next” button.

14. Click the “+ Add all devices” button.
15. Click “Edit filter.”

16. Click on the “Include filtered devices in assignment” button.
17. Click on the appropriate filter for native Teams phones.
18. Click the “Select” button.

19. Click the “Next” button.

20. Click the “Create” button.

Create a Device Compliance Policy for the Teams Phones

  • Follow the steps in the first blog article. At step “3”, choose “Android (AOSP)” instead of “Android Device Administrator”.
  • Provide a new unique name for the policy and add a description as needed.
  • The Intune Compliance Policy Options for the Teams phones from September 14, 2022, remain the same.

Exclude Android Device Administrator Devices From App Protection Policies

  • When you look at the settings for this that you previously made, you should see that Android AOSP devices have been added to the “Device Types” section.

Firmware Upgrade Notes

  • Do not upgrade phones enrolled in Intune until you have prepared Intune to enroll and manage these upgraded phones. Please see the information above.
  • The current certified firmware versions for Native Teams Phones, Android Rooms, Displays and Panels can be found on the Microsoft Teams certified Android Devices Web page.

AudioCodes

  • The current firmware release from AudioCodes is 2.3.423.
  • The firmware can be installed through the Teams Admin center or the AudioCodes OVOC management platform.
  • AudioCodes C448s and C450s phones cannot be upgraded to Android 12.
    • AudioCodes has provided a few methods for converting these phones to function through the Teams SIP Gateway:
      • They can be switched through the OVOC platform’s Device Manager module.
      • The change can be made through the phone’s web interface.

- Upgrading through the Teams Admin Center

  • If your phones are not currently running version 2.3.423, they can be upgraded through the Teams Admin Center (TAC). Please refer to the Update Microsoft Team devices remotely Microsoft article.
  • Upgrades through the Teams Admin Center are made incrementally. For example, if you have a phone that is running version 1.17.561, you will probably have to run through a few intermediate upgrades before the TAC finally installs version 2.3.423.

- Upgrading through the AudioCodes One Voice Operations Center (OVOC)

  • AudioCodes native Teams phones can also be upgraded through the Device Manager module of the OVOC management platform.

  • You must own Device Manager licenses to be able to use the module to manage and update your phones.

  • The Device Manager will let you install specific versions of the firmware to your devices.

  • Before installing version 2.3.423, phones should be running version 1.19.642.

  • Upgrading phones running earlier versions to 2.3.423 is not recommended.

HP | Poly

  • The current firmware release from HP | Poly for the native Teams phones is 9.0.0.10315.

  • It does not appear that this release is available through the Teams Admin Center as of August 9, 2024. · It can be installed using the Poly LENS platform.

  • If a phone is running a firmware version older than 8.1.4, the upgrade to 9.0.0.10315 will automatically install version 8.1.4 as part of the upgrade process.

Yealink

  • The MP54, 56 and 58 have been certified by Microsoft through October 4, 2026, running version 122.15.0.135.

  • The CP965 is certified through the same date running 143.15.0.48.

  • The MP52 is not in the list. This suggests that this model cannot be upgraded to Android 12. Please check with Yealink if you have any of these phones.

  • Available versions:

    • 145.15.0.83: for the MP52 released on January 18,2024. This version appears to run under the Android 9 operating system.

    • 91.15.0.136: for the VP50 released on the same date.

    • 122.15.0.142: for the MP54, 56 and 58 released on October 9, 2023. This version appears to be based on Android 12.

Summary

The changes for Native Teams Phones have begun updating them to run under the Android 12 operating system and replacing the Android Management platform in Microsoft Intune. Organizations should follow the guidance and upgrade their phones before Microsoft starts to deprecate the Android Device Administrator platform at the end of the year. While Microsoft has not provided specifics, it should be inferred that phones currently managed in Intune on the Android Device Administrator will cease to be managed when this platform is sun downed in Intune. We are working with Microsoft to determine how to continue to enroll and manage these devices in Intune.

Stay tuned to the eGroup Enabling Technologies news page for updates! eGroup Enabling Technologies is available and ready to answer any questions that you might have about Microsoft Teams, Teams Phone, and Teams Devices. If you need help with implementing or migrating to Microsoft Teams or Teams Phone or upgrading your devices, please contact us at info@eGroup-us.com.

Links

Need Assistance with Microsoft Intune?

Contact our team today to schedule a call with one of our experts.