# Setting up Microsoft Teams Operator Connect Systems: Microsoft Teams Phone For Teams administrators setting up Microsoft Teams Operator Connect for PSTN calling. Canonical: https://warmtransfer.net/guides/teams-operator-connect-setup Last verified: 2026-09-25 Operator Connect delivers Public Switched Telephone Network (PSTN) connectivity to Microsoft Teams Phone through certified third-party operators that have completed PSTN integration with Microsoft[^59]. A customer establishes a contract with the operator and enables the operator in the Teams admin center[^59]. ## Before you start - Confirm that every user receiving a number is licensed for Teams Phone and configured in Teams Only mode[^60]. A PSTN solution is separate from the Teams Phone license, and a user requires both[^61]. Because a non-Microsoft PSTN operator is being used, no Microsoft Calling Plan license is needed (outside India)[^62]. - Check that a certified operator serves every country or region in your deployment scope[^60]. A single tenant can support multiple PSTN solutions simultaneously[^63]. - Confirm your administrative role: assigning, modifying, or removing phone numbers requires the Teams Administrator, Teams Communications Administrator, or Teams Telephony Administrator role[^7]. Appropriate admin permissions to manage Teams Phone and a network configuration meeting Teams networking requirements are required[^3]. - If you use PowerShell, ensure the MicrosoftTeams module version 3.0.0 or later is installed; `Set-CsPhoneNumberAssignment` is available only in commercial, GCC, GCCH, and DoD cloud environments[^10]. - Have your Microsoft 365 tenant ID available for ordering numbers from the operator[^39]. ## What changes by situation - Where do your Operator Connect phone numbers come from? New numbers ordered from the operator; Existing numbers ported in through the operator; Numbers already used on Teams Direct Routing in this tenant. - Who will receive the phone numbers? Users only; Users, plus resource accounts for auto attendants or call queues. - Which emergency-address model did your operator implement? The operator sets addresses and lets you change them; The operator sets none and you assign them; The operator sets them and you cannot change them. - Are users or resource accounts synced from on-premises Active Directory? Cloud-only accounts, or no phone number held in on-premises AD; Hybrid, and the on-premises AD object may hold a number in msRTCSIP-Line. ## Step 1: Verify user coexistence mode ### Do In the Microsoft Teams admin center, check that users are set to Teams Only coexistence mode[^60]. ### Verify Check Teams > Teams upgrade settings in the Teams admin center to see that coexistence mode is set to TeamsOnly, or if the organization is in Islands mode, check each user's Account tab to verify the coexistence mode under Teams upgrade settings shows TeamsOnly[^56]. ### Rollback Suggested rollback: Revert user coexistence settings in the Teams admin center if they were altered during verification. ## Step 2: Enable the operator in the Teams admin center ### Do Evaluate certified operators on country and regional availability, phone number availability, porting support, service offerings, and existing business relationships[^37]. Navigate to Voice > Operator Connect in the Teams admin center[^54]. Under the All operators tab, select the operator, choose countries or regions under Operator settings, provide contact details (your company size is required, while a phone number is optional), accept the data transfer notice, and select Add as my operator[^26][^11]. Your full name and email address are shared automatically with the operator so they can contact you[^11]. ### Verify Open Voice > Operator Connect > My operators tab and verify that the selected operator and its active status appear in the list[^31]. ### Rollback In the My operators tab, manage operator services by country, suspend the operator, or remove the operator[^31]. Before removing an operator from a country or organization, remove all phone numbers assigned to users in that scope and contact the operator to release those numbers[^51]. ## Step 3: Finalize operator agreement and consent ### Do Wait for the operator to contact you using the submitted contact details to complete their commercial contract[^11][^59]. In the operator onboarding flow, the operator records the relationship as Agreement signed under Customer Consents before numbers can be uploaded to your tenant[^4]. Provide your Microsoft 365 tenant ID to the operator during this step[^39]. ### Verify WarmTransfer's reading of the sources is that enabling an operator in the Teams admin center probably does not deliver numbers on its own until the operator marks the consent agreement as signed, so confirm directly with the operator that the agreement status is completed if numbers do not appear in inventory[^12]. ### Rollback Suggested rollback: Terminate or amend the operator contract according to the terms established in the commercial agreement with the provider. ## Step 4: Create validated emergency addresses ### Do In the Teams admin center, go to Locations > Emergency addresses, select Add, and enter a name, description, country or region, and address[^19]. Use the map search to validate the address and add a geo code automatically, or select the option to edit the address manually if it is not found[^19][^23][^64]. In Belgium, France, Germany, Ireland, the Netherlands, or Spain, ensure the emergency address matches the number's area code, or the number will not activate[^22]. ### Verify Confirm in Locations > Emergency addresses that the address status shows as validated, as an address must be marked validated before assignment to a user or network identifier[^23]. ### Rollback An emergency address can be edited only while it is not yet validated; once validated, delete and recreate it if corrections are needed[^24]. An address can only be removed when no users or phone numbers are assigned to it[^21]. ## Step 5: Acquire phone numbers into inventory **New numbers ordered from the operator** ### Do Order new phone numbers directly on the operator's website, providing your Microsoft 365 tenant ID during the order process[^39][^32]. ### Verify After the operator finishes the order and uploads the numbers, navigate to Voice > Phone numbers to confirm the numbers appear with the operator shown as the provider[^38]. ### Rollback Release an unassigned number by selecting it under Voice > Phone numbers and choosing Release[^49]. **Existing numbers ported in through the operator** ### Do Contact the operator to port existing phone numbers from another carrier or from Microsoft Calling Plans, as porting and PSTN support are owned by the operator[^40][^65][^32]. ### Verify Once the operator completes the porting order and uploads the numbers, verify under Voice > Phone numbers that the numbers appear with the operator listed as the provider[^40][^38]. ### Rollback Suggested rollback: Submit a port reversal or new porting order through the operator or losing carrier to return the numbers to the prior provider. **Numbers already used on Teams Direct Routing in this tenant** ### Do Identify the assignment source for each user by running `Get-CsPhoneNumberAssignment -AssignedPstnTargetId ` to confirm `NumberType` is `DirectRouting`, and run `Get-CsOnlineUser` to inspect `OnPremLineURI`[^14]. - If the number was assigned online, contact the operator to schedule number migration at an agreed date and time[^15]. - If `OnPremLineURI` is populated, coordinate an outage window with the operator because the number will be out of service during migration; clear the line assignment on-premises using Skype for Business Server with `Set-CsUser -Identity -LineURI $null`[^16]. - After directory synchronization reflects an empty `OnPremLineURI` and `LineURI`, unassign the Direct Routing number using `Remove-CsPhoneNumberAssignment -Identity -PhoneNumberType DirectRouting`[^18]. - Remove the user's online voice routing policy with `Grant-CsOnlineVoiceRoutingPolicy -Identity -PolicyName $Null`[^17]. - Order the numbers from the operator using your Microsoft 365 tenant ID[^39]. ### Verify Verify that `Get-CsOnlineUser -Identity | fl LineUri` returns an empty value following unassignment, noting that unassignment takes up to 10 minutes and rarely up to 24 hours[^18]. Verify the numbers reappear under Voice > Phone numbers with the operator listed as the provider[^38]. ### Rollback Before migration is executed by the operator, you can reassign the Direct Routing number and restore the voice routing policy using `Grant-CsOnlineVoiceRoutingPolicy`, as removing the assignment leaves the number available in the tenant[^58]. ## Step 6: Acquire service numbers for voice applications **Users only** ### Do PSTN numbers can be acquired by purchasing new numbers, porting, or migrating users from another Teams Phone PSTN option[^32]. ### Verify Suggested check: Confirm that all planned telephony assignments are restricted to individual end users. ### Rollback Suggested rollback: No configuration change was made in this step. **Users, plus resource accounts for auto attendants or call queues** ### Do Contact the operator to obtain toll or toll-free service numbers for auto attendants and call queues, as service numbers handle hundreds of simultaneous calls compared to user numbers which handle only a few[^52]. Direct inbound phone numbers on auto attendants and call queues are optional and required only when the voice application must be reached directly from the PSTN[^46]. ### Verify Run `Get-CsPhoneNumberAssignment -ActivationState Activated -CapabilitiesContain VoiceApplicationAssignment -PstnAssignmentStatus Unassigned` to view loaded service numbers[^9]. WarmTransfer's reading of the sources is that an Operator Connect number intended for a resource account probably requires the `VoiceApplicationAssignment` capability and cannot be assigned to an auto attendant or call queue if uploaded with only `UserAssignment`[^48]. ### Rollback Release any unassigned service numbers from inventory under Voice > Phone numbers by selecting the number and clicking Release[^49]. ## Step 7: Clear on-premises Active Directory line attributes **Cloud-only accounts, or no phone number held in on-premises AD** ### Do Teams Phone delivers call control and PBX capabilities in the Microsoft 365 cloud[^66]. ### Verify Suggested check: Verify that target user accounts are managed directly in cloud identity services without on-premises phone number sync. ### Rollback Suggested rollback: No configuration change was made in this step. **Hybrid, and the on-premises AD object may hold a number in msRTCSIP-Line** ### Do In your on-premises Active Directory, clear the `msRTCSIP-Line` attribute for every user or resource account scheduled to receive an Operator Connect number, and allow directory synchronization to sync the change to Microsoft 365[^28]. ### Verify Verify that directory synchronization has completed; assignment of an Operator Connect number will fail if a phone number remains populated in `msRTCSIP-Line`[^28]. ### Rollback Repopulate the `msRTCSIP-Line` attribute in on-premises Active Directory and initiate directory synchronization if you must cancel the Operator Connect transition for the account[^28]. ## Step 8: Set emergency locations on phone numbers **The operator sets addresses and lets you change them** ### Do Review the emergency address set by the operator on each number, and update it where necessary under Voice > Phone numbers > Numbers tab by selecting the number, clicking Edit, picking an address under Emergency location, and clicking Apply[^20][^25]. Alternatively, set the location via PowerShell with `Set-CsPhoneNumberAssignment -TelephoneNumber -LocationId ` using an ID obtained from `Get-CsOnlineLisLocation`[^29]. The location, user, and phone number must all be in the same country[^20]. ### Verify Run `Get-CsPhoneNumberAssignment -AssignedPstnTargetId ` or inspect the number in the Teams admin center to verify the intended `LocationId` is populated[^27]. ### Rollback Reassign the previous `LocationId`, or clear the emergency location by passing `-LocationId 'null'` with `Set-CsPhoneNumberAssignment`, which is supported on Operator Connect numbers that are not managed by the Service Desk[^30]. **The operator sets none and you assign them** ### Do Assign a validated emergency location to each Operator Connect number by selecting the number under Voice > Phone numbers > Numbers tab, clicking Edit, choosing a location under Emergency location, and selecting Apply[^20][^25]. Alternatively, execute `Set-CsPhoneNumberAssignment -TelephoneNumber -LocationId ` in PowerShell, which works on both assigned and unassigned numbers[^29]. Ensure the location, user, and number share the same country[^20]. ### Verify Run `Get-CsPhoneNumberAssignment` to verify that `LocationId` contains the assigned GUID and `LocationUpdateSupported` is reflected[^27]. ### Rollback Change the assigned emergency location to a different validated ID, or pass `-LocationId 'null'` using `Set-CsPhoneNumberAssignment` for numbers not managed by the Service Desk[^30]. **The operator sets them and you cannot change them** ### Do Because the operator assigns emergency addresses and does not allow modifications in the Teams admin center, provide any address corrections directly to your operator for update[^25]. ### Verify Run `Get-CsPhoneNumberAssignment -AssignedPstnTargetId ` to verify that `LocationId` displays the operator-provided address ID and that `LocationUpdateSupported` is returned[^27]. ### Rollback Submit an address correction request back to your operator to modify the emergency address assignment[^25]. ## Step 9: Assign phone numbers to users ### Do Verify that the number and the target user's usage location are in the same country or region[^13]. Assign the number using either of two methods in the Teams admin center[^53]: - Go to Voice > Phone numbers, select an unassigned number, click Edit, and search for the user under Assigned to[^53]. - Go to Users > Manage users, select the user's Account tab, select Assign primary phone number, select Operator Connect under Phone number type, and choose the number[^53]. Note that the "Email user with telephone number information" toggle is turned on by default in the admin center[^5]. In PowerShell, assign the number using `Set-CsPhoneNumberAssignment -Identity -PhoneNumber -PhoneNumberType OperatorConnect`[^41]. Assigning a number automatically enables Enterprise Voice for the account[^8]. ### Verify Run `Get-CsPhoneNumberAssignment -AssignedPstnTargetId ` and verify that `NumberType` is `OperatorConnect`, `PstnAssignmentStatus` is `UserAssigned`, and `ActivationState` is `Activated`[^27][^2]. Latency between Microsoft 365 and Teams can take up to 24 hours for users to be enabled; if the number is not assigned correctly after 24 hours, contact the Phone Number Service Center[^6]. ### Rollback In the Teams admin center, open the user's Account tab, click Edit under Assigned phone number, select None, and choose Apply[^55]. In PowerShell, execute `Remove-CsPhoneNumberAssignment -Identity -PhoneNumber -PhoneNumberType OperatorConnect`, which unassigns the number, sets `EnterpriseVoiceEnabled` to False, and retains the number in inventory[^58]. To block re-use, specify `-AssignmentBlockedDays` for 1 to 365 days or `-AssignmentBlockedForever`[^50]. ## Step 10: Assign phone numbers to resource accounts **Users only** ### Do Placing calls by extension or PSTN phone number requires Teams Phone[^67]. ### Verify Suggested check: Confirm that no resource accounts were modified or staged for voice applications. ### Rollback Suggested rollback: No configuration change was made in this step. **Users, plus resource accounts for auto attendants or call queues** ### Do Ensure you hold a Teams administrator role (Teams Telephony, Teams Communications, or Teams Administrator) combined with User Administrator, or Global Administrator / Skype for Business Administrator plus User Administrator[^42]. Create a resource account under Voice > Resource accounts > Add (choosing Display name, Username, and Account type of Auto attendant or Call queue), or run `New-CsOnlineApplicationInstance`[^44]. Keep sign-in disabled on the resource account[^47]. Assign a Microsoft Teams Phone Resource Account license to the account; do not assign Teams Phone Standard[^68][^69]. This is disputed: Microsoft states there is no cost for Teams Phone Resource Account licenses, but administrators must still execute a purchase step at zero cost[^70]. In the Microsoft 365 admin center under Licenses and Apps, configure the Select location value on the resource account to match the country code of the phone number[^45]. Under Voice > Resource accounts, select the account, click Assign/unassign, select Operator Connect as the Phone number type, search for the number including the country code, select Add, and select Save[^43]. Alternatively, assign the number using `Set-CsPhoneNumberAssignment`, which accepts resource accounts and automatically enables Enterprise Voice[^8][^27]. ### Verify Run `Get-CsPhoneNumberAssignment -AssignedPstnTargetId ` to confirm the resource account displays `NumberType` OperatorConnect and `ActivationState` Activated[^27][^2]. ### Rollback Remove the number assignment under Voice > Resource accounts using Assign/unassign[^43], or run `Remove-CsPhoneNumberAssignment -Identity -PhoneNumber -PhoneNumberType OperatorConnect` to unassign the number and reset Enterprise Voice to False[^58]. ## Step 11: Validate PSTN calling and emergency routing **Users only** ### Do Every Operator Connect user is automatically enabled for emergency calling, and emergency calls route directly to the operator[^34]. In the United States and Canada, carrier emergency routing is integrated: US calls from a tenant-defined dynamic location route directly to the serving PSAP, while all Canadian emergency calls are pre-screened nationally[^36]. Calls outside a dynamic location are screened by a national call center, falling back to the registered address PSAP if the caller cannot update their location[^35]. For emergency verification in the United States, test using the test number 933, which can be configured to prevent alerting the security desk[^1]. ### Verify Suggested check: Place inbound and outbound test calls from sample user accounts. WarmTransfer's reading of the sources is that test calls in and out are the practical end-to-end check; if calls fail while the number shows an Activated OperatorConnect assignment in Teams, it is likely a PSTN-side issue for the operator to investigate under the support boundary[^57][^65]. Check that `ActivationState` is Activated, and resolve any number showing AssignmentFailed or UpdateFailed[^2]. ### Rollback Suggested rollback: If calls fail due to incorrect user assignments, unassign and reassign the user phone number using the rollback procedures in Step 9. **Users, plus resource accounts for auto attendants or call queues** ### Do Perform all user call testing described for user accounts, including inbound and outbound testing and emergency test dial strings like 933 in the United States[^34][^36][^35][^1]. ### Verify Suggested check: Place an external PSTN test call to each assigned resource account service number after associating the account with its auto attendant or call queue. WarmTransfer's reading of the sources is that test calls are the practical end-to-end check, and failures on numbers with an Activated assignment in Teams should be escalated to the operator[^57][^65]. Confirm that incoming calls to each service number connect to the expected voice application menu or queue greeting, and verify that no phone number remains in an AssignmentFailed or UpdateFailed activation state[^2]. ### Rollback Suggested rollback: If voice application routing fails, dissociate the service number or unassign the resource account phone number using the rollback procedures in Step 10. ## Applicability Applies to: Microsoft Teams Phone, MicrosoftTeams PowerShell module, and Microsoft Operator Connect (operator portal). Deployments: hybrid and multi-tenant. Sources checked 2026-09-25. The Teams PowerShell module must be version 3.0.0 or later to use `Set-CsPhoneNumberAssignment` (with parameter `-Notify` requiring version 7.3.0 or later)[^10]. Teams PowerShell module 7.5.0 or later introduced the parameters `-AssignmentBlockedForever` and `-AssignmentBlockedDays` in `Remove-CsPhoneNumberAssignment`[^50]. Cmdlets for managing Operator Connect assignments are supported only in commercial, GCC, GCCH, and DoD cloud environments[^10]. In Belgium, France, Germany, Ireland, the Netherlands, and Spain, activation requires the emergency address to match the number's area code[^22]. United States and Canadian tenants have specific carrier national call center screening rules and support emergency testing using 933[^36][^35][^1]. ## What remains uncertain The exact procedure to reverse a completed carrier number port or Direct Routing migration is not covered by the sources below. The criteria determining whether an Operator Connect number is classified as Service Desk managed (which prevents clearing a location ID directly) are not covered by the sources below. The specific commercial contract terms, pricing models, and third-party consent screens used by individual certified operators are not covered by the sources below. Configuration of auto attendant call flows, call queue distribution rules, and dynamic emergency network infrastructure (such as subnets, switches, and access points) is not covered by the sources below. Emergency routing behaviors for Operator Connect in countries outside the United States and Canada are not covered by the sources below. ## Sources [^1]: Teams emergency calling notification settings can be configured per emergency number, and Microsoft gives the example of handling a call to the emergency test number 933 without notifying the security desk. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Security desk notifications, third paragraph. Checked 2026-09-25. [^2]: A phone number's ActivationState is one of Activated, AssignmentPending, AssignmentFailed, UpdatePending or UpdateFailed. Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Parameters -ActivationState. Checked 2026-09-25. [^3]: Microsoft's Operator Connect planning prerequisites also include appropriate administrator permissions to manage Teams Phone and a network and firewall configuration that meets Teams networking requirements. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Onboarding > Step 1: Verify prerequisites; Requirements. Checked 2026-09-25. [^4]: In the operator-side onboarding flow, after a customer selects Add as my operator, the operator records the customer relationship as Agreement signed in the Operator Connect portal's Customer Consents before uploading numbers to that tenant. Source: [Prepare for Operator Connect or Teams Phone Mobile live traffic with Azure Communications Gateway](https://learn.microsoft.com/en-us/azure/communications-gateway/prepare-for-live-traffic-operator-connect), Set up your test tenant, steps 1 and 4 (Operator Portal tab). Checked 2026-09-25. [^5]: When a number is assigned in the Teams admin center, the Email user with telephone number information toggle is on by default. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Use Teams admin center to assign a phone number to a user, step after Emergency location. Checked 2026-09-25. [^6]: Because of latency between Microsoft 365 and Teams it can take up to 24 hours for users to be enabled after number assignment; if the number is still not assigned correctly after 24 hours Microsoft points to the Phone Number Service Center. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Use PowerShell to assign a phone number to a user, first Note. Checked 2026-09-25. [^7]: Assigning, modifying or removing a user's phone number requires the Teams Administrator, Teams Communications Administrator or Teams Telephony Administrator role. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Prerequisites, role list. Checked 2026-09-25. [^8]: Assigning a phone number to a user or resource account automatically sets EnterpriseVoiceEnabled to True. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Description. Checked 2026-09-25. [^9]: Get-CsPhoneNumberAssignment can filter numbers by capability (ConferenceAssignment, VoiceApplicationAssignment, UserAssignment, TeamsPhoneMobile), and Microsoft's example finds activated, unassigned numbers with VoiceApplicationAssignment. Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Parameters -CapabilitiesContain; Example 6. Checked 2026-09-25. [^10]: Set-CsPhoneNumberAssignment requires Teams PowerShell module 3.0.0 or later (the Notify parameter 7.3.0 or later) and is available only in commercial, GCC, GCCH and DoD cloud instances. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Notes. Checked 2026-09-25. [^11]: When enabling an operator, the admin's full name and email address are shared automatically with the operator, company size must be provided and a phone number is optional; operators use this to contact the customer about Operator Connect. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Enable an operator, step 3 Provide contact information. Checked 2026-09-25. [^12]: Enabling an operator in the Teams admin center probably does not by itself deliver numbers: the operator must first complete its own contract with the customer and mark the consent as agreed, so numbers not appearing after enablement usually means the commercial step is unfinished (inferred). Source: [Prepare for Operator Connect or Teams Phone Mobile live traffic with Azure Communications Gateway](https://learn.microsoft.com/en-us/azure/communications-gateway/prepare-for-live-traffic-operator-connect), Set up your test tenant, steps 1 and 4. Checked 2026-09-25. [^13]: When assigning a phone number to a user, the number and the user's usage location must be in the same country or region. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Prerequisites, second paragraph. Checked 2026-09-25. [^14]: Before moving from Direct Routing, run Get-CsPhoneNumberAssignment -AssignedPstnTargetId to confirm NumberType is DirectRouting, and Get-CsOnlineUser to check OnPremLineURI; a populated OnPremLineURI means the number was assigned on-premises and synchronized. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Direct Routing to Operator Connect > Step 1. Checked 2026-09-25. [^15]: Direct Routing numbers assigned online are migrated to Operator Connect by the operator on an agreed date and time after the customer contacts it. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Direct Routing > Step 1, paragraph beginning To migrate existing Direct Routing numbers assigned online. Checked 2026-09-25. [^16]: For Direct Routing numbers assigned on-premises, the admin clears the number with the Skype for Business Server command Set-CsUser -LineURI $null, and the number is out of service during the migration, so it must be coordinated with the operator first. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Direct Routing > Step 1, Important note and Set-CsUser command. Checked 2026-09-25. [^17]: Once a Direct Routing number is unassigned, Microsoft instructs removing the user's online voice routing policy with Grant-CsOnlineVoiceRoutingPolicy -Identity -PolicyName $Null before acquiring Operator Connect numbers. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Direct Routing > Step 2 - Remove the online voice routing policy. Checked 2026-09-25. [^18]: After the on-premises change has synced (RegistrarPool pool.infra.lync.com with empty OnPremLineURI and LineURI), the Direct Routing number is unassigned with Remove-CsPhoneNumberAssignment -PhoneNumberType DirectRouting, which can take up to 10 minutes and in rare cases up to 24 hours. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Direct Routing > Step 1, expected output and Remove-CsPhoneNumberAssignment paragraph. Checked 2026-09-25. [^19]: Emergency addresses are added in the Teams admin center under Locations > Emergency addresses > Add, entering a name, description, country or region and address, with an Edit the address manually option if the address is not found; PowerShell uses New-CsOnlineLisCivicAddress. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Add an emergency location > Use the Microsoft Teams admin center; Use PowerShell. Checked 2026-09-25. [^20]: For Operator Connect numbers the emergency location is assigned in Voice > Phone numbers > Numbers tab by selecting the number, Edit, choosing a location under Emergency location and selecting Apply, with the location, user and number all in the same country. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Assign an emergency location > Calling Plans, Operator Connect, Teams Phone Mobile. Checked 2026-09-25. [^21]: An emergency location can be removed only when no users or phone numbers are assigned to it. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Remove an emergency location. Checked 2026-09-25. [^22]: To activate a phone number in Belgium, France, Germany, Ireland, the Netherlands or Spain, the emergency location's address must match the number's area code. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Add an emergency location, Note. Checked 2026-09-25. [^23]: An emergency address must be marked validated before it can be assigned to a user or network identifier, and addresses defined with the Teams admin center map search are validated automatically. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Emergency address > Emergency address validation. Checked 2026-09-25. [^24]: An emergency address can be edited only while it is not yet validated; a validated address that needs correcting must be deleted and recreated. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Change an emergency location, second paragraph. Checked 2026-09-25. [^25]: The operator implements one of three emergency-address scenarios: it assigns addresses and lets the admin change them in the Teams admin center; it assigns none and lets the admin assign them; or it assigns them and does not allow changes, so changes must go through the operator. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Set up phone numbers > Assign numbers to emergency addresses. Checked 2026-09-25. [^26]: To enable an operator the admin chooses it in the All operators tab (filterable by region or service), selects countries or regions under Operator settings, provides contact information, accepts the data transfer notice and selects Add as my operator. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Enable an operator, numbered steps 1-5. Checked 2026-09-25. [^27]: Get-CsPhoneNumberAssignment -AssignedPstnTargetId accepts a user or resource account and returns the assigned number's NumberType, ActivationState, PstnAssignmentStatus, PstnPartnerName, LocationId and LocationUpdateSupported. Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Examples 1, 4 and 5; Outputs. Checked 2026-09-25. [^28]: In a hybrid deployment with on-premises Active Directory, any number stored in the msRTCSIP-Line attribute of the user or resource account must be removed and synchronized to Microsoft 365 before an Operator Connect number can be assigned. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Prerequisites, Note on hybrid deployment with on-premises Active Directory. Checked 2026-09-25. [^29]: Set-CsPhoneNumberAssignment can set an emergency LocationId, obtained with Get-CsOnlineLisLocation, on both assigned and unassigned phone numbers. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Parameters -LocationId; Example 9; Notes. Checked 2026-09-25. [^30]: Removing a location from a number, by passing the string null as LocationId, is supported for Direct Routing numbers and for Operator Connect numbers that are not managed by the Service Desk. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Parameters -LocationId, second paragraph; Example 4. Checked 2026-09-25. [^31]: The My operators tab shows enabled operators and their status and lets the admin manage operator services by country or region, suspend an operator or remove an operator. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Manage your operators. Checked 2026-09-25. [^32]: Microsoft lists three ways users can receive Operator Connect numbers: purchase new numbers from the operator, port existing numbers, or migrate users from another Teams Phone PSTN connectivity option. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Onboarding > Step 3: Plan your phone numbers. Checked 2026-09-25. [^33]: Whether a tenant admin can set, modify or delete an Operator Connect user's registered emergency address depends on the capabilities the carrier assigned to the number when uploading it to the customer's inventory. Source: [Considerations for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/considerations-operator-connect), Emergency call enablement for Operator Connect, second paragraph. Checked 2026-09-25. [^34]: Each Operator Connect user is automatically enabled for emergency calling, and emergency calls are routed automatically to the Operator Connect carrier for that number. Source: [Considerations for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/considerations-operator-connect), Emergency call enablement for Operator Connect, first paragraph. Checked 2026-09-25. [^35]: For Operator Connect, a client outside any tenant-defined dynamic location that is not a Common Area Phone or Teams Room is screened by a national call center, and if the caller cannot update their location the call goes to the PSAP for the registered address. Source: [Considerations for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/considerations-operator-connect), Emergency call routing for Operator Connect, last two bullets. Checked 2026-09-25. [^36]: For Operator Connect in the United States and Canada, dynamic emergency routing is part of the carrier's service; US calls from a tenant-defined dynamic location route directly to the serving PSAP, while all Canadian emergency calls are screened by a national call center first. Source: [Considerations for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/considerations-operator-connect), Emergency call routing for Operator Connect; Dynamic emergency calling for Operator Connect. Checked 2026-09-25. [^37]: Microsoft suggests evaluating operators on country and regional availability, phone number availability and porting support, calling plans and service offerings, and existing business relationships. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Onboarding > Step 2: Choose a certified operator. Checked 2026-09-25. [^38]: After the operator completes an order or porting order it uploads the numbers to the customer tenant, where they and their provider appear in the Teams admin center under Voice > Phone numbers. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Acquire numbers for new Teams users, step 4; Move numbers from Calling Plans, step 2. Checked 2026-09-25. [^39]: New Operator Connect numbers are ordered on the operator's website rather than in the Teams admin center, and the customer must provide its Microsoft 365 tenant ID. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Set up phone numbers > Acquire numbers for new Teams users, step 3. Checked 2026-09-25. [^40]: To move numbers from Microsoft Calling Plans to Operator Connect, the customer contacts the operator to port them; the operator uploads them after completing the porting order and the admin then assigns them. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Calling Plans to Operator Connect, steps 1-3. Checked 2026-09-25. [^41]: Operator Connect numbers are assigned in PowerShell with Set-CsPhoneNumberAssignment -Identity -PhoneNumber -PhoneNumberType OperatorConnect; PhoneNumber and PhoneNumberType are aliases of TelephoneNumber and NumberType. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Use PowerShell to assign a phone number to a user, For Operator Connect numbers. Checked 2026-09-25. [^42]: Creating and managing a resource account needs a Teams administrator role (Teams Telephony, Teams Communications or Teams Administrator) plus the User Administrator role, and editing one currently needs Global Administrator or Skype for Business Administrator plus User Administrator. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Assign permissions for managing a resource account, role list and Notes. Checked 2026-09-25. [^43]: To number a resource account in the Teams admin center, go to Voice > Resource accounts, select the account, select Assign/unassign, choose the Phone number type, search for the number including its country code, select Add and Save. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Assign a phone number, steps 1-6. Checked 2026-09-25. [^44]: A resource account is created in the Teams admin center under Voice > Resource accounts > Add by entering Display name, Username and a Resource account type of Auto attendant or Call queue, or with New-CsOnlineApplicationInstance. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Create a resource account. Checked 2026-09-25. [^45]: If a resource account will have a phone number, the Select location value on its Licenses and Apps tab in the Microsoft 365 admin center should match the intended country code. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Assign a license, Note. Checked 2026-09-25. [^46]: Phone numbers are optional for auto attendants and call queues, but one that must be reachable directly by phone number needs a resource account with an associated number, and Operator Connect numbers are among the acceptable number types. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Obtain phone numbers. Checked 2026-09-25. [^47]: Resource accounts used for auto attendants and call queues are disabled for sign-in and must remain so. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Introductory Note. Checked 2026-09-25. [^48]: An Operator Connect number intended for a resource account probably needs the VoiceApplicationAssignment capability, and one uploaded only with UserAssignment probably cannot be assigned to an auto attendant or call queue account, so capability is what to check when a service number request goes wrong (inferred). Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Parameters -CapabilitiesContain; Example 6. Checked 2026-09-25. [^49]: A number is released from the Phone numbers page with Release; if it is assigned, it must first be unassigned via Edit before Release is available. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Release numbers. Checked 2026-09-25. [^50]: Remove-CsPhoneNumberAssignment can set an assignment block on the freed number, either indefinite (AssignmentBlockedForever) or for 1 to 365 days (AssignmentBlockedDays), parameters introduced in Teams PowerShell module 7.5.0. Source: [Remove-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/remove-csphonenumberassignment), Parameters -AssignmentBlockedDays and -AssignmentBlockedForever; Notes. Checked 2026-09-25. [^51]: Before removing an operator from the organization or from a country or region, all phone numbers assigned to users there must be removed and the operator contacted to release the numbers. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Manage your operators, Note. Checked 2026-09-25. [^52]: Toll or toll-free service numbers for Audio Conferencing, auto attendants and call queues are obtained by contacting the operator, and a service number can handle hundreds of simultaneous calls whereas a user number handles only a few. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Acquire numbers for new Teams users, Note after step 4. Checked 2026-09-25. [^53]: In the Teams admin center a number can be assigned either from Voice > Phone numbers (select an unassigned number, Edit, Assigned to) or from Users > Manage users > Account > Assign primary phone number, choosing the PSTN connectivity type in Phone number type. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Use Teams admin center to assign a phone number to a user, both tabs. Checked 2026-09-25. [^54]: Operators are enabled, edited and removed in the Teams admin center under Voice > Operator Connect. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Enable an operator, first paragraph. Checked 2026-09-25. [^55]: To remove a user's number in the Teams admin center, open the user's Account tab, select Edit under Assigned phone number, choose None and select Apply. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Use Teams admin center to remove a phone number from a user. Checked 2026-09-25. [^56]: To check Teams Only mode, go to Teams > Teams upgrade settings in the Teams admin center; if the organization is in Islands mode, check each user's Account tab, where the coexistence mode under Teams upgrade settings should be TeamsOnly. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Set up phone numbers > Acquire numbers for new Teams users, step 2. Checked 2026-09-25. [^57]: After assignment, test calls in and out of each number are the practical end-to-end check; a failure there with a correct Activated OperatorConnect assignment in Teams is likely a PSTN-side issue for the operator to investigate under the support boundary (inferred). Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Support boundaries. Checked 2026-09-25. [^58]: Remove-CsPhoneNumberAssignment unassigns a number from a user or resource account, automatically sets EnterpriseVoiceEnabled to False, and leaves the number available in the tenant unless an assignment block is set. Source: [Remove-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/remove-csphonenumberassignment), Description. Checked 2026-09-25. [^59]: Operator Connect uses certified third-party operators that have already completed PSTN integration with Microsoft; the customer needs a contract with the operator and enables the operator in the Teams admin center, with no customer-deployed SBC. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Plan for Operator Connect, introduction and section 'Step 4: Configure Operator Connect'. Checked 2026-09-24. [^60]: Operator Connect requires users to have Teams Phone licenses and to be configured in Teams Only mode, and a certified operator must serve the countries or regions being deployed. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Plan for Operator Connect, section 'Step 1: Verify prerequisites'. Checked 2026-09-24. [^61]: To use PSTN telephony with Teams Phone, a user account must be licensed with the Teams Phone application and also be equipped with a PSTN solution from a PSTN service provider. Source: [PSTN connectivity options](https://learn.microsoft.com/en-us/microsoftteams/pstn-connectivity), PSTN connectivity options, section 'What is the Public Switched Telephone Network (PSTN)?'. Checked 2026-09-24. [^62]: If Microsoft provides PSTN access and numbers, the user needs a Microsoft Calling Plan license in addition to Teams Phone licensing; if a PSTN operator other than Microsoft is used, Microsoft requires no further licensing because PSTN costs come from that operator. Source: [Teams Phone licensing](https://learn.microsoft.com/en-us/microsoftteams/teams-phone-licensing), Teams Phone licensing, section 'Licensing Teams Phone - adding PSTN'. Checked 2026-09-24. [^63]: A single Teams tenant can have more than one PSTN integration, and Microsoft states that any combination of PSTN solutions is supported. Source: [What is Teams Phone](https://learn.microsoft.com/en-us/microsoftteams/what-is-phone-system-in-office-365), What is Teams Phone, add-on options list, PSTN operator solution sub-bullets. Checked 2026-09-24. [^64]: To assign an emergency location to a network identifier for dynamic emergency calling, the emergency address must be validated and carry a geo code; addresses created with the Teams admin center map search get both automatically. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Plan and manage emergency calling, sections 'Emergency address validation' and 'Emergency address geo codes', Important block. Checked 2026-09-24. [^65]: Under Operator Connect, the operator is responsible for PSTN connectivity, number provisioning and porting, calling services and PSTN-related support; Microsoft is responsible for Teams services, Teams Phone administration, the Teams admin center and the Teams-to-operator integration. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Plan for Operator Connect, section 'Support boundaries'. Checked 2026-09-24. [^66]: Microsoft describes Teams Phone as its technology for call control and PBX capabilities delivered in the Microsoft 365 cloud. Source: [What is Teams Phone](https://learn.microsoft.com/en-us/microsoftteams/what-is-phone-system-in-office-365), What is Teams Phone, opening paragraph. Checked 2026-09-24. [^67]: Placing calls by extension or PSTN number, forwarding and simultaneous ring to PSTN numbers, dial plans, emergency calling, unassigned number routing and call blocking of PSTN numbers are all listed as requiring Teams Phone. Source: [Teams Phone features](https://learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system), Teams Phone features, table 'Teams calling features', rows 'Call answer/initiate (by extension or PSTN phone number)', 'Call forwarding options and simultaneous ring', 'Dial plans', 'Emergency calling', 'Unassigned number routing', 'Call blocking'. Checked 2026-09-24. [^68]: Every resource account for an auto attendant or call queue must be assigned a Teams Phone Resource Account license, whether or not it will be assigned a telephone number; a Calling Plan is needed only if the resource account must dial out. Source: [Microsoft Teams Phone Resource Account licenses](https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/virtual-user), Microsoft Teams Phone Resource Account licenses, paragraphs 1-2 and second Note. Checked 2026-09-24. [^69]: Teams Phone Standard must not be assigned to resource accounts; when converting, remove Teams Phone Standard and assign the Resource Account license in the same license activity, otherwise the resource account (and its auto attendants and call queues) may stop working. Source: [Microsoft Teams Phone Resource Account licenses](https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/virtual-user), Microsoft Teams Phone Resource Account licenses, section 'Change an existing resource account to use a Microsoft Teams Phone Resource Account license', Warning block. Checked 2026-09-24. [^70]: Microsoft states there is no longer any cost for Teams Phone Resource Account licenses, but the admin must still complete a Buy step at zero cost through the same purchasing channel used for the subscription containing Teams Phone (disputed). Source: [Microsoft Teams Phone Resource Account licenses](https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/virtual-user), Microsoft Teams Phone Resource Account licenses, opening Note and section 'How to obtain Microsoft Teams Phone Resource Account licenses' step 9 Note. Checked 2026-09-24.