Fix Teams Phone Number Assignment Fails for a Remote User

When you try to assign a phone number to a remote user in Teams, the operation may fail with an error message. This happens even though the user appears in the Teams admin center and has a valid license. The failure often stems from the user’s location, missing location settings, or a licensing mismatch. This article explains the root causes and provides step-by-step fixes to resolve the assignment error.

Why Teams Phone Number Assignment Fails for a Remote User

Teams phone number assignment is tied to the user’s usage location, license, and emergency address. When any of these are missing or incorrect, the assignment fails. Remote users often have a usage location that is empty or set to a country where phone numbers are not available. The Teams admin center checks these attributes before allowing the assignment.

Usage Location Blocks the Assignment

The usage location determines which phone numbers you can assign. If the user’s usage location is not set, or if it is set to a country that doesn’t support Teams Phone, the assignment fails. For example, a user with a usage location of “US” can receive a US number, but a user with “IN” may not get a US number unless you change the location.

Missing or Incorrect License

Teams Phone Standard is a paid add-on license. Without it, the user cannot have a phone number assigned. Remote users might have only a Teams license or a Microsoft 365 E3 license, which does not include the phone system. The admin center may show the number as available, but the assignment fails because the license is absent.

Emergency Location Not Configured

Each phone number must be associated with an emergency location. For remote users, the emergency location is often not set because the user is not in the office. The assignment process requires a valid location ID. If no location exists for the user’s address, the system rejects the number.

Steps to Fix Teams Phone Number Assignment for a Remote User

1. Check the user’s usage location in Microsoft 365 admin center
   Sign in to the Microsoft 365 admin center at admin.microsoft.com. Go to Users > Active users, select the remote user, and open the Account tab. Verify that the Country or region field has a value. If it is blank, select the correct country and save the change.
2. Assign the Teams Phone Standard license
   In the same user account page, open the Licenses and apps tab. Ensure that the Teams Phone Standard license is selected. If not, check the box and click Save changes. Wait 30 minutes for the license to sync.
3. Confirm the user is enabled for Teams Phone in Teams admin center
   Go to the Teams admin center at admin.teams.microsoft.com. Select Voice > Phone numbers. Find the number you want to assign and check its status. If the number is assigned to another user, unassign it first.
4. Add an emergency location for the remote user’s address
   In Teams admin center, go to Locations > Emergency addresses. Click Add, enter the remote user’s physical address, and save. If the address already exists, note the location ID.
5. Assign the phone number using the Teams admin center
   Go to Voice > Phone numbers, select the number, and click Assign. In the pane, search for the remote user, select the user, and choose the emergency location you created. Click Apply. If the assignment fails, use PowerShell as described in the next steps.
6. Use PowerShell to set the usage location and license
   Open Teams PowerShell module as an administrator. Run Connect-MicrosoftTeams. Then run Set-CsPhoneNumberAssignment -Identity user@domain.com -PhoneNumber +12065550123 -PhoneNumberType DirectRouting. If the error persists, run Set-CsUser -Identity user@domain.com -LocationID “location-id” to assign the emergency location.
7. Verify the assignment after a sync delay
   After the assignment, wait up to 24 hours for the number to appear in Teams. Check the user’s account in Teams admin center to confirm the number is listed under Voice > Phone numbers.

If Teams Still Has Issues After the Main Fix

Teams Shows “Number cannot be assigned” Despite Correct License

This error often appears when the number is in a different phone number pool than the user’s location. For example, a US number cannot be assigned to a user with a UK usage location. Change the user’s usage location to match the number’s country, or acquire a number from the correct pool.

Remote User Cannot Make Calls After Number Assignment

If the number is assigned but the user cannot make calls, check the calling policy. Go to Voice > Calling policies in Teams admin center. Ensure the user has a policy that allows outbound calls. Also verify that the user’s Teams client is updated and signed in with the correct account.

PowerShell Error “No location found” When Setting LocationID

This error means the emergency location you tried to use does not exist. Run Get-CsOnlineLisLocation to list all locations. Copy the LocationId of the correct address and use it in the Set-CsUser command. If no location exists, create one in the Teams admin center first.

Teams Admin Center vs PowerShell for Number Assignment

Item	Teams Admin Center	PowerShell
Ease of use	Graphical interface, no commands required	Requires command syntax and module installation
Speed for one user	Quick if all prerequisites are met	Faster after you have the commands ready
Bulk assignment	Manual, one number at a time	Supports scripts for many users at once
Error details	Shows generic error messages	Provides detailed error codes and logs

Now you can fix the assignment failure by checking the usage location, license, and emergency location. Start with the Teams admin center, and if that fails, move to PowerShell for more control. After assigning the number, test the user’s ability to make and receive calls. For future assignments, create a script that sets the usage location and license before the number assignment.