Why Direct Routing numbers don't show in the Teams admin center dropdown

If you're trying to assign a Direct Routing phone number from the Teams admin center and the number type dropdown shows no Direct Routing option, you're not dealing with a misconfiguration. The admin center only lists number types that exist in Microsoft's managed number inventory. Direct Routing numbers live outside that inventory, so they will never appear in that dropdown. You have to assign them with PowerShell.

The correct command

After running it, wait a few minutes and refresh the admin center. The number will appear against the user once it propagates. The command also enables Enterprise Voice on the user automatically, so you do not need to run a separate command for that.

If you share a base number across users with extensions, use this format

For extension-based lookups to work, the incoming SIP INVITE must carry the full number and extension, like this:

Why you should not use Set-CsUser for this

Licensing for Direct Routing

You do not need a Calling Plan license for Direct Routing. The required licenses are different. Here is what you actually need versus what you can leave out.

• Microsoft Teams Phone (formerly Phone System) This is the core license that enables the PBX features Teams Phone relies on, including Direct Routing. Without it, you cannot assign any phone number type to a user.
• Online Voice Routing Policy with Direct Routing routes This is not a license but it is equally required. The user must have an Online Voice Routing Policy assigned that contains PSTN usages and routes pointing to your Direct Routing trunk. Without this, the number assigns successfully but calls will not route.
• Calling Plan license is not required for Direct Routing A Calling Plan is only needed when you are using Microsoft-provided numbers. If you are using Direct Routing exclusively, you do not need it. Having one assigned will not block Direct Routing, but it may be why the admin center defaults to showing only the Calling Plan option in the dropdown.
• Teams Only mode The user must be in Teams Only mode for incoming calls to land in the Teams client. Assign the UpgradeToTeams instance of TeamsUpgradePolicy if your tenant has not already moved all users to Teams Only.

Verify these before assigning the number

The number will assign without these in place, but calls will not route correctly. Check them first.

Check whether Enterprise Voice is enabled on the user

EnterpriseVoiceEnabled should be True. If it is not, and you are managing the number online, running Set-CsPhoneNumberAssignment with the phone number assignment will set it automatically. If you only need to enable Enterprise Voice without assigning a number yet, run:

The user's OnlineVoiceRoutingPolicy must also have PSTN usages and routes that match your trunk configuration. If it is blank or pointing to the wrong policy, assign the correct one:

Optionally: upload your Direct Routing numbers to Microsoft's inventory

Uploading your Direct Routing numbers to Microsoft's telephone number management inventory is optional. If you skip this step, you can still assign numbers to users. Assigning a number automatically adds it to the inventory if it is not already there. Uploading manually first makes the numbers visible in the Teams admin center under Voice then Phone numbers before you assign them, which can be useful for larger rollouts where you want to plan assignments in advance.

To upload numbers via PowerShell:

To upload via the admin center, go to Voice then Phone numbers, select Add, choose From Direct Routing, and follow the order wizard. You can add numbers one by one, as a range, or by uploading a CSV. The CSV format requires a single column with the header TelephoneNumber and one number per row in E.164 format.

Microsoft reference: learn.microsoft.com — Enable users for Direct Routing