# Troubleshooting Teams phone number assignment errors Canonical: https://warmtransfer.net/knowledge/teams-number-assignment-errors Last verified: 2026-09-30 Phone number assignment errors in Microsoft Teams arise from mismatched user attributes, prerequisite licensing gaps, synchronization locks from on-premises directories, and emergency location rules[^13][^9][^27][^28]. Successfully applying numbers requires adhering to specific administrative roles, cmdlet parameters, and connectivity constraints across Calling Plans, Direct Routing, and Operator Connect[^4][^34][^40]. ## Prerequisites, Roles, and Licensing Assigning, modifying, or removing a user's phone number requires one of three roles: Teams Administrator, Teams Communications Administrator, or Teams Telephony Administrator[^4]. When assigning a number to a user, the phone number and the user's usage location must be of the same country/region[^13]. Licensing requirements vary based on the target identity and connectivity type: * A user assigned a Teams Calling Plan number must also hold a Teams Calling Plan license[^9]. * Users assigned Operator Connect numbers require a Teams Phone (Phone System) license and must be in TeamsOnly mode[^41]. * Each resource account requires a Microsoft Teams Phone Resource Account license to work with auto attendants and call queues[^48]. * For a resource account requiring a phone number, Microsoft instructs administrators to verify that the "Select location" value on the account's Licenses and Apps tab in the Microsoft 365 admin center matches the intended country code[^49]. * Editing a resource account currently requires either the Global Admin role or the Skype for Business Administrator role combined with the User Administrator role[^47]. Microsoft documents that assigning a toll service number in the Teams admin center can fail with the error "You need a phone system license", which is resolved by assigning the toll service number using PowerShell cmdlets instead[^56]. ## Assignment Methods and PowerShell Parameters The primary cmdlet for assigning numbers is `Set-CsPhoneNumberAssignment`, available in Teams PowerShell module 3.0.0 or later within commercial, GCC, GCCH, and DoD cloud instances[^30][^12]. Its parameter `-NumberType` (alias `-PhoneNumberType`) is mandatory for an assignment and supports exactly three values: `DirectRouting`, `CallingPlan`, and `OperatorConnect`[^34]. Teams Phone Mobile numbers are also assigned using `-NumberType OperatorConnect`, as no dedicated Teams Phone Mobile value exists[^57]. Assigning a phone number automatically sets the `EnterpriseVoiceEnabled` attribute of the target user or resource account to `True`[^24]. Conversely, unassigning a number with `Remove-CsPhoneNumberAssignment` automatically sets `EnterpriseVoiceEnabled` to `False`[^54]. ``` Set-CsPhoneNumberAssignment -Identity -PhoneNumberType -TelephoneNumber ```[^34] When specifying `-TelephoneNumber`, the parameter accepts E.164 format (such as +12065551234) or the same digits without the plus sign, but the string cannot carry a `tel:` prefix[^31]. For Direct Routing extensions, the value takes the format `+1206555000;ext=1234` or `1206555000;ext=1234`[^16]. In the Teams admin center, assigning from Voice > Phone numbers functions for Direct Routing only if the numbers were uploaded to Teams[^32]. When assigning directly from a user profile in the admin center, an unuploaded Direct Routing number must be typed in manually rather than selected from a drop-down menu[^19]. For resource accounts, the Teams admin center can assign only Direct Routing numbers without extensions; any Direct Routing number with an extension requires assignment through `Set-CsPhoneNumberAssignment`[^46]. Direct Routing users must be homed online, which is verified by checking that the user's `RegistrarPool` value is in the `infra.lync.com` domain[^17]. Uploading Direct Routing numbers to Microsoft's telephone number management inventory is optional, as assigning an unuploaded number to a user automatically uploads it[^23]. However, before Direct Routing numbers can be ported to Teams under another PSTN connectivity option, they must be unassigned from users and released from inventory using `New-CsOnlineTelephoneNumberReleaseOrder`[^22]. ## On-Premises Synchronization Conflicts In hybrid deployments with on-premises Active Directory, `Set-CsPhoneNumberAssignment` cannot assign a phone number to a user or resource account whose phone number is set on-premises and synchronized into Microsoft 365[^44]. A Calling Plan or Operator Connect number can be applied only after any number in the on-premises `msRTCSIP-Line` attribute has been cleared and that synchronization completes to Microsoft 365[^27]. If `Get-CsOnlineUser` shows `OnPremLineUri` populated with an E.164 number, it indicates the number was assigned on-premises[^21]. To manage that Direct Routing user online, an administrator must clear the value on-premises using `Set-CsUser -LineUri $null` within the Skype for Business Management Shell, allow directory synchronization to finish, and then execute the assignment via Teams PowerShell[^21]. If a Direct Routing user's number remains managed on-premises, the administrator does not assign the number online, but instead enables the user by running `Set-CsPhoneNumberAssignment -Identity -EnterpriseVoiceEnabled $true`[^20]. Moving a user from Direct Routing to Operator Connect requires a specific order of operations: unassign the Direct Routing number (first clearing `LineURI` on-premises if `OnPremLineUri` is populated), remove the user's online voice routing policy, acquire numbers from the operator, and assign the Operator Connect number after the operator uploads it[^36]. ## Operator Connect and Inventory Availability Under Operator Connect, support responsibilities are split: the operator handles telephone number provisioning and porting, while Microsoft handles Teams admin center functionality and the integration between Teams and Operator Connect[^42]. Operator Connect numbers are uploaded directly to the customer's tenant by the operator once an order completes, becoming visible under Voice > Phone numbers[^40]. Attempting to use the "Add phone numbers" wizard in the Teams admin center for Operator Connect redirects the administrator away from the console to the operating partner[^43]. WarmTransfer's reading of the sources is that when an expected Operator Connect number is missing from tenant inventory, the administrator has no documented way to add it directly and must contact the operator, since only the operator uploads those numbers[^39]. Available number types and capabilities govern target assignments: * Acceptable numbers for resource accounts are Calling Plans service numbers, Direct Routing numbers, and Operator Connect numbers[^50]. * Toll-free numbers can only be assigned to voice applications (auto attendants and call queues) and audio conferencing bridges, not to individual users[^55]. * Teams Phone defines three number usages: User (users or devices), Voice app (auto attendant and call queue resource accounts), and Conference (conference bridges)[^58]. * The "Change usage" option in the Teams admin center is offered only when a number's assignment status is Unassigned and the tenant has more available usages than licensed usages[^11]. ## Emergency Location Rules Emergency locations must be in the same country as the user and the phone number[^28]. In addition, emergency addresses must be marked as validated before they can be assigned to a user or network identifier; addresses created using the map search in the Teams admin center validate automatically[^3]. Additional geographic and connectivity rules include: * In Belgium, France, Germany, Ireland, the Netherlands, and Spain, activating a number in Microsoft 365 requires the emergency location address to match the number's area code[^5]. * For Calling Plan numbers in the United States and Canada, an emergency location is mandatory at the time the number is assigned to a user[^15]. Outside the United States and Canada (such as in EMEA), the emergency location is required when obtaining or porting the number, rather than at user assignment[^14]. * Direct Routing allows an administrator to assign the phone number first, with emergency location assignment being optional[^18]. * For Operator Connect and Operator Connect Mobile, tenant administrator permissions to set, modify, or delete an emergency location depend on the carrier-assigned capabilities uploaded with the number[^38][^37]. Operators implement one of three arrangements: they assign addresses and allow admin changes, assign none and allow admin assignment, or assign addresses and prohibit admin changes (requiring changes to go through the operator)[^35]. Removing an emergency location by supplying the string `null` for `-LocationId` in `Set-CsPhoneNumberAssignment` is supported only for Direct Routing numbers and Operator Connect numbers not managed by the Service Desk[^29]. ## State Inspection, Latency, and Assignment Blocks Inventory and activation details are evaluated with `Get-CsPhoneNumberAssignment`: * `ActivationState` reports `Activated`, `AssignmentPending`, `AssignmentFailed`, `UpdatePending`, or `UpdateFailed`[^2]. * `PstnAssignmentStatus` reports `Unassigned`, `UserAssigned`, `ConferenceAssigned`, `VoiceApplicationAssigned`, `ThirdPartyAppAssigned`, or `PolicyAssigned`[^45]. * `NumberSource` outputs `Online` for numbers assigned in Microsoft 365 and `OnPremises` for numbers synced from Active Directory[^33]. * The `-CapabilitiesContain` filter tests assignable targets using `ConferenceAssignment`, `VoiceApplicationAssignment`, `UserAssignment`, and `TeamsPhoneMobile`[^10]. After assignment, latency between Microsoft 365 and Teams can require up to 24 hours for the user to be enabled; if the number is still not correctly assigned after 24 hours, Microsoft directs administrators to the Phone Number Service Center[^1]. Unassigning a number via `Remove-CsPhoneNumberAssignment` can take up to 10 minutes, and in rare cases up to 24 hours[^51]. From Teams PowerShell module 4.2.1-preview onward, `Remove-CsPhoneNumberAssignment` reports errors by raising exceptions appended to `$Error` and honours `ErrorAction`, replacing the older result object containing `Code` and `Message` strings[^53]. If a number has an `AssignmentBlockedState` of `BlockedForever` or `BlockedUntil`, it cannot be assigned until an administrator clears the restriction using `Remove-CsPhoneNumberAssignmentBlock -TelephoneNumber`[^6][^52]. Regarding time-limited blocks, sources disagree: the `Remove-CsPhoneNumberAssignment` documentation indicates administrators can set a temporary block via `-AssignmentBlockedDays` (1 to 365 days), whereas the `Get-CsPhoneNumberAssignment` documentation states that the time-limited block (`BlockedUntil`) is currently not available[^7][^8]. ## See also * [Microsoft Teams Calling Plans](https://warmtransfer.net/knowledge/teams-calling-plans) * [Teams Phone Direct Routing and SBC certification](https://warmtransfer.net/knowledge/teams-direct-routing) * [Teams Operator Connect and Azure Communication routing](https://warmtransfer.net/knowledge/teams-operator-connect) * [Microsoft Teams auto attendants and call queues](https://warmtransfer.net/knowledge/teams-auto-attendant-call-queue) * [Teams voice administration with PowerShell](https://warmtransfer.net/knowledge/teams-powershell-voice-admin) ## Applicability Applies to: Microsoft Teams Phone, Microsoft Teams Phone - Operator Connect, MicrosoftTeams PowerShell module, Microsoft Teams Phone - Direct Routing, and Microsoft Teams Phone - Calling Plans. Deployments: cloud, hybrid, and multi-tenant. Sources checked 2026-09-30. Set-CsPhoneNumberAssignment is available in Teams PowerShell module 3.0.0 or later, with the Notify parameter arriving in 7.3.0 and alternate number assignment in 7.6.0[^30]. Set-CsPhoneNumberAssignment operates solely within commercial, GCC, GCCH, and DoD cloud environments[^12]. Region-specific area-code matching rules apply to Belgium, France, Germany, Ireland, the Netherlands, and Spain[^5]. ## What remains uncertain * Which licence SKUs permit each NumberType for users and resource accounts is not covered by the sources below. * A catalogue of exact Set-CsPhoneNumberAssignment and Teams admin center assignment error strings with causes is not covered by the sources below. * The effect of changing a user's usage location after a number is already assigned is not covered by the sources below. * Operator Connect number upload latency and what operators commit to is not covered by the sources below. * Multi-line alternate and private number assignment rules and errors are not covered by the sources below. * What causes ActivationState AssignmentFailed or UpdateFailed and how to clear them is not covered by the sources below. * The delay between licence assignment and a user becoming assignable is not covered by the sources below. * Shared Calling policy numbers and the PolicyAssigned status are not covered by the sources below. ## Sources [^1]: After a number is assigned, it can take up to 24 hours for the user to be enabled because of latency between Microsoft 365 and Teams; if the number is not correctly assigned after 24 hours, Microsoft directs admins 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-30. [^2]: Get-CsPhoneNumberAssignment reports an ActivationState for each number whose supported values are Activated, AssignmentPending, AssignmentFailed, UpdatePending and UpdateFailed. Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Parameters, -ActivationState. Checked 2026-09-30. [^3]: An emergency address must be marked as validated before it can be assigned to a user or to a network identifier; addresses defined through the address map search in the Teams admin center are marked 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 validation. Checked 2026-09-30. [^4]: Assigning, modifying or removing a user's phone number requires one of the roles Teams Administrator, Teams Communications Administrator or Teams Telephony Administrator. 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-30. [^5]: To activate a phone number in Microsoft 365 in Belgium, France, Germany, Ireland, the Netherlands and Spain, the address in the emergency location must match the phone number's area code. Source: [Manage emergency locations - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/assign-change-emergency-location-user), Add an emergency location, Note. Checked 2026-09-30. [^6]: A number that carries an assignment block (AssignmentBlockedState of BlockedForever or BlockedUntil) cannot be assigned to another user until the block is removed. Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Example 14 and Example 15; Outputs, AssignmentBlockedState; Notes (introduced in 7.5.0). Checked 2026-09-30. [^7]: Remove-CsPhoneNumberAssignment can set a time-limited assignment block on the number it unassigns through AssignmentBlockedDays, an integer from 1 through 365, after which the number automatically becomes assignable again (disputed). Source: [Remove-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/remove-csphonenumberassignment), Parameters, -AssignmentBlockedDays; Example 6; Notes. Checked 2026-09-30. [^8]: The Get-CsPhoneNumberAssignment reference states that the limited-time assignment block (BlockedUntil) is currently not available (disputed). Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Outputs, AssignmentBlockedState. Checked 2026-09-30. [^9]: A user who is to be assigned a Teams Calling Plan number must also have a Teams Calling Plan license. Source: [Manage phone numbers for users](https://learn.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone-number-for-a-user), Prerequisites, paragraph after the role list. Checked 2026-09-30. [^10]: A number's assignable targets are expressed as capabilities; the capability filter of Get-CsPhoneNumberAssignment supports ConferenceAssignment, VoiceApplicationAssignment, UserAssignment and TeamsPhoneMobile. Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Parameters, -CapabilitiesContain. Checked 2026-09-30. [^11]: The 'Change usage' option in the Teams admin center is offered only for a number whose assignment status is Unassigned and which has more available usages than licensed usages. Source: [Manage the usage of a phone number - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-the-usage-of-a-phone-number), How to manage the usage of a phone number, step 3 sub-bullets. Checked 2026-09-30. [^12]: Set-CsPhoneNumberAssignment is available only in the commercial, GCC, GCCH and DoD cloud instances. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Notes, second paragraph. Checked 2026-09-30. [^13]: When a phone number is assigned to a Teams user, the phone number and the user's usage location must be of the same country/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-30. [^14]: For Calling Plan numbers outside the United States and Canada, such as in EMEA, the emergency location is required when the number is obtained from Microsoft 365 or ported in from another provider, not at the point of user assignment. Source: [Considerations for Calling Plans](https://learn.microsoft.com/en-us/microsoftteams/considerations-calling-plan), Emergency call enablement for Calling Plans, second bullet. Checked 2026-09-30. [^15]: For Calling Plan numbers in the United States and Canada, an emergency location is required at the moment a number is assigned to a user. Source: [Considerations for Calling Plans](https://learn.microsoft.com/en-us/microsoftteams/considerations-calling-plan), Emergency call enablement for Calling Plans, first bullet. Checked 2026-09-30. [^16]: Direct Routing numbers with extensions are assigned to a user or resource account in the form +1206555000;ext=1234 or 1206555000;ext=1234. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Parameters, -TelephoneNumber, second paragraph; Example 6. Checked 2026-09-30. [^17]: Direct Routing requires the user to be homed online, which is checked by confirming that the user's RegistrarPool value is in the infra.lync.com domain. Source: [Enable users for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-enable-users), Ensure that the user is homed online, second paragraph. Checked 2026-09-30. [^18]: For Direct Routing users the admin assigns the Direct Routing phone number and then optionally an emergency location. Source: [Manage emergency locations - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/assign-change-emergency-location-user), Assign an emergency location, Use the Microsoft Teams admin center, Direct Routing. Checked 2026-09-30. [^19]: When assigning from the user profile in the Teams admin center, a Direct Routing number that has not been uploaded to Teams is typed in manually rather than picked from the drop-down. 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, tab 'Assign a number to a user from the user profile', step 6. Checked 2026-09-30. [^20]: When a Direct Routing user's phone number is managed on-premises, the admin does not assign the number online but runs Set-CsPhoneNumberAssignment -Identity -EnterpriseVoiceEnabled $true to make the user Enterprise Voice enabled online. Source: [Enable users for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-enable-users), Configure the phone number and enable enterprise voice, Use PowerShell, step 2 first bullet. Checked 2026-09-30. [^21]: If Get-CsOnlineUser shows OnPremLineUri populated with an E.164 number, the number was assigned on-premises and synchronized; to manage it online the admin clears it with Set-CsUser -LineUri $null in the on-premises Skype for Business Management Shell and waits for the sync before assigning with Teams PowerShell. Source: [Enable users for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-enable-users), Ensure that the user is homed online, steps 2 and 3. Checked 2026-09-30. [^22]: Before Direct Routing numbers are ported to Teams under another PSTN connectivity option, they must be unassigned from users and released from Microsoft's telephone number management inventory with New-CsOnlineTelephoneNumberReleaseOrder. Source: [Enable users for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-enable-users), Order history, Note. Checked 2026-09-30. [^23]: Uploading Direct Routing numbers to Microsoft's telephone number management inventory is optional; assigning a Direct Routing number to a user uploads it automatically if it is not already there. Source: [Enable users for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-enable-users), Upload Direct Routing numbers to your tenant, third paragraph. Checked 2026-09-30. [^24]: Assigning a phone number automatically sets the EnterpriseVoiceEnabled attribute of the user or resource account to True. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Description, first paragraph; also parameter -TelephoneNumber. Checked 2026-09-30. [^25]: A community thread reports a newly provisioned, licensed user for whom assignment failed in the Teams admin center with 'We can't save changes for the number right now. Try again later' and in PowerShell with a 'Bad Request' user-not-found error; the poster says Microsoft support completed the assignment after two to three days without disclosing a root cause (field report). Source: [Unable to assign a Teams Phone number to a brand new user account (Error: we can't save changes)](https://techcommunity.microsoft.com/discussions/microsoftteams/unable-to-assign-a-teams-phone-number-to-a-brand-new-user-account-error-we-cant-/3070818), Original post and Reply 1 by manojviduranga, marked as solution. Checked 2026-09-30. [^26]: A community reply marked as the solution reports that assigning a number from a different country than the user's usage location works only with Direct Routing, and that Operator Connect and Calling Plans require the usage location to match the number (field report). Source: [MS Teams Phone Number Assignment and Usage Location](https://techcommunity.microsoft.com/discussions/microsoftteams/ms-teams-phone-number-assignment-and-usage-location/4024289), Reply 1 by LinusCansby, marked as solution. Checked 2026-09-30. [^27]: In a hybrid deployment with on-premises Active Directory, a Calling Plan or Operator Connect number can be assigned to a user or resource account only after any phone number in the on-premises msRTCSIP-Line attribute has been removed and that change has synchronized to Microsoft 365. 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 Note (hybrid deployment). Checked 2026-09-30. [^28]: An emergency location can be assigned only when the location, the users and the phone numbers are all in the same country. Source: [Manage emergency locations - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/assign-change-emergency-location-user), Assign an emergency location, second paragraph. Checked 2026-09-30. [^29]: Removing the emergency location from a phone number, by passing the string null as LocationId, is supported only 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-30. [^30]: Set-CsPhoneNumberAssignment is available in Teams PowerShell module 3.0.0 or later; the Notify parameter arrived in 7.3.0 and alternate number assignment in 7.6.0. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Notes, first paragraph. Checked 2026-09-30. [^31]: The TelephoneNumber parameter of Set-CsPhoneNumberAssignment accepts E.164 format (for example +12065551234) and the same digits without the plus sign, and the number cannot carry a 'tel:' prefix. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Parameters, -TelephoneNumber. Checked 2026-09-30. [^32]: In the Teams admin center, assigning from the Voice > Phone numbers list works for Direct Routing numbers only if the Direct Routing numbers were uploaded to Teams. 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, tab 'Assign a number to a user from the phone number list'. Checked 2026-09-30. [^33]: The NumberSource output of Get-CsPhoneNumberAssignment is Online for numbers assigned in Microsoft 365 and OnPremises for numbers assigned in on-premises Active Directory and synchronized into Microsoft 365. Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Outputs, NumberSource; Notes (introduced in 5.7.0). Checked 2026-09-30. [^34]: The NumberType parameter of Set-CsPhoneNumberAssignment (alias PhoneNumberType) is mandatory for an assignment and supports exactly the values DirectRouting, CallingPlan and OperatorConnect. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Parameters, -NumberType. Checked 2026-09-30. [^35]: For Operator Connect numbers the operator implements one of three emergency address arrangements: it assigns addresses and lets the admin change them, it assigns none and lets the admin assign them, or it assigns them and does not let the admin change them, in which case changes go through the operator. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Assign numbers to emergency addresses. Checked 2026-09-30. [^36]: Moving a user from Direct Routing to Operator Connect follows the order: unassign the Direct Routing number (clearing LineURI on-premises first if OnPremLineUri is populated), remove the user's online voice routing policy, acquire numbers from the operator, then assign the Operator Connect number once the operator has uploaded it. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Direct Routing to Operator Connect, Steps 1 to 4. Checked 2026-09-30. [^37]: Whether a tenant admin is required or able to set, modify or delete the emergency location of an Operator Connect user depends on the capabilities assigned to the number when the carrier uploads it into 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-30. [^38]: For Operator Connect and Operator Connect Mobile numbers, whether the tenant admin can assign or change the associated emergency location depends on the operator. 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, Note after the emergency location step (both tabs). Checked 2026-09-30. [^39]: When an expected Operator Connect number is not listed in the tenant, the tenant admin has no documented way to add it and the remedy runs through the operator, because only the operator uploads Operator Connect numbers (inferred). Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Acquire numbers for new Teams users, steps 3 and 4. Checked 2026-09-30. [^40]: Operator Connect numbers are uploaded to the customer's tenant by the operator once the operator completes the order, after which they are visible 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. Checked 2026-09-30. [^41]: Users who will be assigned Operator Connect numbers need a Teams Phone (Phone System) license and must be in TeamsOnly mode. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Acquire numbers for new Teams users, steps 1 and 2. Checked 2026-09-30. [^42]: Under Operator Connect the operator is responsible for telephone number provisioning and porting, while Microsoft is responsible for Teams admin center functionality and the integration between Teams and Operator Connect. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Support boundaries. Checked 2026-09-30. [^43]: Trying to add Operator Connect numbers through the 'Add phone numbers' wizard in the Teams admin center redirects the admin away from the Teams admin center to the operating partner. Source: [Get Operator Connect telephone numbers for your organization - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/get-phone-numbers-with-operator-connect), Considerations for getting Operator Connect numbers in your tenant. Checked 2026-09-30. [^44]: Set-CsPhoneNumberAssignment cannot set a phone number on a user or resource account whose phone number is set in on-premises Active Directory and synchronized into Microsoft 365; the number must first be cleared on-premises and that change allowed to sync. Source: [Set-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csphonenumberassignment), Notes, third paragraph. Checked 2026-09-30. [^45]: The PstnAssignmentStatus of a number takes one of the values Unassigned, UserAssigned, ConferenceAssigned, VoiceApplicationAssigned, ThirdPartyAppAssigned or PolicyAssigned. Source: [Get-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/get-csphonenumberassignment), Parameters, -PstnAssignmentStatus. Checked 2026-09-30. [^46]: The Teams admin center can assign only Direct Routing numbers without extensions to a resource account; a Direct Routing number with an extension must be assigned with Set-CsPhoneNumberAssignment. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Obtain phone numbers, Note. Checked 2026-09-30. [^47]: Editing a resource account currently requires either the Global Admin role or the Skype for Business Administrator role together with the User Administrator role. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Assign permissions for managing a resource account, Note beginning 'Currently, when editing'; repeated under Edit a resource account. Checked 2026-09-30. [^48]: Each resource account needs a Microsoft Teams Phone Resource Account license to work with auto attendants and call queues. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Obtain Microsoft Teams Phone Resource Account licenses, first paragraph; Assign a license. Checked 2026-09-30. [^49]: For a resource account that needs a phone number, Microsoft tells admins to check that the 'Select location' value on the account's Licenses and Apps tab in the Microsoft 365 admin center matches 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-30. [^50]: The phone numbers that can be applied to a resource account are Calling Plans service numbers, Direct Routing numbers and Operator Connect numbers. Source: [Manage - Resource accounts for voice applications](https://learn.microsoft.com/en-us/microsoftteams/manage-resource-accounts), Obtain phone numbers, 'Acceptable phone numbers' list. Checked 2026-09-30. [^51]: Removing a phone number from a user with Remove-CsPhoneNumberAssignment may take up to 10 minutes and in rare cases up to 24 hours to take effect. 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, paragraph after the Remove-CsPhoneNumberAssignment code block. Checked 2026-09-30. [^52]: An admin removes an assignment block from a number with Remove-CsPhoneNumberAssignmentBlock -TelephoneNumber. Source: [Remove-CsPhoneNumberAssignmentBlock (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/remove-csphonenumberassignmentblock), Description; Example 1. Checked 2026-09-30. [^53]: From Teams PowerShell module 4.2.1-preview onward, Remove-CsPhoneNumberAssignment reports a failure by raising an exception appended to $Error and honours ErrorAction, where earlier versions returned a result object with Code and Message strings. Source: [Remove-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/remove-csphonenumberassignment), Description, third paragraph and Note. Checked 2026-09-30. [^54]: Unassigning a phone number with Remove-CsPhoneNumberAssignment automatically sets EnterpriseVoiceEnabled to False on the user or resource account. Source: [Remove-CsPhoneNumberAssignment (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/microsoftteams/remove-csphonenumberassignment), Description, second paragraph. Checked 2026-09-30. [^55]: Toll-free numbers can be assigned only to voice apps (auto attendants and call queues) and audio conferencing bridges, not to users. Source: [Manage the usage of a phone number - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-the-usage-of-a-phone-number), Introduction, 'Before changing the usage of a number', second bullet. Checked 2026-09-30. [^56]: Microsoft documents that assigning a toll service number in the Teams admin center can fail with the error 'You need a phone system license', and that the resolution is to assign the toll service number with PowerShell cmdlets instead. Source: [You need a phone system license error when you assign a toll service number - Microsoft Teams](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/teams-conferencing/need-a-license-error-when-assigning-a-number), Symptoms; Resolution. Checked 2026-09-30. [^57]: Teams Phone Mobile numbers are assigned with Set-CsPhoneNumberAssignment using the number type OperatorConnect; there is no separate Teams Phone Mobile value. 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 Teams Phone Mobile numbers' code block. Checked 2026-09-30. [^58]: Teams Phone defines three number usages: User for numbers assigned to users or devices, Voice app for numbers assigned to the resource accounts of auto attendants and call queues, and Conference for numbers assigned to conference bridges. Source: [Acquire phone numbers for your organization - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/different-kinds-of-phone-numbers-used-for-calling-plans), Number usage types, table. Checked 2026-09-30.