# Teams Phone in GCC and GCC High and DoD Canonical: https://warmtransfer.net/knowledge/teams-phone-government-clouds Last verified: 2026-10-02 Microsoft's Teams service description says Direct Routing must be configured for Teams voice and audio conferencing to work in GCC High and DoD[^29]. In the same service description's feature table, PSTN calling enablement via Teams Phone is marked Yes for GCC without the Direct Routing footnote that applies to GCC High and DoD[^55]. ## How PSTN calling is delivered in each cloud The Office 365 GCC High and DoD service description states that Phone System and Audio Conferencing for GCC High and DoD are delivered via Direct Routing[^49]. Under its Skype for Business Online heading, that service description says PSTN Calling and PSTN Conferencing services are currently not available in GCC High and DoD[^56]. The Teams service description marks Audio conferencing as available in GCC High and DoD, but only subject to the footnote that Direct Routing must be configured[^12]. Integrating on-premises IP-PBX systems with Exchange Online Unified Messaging isn't supported in GCC High and DoD subscriptions[^30]. Third-party Teams applications and application publishing aren't available in GCC High and DoD, according to the Teams service description[^58]. See also [Microsoft Teams Phone architecture and licensing](https://warmtransfer.net/knowledge/teams-phone-architecture). ## Direct Routing connection points Office 365 GCC uses the same Direct Routing connection points as commercial Microsoft 365: sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com and sip3.pstnhub.microsoft.com, in that priority order[^24]. GCC High and DoD run in dedicated Microsoft Government clouds, and Direct Routing there doesn't require the secondary and tertiary SIP FQDNs used in commercial and GCC[^27]. | Cloud | SBC SIP signaling FQDN | Media processor IP range | |---|---|---| | GCC High | sip.pstnhub.gov.teams.microsoft.us[^26] | 52.127.88.0/21[^25] | | DoD | sip.pstnhub.dod.teams.microsoft.us[^23] | 52.127.64.0/21[^22] | GCC High Teams endpoint sets are *.gov.teams.microsoft.us on TCP 443 and 80 (set 31), plus an Optimize media set (set 7) including 52.127.88.0/21 on UDP 3478-3481[^38]. The DoD Teams endpoint set 7 is *.dod.teams.microsoft.us with ranges including 52.127.64.0/21, on TCP 443 and UDP 3478-3481[^20]. Media processors for Teams meeting traffic in GCC High are located in, and routed through, USGov Arizona and USGov Texas datacenters only[^37]. See also [Setting up Microsoft Teams Direct Routing](https://warmtransfer.net/knowledge/teams-direct-routing-setup). ## Audio Conferencing with Direct Routing in GCC High and DoD With Audio Conferencing with Direct Routing for GCC High and DoD, the organization uses its own numbers as dial-in numbers and all meeting dial-outs route via Direct Routing, unlike non-GCC High and non-DoD Audio Conferencing, where Microsoft provides the dial-in numbers[^1]. ### Licensing and order of operations - GCC High requires an 'Audio Conferencing - GCC High Tenant' licence for the organization plus 'Audio Conferencing - GCC High' licences for users[^4]. - DoD requires an 'Audio Conferencing - DoD Tenant' licence for the organization plus 'Audio Conferencing - DoD' licences for users[^3]. - The service needs a tenant licence and at least 1 user licence, and it can't be enabled with only one of them[^11]. - Microsoft recommends finishing the Direct Routing deployment before assigning Audio Conferencing licenses[^21]. - Microsoft warns that assigning these licences before setting up dial-in numbers may cause the dial pad to be completely missing in the Teams client[^2]. ### Defining and registering service numbers Service phone numbers are defined in the tenant with New-CsOnlineDirectRoutingTelephoneNumberUploadOrder, using E.164 format[^9]. Service numbers are attached to the organization's Audio Conferencing bridge with Register-CsOnlineDialInConferencingServiceNumber, with the bridge ID taken from Get-CsOnlineDialInConferencingBridge[^10]. See also [Teams voice administration with PowerShell](https://warmtransfer.net/knowledge/teams-powershell-voice-admin). ### Dial-out routing The GCC High and DoD audio conferencing article, in its wording as of 2026-02-04, says use of the global voice routing policy for meeting dial-outs will be deprecated by end of 2025, in favour of the audio conferencing routing policy (New-CsOnlineAudioConferencingRoutingPolicy)[^5]. Whether that deprecation took effect is not covered by the sources below. See also [Teams voice routing policies and dial plans](https://warmtransfer.net/knowledge/teams-voice-routing). ### Unsupported Audio Conferencing capabilities - Entry and exit notifications using name recording aren't supported, and tones are played instead[^6]. - Per-organizer controls that restrict toll-free number use don't apply to calls routed via Direct Routing[^8]. - Notification emails to users when their Audio Conferencing settings change aren't supported[^7]. ## Teams Phone features not available in GCC High and DoD - Shared Calling isn't yet available in GCC High and DoD clouds[^46]. - Private Line and Multi-line for users aren't yet available in GCC High and DoD clouds[^44]. - Transferring a call to voicemail mid-call isn't yet available in GCC High and DoD clouds[^43]. - Microsoft Entra ID reverse number lookup isn't yet available in GCC High and DoD clouds[^42]. - Calling a phone number from the Teams search bar isn't yet available in GCC High and DoD clouds[^45]. - Call settings for secondary ringer, voicemail and enhanced delegation aren't yet available in GCC High and DoD clouds[^41]. - The 'skip internal VoIP reverse number lookup' option isn't yet available in GCC High and DoD clouds[^47]. - Location-Based Routing isn't available in Microsoft 365 GCC High or DoD deployments[^40]. - Teams SIP Gateway isn't yet available for DoD[^57]. See also [Microsoft Teams shared calling and call delegation](https://warmtransfer.net/knowledge/teams-shared-calling). See also [Teams location-based routing](https://warmtransfer.net/knowledge/teams-location-based-routing). ## Emergency calling Dynamic emergency calling is available on all Teams clients in GCC, the same as worldwide multi-tenant[^16]. In GCC High, dynamic emergency calling is available on Teams desktop, Teams mobile clients, and Teams phones running app version 1449/1.0.94.2022061702[^17]. In DoD, dynamic emergency calling is available on Teams desktop, Teams mobile clients, and the Teams phone application released in the Teams admin center[^15]. For Direct Routing, dynamic emergency calling requires the SBC's online PSTN gateway to have PidfloSupported set to true and a connection to an Emergency Routing Service provider (US and Canada) or an ELIN configuration on the SBC[^28]. See also [Setting up dynamic emergency calling in Microsoft Teams](https://warmtransfer.net/knowledge/teams-dynamic-e911-setup). ## Device management The Teams Rooms Pro Management portal for GCC High tenants is at devices.gov.teams.microsoft.us, while Public and GCC use portal.rooms.microsoft.com[^53]. The Teams Rooms Pro Management portal for DoD tenants is at devices.dod.teams.microsoft.us[^50]. Microsoft says government cloud customers (GCC, GCC High, DoD) will have Teams Android devices auto-updated to minimum Admin Agent version AA 856 (1.0.0.202607160723) before Teams admin center device management is deprecated, and these updates can't be paused[^54]. The Pro Management portal table marks Teams Phones device inventory for GCC High as completed in July 2026 and update management for GCC High as completed in August 2026[^52]. As of 2026-09-30, Microsoft scheduled Teams Phones device inventory, update management and settings management in the Pro Management portal for October 2026 in both GCC and DoD[^51]. See also [Teams phones and certified devices](https://warmtransfer.net/knowledge/teams-phone-devices). ## Compliance recording The Graph API that supports a third-party compliance recorder's recording status is available in US Government L4 and US Government L5 national cloud deployments[^13]. Licences that make a user eligible for Teams compliance recording include Microsoft 365 G3 and G5, alongside A3, A5, E3, E5, Business Premium, Business Standard, Teams Rooms and Teams Shared Device licences[^14]. See also [Microsoft Teams compliance recording](https://warmtransfer.net/knowledge/teams-compliance-recording). ## Eligibility, compliance and support boundary Office 365 GCC requires an eligibility validation before an environment is established, and trials are available only to US Government entities[^33]. GCC High and DoD are available through Volume Licensing after an eligibility validation process, and trials aren't available[^35]. Only Department of Defense entities may purchase licences for the Office 365 DoD environment, while non-DoD entities that meet eligibility may purchase GCC High[^18]. Office 365 GCC High and DoD are assessed using NIST SP 800-53 controls at a FIPS 199 High categorization[^34]. Office 365 DoD meets the DoD Cloud Computing Security Requirements Guide security controls for information up to Impact Level 5[^19]. Office 365 GCC High and DoD customer support isn't included in the service accreditation boundary and provides no FedRAMP, DoD SRG, ITAR, IRS 1075 or CJIS data-handling assurances[^36]. ## Applicability Applies to: Microsoft Teams Phone, Microsoft Skype for Business Online, Microsoft Teams Audio Conferencing, Microsoft Exchange Online, Microsoft Teams, Microsoft Teams Direct Routing, Microsoft Teams PowerShell, Microsoft Teams SIP Gateway, Microsoft Teams Rooms Pro Management portal, Microsoft Graph, Microsoft Office 365 GCC, Microsoft Office 365 GCC High, and Microsoft Office 365 DoD. Deployments: multi-tenant, dod, gcc, and gcc-high. Sources checked 2026-10-02. Office 365 Government - GCC High is only available in the United States[^39]. The Pro Management portal rollout status reflects Microsoft's schedule as of 2026-09-30[^51]. ## What remains uncertain - Operator Connect availability in GCC and GCC High is not covered by the sources below. - Microsoft Calling Plans availability in GCC is not covered by the sources below. - The list of certified Teams phones per government cloud is not covered by the sources below. - Which compliance recording partners are certified per government cloud is not covered by the sources below. - Which Emergency Routing Service providers serve GCC High Direct Routing is not covered by the sources below. - The scope of Direct Routing SBC certification for GCC High and DoD is not covered by the sources below. - Media bypass support in GCC High and DoD Direct Routing is not covered by the sources below. - Availability of the Queues app and Teams Premium calling features in government clouds is not covered by the sources below. ## Sources [^1]: With Audio Conferencing with Direct Routing for GCC High and DoD, the organization uses its own numbers as dial-in numbers and all meeting dial-outs route via Direct Routing, unlike non-GCC High and non-DoD Audio Conferencing, where Microsoft provides the dial-in numbers. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Introduction, second paragraph. Checked 2026-10-02. [^2]: Microsoft warns that assigning Audio Conferencing with Direct Routing licences for GCC High or DoD before setting up dial-in numbers may cause the dial pad to be completely missing in the Teams client. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Step 1, Important callout. Checked 2026-10-02. [^3]: DoD requires an 'Audio Conferencing - DoD Tenant' licence for the organization plus 'Audio Conferencing - DoD' licences for users. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Step 1: Get Audio Conferencing with Direct Routing for GCC High or DoD licenses. Checked 2026-10-02. [^4]: GCC High requires an 'Audio Conferencing - GCC High Tenant' licence for the organization plus 'Audio Conferencing - GCC High' licences for users. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Step 1: Get Audio Conferencing with Direct Routing for GCC High or DoD licenses. Checked 2026-10-02. [^5]: The GCC High and DoD audio conferencing article says use of the global voice routing policy for meeting dial-outs will be deprecated by end of 2025, in favour of the audio conferencing routing policy (New-CsOnlineAudioConferencingRoutingPolicy). Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Step 4, second Note; Step 4.1. Checked 2026-10-02. [^6]: Audio Conferencing with Direct Routing for GCC High and DoD doesn't support entry and exit notifications using name recording; tones are played instead. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Audio Conferencing capabilities not supported in Audio Conferencing with Direct Routing for GCC High and DoD, bullet 1. Checked 2026-10-02. [^7]: Audio Conferencing notification emails to users when their settings change aren't supported for Audio Conferencing with Direct Routing for GCC High and DoD. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Audio Conferencing capabilities not supported..., bullet 3. Checked 2026-10-02. [^8]: Per-organizer controls that restrict toll-free number use don't apply to calls routed via Direct Routing in GCC High and DoD Audio Conferencing. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Audio Conferencing capabilities not supported..., bullet 2. Checked 2026-10-02. [^9]: Service phone numbers for Audio Conferencing with Direct Routing in GCC High and DoD are defined in the tenant with New-CsOnlineDirectRoutingTelephoneNumberUploadOrder, using E.164 format. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Step 3 > Define service phone numbers in your tenant. Checked 2026-10-02. [^10]: Service numbers are attached to the organization's Audio Conferencing bridge with Register-CsOnlineDialInConferencingServiceNumber, with the bridge ID taken from Get-CsOnlineDialInConferencingBridge. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Step 3 > Assign the service phone numbers to the Audio Conferencing bridge of your organization. Checked 2026-10-02. [^11]: Audio Conferencing with Direct Routing for GCC High or DoD needs a tenant licence and at least one user licence; it can't be enabled with only one of them. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Step 1, paragraph after the licence bullets. Checked 2026-10-02. [^12]: Audio conferencing is marked available in GCC High and DoD in the Teams service description, but only subject to the footnote that Direct Routing must be configured. Source: [Microsoft Teams service description](https://learn.microsoft.com/en-us/office365/servicedescriptions/teams-service-description), Feature availability table, row 'Audio conferencing', footnote 2. Checked 2026-10-02. [^13]: The Graph API that supports a third-party compliance recorder's recording status is available in US Government L4 and US Government L5 (DoD) national cloud deployments. Source: [Microsoft Teams compliance recording (third-party)](https://learn.microsoft.com/en-us/microsoftteams/teams-recording-compliance), Compliance recording overview, national cloud availability table. Checked 2026-10-02. [^14]: Licences that make a user eligible for Teams compliance recording include Microsoft 365 G3 and G5, alongside A3, A5, E3, E5, Business Premium, Business Standard, Teams Rooms and Teams Shared Device licences. Source: [Microsoft Teams compliance recording (third-party)](https://learn.microsoft.com/en-us/microsoftteams/teams-recording-compliance), Considerations > Licensing. Checked 2026-10-02. [^15]: In DoD, dynamic emergency calling is available on Teams desktop, Teams mobile clients, and the Teams phone application released in the Teams admin center. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Government support table, DoD row. Checked 2026-10-02. [^16]: Dynamic emergency calling is available on all Teams clients in GCC, the same as worldwide multi-tenant. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Government support table, GCC row. Checked 2026-10-02. [^17]: In GCC High, dynamic emergency calling is available on Teams desktop, Teams mobile clients, and Teams phones running app version 1449/1.0.94.2022061702. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Government support table, GCCH row. Checked 2026-10-02. [^18]: Only Department of Defense entities may purchase licences for the Office 365 DoD environment; non-DoD entities that meet eligibility may purchase GCC High. Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Compliance section, paragraph after the bullets. Checked 2026-10-02. [^19]: Office 365 DoD meets the DoD Cloud Computing Security Requirements Guide security controls for information up to Impact Level 5. Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Compliance section, second bullet. Checked 2026-10-02. [^20]: The DoD Teams endpoint set 7 is *.dod.teams.microsoft.us with ranges including 52.127.64.0/21, on TCP 443 and UDP 3478-3481. Source: [Microsoft 365 US Government DOD endpoints](https://learn.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-u-s-government-dod-endpoints), Microsoft Teams table, endpoint set ID 7. Checked 2026-10-02. [^21]: For GCC High and DoD, Microsoft recommends finishing the Direct Routing deployment before assigning Audio Conferencing licenses. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Direct Routing with Audio Conferencing. Checked 2026-10-02. [^22]: The Direct Routing media processor IP range for DoD is 52.127.64.0/21. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Media processor IP ranges > DoD. Checked 2026-10-02. [^23]: For Office 365 DoD, the Direct Routing SBC connects to the SIP signaling FQDN sip.pstnhub.dod.teams.microsoft.us. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), SIP signaling > SIP signaling: DoD. Checked 2026-10-02. [^24]: Office 365 GCC uses the same Direct Routing connection points as commercial Microsoft 365: sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com and sip3.pstnhub.microsoft.com, in that priority order. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), SIP signaling > SIP signaling: FQDNs, first table. Checked 2026-10-02. [^25]: The Direct Routing media processor IP range for GCC High is 52.127.88.0/21. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Media processor IP ranges > GCC High. Checked 2026-10-02. [^26]: For Office 365 GCC High, the Direct Routing SBC connects to the SIP signaling FQDN sip.pstnhub.gov.teams.microsoft.us. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), SIP signaling > SIP signaling: GCC High. Checked 2026-10-02. [^27]: Because GCC High and DoD run in dedicated Microsoft Government clouds, Direct Routing there doesn't require the secondary and tertiary SIP FQDNs used in commercial and GCC. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), SIP signaling > SIP signaling: DoD, closing sentence. Checked 2026-10-02. [^28]: For Direct Routing, dynamic emergency calling requires the SBC's online PSTN gateway to have PidfloSupported set to true and a connection to an Emergency Routing Service provider (US and Canada) or an ELIN configuration on the SBC. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Emergency calling prerequisites for Direct Routing; Set up an Emergency Routing Service provider. Checked 2026-10-02. [^29]: Microsoft's Teams service description says Direct Routing must be configured for Teams voice and audio conferencing to work in GCC High and DoD. Source: [Microsoft Teams service description](https://learn.microsoft.com/en-us/office365/servicedescriptions/teams-service-description), Feature availability table, footnote 2. Checked 2026-10-02. [^30]: Integrating on-premises IP-PBX systems with Exchange Online Unified Messaging isn't supported in GCC High and DoD subscriptions. Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Feature nuances based on compliant cloud architecture > Exchange Online. Checked 2026-10-02. [^31]: The Office 365 GCC service description says Office 365 Government supports FedRAMP accreditation at a High Impact level (disputed). Source: [Office 365 GCC - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc), US Government community compliance section. Checked 2026-10-02. [^32]: The Teams GCC deployment planning page says Microsoft 365 Government - GCC provides compliance with FedRAMP Moderate (disputed). Source: [Microsoft 365 Government - GCC deployments - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/plan-for-government-gcc), Step 1, first paragraph. Checked 2026-10-02. [^33]: Office 365 GCC requires an eligibility validation before an environment is established, and trials are available only to US Government entities. Source: [Office 365 GCC - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc), Introduction paragraph. Checked 2026-10-02. [^34]: Office 365 GCC High and DoD are assessed using NIST SP 800-53 controls at a FIPS 199 High categorization. Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Compliance section, first bullet. Checked 2026-10-02. [^35]: GCC High and DoD are available through Volume Licensing after an eligibility validation process, and trials aren't available. Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Introduction paragraph. Checked 2026-10-02. [^36]: Office 365 GCC High and DoD customer support isn't included in the service accreditation boundary and provides no FedRAMP, DoD SRG, ITAR, IRS 1075 or CJIS data-handling assurances. Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Customer support section. Checked 2026-10-02. [^37]: Media processors for Teams meeting traffic in GCC High are located in, and routed through, USGov Arizona and USGov Texas datacenters only. Source: [Microsoft 365 U.S. Government GCC High endpoints](https://learn.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-u-s-government-gcc-high-endpoints), Notes for this table (below Microsoft 365 Common and Office Online), third bullet. Checked 2026-10-02. [^38]: GCC High Teams endpoint sets are *.gov.teams.microsoft.us on TCP 443 and 80 (set 31), plus an Optimize media set (set 7) including 52.127.88.0/21 on UDP 3478-3481. Source: [Microsoft 365 U.S. Government GCC High endpoints](https://learn.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-u-s-government-gcc-high-endpoints), Microsoft Teams table, endpoint set IDs 7 and 31. Checked 2026-10-02. [^39]: Office 365 Government - GCC High is only available in the United States. Source: [Microsoft 365 Government - GCC High deployments - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/plan-for-government-gcc-high), Step 1, Note after the decision points table. Checked 2026-10-02. [^40]: Location-Based Routing isn't available in Microsoft 365 GCC High or DoD deployments. Source: [Audio Conferencing with Direct Routing, GCC High and DoD - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/audio-conferencing-with-direct-routing-for-gcch-and-dod), Step 4, first Note. Checked 2026-10-02. [^41]: Call settings for secondary ringer, voicemail and enhanced delegation aren't yet available in GCC High and DoD clouds. Source: [Teams Phone features](https://learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system), Availability in GCC High and DoD clouds, list item 'Call settings for secondary ringer, voicemail, and enhanced delegation'. Checked 2026-10-02. [^42]: Microsoft Entra ID reverse number lookup isn't yet available in GCC High and DoD clouds. Source: [Teams Phone features](https://learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system), Availability in GCC High and DoD clouds, list item 'Microsoft Entra ID reverse number lookup'. Checked 2026-10-02. [^43]: Transferring a call to voicemail mid-call isn't yet available in GCC High and DoD clouds. Source: [Teams Phone features](https://learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system), Availability in GCC High and DoD clouds, list item 'Transfer to voicemail mid call'. Checked 2026-10-02. [^44]: Private Line and Multi-line for users aren't yet available in GCC High and DoD clouds. Source: [Teams Phone features](https://learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system), Availability in GCC High and DoD clouds, list item 'Private Line and Multi-line for users'. Checked 2026-10-02. [^45]: Calling a phone number from the Teams search bar isn't yet available in GCC High and DoD clouds. Source: [Teams Phone features](https://learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system), Availability in GCC High and DoD clouds, list item 'Call phone number from search bar'. Checked 2026-10-02. [^46]: Shared Calling isn't yet available in GCC High and DoD clouds. Source: [Teams Phone features](https://learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system), Availability in GCC High and DoD clouds, list item 'Shared Calling'. Checked 2026-10-02. [^47]: The 'skip internal VoIP reverse number lookup' option isn't yet available in GCC High and DoD clouds. Source: [Teams Phone features](https://learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system), Availability in GCC High and DoD clouds, list item 'Skip internal VoIP reverse number lookup option'. Checked 2026-10-02. [^48]: Microsoft Calling Plans and Operator Connect are probably not offered as PSTN options in GCC High and DoD, because Microsoft documents only Direct Routing as the delivery path for Phone System there (inferred). Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Feature nuances based on compliant cloud architecture > Microsoft Teams (read with Teams service description footnote 2). Checked 2026-10-02. [^49]: The Office 365 GCC High and DoD service description states that Phone System and Audio Conferencing for GCC High and DoD are delivered via Direct Routing. Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Feature nuances based on compliant cloud architecture > Microsoft Teams. Checked 2026-10-02. [^50]: The Teams Rooms Pro Management portal for DoD tenants is at devices.dod.teams.microsoft.us. 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-10-02. [^51]: As of 2026-09-30, Microsoft scheduled Teams Phones device inventory, update management and settings management in the Pro Management portal for October 2026 in both GCC and 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), Specific feature availability in PMP table, GCC and DoD columns. Checked 2026-10-02. [^52]: The Pro Management portal table marks Teams Phones device inventory for GCC High as completed in July 2026 and update management for GCC High as completed in August 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, rows 'Devices view for Teams Phones' and 'Update management for MTR-A, Panels and Phones', GCCH column. Checked 2026-10-02. [^53]: The Teams Rooms Pro Management portal for GCC High tenants is at devices.gov.teams.microsoft.us, while Public and GCC use portal.rooms.microsoft.com. 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-10-02. [^54]: Microsoft says government cloud customers (GCC, GCC High, DoD) will have Teams Android devices auto-updated to minimum Admin Agent version AA 856 (1.0.0.202607160723) before Teams admin center device management is deprecated, and these updates can't be paused. 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), Step 2, Important callout 'Admin Agent update readiness'. Checked 2026-10-02. [^55]: In the Teams service description feature table, PSTN calling enablement via Teams Phone is marked Yes for GCC without the Direct Routing footnote that applies to GCC High and DoD. Source: [Microsoft Teams service description](https://learn.microsoft.com/en-us/office365/servicedescriptions/teams-service-description), Feature availability table, row 'PTSN calling enablement (via Teams Phone)', GCC column. Checked 2026-10-02. [^56]: Under its Skype for Business Online heading, the GCC High and DoD service description says PSTN Calling and PSTN Conferencing services are currently not available in GCC High and DoD. Source: [Office 365 GCC High and DoD - Service Descriptions](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod), Feature nuances based on compliant cloud architecture > Skype for Business Online. Checked 2026-10-02. [^57]: Teams SIP Gateway isn't yet available for DoD. Source: [Plan SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan), Requirements to use SIP Gateway, Note. Checked 2026-10-02. [^58]: Third-party Teams applications and application publishing aren't available in GCC High and DoD, according to the Teams service description. Source: [Microsoft Teams service description](https://learn.microsoft.com/en-us/office365/servicedescriptions/teams-service-description), Feature availability table, row 'Teams Apps', footnote 1. Checked 2026-10-02.