# Teams phones and certified devices Canonical: https://warmtransfer.net/knowledge/teams-phone-devices Last verified: 2026-09-25 Microsoft Teams certified phone devices provide voice capabilities and device management natively within the Microsoft Teams ecosystem[^17][^55]. Organizations manage these endpoints alongside compatible third-party hardware using specialized provisioning, licensing, and firmware lifecycle policies[^29][^46][^16]. ## Device Certification and Hardware Lifecycle Teams phone certification end dates depend on the Android version running on the hardware when it enters the program, though original equipment manufacturers (OEMs) can extend certification by upgrading Android and recertifying[^16]. The OEM is responsible for maintaining a device's certified status, and decisions to end life, end sales, or decline recertification belong to the OEM[^31]. After device certification expires, Microsoft commits to supporting the latest version of Teams device applications on it for 2 years, while retaining the right to modify that support policy[^53]. As of the 2026-09-23 page update, the certified Teams phones catalog includes only AudioCodes, Poly, and Yealink models (AudioCodes C4xxHD, Poly CCX and Trio C60, Yealink MP and CP965) along with their expansion modules, with no Crestron models listed[^17]. Yealink MP52 E2, MP54 E2, MP55 E2, MP56 E2, MP58 E2, and MP66 W run Android 15 with certification through October 15, 2030[^59]. Poly CCX350, CCX400, CCX500, CCX505, CCX600, and Trio C60 run Android 12 with certification ending August 15, 2028[^36]. Certain expansion modules carry earlier certification end dates than their host phones: the AudioCodes Exp Module on C455HD-DBW, Poly EM60, and Yealink EXP50 end certification on August 15, 2027, whereas the AudioCodes G2 Exp module on the C456HD ends August 15, 2028[^21]. The support table contains no Android 16 row[^6]. The certification end date for Android 10 and Android 11 Teams devices was extended from September 3, 2025 to September 3, 2026, with Microsoft support remaining at September 3, 2027[^4]. Teams devices on Android 12 and Android 13 have a certification end date of August 15, 2028 and a Microsoft support end date of August 15, 2030, extended from an earlier certification end date of October 6, 2026[^5]. Certification and support end dates for newer Android versions are October 4, 2029 and October 4, 2031 for Android 14, October 15, 2030 and October 15, 2032 for Android 15, and June 16, 2031 and June 16, 2033 for Android 17[^6]. Android 7 Teams phones (including the Yealink T55/T56/T58 families, Yealink CP960, and Poly Trio 8500/8800) reached end of certification on October 4, 2021 and end of Microsoft support on October 4, 2023[^19]. Android 9 Teams phones (including the Yealink MP52, VP59, AudioCodes C448HD, C450HD, and Crestron UC-2, UC-P8, and UC-P10 with -C variants) reached end of certification on August 5, 2023 and end of Microsoft support on August 5, 2025[^20]. Microsoft tests and supports only the latest and latest-minus-1 versions of Microsoft applications on Teams Android devices, requiring customers to install the latest version to obtain code defect fixes[^27]. ## Device Management and Migration to PMP Managing Teams phones requires an administrator assigned the Global admin, Teams Service admin, or Teams Device admin role, with Microsoft recommending the least-privileged role[^29]. Starting in June 2026, device inventory, monitoring, and management for Teams phones, Teams Rooms on Android, Teams panels, and SIP devices move from the Teams admin center (TAC) to the Teams Rooms Pro Management Portal (PMP); Teams Displays management is not moving[^55]. Accessing PMP requires at least 1 Teams Rooms Pro, Basic, or Standard licence, a Teams Shared Space licence (formerly Shared devices), or an existing device enrolled in PMP[^34]. Existing TAC-enrolled phones migrate into PMP automatically upon updating to Admin Agent 830 or later[^34]. PMP portal URLs are: - Public and GCC: portal.rooms.microsoft.com[^35] - GCC High: devices.gov.teams.microsoft.us[^35] - DoD: devices.dod.teams.microsoft.us[^35] During migration, TAC device tags can be imported into PMP as Groups; TAC tags bind to the signed-in account, whereas PMP Groups bind to the device itself[^56]. TAC configuration profiles can be imported into PMP as Settings Templates[^18]. ## Updates and Maintenance Windows Now that PMP Android update management is generally available, automatic updates through TAC have ceased, except for the minimum required Admin Agent[^54]. Automatic updates run and pause exclusively in PMP[^54]. PMP update management requires Admin Agent 830 (1.0.0.202606082157) or later[^2]. Teams phones running agents below 830 receive only Admin Agent updates via TAC and obtain no other firmware or application updates until upgraded to 830[^2]. Government cloud tenants (GCC, GCC High, DoD) require Admin Agent 856 (1.0.0.202607160723), and these mandatory updates cannot be paused[^3]. Devices on Admin Agent 794 or later are updated to the latest eligible agent by Microsoft Zero-Day Update when powered on and connected; devices below 794 must be updated manually via OEM firmware containing agent 794 or later[^60]. Public cloud firmware for Poly CCX350/400/500/505/600 and Trio C60 lists 9.5.1.0067 (AOSP), released September 15, 2026, which bundles Admin Agent 1.0.0.202604060507 (820)[^37]. Microsoft publishes a separate firmware table for federal clouds (GCC High and DoD), which features later release dates and sometimes different versions compared to public releases[^22]. Microsoft has recalled certain firmware releases, keeping them visible in firmware listings with Recalled marked instead of a release date (such as Poly 9.0.0.10460 and Yealink MP54/MP56/MP58 122.15.0.157 and 122.15.0.160)[^23]. OEM firmware delivered via OEM services must be certified and available in TAC or PMP for the hardware to remain eligible for Microsoft support[^30]. Neither TAC nor PMP manages firmware or application updates for SIP Gateway devices[^42]. When administrators confirm switching to PMP update rings, an irreversible one-time mapping places every Teams phone into the General ring regardless of its previous TAC phase[^33]. PMP update rings cycle faster than previous TAC phases: - Staging: 0 to 6 days (compared to TAC Validation at 0 to 15 days)[^39] - General: 7 to 13 days (compared to TAC General at 16 to 45 days)[^39] - Executive: 14 to 20 days (compared to TAC Final at 46 to 60 days)[^39] PMP applies automatic updates only during a fixed maintenance window from 12 AM to 5 AM device local time; custom windows are not supported, and updates postpone if the device is busy[^28]. A tenant-wide pause of auto-updates lasts 2 weeks, after which updates resume automatically unless resumed earlier by an administrator[^57]. ## Enrollment, Provisioning, and Configuration Certified devices auto-enroll into Teams device management upon initial user sign-in, and auto-enroll into Microsoft Intune if the tenant has Intune licensing[^11]. Teams Android devices enroll into Intune using Android Open Source Project (AOSP) Device Management, which replaced legacy Device Administrator enrollment[^10]. Tenants may configure only 1 AOSP enrollment profile where "For Microsoft Teams devices" is Enabled[^9]. The token lifetime defaults to 65 years; if expired, existing devices cannot complete sign-in and new devices cannot enroll[^9]. Devices enroll using Teams resource account credentials rather than the profile QR code[^8]. If Conditional Access requires Intune compliance at sign-in without an assigned AOSP compliance policy, devices sign out following AOSP migration[^7]. Intune enrollment is optional, and removing Intune licences from resource accounts eliminates the need for an AOSP profile[^25]. Remote provisioning occurs in PMP by uploading the device MAC address or hardware ID under Planning > Android Devices, generating a verification code (valid for 24 hours in single or bulk operations), entering the code on the hardware under Settings > Provision device, and completing sign-in at microsoft.com/devicelogin[^38][^58]. Partial configuration profile application applies only explicitly configured settings, requiring minimum firmware of AudioCodes AOSP 2.3.497, Poly 9.1.0.9017, or Yealink 122.15.0.166; unsupported devices apply every setting, reverting unconfigured values to default[^32]. ## Phone Policies, Better Together, and Calling The `Set-CsTeamsIPPhonePolicy` cmdlet controls endpoint behavior via several parameters: - `SignInMode`: Accepts `UserSignIn` (individual user experience), `CommonAreaPhoneSignIn` (common area phone experience), or `MeetingSignIn` (meeting/conference room experience)[^41]. - `AllowBetterTogether`: Controls Better Together locking and unlocking alongside a connected Windows PC running the 64-bit Teams desktop client; defaults to `Enabled`[^12]. - `AllowHomeScreen`: Configured as `Enabled`, `EnabledUserOverride`, or `Disabled` (defaults to `EnabledUserOverride`)[^26]. - `AllowHotDesking`: Boolean value enabling hot desking[^26]. - `HotDeskingIdleTimeoutInMinutes`: Signs the account out when idle timeout is reached[^26]. - `SearchOnCommonAreaPhoneMode`: Controls global address book search while in common area phone mode[^26]. Teams Rooms Basic licences are blocked from signing in to Teams phone devices and are unsupported on them[^40]. Teams Rooms Basic licences do not include Intune[^25]. The Teams Shared Space licence includes Phone System features, and Calling Plans can be added if Direct Routing or Operator Connect is not used[^14]. Applying a policy to a common area phone account can take up to an hour to take effect, and the phone should be signed out and back in[^15]. Because common area accounts do not reliably report presence, common area phones cannot serve as agents in call queues using presence-based routing[^13]. In the United States, a Teams phone cannot place 911 emergency calls if it has no internet connection or is not signed in; the device displays an alert notification under these conditions[^1]. ## SIP Gateway Integration SIP Gateway enables compatible third-party SIP hardware—including Cisco MPP IP phones (enterprise firmware must first be converted to MPP), Poly VVX and Trio, Yealink T-series, and AudioCodes 400HD—to sign in and make or receive Teams calls[^46]. SIP Gateway requires Teams, Skype for Business Online Plan 2, Microsoft Phone System, PSTN connectivity, and an assigned phone number with PSTN calling enabled[^51]. SIP Gateway is not yet available for DoD[^51]. SIP Gateway supports IPv4 only, even though Microsoft Teams core services and clients support both IPv4 and IPv6[^48]. Provisioning server URLs are: - `http://emea.ipp.sdg.teams.microsoft.com`[^50] - `http://noam.ipp.sdg.teams.microsoft.com`[^50] - `http://apac.ipp.sdg.teams.microsoft.com`[^50] These are deployed using DHCP option 66 (Yealink, Alcatel-Lucent Enterprise) or option 160 (Cisco, Poly, AudioCodes); Cisco endpoints require `/$PSN.xml` appended[^50]. Starting January 1, 2026, location-based Conditional Access exclusions must also exclude SIP Gateway service IPs in the `70.152.x.x` range for each region[^44]. To allow calling, admins must enable `AllowSIPDevicesCalling` in the Teams calling policy (defaults to `False`) or enable "SIP devices can be used for calls" in TAC, which can take up to 24 hours to take effect[^45]. SIP Gateway devices can participate as call queue agents, but presence-based routing is not supported because SIP Gateway does not publish device presence[^49]. To enroll a SIP device as a common area phone, in this order: onboard it to SIP Gateway; add its MAC address under Teams devices > SIP devices > Provision devices; generate a verification code; dial *55* followed by the code on the device; then sign in with the pairing code shown in the Sign in a user dialog[^47]. Bulk sign-in signs in shared accounts in batches of up to 100 devices, with at most 3 concurrent batches per region, within 72 hours of onboarding or within 7 days of a device being signed out, provided accounts have CommonAreaPhone policy, a phone number, and AllowSIPDevicesCalling, and do not have MFA[^43]. SIP Gateway automatically offboards stale devices: signed-in (paired) devices after 30 days without a connection, signed-out (unpaired) devices after 14 days, and an offboarded device can be onboarded again after a factory reset[^52]. ## See also - See also [Teams Rooms and common area phones calling](https://warmtransfer.net/knowledge/teams-rooms-common-area-phones). - See also [Microsoft Teams Phone architecture and licensing](https://warmtransfer.net/knowledge/teams-phone-architecture). - See also [Teams Phone Direct Routing and SBC certification](https://warmtransfer.net/knowledge/teams-direct-routing). - See also [Teams Operator Connect and Azure Communication routing](https://warmtransfer.net/knowledge/teams-operator-connect). - See also [Teams voice routing policies and dial plans](https://warmtransfer.net/knowledge/teams-voice-routing). - See also [Teams contact center integration models](https://warmtransfer.net/knowledge/teams-contact-center-integration). - See also [Setting up Microsoft Teams Direct Routing](https://warmtransfer.net/knowledge/teams-direct-routing-setup). - See also [Microsoft Teams Calling Plans](https://warmtransfer.net/knowledge/teams-calling-plans). - See also [Microsoft Teams auto attendants and call queues](https://warmtransfer.net/knowledge/teams-auto-attendant-call-queue). - See also [Setting up Microsoft Teams auto attendants and call queues](https://warmtransfer.net/knowledge/teams-auto-attendant-call-queue-setup). - See also [Setting up dynamic emergency calling in Microsoft Teams](https://warmtransfer.net/knowledge/teams-dynamic-e911-setup). - See also [Microsoft Teams compliance recording](https://warmtransfer.net/knowledge/teams-compliance-recording). - See also [Microsoft Teams shared calling and call delegation](https://warmtransfer.net/knowledge/teams-shared-calling). - See also [Porting numbers to Microsoft Teams](https://warmtransfer.net/knowledge/teams-number-porting). - See also [Troubleshooting Teams call queues and auto attendants](https://warmtransfer.net/knowledge/teams-call-queue-troubleshooting). ## Applicability Applies to: Microsoft Teams phones, Microsoft Teams devices on Android, Microsoft Intune for Teams Android devices, Microsoft Teams Rooms Pro Management Portal, Microsoft Teams admin center, MicrosoftTeams PowerShell module, and Microsoft Teams SIP Gateway. Deployments: cloud and multi-tenant. Sources checked 2026-09-25. In GCC and DoD environments, every Android management feature including phone inventory, update management, and settings is scheduled for September 2026 and none is marked completed, while public cloud features are marked completed from June to mid-July 2026[^24]. Dynamic 911 calling limitations when offline or signed out apply to the United States region[^1]. SIP Gateway is not yet available for DoD[^51]. ## What remains uncertain Whether the rename of Teams Shared Devices to the Teams Shared Space licence changed the underlying SKU or price is not covered by the sources below. Authentication best practices for Teams phones regarding Conditional Access and MFA are not covered by the sources below. The existence or contents of a certified device apps page listing Admin Agent releases 830 and 856 is not covered by the sources below. Dynamic emergency calling behavior on Teams phones and SIP Gateway devices beyond the requirement to be signed in with internet connectivity is not covered by the sources below. The configuration of PMP update rings and custom rings is not covered by the sources below. What's new in Microsoft Teams devices release notes for phone applications is not covered by the sources below. The availability or configuration of SIP Gateway dynamic filters for Conditional Access exclusion is not covered by the sources below. The final GCC and DoD completion status of Android management in PMP beyond the scheduled September 2026 date is not covered by the sources below. ## Sources [^1]: A Teams phone that is not signed in, or has no internet connection, cannot place 911 calls; the phone shows a notification when this is the case. Source: [Phones for Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/devices/phones-for-teams), Features supported by Teams phones, Dynamic and enhanced E911 support, Important callout. Checked 2026-09-25. [^2]: PMP update management for Teams Android devices requires Admin Agent 830 (1.0.0.202606082157) or later. Teams phones below 830 receive only Admin Agent updates, through TAC, and get no other app or firmware updates until they reach 830. Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), Moving Android updates from auto-update phases in TAC to rings in PMP; Device type specific updates guidance, Teams phones. Checked 2026-09-25. [^3]: For government cloud tenants (GCC, GCC High, DoD), the minimum Admin Agent for PMP management is 856 (1.0.0.202607160723). These mandatory Admin Agent updates cannot be paused. Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), Updates guidance for government cloud customers. Checked 2026-09-25. [^4]: The certification end date for Android 10 and Android 11 Teams devices was extended from September 3, 2025 to September 3, 2026; the Microsoft support end date stays at September 3, 2027. Source: [Android versioning support for Teams devices](https://learn.microsoft.com/en-us/microsoftteams/devices/android-version-support), Android OS and OEM firmware support, Note and support table. Checked 2026-09-25. [^5]: Teams devices on Android 12 and Android 13 have a certification end date of August 15, 2028 and a Microsoft support end date of August 15, 2030. Both dates were extended; the certification end was previously October 6, 2026. Source: [Android versioning support for Teams devices](https://learn.microsoft.com/en-us/microsoftteams/devices/android-version-support), Android OS and OEM firmware support, Note and support table. Checked 2026-09-25. [^6]: Certification and support end dates for newer Android versions are: Android 14, October 4, 2029 and October 4, 2031; Android 15, October 15, 2030 and October 15, 2032; Android 17, June 16, 2031 and June 16, 2033. The table has no Android 16 row. Source: [Android versioning support for Teams devices](https://learn.microsoft.com/en-us/microsoftteams/devices/android-version-support), Android OS and OEM firmware support, support table. Checked 2026-09-25. [^7]: If a tenant's Conditional Access requires Intune compliance at sign-in and no AOSP compliance policy is assigned, a Teams Android device signs out after migrating to AOSP Device Management. Source: [Intune Enrollment for Teams Android Devices](https://learn.microsoft.com/en-us/microsoftteams/rooms/android-migration-guide), Step 2 - Set up AOSP Device Management Compliance Policies (if necessary), first paragraph. Checked 2026-09-25. [^8]: Teams Android devices do not use the QR code included in an AOSP enrollment profile; instead they enroll with the Teams resource account credentials. Source: [Intune Enrollment for Teams Android Devices](https://learn.microsoft.com/en-us/microsoftteams/rooms/android-migration-guide), Step 1, final Note. Checked 2026-09-25. [^9]: A tenant can have only one AOSP enrollment profile with For Microsoft Teams devices set to Enabled. If that profile's enrollment token expires, devices cannot complete sign-in and new devices cannot enroll. The token lifetime defaults to 65 years. Source: [Intune Enrollment for Teams Android Devices](https://learn.microsoft.com/en-us/microsoftteams/rooms/android-migration-guide), Step 1 - Set up a new AOSP device management enrollment profile, profile settings and Note. Checked 2026-09-25. [^10]: Teams Android devices, including Teams phones, enroll in Intune through Android Open Source Project (AOSP) Device Management, which replaced the legacy Device Administrator enrollment method. Source: [Intune Enrollment for Teams Android Devices](https://learn.microsoft.com/en-us/microsoftteams/rooms/android-migration-guide), Introduction, first paragraph. Checked 2026-09-25. [^11]: A certified device is enrolled for Teams device management automatically the first time a user signs in to Teams on it. Phones are also enrolled in Microsoft Intune automatically if the organization has signed up for Intune. Source: [Manage devices in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/devices/device-management), What devices can you manage?; Manage phones, Teams Rooms on Android, Teams displays, and Teams panels. Checked 2026-09-25. [^12]: With Better Together, a Teams phone locks and unlocks along with a connected Windows PC running the 64-bit Teams desktop client; the IP phone policy parameter AllowBetterTogether controls it and defaults to Enabled. Source: [Set-CsTeamsIPPhonePolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamsipphonepolicy), Parameters, -AllowBetterTogether. Checked 2026-09-25. [^13]: A common area phone cannot be an agent in a call queue that uses presence-based routing, because common area phone accounts do not reliably report presence. Source: [Set up the common area phones for Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/set-up-common-area-phones), Step 6 - Set up Advanced calling on common area phones, Note. Checked 2026-09-25. [^14]: The Teams Shared Space licence for common area phones includes Phone System features. Calling Plans licences may be added if the tenant does not use Direct Routing or Operator Connect. Source: [Set up the common area phones for Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/set-up-common-area-phones), Step 2, Using the Microsoft 365 admin center, Note. Checked 2026-09-25. [^15]: After a policy is assigned to a common area phone account, the phone should be signed out and back in; the assignment can take up to an hour to take effect. Source: [Set up the common area phones for Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/set-up-common-area-phones), Step 3, Calling policies, Note. Checked 2026-09-25. [^16]: A Teams phone's certification end date depends on the Android version the device runs when it enters the certification program. OEMs can extend certification by upgrading Android and recertifying the device. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Introductory paragraphs, second paragraph. Checked 2026-09-25. [^17]: As of the 2026-09-23 page update, the Certified Teams phones list contains only AudioCodes, Poly and Yealink models (AudioCodes C4xxHD, Poly CCX and Trio C60, Yealink MP and CP965) plus their expansion modules; no Crestron phone is listed as certified. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Certified Teams phones tab, device table. Checked 2026-09-25. [^18]: TAC configuration profiles for Teams Android devices can be imported into PMP as Settings Templates. Source: [Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/rooms/aboutunifieddevicemanagement-pmp1), Migration checklist, Step 3, Settings management. Checked 2026-09-25. [^19]: Android 7 Teams phones, including the Yealink T55/T56/T58 families, Yealink CP960 and Poly Trio 8500/8800, reached end of certification on October 4, 2021 and end of Microsoft support on October 4, 2023. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), End of certification tab. Checked 2026-09-25. [^20]: Android 9 Teams phones, including the Yealink MP52 and VP59, AudioCodes C448HD and C450HD, and Crestron UC-2, UC-P8 and UC-P10 (with -C variants), reached end of certification on August 5, 2023 and end of Microsoft support on August 5, 2025. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), End of certification tab. Checked 2026-09-25. [^21]: Some expansion modules have an earlier certification end date than the phones they attach to: the AudioCodes Exp Module on C455HD-DBW, the Poly EM60 and the Yealink EXP50 all end August 15, 2027. The AudioCodes G2 Exp module on the C456HD ends August 15, 2028. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Certified Teams phones tab, expansion module rows. Checked 2026-09-25. [^22]: Microsoft publishes a separate firmware release table for the federal clouds (GCC High and DoD). Its release dates are later than, and sometimes its versions differ from, the public cloud releases. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Firmware tab, Firmware versions released to the Federal clouds. Checked 2026-09-25. [^23]: Microsoft has recalled some Teams phone firmware releases: they stay listed in the firmware table with Recalled in place of a release date. Examples include Poly 9.0.0.10460 and Yealink MP54/MP56/MP58 122.15.0.157 and 122.15.0.160. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Firmware tab, Firmware versions released to the Public cloud, Release date column. Checked 2026-09-25. [^24]: In the transition guide's feature availability table, every Android management feature for GCC and DoD tenants, including phone inventory, update management and settings, is scheduled for September 2026 and none is marked completed. Public cloud features are marked completed from June to mid-July 2026. Source: [Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/rooms/aboutunifieddevicemanagement-pmp1), Specific feature availability in PMP, table columns DoD and GCC. Checked 2026-09-25. [^25]: Intune enrollment of Teams Android devices is optional: removing the Intune licence from resource accounts means no AOSP enrollment profile is needed. Teams Rooms Basic licences do not include Intune. Source: [Intune Enrollment for Teams Android Devices](https://learn.microsoft.com/en-us/microsoftteams/rooms/android-migration-guide), Prerequisites, Important callout. Checked 2026-09-25. [^26]: Set-CsTeamsIPPhonePolicy also sets AllowHomeScreen (Enabled, EnabledUserOverride or Disabled; default EnabledUserOverride), AllowHotDesking (Boolean), HotDeskingIdleTimeoutInMinutes (signs the account out when the idle timeout is reached) and SearchOnCommonAreaPhoneMode (controls global address book search in common area phone mode). Source: [Set-CsTeamsIPPhonePolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamsipphonepolicy), Parameters section, one heading per parameter. Checked 2026-09-25. [^27]: Microsoft tests and supports only the latest and the latest-minus-one versions of the Microsoft applications on Teams Android devices; to get a fix for a code defect, the customer must install the latest version. Source: [Android versioning support for Teams devices](https://learn.microsoft.com/en-us/microsoftteams/devices/android-version-support), Microsoft Teams Devices Applications Support, second and third paragraphs. Checked 2026-09-25. [^28]: PMP installs automatic updates on Teams Android devices only during a fixed nightly maintenance window, 12 AM to 5 AM device local time, and admins cannot set a custom window. If the device is busy, the update is postponed. Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), Key update management capabilities, items 5 and 7; FAQ, Does PMP support custom maintenance window. Checked 2026-09-25. [^29]: To manage Teams phones an administrator needs the Global admin, Teams Service admin or Teams Device admin role; Microsoft recommends using the least-privileged role. Source: [Phones for Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/devices/phones-for-teams), Introductory section, paragraph beginning To manage phones. Checked 2026-09-25. [^30]: The OEM supplies Android OS and firmware updates to Microsoft for certification, and they are distributed through the Teams admin center or Pro Management Portal. Firmware installed through an OEM's own service must be certified and available in TAC or PMP for the device to be eligible for Microsoft support. Source: [Android versioning support for Teams devices](https://learn.microsoft.com/en-us/microsoftteams/devices/android-version-support), Android OS and OEM firmware support, first two paragraphs. Checked 2026-09-25. [^31]: The OEM is responsible for keeping a device's Teams certified status, and the decisions not to recertify, to end sale or to end life are the OEM's. Source: [Android versioning support for Teams devices](https://learn.microsoft.com/en-us/microsoftteams/devices/android-version-support), Certification overview, paragraph beginning Original Equipment Manufacturers (OEM) are responsible. Checked 2026-09-25. [^32]: Partial application of Teams device configuration profiles applies only explicitly configured settings. It requires minimum phone firmware of AudioCodes AOSP 2.3.497, Poly 9.1.0.9017 or Yealink 122.15.0.166; on devices without support, every profile setting is applied, with defaults for unconfigured ones. Source: [Manage devices in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/devices/device-management), Use configuration profiles in Teams, Assign a configuration profile, OEM minimum firmware table; Frequently asked questions 1 and 2. Checked 2026-09-25. [^33]: When a tenant confirms that it wants to use PMP update rings, a one-time mapping places every Teams phone in the default General ring, whatever its TAC auto-update phase. The confirmation cannot be reversed. Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), Moving Android updates from auto-update phases in TAC to rings in PMP, one-time mapping list and Warning. Checked 2026-09-25. [^34]: To access PMP, an organization needs at least one of: a Teams Rooms Pro, Basic or Standard licence; a Teams Shared Space licence (formerly Shared devices); or a Teams device already enrolled in PMP. Existing Teams phones enrolled in TAC enroll in PMP automatically once they update to Admin Agent 830 or later. Source: [Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/rooms/aboutunifieddevicemanagement-pmp1), Migration checklist and prerequisites, Step 1, Licensing requirements for PMP access. Checked 2026-09-25. [^35]: The Pro Management Portal is at portal.rooms.microsoft.com for public and GCC tenants, devices.gov.teams.microsoft.us for GCC High and devices.dod.teams.microsoft.us for DoD. Source: [Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/rooms/aboutunifieddevicemanagement-pmp1), Migration checklist and prerequisites, Step 1. Checked 2026-09-25. [^36]: The Poly CCX350, CCX400, CCX500, CCX505, CCX600 and Trio C60 are certified on Android 12, with a certification end date of August 15, 2028. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Certified Teams phones tab, Poly rows. Checked 2026-09-25. [^37]: The most recent public-cloud firmware listed for Poly CCX350/400/500/505/600 and Trio C60 is 9.5.1.0067 (AOSP), released September 15, 2026. It bundles Admin Agent 1.0.0.202604060507 (820). Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Firmware tab, Public cloud, HP | Poly table, first row. Checked 2026-09-25. [^38]: Remote provisioning of a Teams Android device happens in the Teams Pro Management Portal, in this order: upload the device's ethernet MAC address or hardware ID under Planning > Android Devices; generate a verification code; a technician enters the code on the device under Settings > Provision device; the admin then completes sign-in remotely with the code shown, at microsoft.com/devicelogin. Source: [Remote provisioning and sign in for Teams Android devices](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-provision-remote-login), Steps 1 through 4. Checked 2026-09-25. [^39]: Default PMP update rings roll out faster than the TAC phases they replace: Staging 0-6 days (TAC Validation 0-15), General 7-13 days (TAC General 16-45) and Executive 14-20 days (TAC Final 46-60). Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), Moving Android updates from auto-update phases in TAC to rings in PMP, mapping table and Caution. Checked 2026-09-25. [^40]: Microsoft Teams Rooms Basic licences are not supported on Teams phone devices, and an account with a Basic licence is blocked from signing in to one. Source: [Phones for Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/devices/phones-for-teams), Required licenses, Important callout. Checked 2026-09-25. [^41]: The SignInMode parameter of the Teams IP phone policy takes one of three values: UserSignIn for an individual user's experience, CommonAreaPhoneSignIn for the common area phone experience, and MeetingSignIn for the meeting or conference room experience. Source: [Set-CsTeamsIPPhonePolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamsipphonepolicy), Parameters, -SignInMode. Checked 2026-09-25. [^42]: Neither the Teams admin center nor the Pro Management Portal manages app or firmware updates for SIP Gateway devices. Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), FAQ, Can admins manage app/firmware updates for SIP devices via PMP?. Checked 2026-09-25. [^43]: SIP Gateway bulk sign-in signs in shared accounts in batches of up to 100 devices, with at most 3 concurrent batches per region. It works only within 72 hours of onboarding, or within 7 days of a device being signed out. Accounts must have CommonAreaPhone policy, a phone number and AllowSIPDevicesCalling, and must not have MFA. Source: [Configure SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-configure), Bulk sign in; Bulk sign in prerequisites. Checked 2026-09-25. [^44]: From January 1, 2026, tenants that use location-based Conditional Access exclusions for SIP Gateway must also exclude additional SIP Gateway service IPs in the 70.152.x.x range, for each region. Source: [Configure SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-configure), Configure conditional access, Note and additional service IP list. Checked 2026-09-25. [^45]: To let users make calls from SIP devices, admins set AllowSIPDevicesCalling to True in the Teams calling policy (the default is False), or turn on SIP devices can be used for calls in the Teams admin center. Propagation can take up to 24 hours. Source: [Configure SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-configure), Enable SIP Gateway for the users in your organization. Checked 2026-09-25. [^46]: SIP Gateway lets compatible third-party SIP devices sign in to Teams and make and receive calls. Examples are Cisco IP phones on multiplatform (MPP) firmware, Poly VVX and Trio, Yealink T-series and AudioCodes 400HD; Cisco phones on enterprise firmware must be converted to MPP first. Source: [Plan SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan), Introduction; Compatible devices table, Cisco remarks. Checked 2026-09-25. [^47]: To enroll a SIP device as a common area phone, in this order: onboard it to SIP Gateway; add its MAC address under Teams devices > SIP devices > Provision devices; generate a verification code; dial *55* followed by the code on the device; then sign in with the pairing code shown in the Sign in a user dialog. Source: [Configure SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-configure), Provision and enroll SIP devices as common area phones, steps 1 to 8. Checked 2026-09-25. [^48]: SIP Gateway supports only IPv4, although the Teams service and clients support both IPv4 and IPv6. Source: [Configure SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-configure), Microsoft Teams and IPv6. Checked 2026-09-25. [^49]: SIP Gateway devices can be call queue agents, but SIP Gateway does not publish presence for devices, so presence-based routing is not supported for them. Source: [Plan SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan), Benefits of SIP Gateway, Call Queues and voice apps support. Checked 2026-09-25. [^50]: SIP Gateway provisioning server URLs are http://emea.ipp.sdg.teams.microsoft.com, http://noam.ipp.sdg.teams.microsoft.com and http://apac.ipp.sdg.teams.microsoft.com. They are set through DHCP option 66 for Yealink and Alcatel-Lucent Enterprise, or option 160 for Cisco, Poly and AudioCodes. Cisco devices also need /$PSN.xml appended. Source: [Configure SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-configure), Set the SIP Gateway provisioning server URL, Using DHCP and Note. Checked 2026-09-25. [^51]: To use SIP Gateway, a Teams user must have a phone number with PSTN calling enabled; the licence requirements listed are Teams, Skype for Business Online Plan 2, Microsoft Phone System and PSTN connectivity. SIP Gateway is not yet available for DoD. Source: [Plan SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan), Requirements to use SIP Gateway; Hardware, software, and licenses. Checked 2026-09-25. [^52]: SIP Gateway automatically offboards stale devices: signed-in (paired) devices after 30 days without a connection, signed-out (unpaired) devices after 14 days. An offboarded device can be onboarded again after a factory reset. Source: [Plan SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan), Benefits of SIP Gateway, Off board stale devices. Checked 2026-09-25. [^53]: After a device's certification expires, Microsoft commits to supporting the latest version of the Teams devices applications on it for two years, and keeps the right to change that support policy. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Introductory paragraphs, paragraph beginning After a certification expires. Checked 2026-09-25. [^54]: Now that Android update management in PMP is generally available, automatic updates through the Teams admin center have stopped except for the minimum required Admin Agent. Auto-updates run only through PMP, and pausing them is done only in PMP. Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), Moving Android updates from auto-update phases in TAC to rings in PMP, As part of general availability; FAQ, Can admins still pause updates via TAC?. Checked 2026-09-25. [^55]: Device inventory, monitoring and management for Teams Rooms on Android, Teams phones, Teams panels and SIP devices are moving from the Teams admin center to the Teams Rooms Pro Management Portal, starting June 2026. Teams Displays management is not moving. Source: [Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/rooms/aboutunifieddevicemanagement-pmp1), What's Changing? section and Note. Checked 2026-09-25. [^56]: TAC device tags can be imported into PMP as Groups. TAC tags are tied to the account signed in to a device, whereas PMP Groups are tied to the device itself. Source: [Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/rooms/aboutunifieddevicemanagement-pmp1), Migration checklist, Step 3, Tags, Note. Checked 2026-09-25. [^57]: In PMP, a tenant-wide pause of Android auto-updates lasts two weeks, after which updates resume automatically; admins can also resume earlier. Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), Key update management capabilities, item 8, Pause updates. Checked 2026-09-25. [^58]: The verification code used to remotely provision a Teams Android device is valid for 24 hours, and can be generated for one device or in bulk. Source: [Remote provisioning and sign in for Teams Android devices](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-provision-remote-login), Step 2: Generate a verification code. Checked 2026-09-25. [^59]: The Yealink MP52 E2, MP54 E2, MP55 E2, MP56 E2, MP58 E2 and MP66 W are certified on Android 15, with a certification end date of October 15, 2030. Source: [Teams phones certified hardware](https://learn.microsoft.com/en-us/microsoftteams/devices/teams-phones-certified-hardware), Certified Teams phones tab, Yealink rows. Checked 2026-09-25. [^60]: A Teams Android device on Admin Agent 794 or later is brought up to the latest eligible Admin Agent by Microsoft's Zero-Day Update once it is powered on and online. A device on an agent older than 794 must first be updated manually with OEM portal firmware that includes Admin Agent 794 or later. Source: [Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal](https://learn.microsoft.com/en-us/microsoftteams/devices/remote-update), Guidance for devices that remain offline for an extended period; Guidance for devices with older Admin Agent versions. Checked 2026-09-25.