Troubleshooting Teams phone number assignment errors

Set-CsPhoneNumberAssignment -Identity <user> -PhoneNumberType <DirectRouting|CallingPlan|OperatorConnect> -TelephoneNumber <number>
``` <cite data-claim="teams-number-assignment-errors-numbertype-values"><a href="#claim-teams-number-assignment-errors-numbertype-values">34</a></cite>

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 <cite data-claim="teams-number-assignment-errors-no-tel-prefix"><a href="#claim-teams-number-assignment-errors-no-tel-prefix">31</a></cite>. For Direct Routing extensions, the value takes the format `+1206555000;ext=1234` or `1206555000;ext=1234` <cite data-claim="teams-number-assignment-errors-dr-extension-format"><a href="#claim-teams-number-assignment-errors-dr-extension-format">16</a></cite>. 

In the Teams admin center, assigning from Voice > Phone numbers functions for Direct Routing only if the numbers were uploaded to Teams <cite data-claim="teams-number-assignment-errors-number-list-dr-upload"><a href="#claim-teams-number-assignment-errors-number-list-dr-upload">32</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-dr-manual-entry"><a href="#claim-teams-number-assignment-errors-dr-manual-entry">19</a></cite>. 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` <cite data-claim="teams-number-assignment-errors-ra-dr-extension-tac"><a href="#claim-teams-number-assignment-errors-ra-dr-extension-tac">46</a></cite>.

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 <cite data-claim="teams-number-assignment-errors-dr-homed-online"><a href="#claim-teams-number-assignment-errors-dr-homed-online">17</a></cite>. Uploading Direct Routing numbers to Microsoft's telephone number management inventory is optional, as assigning an unuploaded number to a user automatically uploads it <cite data-claim="teams-number-assignment-errors-dr-upload-optional"><a href="#claim-teams-number-assignment-errors-dr-upload-optional">23</a></cite>. 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` <cite data-claim="teams-number-assignment-errors-dr-release-before-port"><a href="#claim-teams-number-assignment-errors-dr-release-before-port">22</a></cite>.

## 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 <cite data-claim="teams-number-assignment-errors-onprem-synced-blocked"><a href="#claim-teams-number-assignment-errors-onprem-synced-blocked">44</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-hybrid-msrtcsip-line"><a href="#claim-teams-number-assignment-errors-hybrid-msrtcsip-line">27</a></cite>. 

If `Get-CsOnlineUser` shows `OnPremLineUri` populated with an E.164 number, it indicates the number was assigned on-premises <cite data-claim="teams-number-assignment-errors-dr-onpremlineuri"><a href="#claim-teams-number-assignment-errors-dr-onpremlineuri">21</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-dr-onpremlineuri"><a href="#claim-teams-number-assignment-errors-dr-onpremlineuri">21</a></cite>. 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 <user> -EnterpriseVoiceEnabled $true` <cite data-claim="teams-number-assignment-errors-dr-onprem-managed-ev"><a href="#claim-teams-number-assignment-errors-dr-onprem-managed-ev">20</a></cite>.

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 <cite data-claim="teams-number-assignment-errors-oc-dr-move-sequence"><a href="#claim-teams-number-assignment-errors-oc-dr-move-sequence">36</a></cite>.

## 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 <cite data-claim="teams-number-assignment-errors-oc-support-boundary"><a href="#claim-teams-number-assignment-errors-oc-support-boundary">42</a></cite>. Operator Connect numbers are uploaded directly to the customer's tenant by the operator once an order completes, becoming visible under Voice > Phone numbers <cite data-claim="teams-number-assignment-errors-oc-operator-uploads"><a href="#claim-teams-number-assignment-errors-oc-operator-uploads">40</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-oc-wizard-redirect"><a href="#claim-teams-number-assignment-errors-oc-wizard-redirect">43</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-oc-missing-number-path"><a href="#claim-teams-number-assignment-errors-oc-missing-number-path">39</a></cite>.

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 <cite data-claim="teams-number-assignment-errors-ra-number-types"><a href="#claim-teams-number-assignment-errors-ra-number-types">50</a></cite>.
* Toll-free numbers can only be assigned to voice applications (auto attendants and call queues) and audio conferencing bridges, not to individual users <cite data-claim="teams-number-assignment-errors-toll-free-voice-apps"><a href="#claim-teams-number-assignment-errors-toll-free-voice-apps">55</a></cite>.
* Teams Phone defines three number usages: User (users or devices), Voice app (auto attendant and call queue resource accounts), and Conference (conference bridges) <cite data-claim="teams-number-assignment-errors-usage-types"><a href="#claim-teams-number-assignment-errors-usage-types">58</a></cite>.
* 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 <cite data-claim="teams-number-assignment-errors-change-usage-unassigned"><a href="#claim-teams-number-assignment-errors-change-usage-unassigned">11</a></cite>.

## Emergency Location Rules

Emergency locations must be in the same country as the user and the phone number <cite data-claim="teams-number-assignment-errors-location-same-country"><a href="#claim-teams-number-assignment-errors-location-same-country">28</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-address-validated"><a href="#claim-teams-number-assignment-errors-address-validated">3</a></cite>. 

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 <cite data-claim="teams-number-assignment-errors-area-code-match"><a href="#claim-teams-number-assignment-errors-area-code-match">5</a></cite>.
* 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 <cite data-claim="teams-number-assignment-errors-cp-location-us-ca"><a href="#claim-teams-number-assignment-errors-cp-location-us-ca">15</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-cp-location-elsewhere"><a href="#claim-teams-number-assignment-errors-cp-location-elsewhere">14</a></cite>.
* Direct Routing allows an administrator to assign the phone number first, with emergency location assignment being optional <cite data-claim="teams-number-assignment-errors-dr-location-optional"><a href="#claim-teams-number-assignment-errors-dr-location-optional">18</a></cite>.
* 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 <cite data-claim="teams-number-assignment-errors-oc-location-operator"><a href="#claim-teams-number-assignment-errors-oc-location-operator">38</a></cite>​<cite data-claim="teams-number-assignment-errors-oc-location-capability"><a href="#claim-teams-number-assignment-errors-oc-location-capability">37</a></cite>. 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) <cite data-claim="teams-number-assignment-errors-oc-address-scenarios"><a href="#claim-teams-number-assignment-errors-oc-address-scenarios">35</a></cite>.

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 <cite data-claim="teams-number-assignment-errors-locationid-remove"><a href="#claim-teams-number-assignment-errors-locationid-remove">29</a></cite>.

## State Inspection, Latency, and Assignment Blocks

Inventory and activation details are evaluated with `Get-CsPhoneNumberAssignment`:
* `ActivationState` reports `Activated`, `AssignmentPending`, `AssignmentFailed`, `UpdatePending`, or `UpdateFailed` <cite data-claim="teams-number-assignment-errors-activation-states"><a href="#claim-teams-number-assignment-errors-activation-states">2</a></cite>.
* `PstnAssignmentStatus` reports `Unassigned`, `UserAssigned`, `ConferenceAssigned`, `VoiceApplicationAssigned`, `ThirdPartyAppAssigned`, or `PolicyAssigned` <cite data-claim="teams-number-assignment-errors-pstn-status-values"><a href="#claim-teams-number-assignment-errors-pstn-status-values">45</a></cite>.
* `NumberSource` outputs `Online` for numbers assigned in Microsoft 365 and `OnPremises` for numbers synced from Active Directory <cite data-claim="teams-number-assignment-errors-numbersource"><a href="#claim-teams-number-assignment-errors-numbersource">33</a></cite>.
* The `-CapabilitiesContain` filter tests assignable targets using `ConferenceAssignment`, `VoiceApplicationAssignment`, `UserAssignment`, and `TeamsPhoneMobile` <cite data-claim="teams-number-assignment-errors-capability-values"><a href="#claim-teams-number-assignment-errors-capability-values">10</a></cite>.

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 <cite data-claim="teams-number-assignment-errors-24h-latency"><a href="#claim-teams-number-assignment-errors-24h-latency">1</a></cite>. Unassigning a number via `Remove-CsPhoneNumberAssignment` can take up to 10 minutes, and in rare cases up to 24 hours <cite data-claim="teams-number-assignment-errors-removal-timing"><a href="#claim-teams-number-assignment-errors-removal-timing">51</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-remove-error-model"><a href="#claim-teams-number-assignment-errors-remove-error-model">53</a></cite>.

If a number has an `AssignmentBlockedState` of `BlockedForever` or `BlockedUntil`, it cannot be assigned until an administrator clears the restriction using `Remove-CsPhoneNumberAssignmentBlock -TelephoneNumber` <cite data-claim="teams-number-assignment-errors-assignment-block"><a href="#claim-teams-number-assignment-errors-assignment-block">6</a></cite>​<cite data-claim="teams-number-assignment-errors-remove-block-cmdlet"><a href="#claim-teams-number-assignment-errors-remove-block-cmdlet">52</a></cite>. 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 <cite data-claim="teams-number-assignment-errors-block-days-available"><a href="#claim-teams-number-assignment-errors-block-days-available">7</a></cite>​<cite data-claim="teams-number-assignment-errors-block-days-unavailable"><a href="#claim-teams-number-assignment-errors-block-days-unavailable">8</a></cite>.

## See also

* [Microsoft Teams Calling Plans](/knowledge/teams-calling-plans)
* [Teams Phone Direct Routing and SBC certification](/knowledge/teams-direct-routing)
* [Teams Operator Connect and Azure Communication routing](/knowledge/teams-operator-connect)
* [Microsoft Teams auto attendants and call queues](/knowledge/teams-auto-attendant-call-queue)
* [Teams voice administration with PowerShell](/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 <cite data-claim="teams-number-assignment-errors-module-versions"><a href="#claim-teams-number-assignment-errors-module-versions">30</a></cite>. Set-CsPhoneNumberAssignment operates solely within commercial, GCC, GCCH, and DoD cloud environments <cite data-claim="teams-number-assignment-errors-cloud-availability"><a href="#claim-teams-number-assignment-errors-cloud-availability">12</a></cite>. Region-specific area-code matching rules apply to Belgium, France, Germany, Ireland, the Netherlands, and Spain <cite data-claim="teams-number-assignment-errors-area-code-match"><a href="#claim-teams-number-assignment-errors-area-code-match">5</a></cite>.

## 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.