teams assign on premise phone number

teams assign on premise phone number

How To Automate Microsoft Teams Number Provisioning 

  • June 28, 2023
  • Microsoft Teams , Orto for Teams

When you need to provision phone numbers on Microsoft Teams, it’s no secret that the process is *less than great*. 

It’s not Microsoft’s fault and it’s not your fault. It’s simply the nature of the beast.  

Until now (spoiler alert), there has been no way to genuinely automate Microsoft Teams number provisioning.  

In this post, we’re going to introduce the three most viable ways to provision numbers on Teams. We’re massively biased about the third option as we’ve built a self-service portal with the purpose of automating Microsoft Teams provisioning. 

That said, we recognize some companies won’t need our product. So, in the interest of education, let’s run through all your options for Teams number provisioning. 

Microsoft Teams number provisioning options 

When it comes to number management and provisioning in Teams, you have three main options depending on your phone system connectivity. 

1 – Teams Admin Center (TAC) 

The Teams Admin Center provides some number management and provisioning features if you use either Microsoft Calling Plans or Operator Connect. In the Teams Admin Center, you can view a list of the numbers allocated to your Teams tenant by Microsoft or your chosen Operator(s). 

From the Admin Center, you can assign numbers to users and resource accounts using the web interface, or for automation purposes, PowerShell.  

Provisioning Microsoft Teams numbers in the Teams Admin Center

Benefits of using the Teams Admin Center for number provisioning include: 

  • Uses native Microsoft functions to provision, reducing manual errors  
  • Numbers stored in the same portal as your Teams user settings 
  • Can order more numbers from Microsoft directly in the TAC 
  • Can convert numbers between service and user types 

Disadvantages of using the Teams Admin Center for number provisioning: 

  • Must create your own automated provisioning scripts 
  • Not user-friendly for searching and filtering numbers 
  • No support for Direct Routing number management 
  • Can’t categorize numbers 
  • Can’t reserve numbers 
  • No built-in automation  

2 – Excel spreadsheet 

It seems bonkers that, in 2023, we’re still reliant on spreadsheets as a database of our enterprise phone numbers.  

Yet, enterprises still rely on these today as their primary register for their owned number ranges. 

If you use Direct Routing for your Teams phone system connection, you will no doubt be using an Excel sheet or SharePoint List to keep track of your numbers and assignments.  

Why?  

Because the Teams Admin Center doesn’t allow you to add your own numbers to its number management solution. 

Depending on how much you have thought about this, you may have created your own PowerShell scripts to find all numbers assigned to users in Teams and update your Excel sheet automatically.  

If not, then you (or your team) are doing this manually after each change, right?  

Or maybe not… 

Without an integrated and automated number management solution for Direct Routing, you are leaving your organization open to inefficiencies. It will take longer to assign numbers with outdated information. 

What if you are using all three connectivity methods?  

(Calling Plans, Operator Connect, and Direct Routing.) 

Your number management is all over the place. 

So, what is the alternative? 

3 – Number management solution from Callroute 

Using Callroute’s number management solution , you can add your Direct Routing numbers and synchronize your Calling Plan and Operator Connect number ranges directly from your Teams tenant. 

No matter what connectivity types you have, you can use our number management solution to provision and track your user numbers. 

If you use Microsoft Calling Plan and/or Operator Connect for your Teams phone system, you can easily add these ranges to Callroute by pressing the Sync Numbers button. 

Automatically sync numbers in Microsoft Teams

Synchronization takes only a few seconds, and we automatically group your numbers into ranges using their metadata received from Teams.  

This means all your numbers, whether they are contiguous or sporadic, are merged automatically together in a single range if they are from the same area code, city, and provider.  

Numbers that are already assigned to users and resource accounts are updated with their assignments so that you can easily see what number is assigned to a particular user. 

If you use Direct Routing for your phone system connection, you can add your ranges directly into the Callroute number management feature. When user synchronization is performed, numbers are updated with their assignment. 

Going further into number management, you can assign tags to numbers across ranges to make them searchable and assignable in different circumstances.  

Of course, you are also able to assign phone numbers to your users directly in the Callroute portal. 

With Callroute number management, you have all of the benefits of number management provided by the Teams Admin Center and none of the downsides.  

How to assign a phone number using Callroute number management 

Callroute number management is a 100% cloud SaaS solution with no software to install. You will need to authenticate Callroute to your Teams tenant, but that’s it.  

Once you have added and synchronized your numbers and users, you can start assigning numbers to your users. 

To do this, navigate to the Numbers page, search for a number, or select a number from a particular range. 

Searching for numbers when provisioning Microsoft Teams numbers

Press the cogwheel icon next to the number and then choose which user to assign the number to and press assign. 

Assign numbers to users in Microsoft Teams

That’s it. Sit back and watch the magic happen. 

How to assign a phone number and a voice routing policy to a user 

The previous section was the simplest of scenarios. But what if you also need to assign a specific dial plan and voice routing policy to a user? 

You can do this by creating a user persona that contains the dial plan and voice routing policy you want to assign. 

Adding Microsoft Teams policies to a user persona when provisioning Microsoft Teams users

Find the user from your user list and click the cogwheel icon. From the persona drop down, select the persona you just created. 

Assign numbers in Microsoft Teams

Select the number range to pick the next free number from. 

Now you will be able to choose what number to assign to the user. Once chosen, press Save. 

Sit back and wait for Callroute to apply those changes directly to the user in Teams. 

How to pre-select the right phone number for the user 

In the case where you want to assign a phone number from a particular segment of a number range to a user, you can use number tags and user personas together. 

First, tag the numbers in the segment you want to use. Call the tag whatever you want, e.g. “customer service”. 

Edit tags on phone numbers in Microsoft Teams

Next, go to the user persona you created, choose the number range the segment is part of, and select the tag you created, e.g., customer service, and press Save. 

Phone number assignment Microsoft Teams

Now, when you go to your user and select the user persona, the next free number from that segment is chosen for you and all you need to do is confirm. You can override the selection at this stage if you wish. 

Automate Microsoft Teams Number Provisioning 

But how do I automate this? 

Now you have added your numbers, created your tags and personas, you are ready to automate. 

Using Callroute’s auto-provisioning solution, you can use your Azure AD user attributes to create condition logic that will automatically apply a user persona to matching users, including phone numbers. 

Match users and phone numbers in Microsoft Teams

Our automated provisioning is an admin hands-off solution that runs automatically every hour.  

This means that you no longer have to spend hours every day assigning Teams policies and wondering what numbers you have available to assign to the next new starter. 

If you agree that number provisioning and auto-provisioning go hand-in-hand, try Callroute here .  

Some Other Articles You Might Like

Tips For Microsoft Teams User: How To Simplify Your Chats, Channels, and Notifications

Tips For Microsoft Teams User: How To Simplify Your Chats, Channels, and Notifications

Calling all users of Microsoft Teams! Ever wish you could be using Teams more productively? You’re not alone. But all the guides that tell you

Make Microsoft Teams Management Tasks Easier With Your New Favorite Tool

Make Microsoft Teams Management Tasks Easier With Your New Favorite Tool

When we talk about simplifying processes, what usually follows is an extended period of changes, new procedures, and pushback from every department.  But, when talking

How To Simplify Microsoft Teams Management Without Reinventing The Wheel

How To Simplify Microsoft Teams Management Without Reinventing The Wheel 

  • Number Management
  • Teams Policy Personas
  • Microsoft 365 Licensing
  • Manage Call Queues
  • Manage Team Membership
  • Migrate to Teams
  • Manage Teams Phone
  • Managed Service Providers

Book cover

Troubleshooting Microsoft Teams pp 75–146 Cite as

Microsoft Teams Phone (Voice) Configuration and Management

  • Balu N Ilag 3 &
  • Arun M Sabale 4  
  • First Online: 28 September 2022

446 Accesses

Teams brings together calling, meeting, chat collaboration, and apps, thereby helping users easily stay connected right in their workflow. Microsoft Teams provides calls (1:1 and group) and multiparty meetings with optimal audio/video quality. Apart from VoIP communication, Teams provides external calling (PSTN calling) through calling plans, Operator Connects, and Direct Routing. Teams (Microsoft 365) Phone System is Microsoft's technology for enabling call control and PBX capabilities in the Microsoft 365 cloud.

This is a preview of subscription content, log in via an institution .

Buying options

  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
  • Available as EPUB and PDF
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Author information

Authors and affiliations.

Tracy, CA, USA

Balu N Ilag

New Jersey, NJ, USA

Arun M Sabale

You can also search for this author in PubMed   Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

© 2022 The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature

About this chapter

Cite this chapter.

Ilag, B.N., Sabale, A.M. (2022). Microsoft Teams Phone (Voice) Configuration and Management. In: Troubleshooting Microsoft Teams. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-8622-7_3

Download citation

DOI : https://doi.org/10.1007/978-1-4842-8622-7_3

Published : 28 September 2022

Publisher Name : Apress, Berkeley, CA

Print ISBN : 978-1-4842-8621-0

Online ISBN : 978-1-4842-8622-7

eBook Packages : Professional and Applied Computing Professional and Applied Computing (R0) Apress Access Books

Share this chapter

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

  • Publish with us

Policies and ethics

  • Find a journal
  • Track your research

How to Sync Microsoft Teams Phone Numbers (LineURI) with Active Directory

Teams Phone Numbers (LineURI)

Do you have PSTN Calling in Microsoft Teams via Calling Plans, Operator Connect, or Direct Routing? Are you manually updating your users’ telephoneNumber attribute in your on-premises Active Directory every time you onboard a new user to Microsoft Teams Calling? In this article, I will show you how to sync Teams phone numbers with Azure Active Directory (AAD) and On-Premises Active Directory (AD) with an easy-to-use script. I’ll walk you through how to set it up and run it to save you time and headaches.

  • Microsoft currently has no built-in means to push a user’s Teams Calling phone number to AAD or AD directly. IT teams are left to figure out on their own how to sync Teams phone numbers with other applications.
  • To eliminate this hassle and make your life easier, we have developed a script that updates the telephoneNumber attribute automatically for all your users.
  • After some initial setup, you can download the script right in this article and, with some additional configuration, run it

If your organization is using Teams, you need your users’ Teams Calling numbers (LineURI) to be reflected in crucial business applications. Most of these programs pull your users’ numbers by syncing with AAD, although many legacy applications do continue to sync with AD.

Unfortunately, Microsoft currently offers no built-in solution to push a user’s Teams Calling number to AAD or AD directly. This is a huge hassle.

To their credit, they do help alleviate part of this problem with Azure AD Connect, which allows for one-way synchronization from AD to AAD (but not the other way around). But it adds no value until you manually update AD with the Teams Calling number.

Azure AD Connect still fails to solve the root problem as it does not completely bridge the gap between Teams Calling and AD/AAD.

Teams Phone Numbers in Active Directory

Our customers have repeatedly expressed their frustration about this, and I don’t blame them. It is painful to manually intervene after every Teams Calling user is onboarded or whenever a user’s number changes.

How to Sync Teams Phone Numbers (LineURI) with Active Directory

To eliminate this hassle, we developed an easy-to-use script (which you can download below) to bridge the gap between Teams Calling and AAD/AD. It connects to your Teams tenant, grabs the assigned Teams Calling numbers of all your users, and then updates the telephoneNumber attribute of those users in On-Premises AD. Azure AD Connect can then be used to push that same information up from AD to AAD – gap bridged!

What You Will Need

  • Microsoft 365 User Account with Teams Administrator Role: This account will be used to query your Microsoft Teams tenant and retrieve the assigned number of all your active Teams Calling Users.
  • On-Premises AD Service Account with Write Permission to a Search Base: This account will be used to update the newly onboarded Teams Calling Users’ telephoneNumber attribute in your On-Premises Active Directory.
  • Windows Machine: The script will need to run from a Windows machine with network access to both On-Premises AD and your Microsoft Teams tenant. It will also need to have the relevant PowerShell modules installed to support the commands executed by the script.
  • Our Script: The script will query your Microsoft Teams Tenant for all users with a Teams Calling number and write the value to the respective user’s telephoneNumber attribute in your On-Premises Active Directory.

How to Set Up the Script

Step 1: determine the search base containing teams calling users.

The AD Service account which will update the telephoneNumber attribute of your users will need write permissions.  To provide the most granular level of permission needed, you’ll want to identify the Search Base of your target users.

First, find the directory or sub-directory containing your Teams Calling users, right-click and select Properties.

Teams Phone Numbers

Select the Attribute Editor tab and find the distinguishedName attribute and click View.

Teams Phone Numbers

Take note of this value, it will be required to configure the script .

Step 2: Create On-Premises AD Service Account with Write Permission to telephoneNumber Attribute

Now, you’ll need to create the AD service account with the required write permission to the telephoneNumber attribute for users part of the Search Base identified in the previous section.

1) Connect to your On-Premises AD server via Remote Desktop.

2) Create a user.

3) Provide the user account with write permission to the telephoneNumber attribute for the OU your users are located in.

Right-click the OU which contains your Teams Calling users and select Delegate Control.

Teams Phone Numbers

Use the Delegation of Control Wizard to find and select the user created in step 2. Click OK , then click Next .

Teams Phone Numbers

On the Tasks to Delegate screen, select the 2nd radio button Create a custom task to delegate and click Next .

Teams Phone Numbers

You’ll then see the Active Directory Object Type screen. Select the 2nd radio button Only the following objects in the folder , then enable the User Objects checkbox and click Next .

Teams Phone Numbers

Finally, on the Permissions screen, enable the Property Specific checkbox. Under the Permissions list, enable the Write Telephone Number checkbox and click Next . On the next screen click Finish .

Teams Phone Numbers

Step 3: Create Microsoft 365 Admin Account with the Teams Administrator Role assigned

To create the required Microsoft 365 Admin account, you have 2 possible options:

Option 1 – Use the same account created for On-Premises AD

Recycle the same On-Premises AD account you created in the previous section by performing a manual sync between your On-Premises AD and your AAD. This will push the account to AAD and make it available for you to select and configure it from your Microsoft 365 tenant.

1) Connect to the windows machine from which you’ll be running the script.

2) Search for PowerShell from the Start Menu, right-click PowerShell, and Run as Administrator

3) Run the following command:

Start-ADSyncSyncCycle -PolicyType Delta

Note: If you encounter any issues running the command, consult this Microsoft knowledge base article .

Option 2 – Create a new Admin account directly in the Microsoft 365 Admin Center

Follow the walkthrough guide for Creating a PowerShell Account available here .

Step 4: Prepare Windows Machine from which the Script Will Run

You’ll need to run the script from a Windows machine that meets the following requirements.

  • Network Access to your On-Premises AD
  • Network Access to your Microsoft Teams Tenant
  • Active Directory
  • Microsoft Teams

How to install Microsoft Teams PowerShell Module

2) Search for PowerShell from the Start Menu, right-click PowerShell 7 (x64) and Run as Administrator Note: Make sure to select PowerShell 7, as this version uses the most recent cmdlets required by the script.

Teams Phone Numbers in Active Directory

3) Run this command:

Install-Module -Name MicrosoftTeams

How to install Active Directory PowerShell Module

Repeat steps 1 and 2 from above, then run this command:

Add-WindowsCapability -Name Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0 -Online

Note: If you encounter any issues running the command, consult this knowledge base article .

Download and Run the Script

☁️ Download Script

Import-Module ActiveDirectory Import-Module MicrosoftTeams # This script logs the results of the update operations to the console. # If needed, you can redirect these to a log file (e.g.: `.\script.ps1 6> .\results.log`). ####### Set the following variables $msTeamsUserName = '[email protected]' $msTeamsPassword = 'YOUR_PASSWORD_HERE' $adUserName = 'jdoe' $adPassword = 'YOUR_PASSWORD_HERE' $searchBase = 'OU=S8 Employee Accounts,DC=dev-stack8,DC=com' ####### function Create-Credential {    param (        $UserName,        $Password    )    $securePassword = ConvertTo-SecureString -String $Password -AsPlainText -Force    return New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $UserName, $securePassword } $adCredential = Create-Credential -UserName $adUserName -Password $adPassword $msTeamsCredential = Create-Credential -UserName $msTeamsUserName -Password $msTeamsPassword Connect-MicrosoftTeams -Credential $msTeamsCredential $voiceUsers = Get-CsOnlineUser -Filter {EnterpriseVoiceEnabled -eq $True} | Select UserPrincipalName, LineUri foreach ( $voiceUser in $voiceUsers ) {    $upn = $voiceUser.UserPrincipalName    try    {        $adUserToUpdate = Get-ADUser -Credential $adCredential -Filter "userPrincipalName -eq '$upn'" -SearchBase $searchBase        if ($null -eq $adUserToUpdate)        {            Write-Host "WARNING: Could not update user $upn - user does not exist in local AD" -ForegroundColor Yellow            continue        }        $phoneNumber = $voiceUser.LineUri.replace('tel:', '').split(';ext=')[0]        Set-ADUser -Credential $adCredential -Identity $adUserToUpdate.DistinguishedName -Replace @{telephoneNumber=$phoneNumber}        Write-Host "Updated user $upn with phone number $phoneNumber"    }    catch    {        Write-Host "ERROR: Something went wrong when trying to update user $upn - $PSItem" -ForegroundColor Red    } }

What the Script Does

The script will perform the following actions:

  • Connect to Microsoft Teams and gather all phone numbers (LineUri’s) for voice-enabled users (i.e. users whose enterpriseVoiceEnabled flag is set to true) via the Get-CsOnlineUser cmdlet
  • Get the LineURI of the user
  • Set the LineURI in AD via Set-ADUser

How to Configure the Script

Update the script to reference your account(s) and environment information.

  • Update the $msteamsUserName to the UPN of the Microsoft 365 Admin account with Teams Administrator role created in the earlier section [anchor link].
  • Provide the associated $msteamsPassword for the account.
  • Update the $adUserName to the samAccountName of the On-Premises AD service account created in the earlier section [anchor link].
  • Provide the associated $adPassword for the account.
  • Provide the $adSearchBase identified in the earlier section.

You’re ready to run the script!

Running the Script

Now that you’ve identified your Windows machine and fulfilled all the requirements needed for the script to run, we can run the script.

1) Search for PowerShell from the Start Menu, right-click PowerShell 7 (x64) and click Run as Administrator.

Note: Make sure to select PowerShell 7, this version uses the most recent cmdlets required by the script.

2) From the PowerShell terminal, use the change location command to locate the script. In this example that would look like this:

cd C:\Users\s8support\Desktop\ziroscript\

Teams Phone Numbers in Active Directory

3) You can now run the script. In this example, the name of the script is “ script ”, so that would look like this:

.\script.ps1

Although the script will log the results of the update operations in the console, you can also redirect these to a log file by running the script like this:

.\script.ps1 > .\results.log

Teams Calling script

Please note that the script will scan all your Microsoft Teams Users to determine which have a LineURI configured and update their telephoneNumber attribute in On-premises AD. The amount of time required for the script to run will vary depending on the number of users in your environment.

In this example, the script identified 3 users with LineURI’s which were not set in On-Premises AD and updated the telephoneNumber attribute of those users with the relevant Teams Calling LineURI.

Teams Phone Numbers

Notice the warnings about users which were found in the Microsoft Teams tenant, but that do not exist in On-Premises AD. You can ignore these as they are not valid targets of the script.

And that’s it – you’re all done!

You Know How to Sync Teams Phone Numbers with Active Directory. What Now?

Now that you know how to sync Teams phone numbers with AD/ADD, you can spend less time manually updating the telephoneNumber attribute and more time on the work that really matters.

If you have any questions about the script or hit any snags, don’t hesitate to reach out! Our UC experts can answer any of your Teams Calling questions.

Looking for even more simplicity? Our no-nonsense software empowers your helpdesk so you can offload even more of those tedious routine MS Teams tasks without worrying about complicated templates or accessing the MS Teams Admin Center. Click here to discover how ZIRO Provisioning for Microsoft Teams can make your life easier.

Other Blogs You Might Enjoy

Ziro Logo

How to Convert Cisco Phone to MPP and Register with Microsoft

Teams-Voicemail-Not-Working

Handset Notifications For Microsoft Teams Voicemail Not Working 

Microsoft Teams Calling Specialist

ZIRO Awarded Microsoft Teams Calling Specialist Certification

Managing Resistance to Change

5 Steps to Managing Resistance to Change

Ready to take your unified communications from headache to hassle-free.

No throwing darts at proposals or contracts. No battling through the back-end. No nonsense, no run-around.

Schedule a call

teams assign on premise phone number

Microsoft Teams Phone

Teams Phone—more than a cloud phone system. Experience smart communication and seamless collaboration with the only calling solution native to Teams.

Flexible and easy to use

Communicate and collaborate effortlessly across devices and spaces with intuitive, seamless calling.

Intelligent and connected

Create meaningful engagements with intelligent capabilities that connect your business and increase productivity

Secure, reliable, and easy to manage

Save time and enjoy peace of mind with a reliable and secure calling solution that is easy to manage.

Learn how Microsoft helped customers achieve more efficient and effective communication, lower costs, and help IT teams save time in the commissioned Forrester study: The Total Economic Impact™ Of Microsoft Teams Phone. 1

According to new research by GigaOm, Microsoft has the highest average score for voice quality—with network and server uptime at par with competitors—and offers competitive service level agreements with generous service credits. 2

teams assign on premise phone number

Simplified, enterprise-grade calling in Microsoft Teams

Basic call control.

The Call tab in Teams showing ongoing calls, other delegates, history and more.

Connect with your team, customers, and partners with voice and video calls from a Teams chat, the Calls app, or the public switched telephone network (PSTN).

A call being answered in Teams.

Make and answer calls

Make one-on-one or group calls directly from a chat or use the dial pad to call a phone number.

Calls being merged in Teams.

Merge calls

Bring someone else into your one-on-one or group call with the merge function.

Suggestions for where to transfer a call being displayed in Teams.

Transfer and ring back

Transfer a call to a colleague and select  ring back  if there’s no answer.

Two options displayed in Teams to either add a new device to a Teams meeting or transfer a Teams meeting to this device.

Transfer calls between devices

Whether on the go or at a desk, at home, or in the office, transfer calls from one device to another while on a call.

Phone history and a voicemail being viewed in Teams.

Access your voicemail

Access, listen to, and review your voicemails using playback controls, voicemail summary, and transcripts.

A transcript of a past call being viewed in Teams.

Transcribe your calls

Transcribe calls no matter where you are. Focus on what’s being said, knowing you’ll be able to go back to the recording and transcription afterwards.

The Apple CarPlay view of a call in progress on Teams

Call on the go with Apple Carplay

Join calls and meetings using your vehicle’s built-in controls or hands-free with Siri.

Advanced call control

Call group information being displayed in Teams.

Meet the needs of your evolving business with modern phone capabilities.

The process to create a call queue in Teams.

Auto attendant

Let people call your organization and navigate a menu system to speak to the right department, call queue, person, or an operator.

The process to create a call queue in Teams.

Call queues

Route callers to people in your organization who can help with a particular issue or question.

The display showing how to add a voice-enabled channel in Teams.

Voice-enabled channels

Collaborate and share information within the channel while taking calls in the call queue.

Side-by-side windows of a customer call in Teams and their customer records.

Automatically display information via web browser window when an incoming call is answered by a call queue agent.

Copilot in Teams Phone generating summaries and next steps from a call transcript.

Copilot in Teams Phone

Add generative AI capabilities to phone calls to get real-time summarization and insights.

PSTN calling

A list of a user’s ongoing and historical calls in Teams.

Make phone calls using PSTN connectivity options combined with the Teams Phone system.

A world map with pins on North America, Europe, Africa, Asia and Australia.

Operator Connect

Manage your PSTN calling and session border controllers (SBCs) with participating operators in the Microsoft Operator Connect program.

Desktop and mobile displays of an incoming call in Teams.

Teams Phone Mobile

Seamlessly integrate your users' mobile identities with Teams. Assign a single number and implement a solution that works across network and devices.

A map with pins placed all over the world.

Direct Routing

Connect your SBCs to Teams Phone to use your own PSTN operator.

A world map with pins on North America, South America, Europe, Asia, Africa and Australia.

Microsoft Teams Calling Plans

Take advantage of this all-in-the-cloud solution with Microsoft as your PSTN operator.

Contact center

Five people in a meeting room participating in a Teams video call being displayed on a wall while a presentation is being displayed on a large screen.

Support customer interaction work streams, using Teams as the hub for internal and external customer connections.

A person wearing a headset working at their desk with a laptop connected to two monitors and a keyboard.

Microsoft Digital Contact Center Platform

Quickly set up phone systems for agents to assist customers on a scalable platform built, owned, and operated by Microsoft.

A person sitting at their desk wearing a headset participating in a Teams video call being displayed on one screen and looking at data on another.

Contact center partner integrations

Use your existing contact center solution together with Teams Phone for a more connected contact center experience.

A person standing at a desk wearing over-the-ear headphones and using a laptop connected to two desktop monitors.

Experience instant, high-quality audio and video communication everywhere you work with seamless transitions across devices.

A desk phone with a Teams video display.

Desk phones and Teams displays

Make and receive calls from devices certified for use with Teams, including intuitive screens and controls to enhance the Teams calling experience.

A person wearing a headset and using a tablet.

Choose from a variety of headsets certified for Teams—wired, Bluetooth, over the ear, or on the ear—to suit every preference or need.

A hand reaching to press a button on a Teams speakerphone device.

Speakerphones

Connect with USB- or Bluetooth-enabled speakerphone options to easily scale audio based on the room size and number of meeting participants.

Add your Microsoft Teams plan today

Microsoft teams phone standard.

Originally starting from $8.00 now starting from $8.00

$8.00 $8.00

(Annual subscription–auto renews) 4

Cloud-based phone system

Make and receive voice and video calls over PSTN or an internet connection

  • Join calls from a range of devices and seamlessly transfer calls between devices

Add operator PSTN service with Operator Connect or Direct Routing

Combine mobile calling plans with Operator Connect Mobile

99.99% uptime SLA

Teams Phone with Calling Plan (country zone 1 - US)

Originally starting from $15.00 now starting from $15.00

$15.00 $15.00

Price includes communication taxes and fees. 5

Everything included in Teams Phone Standard

Phone number and PSTN service from Microsoft

Inclusive of domestic calling 6

Teams Essentials and Teams Phone with domestic calling

Originally starting from $20.00 now starting from $16.00

$20.00 $16.00

Price includes communication taxes and fees . 5

Includes Teams Phone with Calling Plan and Teams Essentials, featuring:

Unlimited meetings and messaging

File sharing, tasks, and polling

10 GB of cloud storage per user

Microsoft 365 E5

Originally starting from $57.00 now starting from $57.00

$57.00 $57.00

(Annual commitment)

Productivity apps and services

Enterprise-grade security and compliance

teams assign on premise phone number

Save up to 33% when you buy Teams Essentials and Teams Phone together

Save money and boost collaboration with Teams Essentials plus Teams Phone—now starting at  $8.00 per person per month. Improve workflows by simplifying communications channels with chat, video, file sharing, and calling. 10

What customers say about Teams Phone

AHW

AHW uses Teams Phone to transform the way it communicates with customers and improve its selling process.

REED

Reed uses Teams Phone to untether workers from their desks, improving productivity and morale.

ISUZU

Isuzu Motors Limited

Isuzu Motors Limited drives workplace flexibility and efficiency with Teams Phone.

Custom pricing available

Add Teams Phone to your current Microsoft 365 plan to get the calling features every organization needs. Contact Sales for custom pricing.

See rates for where you want to call

Get a detailed list of the stndard subscription and pay-per-minute rates for your agreement by country or region and by currency. Communications Credits rates are for charges not included in your subscription plan. 7

Select the country or region for your organization’s billing address.

Select currency

Select your rate type. 8

Frequently asked questions

What is microsoft teams phone.

Teams subscriptions include Teams Phone and enable calls from one Teams app to another. Making and receiving calls to and from landlines and mobile phones on the PSTN in Teams is available with an add-on such as Teams Phone Standard or Teams Phone with Calling Plan or is included in Microsoft 365 E5. These options provide a cloud-based phone system in Teams with features such as hold, blind and safe transfers, and reporting features for professionals who manage calling solutions.

How does Teams Phone work?

It replaces traditional PBXs and enables key calling capabilities with a cloud-based call control system that provides the overall telephony workload for Microsoft Teams.

What is a Microsoft Teams Calling Plan?

A calling plan provides customers with a primary phone number and calling minutes to make and receive phone calls. A domestic calling plan is included in Teams Phone with Calling Plan or can be added onto Microsoft 365 E5. 9

What is Direct Routing?

Direct Routing helps you connect a supported, customer-provided SBC to Teams Phone. With this capability, you can configure on-premises PSTN connectivity with Microsoft Teams client.  Learn more .

What is Operator Connect?

Operator Connect is another option for providing PSTN connectivity with Teams Phone. For more information about Teams voice solutions and PSTN connectivity options, see  Plan your Teams voice solution  and  PSTN connectivity options .

Can I use my existing phone numbers?

Yes. You can transfer your phone numbers from your current service provider. After you port your phone numbers over, Microsoft will become your service provider.

Can I bring my own calling plan?

Yes, customers can work with their Microsoft partner to bring their own calling plan. A configuration called  Direct Routing  allows customers to connect voice trunks directly from their network to Teams or interconnect other telephony entities, such as call centers or analog devices.

Microsoft Teams Phone Standard is a standalone subscription (without a calling plan) that is specifically designed for this situation.

What phones are supported?

Devices certified for Teams provide a seamless Teams experience on desk phones, conference phones, and meeting room systems.  Learn more about Microsoft Teams-certified devices . For available devices go to the  Microsoft Teams Devices Marketplace . 

Teams supports a portfolio of desk phones for customers requiring a traditional phone experience.

To deliver a high-quality and reliable Teams experience on phones, Microsoft is partnering and actively working with Yealink, Crestron, Lenovo, Polycom, and Audiocodes to develop and certify a wide portfolio of desk phones and conference room audio devices. To get the latest information on Teams devices, go to  Teams Devices Marketplace .

What is the difference between the offers for small and medium-sized businesses and enterprises?

There are two offers for small and medium-sized businesses:

  • Teams Phone with Calling Plan combines a phone system and a domestic calling plan.
  • Teams Phone Standard without a calling plan provides a phone system that requires a calling plan from a service provider.  

For enterprises: A phone system and audio conferencing are included in Office 365 E5 and Microsoft 365 E5. A Teams calling plan can be added or it can all be purchased separately. Enterprises can also add Teams Phone with Calling Plan as an add-on to qualifying subscriptions.

Teams Phone with Calling Plan is currently available in 35 markets.  See country and region availability . A phone system is available in more than 120 countries, everywhere Microsoft 365 is available. 

The product features and experience are the same across the offers for small and medium-sized businesses and enterprises. Pricing and availability may differ.

What is Microsoft Teams Phone with Calling Plan?

A Teams Phone with Calling Plan package is a cloud-based phone system that enables users to make, receive, and transfer calls to and from landlines and mobile phones on the PSTN in Teams. Teams Phone with Calling Plan includes a phone system and a domestic calling plan— available in 35 markets .

Who is Teams Phone with Calling Plan intended for?

Teams Phone with Calling Plan is designed for small and medium-sized businesses and enterprise customers using Microsoft 365 that are seeking a modern phone system. Teams Phone with Calling Plan can be added onto Microsoft Teams Essentials or Microsoft 365 subscriptions that include Microsoft Teams. Qualifying plans include Microsoft 365 Business Basic, Business Standard, Business Premium, E3, or A3; Office 365 E1, E3, A1, or A3; and  Teams Essentials .

What’s included in Teams Phone with Calling Plan?

A Teams Phone with Calling Plan includes a phone system and a domestic calling plan.  Learn more .

A prepaid wallet (known as  Communications Credits ) is available for adding toll-free, additional minutes, and other pay-per-minute charges.

An optional international calling plan that includes 600 minutes per person per month can be purchased as an add-on.

Where is Teams Phone with Calling Plan available?

Businesses operating across 35 markets: Australia, Austria, Belgium, Canada, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hungary, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Mexico, Netherlands, New Zealand, Norway, Poland, Portugal, Puerto Rico, Romania, Singapore, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, United Kingdom (UK), United States (US). Go to this  Microsoft Teams documentation  page to learn how to plan, set up, and use Teams Phone with Calling Plan.

Where can I share thoughts and ideas?

Got a suggestion? We’d love to hear from you. Here are three ways to share feedback:

  • Microsoft Teams desktop app—Select Help on the bottom left. Then select Report a problem or Suggest a feature .
  • Microsoft Tech Community —Ask questions and join discussions.

Learn more about Microsoft Teams

teams assign on premise phone number

Collaboration

Empower your team to collaborate seamlessly with file sharing and project management on one centralized platform.

teams assign on premise phone number

Voice over Internet Protocol (VoIP)

Elevate your business communication with the VoIP feature, enabling crystal-clear voice calls and real-time collaboration.

teams assign on premise phone number

Private Branch Exchange (PBX)

Transform your organization's telephony system with PBX capabilities, providing a reliable and flexible solution for managing internal and external calls efficiently.

teams assign on premise phone number

Business phone systems

Enhance your company's communication infrastructure with comprehensive business phone systems, enabling seamless connectivity and advanced call management features.

teams assign on premise phone number

Unified communications as a service (UCaaS)

Streamline your communication channels with UCaaS, an all-in-one solution that combines voice, video, and messaging capabilities, empowering your team to collaborate effectively from anywhere.

teams assign on premise phone number

Experience enhanced productivity and seamless communication that integrates your Teams business phone system directly into the platform.

teams assign on premise phone number

Enterprise-grade calling

Take your organization's calling capabilities to the next level with the enterprise-grade Teams calling feature, delivering high-quality voice and video calls, advanced call routing, and robust security measures.

teams assign on premise phone number

Voice and video calling

Connect face-to-face with colleagues, clients, and partners through the video calling feature, enabling immersive virtual meetings and fostering collaboration across distances.

Get started with Microsoft Teams today

teams assign on premise phone number

  • [1] The Total Economic Impact™ Of Microsoft Teams Phone, a commissioned study conducted by Forrester Consulting, December 2022.
  • [2] GigaOm, Hands-On Field Test: Voice Services Comparison, Competitive Voice Services Reliability Benchmark v1.0, Dana Hernandez, September 13, 2022.
  • [3] Cancellation policies for paid subscriptions may vary based on factors such as your customer status, your product, and your domain selections on Microsoft. You may cancel your subscription at any time in the Microsoft 365 admin center. Certain subscriptions may incur a cancellation fee.  Learn how to cancel your Microsoft 365 subscription . When a subscription is canceled, all associated data will be deleted.  Learn more about data retention, deletion, and destruction in Microsoft 365 .
  • [4] The Microsoft Teams Phone with Calling Plan service component—domestic calling plan—is sold inclusive of all required taxes and fees, including 911 fees and other transactional taxes that typically apply to communication services in the US. The price includes these taxes and fees. The phone system component is sold tax-exclusive and any applicable sales tax will appear as a separate charge in the US.
  • [5] Domestic Calling Plan includes 3,000 minutes for the US and UK, and 1,200 minutes for the rest of world.
  • [6] Rates listed (for tenants provisioned in the US) do not include tax. International dial-out rates are subject to change monthly, and individual rates are not locked during the term of your agreement. Changes will be minimized where possible to avoid disruption while ensuring prices remain competitive with local market rates and conditions.
  • [7] Download standard subscription or pay-per-minute rates. Standard subscription rates include dial-in calls to toll-free numbers, and dial-out calls. Pay-per-minute rates include dial-in calls to toll numbers, dial-in calls to toll-free numbers, and dial-out calls.
  • [8] Availability of audio conferencing and calling plans varies by country and region.  See supported countries and regions  for more information.
  • [9] The discount offer is available to new and existing customers who license a 12-month Microsoft Teams Essentials and Microsoft Teams Phone bundle (with or without a Microsoft Teams calling plan) through Direct and CSP direct channels between July 17, 2023, and July 1, 2024. This promotion is valid in the United States, Canada, and the United Kingdom. This annual subscription automatically renews and is subject to recurring billing at the regular price and selected term. Customers can cancel at any time to stop future charges. Microsoft reserves the right to cancel, change, or suspend this offer at any time without notice.  Learn more about recurring billing in the U.K .

Follow Microsoft Teams

Twitter logo

teams assign on premise phone number

UC Status – The home of UC News, Reviews & How-to's

Blog , How-to , Microsoft Teams , PowerShell , UC News

How to: Assign a Direct Routing Number to an Auto Attendant or Call Queue in Microsoft Teams Phone System

teams assign on premise phone number

Hello Readers, hope you’re well.

Another really quick post for you.  There was a Tech Community post today regarding updates to Auto Attendants and Call Queues.

The updates introduce new capabilities, including;

  • Centralized holiday tables that can be reused across apps. You will find it under Org wide settings
  • You can assign Direct Routing numbers to Auto Attendants and Call Queues (as of today DR with AA/CQ support Teams users only)
  • You can assign a hybrid number to AA/CQ (currently in preview)
  • You can assign Multiple numbers to an auto attendant or call queue
  • Round Robin routing option is introduced in call queues

They also list some new features coming soon:

  • Transfer out to PSTN from auto attendant and call queues
  • Extension dialing from auto attendant
  • Voicemail shared mailbox for auto attendant and call queues

This update comes just a few days after the control panels for AA & CQ moved from the Skype for Business Admin Centre to the Teams Admin Centre.  See my recent post here .

The focus of this post is the ability to use telephone numbers from your Direct Routing setup for your Teams Auto Attendants and Call Queues.

What do you need?

  • You need to have Direct Routing set up using your own SBC or using a Direct Routing service from a DRaaS provider.
  • You need an unused telephone number
  • You need a Resource Account (licensed with E1 and Phone System… for now*)
  • You need an Auto Attendant or Call Queue

You can set up a new Resource Account using the Teams Admin Centre or using PowerShell.

From TAC, expand Org-wide settings -> Click Resource Accounts -> New Account

new resource account 1

This opens the new resource account form.  Give it a Display Name, User name and choose a domain.  Then decide if it will be used for an Auto Attendant or Call Queue.

new resource account

If you want to do this using PowerShell, run the following

New-CsOnlineApplicationInstance -UserPrincipalName [email protected] -DisplayName “Resource Account – DR Num” -ApplicationId “ce933385-9390-45d1-9512-c8d228074e07”

ApplicationId “ce933385-9390-45d1-9512-c8d228074e07” is the same as choosing Auto Attendant in the TAC.  If you want to use it for a Call Queue, the ApplicationID is “11cd3e2e-fccb-42ad-ad00-878b93575e07”.

One you have created your Resource Account, it should display in the TAC

new resource account 2

You’ll also need to assign this Resource Account an E1 and Phone System add-on license because you’re assigning it a number.  Microsoft did initioally say that they were working on a new license type for Resource Accounts that needed telephone numbers.  I had assumed it would have a charge.

They also announced this:

  • …You will need to use a user-based licensing temporarily until an app cost-free license model is available (work in progress)

For the next bit, I’ll assume you have an Auto Attendant.  I’ll do another post on the creation of an AA.

Now assign your Resource Account to the Auto Attendant you created.

assign Resource Account to AA

Now you need to assign your telephone number.  Since Office 365 isn’t aware of your on-premises number range, you need to do this next bit using PowerShell.  Run the following.

Set-CsOnlineApplicationInstance -Identity [email protected] -OnpremPhoneNumber +442077891234

Assign a DR Number to Resource Account

Shortly after, you should see your Resource Account in the TAC, with your phone number

see number assigned in TAC

That’s all folks!

Update :  I’m getting a lot of reports from people that they’re unable to route calls to their Auto Attendant or Call Queue that uses the resource account with the direct routing phone number.  They say that they get a “404 not found” in their SBC traces.

Like many other problems with Teams admin, the solution, it seems, is time.  If you get this, just wait a while and it should start working.  This could be as little as 30 minutes or as much as several hours.

The moral of the story is, if it doesn’t work, wait a while and try again.

If this has happened to you, please leave a comment with an estimate of the time it took to start working.  Of if you have a different experience, please let us know.  We’d love to hear your story.

Hope that was useful.  Stay tuned for more.

If this or any other post has been useful, why not take a moment to like and share. Thanks

  • Share to Teams

112 thoughts on “ How to: Assign a Direct Routing Number to an Auto Attendant or Call Queue in Microsoft Teams Phone System ”

Add Comment

  • Pingback: How to: Assign a Direct Routing Number to an Auto Attendant or Call Queue in Microsoft Teams Phone System – JC's Blog-O-Gibberish
  • Pingback: The New Microsoft Teams Auto Attendants & Call Queues Part 2

Thanks for the cross links and mention Tom 😊

Did you manage to get this to route successfully? We are getting a 404 not found when trying to reach the numbers assigned to these queues.

Like Liked by 1 person

Never mind, it was a case of “just wait longer”

Out of curiosity, how long did you wait before it started working? I’ve had a lot of questions about 404 not found. I’d like to update the post. Thanks

Our customer tenant took 2 1/2 hours, our own tenant (same region) took approximately 30 minutes.

Thank you Sean

Hey Randy, have you done much testing on this?

We are unable to route a call to users in a call queue if the call lands on an Auto Attendant. We get the following error in the client logs:

ms-diagnostics: 42004;reason=”Unexpected error occured routing the request”;source=”ME10R04RFE06.INFRA.LYNC.COM”;Cause=”ErrorRetrievingNumberFromBVD”;appName=”BusinessVoiceRouting”

This looks suspiciously like the BYO DDI is not being replicated to some application causing the calls to fail.

Have you seen this before?

Are the recipients EV enabled and do they have the Phone System license?

Randy Chapman ________________________________

Hi, I had this issue useing AA with resource account and a phone number series. Getting the 404 error with reason code =111. I have been working together with Microsoft support for about 3 weeks now. First I was thinking sync issues. But it’s not. Have done recreated of the AA and CQ and for the resource account aswell. Has proper license (has only E5). Tried all the trick in the book, and today Microsoft support tells me this. I would like to inform you that the User (subscriber) phone numbers cannot be assigned to a resource account. Only service toll or toll-free phone numbers can be used. Please find the below URL for the Microsoft Article: https://docs.microsoft.com/en-us/microsoftteams/manage-resource-accounts

I think they are looking at this from an Calling plan perspective and not a Direct Routing perspective.

Hey Kai. I had a problem with one of mine too. Took them 10 days to fix. I asked for a reason and whether it was likely to happen to my next attempt

“Our engineers tried to force a sync multiple times but some of the attributes of the affected phone number was not syncing in our Business Voice Directory (BVD). One of our engineers identified that the cookie for the service instance which the tenant lives on seems to not have been updated to include the newer attributes. The said cookie was updated on the back end to sync the new attributes. BVD is now in sync with the new attributes which resolved the issue.   This is something that rarely happens and I don’t think this will affect the other phone number that you are going to port to your SIP provider. If in case this happens again we can refer to this case/incident to resolve the issue much faster. We cannot guarantee a 100% that we will not encounter a similar issue in the future but with the information that we have gathered during this incident will definitely help in preventing this kind of issues in the future.”

Hi Randy, thanks for your answer. But what about they say that Resource Account only support service numbers? Either Toll or Toll-free. This must as how I see it must be regarding to Calling plan who is not here in Norway 🙂

The article they liked to says direct routing numbers can be assigned to resource accounts. They just need E1 or better and Phone System. This is what went live a couple of weeks ago. Unless they are pulling back support for this feature because of all of the problems, I don’t know why they would say this. As you said, if you can’t buy calling plans, you can’t obtain service numbers. So they need to support this and make it work consistently.

Exactly the same story here: i can create resource accounts, I can assign OnPrem PSTN numbers. It’s only not possible to call them using our Direct Routing SIP Trunk. I keep getting a 404 Error. I have a ticket open now for 3 weeks now.

The problem is visible like this: in the Teams Admin Center, when editing the Auto Attendant, I don’t see any Phone number next to the Resource account. In the menu ‘Resource Accounts’ under ‘Org-Wide settings’, I do see the number next to it. So it seems like the number is succesfully assigned, but the link with the auto attendant itself is not there.

Same problem I had. Hopefully you can give your assigned engineer my resolution notes and they can fix it for you.

Thanks, did that. Fingers crossed.

Thanks for the pingback

Does “You can assign a hybrid number to AA/CQ (currently in preview)” refer to Skype CCE? We have not been able to get this to work via CCE. Getting error 480 Temporarily Unavailable between the CCE Mediation and Audiocodes SBC.

No. Only for use with Direct Routing which only works with Teams calling.

I think you will soon be able to set up hybrid numbers and hybrid AA/CQ with SfB server. But not with CCE

Other bloggers are stating the “hybrid number to AA/CQ (currently in preview)” is CCE. Are you stating that it actually refers to Skype for Business Hybrid and that it is in private preview?

The only point to CCE is to use on prem call handling for users homes in Skype online. This is because Direct Routing isn’t supported for users that aren’t in TeamsOnly mode.

I think if it is possible to assign the cloud AA/CQ an on prem number it would be from the hybrid application endpoint cmdlets https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/configure-cloud-auto-attendant which is an on prem cmdlet used for creating on prem resource accounts for cloud AA

My post is specifically about using Direct Routing numbers for Cloud Resource Accounts. No on prem Skype or CCE needed.

I don’t know if the hybrid app instance cmdlet exists in CCE. Or whether it’s just SfBS19

I hope I’ve cleared that up?

Well somewhere between 24-48 hours it all of sudden started working with a CCE number so it looks like it just takes a long time as stated. Of note, Premier support did not even pick up our Premier Support case for 12 days on a Severity B. The TAM stated the team is so backed up that there would be a week wait to get it assigned. There must be a lot of pain out there.

Glad it was just a replication thing and finally started working for you.

To be clear, did you use the online application instance? Or the hybrid one? I want to add that to my post regarding CCE and credit you, if that’s ok.

Also, can’t believe support is so backed up. But I can tell you there are a lot of people trying out this DR number stuff. And not knowing up front that you only need to wait 4-48 hours for it to work doesn’t help anyone. Plus, there are still people having problems even when it starts working. Maybe it wasn’t tested enough in private preview/TAP. Because surely these things would have been discovered and ironed out before GA.

The problem of the number not showing up next to the AA has been resolved. (I don’t know yet if this is thanks to your information I gave them or something else). Unfortunatelly, the ‘SIP/2.0 404 Not Found’ error persists. We still cannot call this AA using our Direct Routing SIP trunk, it is also not working directly from a Teams user (which I suppose will be completely processed within the Teams backbone). So at this point, I still seems like this On-Prem telephoneNumber feature is broken. Ticket is still open.

I moved my E1 and Phone System licences to a new resource account and then assigned a number. I assigned the resource account to an existing auto attendant and the Number showed up in the TAC immediately.

Hope your issue gets resolved soon.

Having read this blog thought i might give a little inside baseball on this weird 404 issue we all seem to be having.

I’ve raised a case with MS and spoken with a few engineers, they have admitted they have a known issue with the Business Voice Directory in Azure.

Some tenant’s resource accounts and the associated call queues/AAs that are created through the admin console don’t get pushed to this directory and as such the teams front ends don’t know where to send the call!

I’m working with them to find a workaround until they fix this issue.

Thanks Alex. I created one yesterday In PowerShell and then assigned the number and it showed up in the TAC immediately.

So do you think this is just for Resource Accounts set up in TAC?

It looks to be any resource account where you then assign a direct routing number.

As a test i created a new resource account and queue with a domestic calling plan via TAC, then assigned a service number with the Set-CsOnlineVoiceApplicationInstance -Identity [email protected] – TelephoneNumber +44123456789 command.

This works fine, so my guess is when you go to assign a number to a queue/aa if Microsoft doesn’t have a record of that number (ie it isnt a service number they have supplied), for some reason it doesn’t sync it into the business voice directory. Again this only appears to effect some tenants!

I have passed back to MS to see what they can advise.

Thanks for testing and confirming.

Basically, what is happening is that numbers need to be added to their Business Voice Directory. This takes time. Sometimes a couple of hours and sometimes days. Sometimes it needs some coercion by Microsoft to remove blockers (like in my case).

I heard that Microsoft is adding the ability to manage phone numbers, including DR and hybrid numbers, to Teams and the Teams Admin Centre. I’m thinking it will be a little like the unassigned number service in SfB, where you declare all of your DDI ranges so Teams knows about them, and more importantly, adds them to the BVD. Maybe in advance of needing to use them.

It is clear that this didn’t get nearly enough testing in private preview and TAP. Definitely wasn’t ready for GA when it was released.

I seem to be able to get the AA answering from my direct number, but there is no transfer to any other, legitimate user from the dial-by-name AA. After “transferring your call to xx” I get a Sorry I couldn’t help, please call back later, goodbye” message.

I’ve seen problems with Transfer from the AA to a user or CQ. Can be caused by an issue with config or code on the SBC. Basically not receiving the right response and sending bye.

What SBC are you using?

Thanks for the reply, and all the other messages on here. It is audiocodes, and I’ve been working with vendor today. It does have to do with the refer and secondary invite having a different from uri. Manipulation rules don’t seem to address it. I’ll try the recommendations I see below. If i have a successful transfer, I’ll post the config details.

Like Liked by 2 people

That’s great. Thanks John. Maybe I can turn it into a separate post. Seems like the fix deserves more than a comment on a blog. It goes without saying I’ll credit you.

Hi, I’m a college of Kai Stenberg. We discovered (by accident) that transfer from Teams user that first answered a AA/CQ call, start working when we:

1. Disabled voice mail for teams users (per user) 2. Granted all users voice policy: AllowCalling. 3. Configured AllowCalling as below:

Identity : Tag:AllowCalling Description : AllowPrivateCalling : True AllowVoicemail : UserOverride AllowCallGroups : True AllowDelegation : True AllowCallForwardingToUser : True AllowCallForwardingToPhone : True PreventTollBypass : False BusyOnBusyEnabledType : Disabled

I think PreventTollBypass = false is important, even though is has nothing to do with transferring AA/CQ calls to other users. We was not able to use Global policy even when we configured global policy with the same properties as for AllowCalling.

Think I had this. Could be something to do with a REFER in sbc trace and that there is some new IP adress from Microsoft

Yep. If you look at the trace on the SBC you should see a bye just after the attempt at transfer.

Saw some new ther in the 13.x.x.x/24 range uswest and euno we never seen before

We also have this problem. It seems our AudioCodes SBC does not handle the REFER correctly. The Direct Routing is set up following the guidelines of AudioCodes which should comply to the needs of Microsoft. Completely stuck at this point now.

The vendor should be able to help if you send them the trace. They just need to reverse engineer the fix.

Do you have specific information about this fix so I can pass it to them?

I don’t unfortunately. Not for AudioCodes

What is the number of DSP licenses you have on the Audiocodes sbc. I guess its 0 or 2. Try this:The GOOD NEWS is that transfer work after we uploaded the PRT .dat file and set the SBCPerformanceProfile = 2. Then reboot the Audiocodes sbc

hi, in the license tab we see ‘DSP channels: 52’. What is the PRT.dat file? Version from our SBC is: 7.20A.250.003

Hi, 7.20A.250.003 is the version MS has certified. There is a newer version that is out who is 7.20A.250.256 who we have btw. PRT.dat is the The Prerecorded Tone (PRT) file contains user-defined prerecorded tones that can be played by the device. You will find information in the Auxilleries files its prerecordedtone files. We got this tip from Yair Fanash at the audiocode support. Check this out: https://www.manualslib.com/manual/921870/Audiocodes-Mediant-1000b.html?page=581 If off now for one week on vacation and good luck.

Thanks for all your advice Kai. Have a great vacation

Also, we have a Virtual Edition, so I think that’s why I don’t find this performance profile. The underlying VMWARE platform always runs on the highest performance profile..

  • Pingback: New License Available for Microsoft Teams Resource Accounts

Does this allow you to use Audio Conferencing via our Direct Routing (i.e. using our own numbers) or are we still forced to buy Microsoft’s Audio Conferencing add-on?

Audio Conferencing is still just Microsoft numbers. But you get numbers all over the world along with the license. So I think that’s a good thing. If you could use your own number for a conference bridge, it would be one number or maybe more if you have them like Skype for Business Server. But you have to own them. And international numbers are expensive to own.

  • Pingback: Hybrid resource accounts with AA/CQ – Paul Lange's Blog

I’m calling it a Teams Minute…. e.g. 1-24 hours

This actually worked for me almost immediately after assigning the number. I created a resource account with New-CsOnlineApplicationInstance, assigned a license (my tenant actually now has the no-cost Phone System – Virtual User license), applied a freshly acquired DID from my provider via the set command, and it just pretty much worked.

That’s my top tip. Use PowerShell, not the TAC to create it and assign the number. When I do it that way, it works within a few minutes.

Thanks for confirming

Finaly mine start to work aswell. Dang MS support. Almost 8 weeks to figure out that there was a sync issue in Microsoft Backend. Have tried to tell them this of about 4 weeks. 🙂

Direct routing numbers weren’t ready for GA. And whoever was in TAP “testing” it before debut clearly didn’t. All these things would have spotted and fixed.

Glad it’s finally working for you

Tested things in TAP and reported stuff that didn’t work. Can’t do a lot more!

Here the same issue, 404 error on SBC… Created case but no feedback (yet)..

Hello Randy,

Once Resource Account configured and number associated it took 24 hrs for the number to be fully active in our setup.

Which one is cmd recommended to use to assigned number on AA Teams because we use DIrect Routing Teams.

Set-CsOnlineVoiceApplicationInstance -Identity [email protected] -TelephoneNumber +14255550100

Set-CsOnlineApplicationInstance -Identity [email protected] -OnpremPhoneNumber +14250000000

I wrote a blog post that explains it

what is the different if we use this Set-CsOnlineVoiceApplicationInstance -Identity [email protected] -TelephoneNumber +14255550100?

I think that’s an old command for Skype online only. Use the one without voice.

Understand. Now i have problem with customer environment. i have assigned number onprem to AA and then i reassigned it back and assigned that number to user. i also have delete resource account and AA to clean but until now user unable to make or received call from PSTN.

Norafify: how long have you waited after making those changes? As per comments here, it can take, well, hours or days for replication.

i have been waiting for more than 1 week. now i’m engage with Microsoft guys but still not solve yet.

Thank you for this, I will like to clarify, the on-premise number i’m assigning to the resource account, can it be an existing on-premise number currently terminated on a PBX (e.g Avaya). Since i will like to migrate my phone numbers to Teams, so when someone attempts to call the number assigned to the resoure account, it can route it to the individual specified in the Auto-attendant.

If yes,my question now is, what number will i now specify when I enable the user (that use the number assigned to AA) for Enterprise Voice? Can it be a dummy number?

You can assign any number to a resource account. Real or made up. If you want to route calls to it, it should be real. And one that you’ll port to the SIP connected to your direct routing enabled SBC

Ever come across this error before?

PS C:\Users\shaun\Desktop\Teams> Set-CsOnlineApplicationInstance -Identity shauntestresource -OnpremPhoneNumber ++14255550100 WARNING: Attention: On-premises domain must use on-premises cmdlet. Please copy and paste the below commands and run them with appropriate admin privileges in your on-premises Skype for Busin ess environment. WARNING: Set-CsHybridApplicationEndpoint -Identity shauntestresource -LineUri tel:++14255550100 This cmdlet is for online domain only. Please run corresponding on-premises cmdlets for on-premises domain. + CategoryInfo : InvalidOperation: (:) [Set-CsOnlineApplicationInstance], InvalidOperationException + FullyQualifiedErrorId : Microsoft.Rtc.Management.Hosted.PlatformService.ApplicationInstance.SetCsOnlineApplicationInstanceCmdlet + PSComputerName : admingb1.online.lync.com

Sorry, for context I am using an evaluation tenancy only. There is no on-prem SfB kit available.

I haven’t seen that error with that command. As far as I can see it’s correct. The only difference in my blog post is that I use the full [email protected]

I got the same problem and I fixed it by assigning a MYDOMAIN.onmicrosoft.com mail-address. Every other mail that my company got is not working anymore. I think Microsoft changed something.

Maybe you can fix your problem as well with that.

So I stumbled upon this blog because I seem to have the same issue. Direct Routing on prem number works when assigned to an end user but not when assigned to the AA. Case open now for 3 days with no result. I’ve don’t the “create a new resource account” and still the same. SBC of course fails with the 404 and Teams logs clearly show the issue is with the BVD. As a last resort I’m trying the suggestion that giving the resource account the onmicrosoft address. First test has failed but of course I’ll wait a “Teams” minute and try again. If this works I’ll report back.

I’m having this exact problem. Used Randy’s guide earlier with no issues, but now I get the same message as you do.

Did you figure out the problem?

we have deleted an old ressource account 30 hours ago and reassigned the on prem phone number to a new ressource account. However, the phone number are not reachable anymore from the PSTN. We always get 404 Not found.

The unreachable phone number is a central service number. This is a business critical issue. What can we do? Waiting days is not an option.

Best regards Jan

Hi Jan, When you add a phone number to a resource account, it starts a process at Microsoft to add that number to a directory called the Business Voice Directory (BVD). That number gets tied to the resource account in the directory. There is also an attribute for whether the resource account is a call queue or an auto attendant. Again, these are in the directory. The unfortunate thing is that only Microsoft has access to the BVD to make changes. In your case, the change would be to associate that number with another resource account after the one it was previously tied to was deleted. It can also affect when you want to reassign a resource account that was used for a call queue to an auto attendant.

I’m afraid you’ll have to raise a ticket with Microsoft and explain what you want. Hopefully they should be able to re-associate the number or maybe just delete it from the BVD so you can start again.

For future reference. It is best to keep a resource account and phone number association. And just move the resource account from one AA to another one. Or one CQ to another.

Heard this from a Microsoft engineer: if you want to delete old resource account, FIRST remove the number, wait a few hours (I would wait 48hours to be sure) and then delete the object.

Sounds reasonable

We have done the recreation of the ressource accounts for two call queues (our phone central and our customer service) at the same time.

A few minutes after my last post the ressource account of the phone central works again. However, the one of the customer service did not. I have already tried to remove the on prem number on the customer service ressource account and then reassigned it. It does work. I will wait another few hours and then open a ticket at Microsoft.

However, the current implementation of Microsoft is unacceptable.

Sorry, there was a typo in my last post: It does NOT work

Hi, I have a question about replacing outbound caller ID’s with a central switchboard number and I think the answer lies somewhere on the page. In TAP, I can create a new policy by it seems the only way to replace an outbound caller ID is with a Service Number. I tried creating one in Powershell but got the error about the number not being in the BVD or tenant.

Is this possible with Direct Routing? And if so, do I need to create a resouce account first?

I think it’s only service numbers for now. Not sure when it will be available for on prem numbers. But it’s logical to assume that’s coming

We desperately need this as well. At the moment it looks like the options are give out everyone’s DDIs, or make the outbound call anonymous…

We have masked the service number outbound on the SBC and then used the service number as a mask for users.

Hacky, but it achieves “an” outcome

just set the on-prem number and it does not work…hopefully its replication time!

You just have to wait a “Teams minute”

Hello Randy

Can I assign my own numbers to the users, instead of Microsoft numbers while configuring direct routing? “on-premise PSTN” option is not available in my tenant?

Yes you can. The user needs a phone system license. To be enabled for Enterprise voice and cloud voicemail. And an onpremlineuri

Hi Randy, Thanks for the perfect guide. Could you please mention how we can use a direct routing number as a service number and use it for CallingLineID? (purpose is to use a Direct Routing number as the Call Display for any outgoing Call) Regards Ali

  • Pingback: Use Extension Dialing in Microsoft Teams

Great guide, works fine for the ones I’ve created so far! Just wondering if there is anything out there on official licencing aside from the user specific ones currently in use. Haven’t read all of the comments so I may have missed this!

Official licensing for the Resourse account? Or the users in a queue etc?

Resource accounts with telephone numbers need the Phone System Virtual user license

Users that Teams hands calls to need Phone System

Thanks for the ping back. Great post

we have an issue it’s work from one number When I dial from the cell phone works and when I dial from another number does not work. and it’s not related to the sip provider.

I get an error on sbc – 500 The server encountered an unexpected internal error

I adding the steps for creating Hybrid Endpoint:

1. We upgrade the Environment to CU 10 HF1. 2. Create an on-premises resource account – New-CsHybridApplicationEndpoint -DisplayName TestIVR -SipAddress sip:[email protected] -OU “ou=Resource Accounts,ou=radwinusers ,dc=msftnettest,dc=co” -application id “ce933385-9390-45d1-9512- c8d228074e07”. (app id for AA) 3. Assign a phone number to the resource account- Set-CsHybridApplicationEndpoint -Identity [email protected] -LineURI tel:+XXXXXXXXX 4.Force sync to Azure AD 5. Add Licence Phone System – virtual user. 6. connect to skype online – Set-CsOnlineApplicationInstance -Identity [email protected] -OnpremPhoneNumber +97237662916 7.wait for synchronization and assigned to AA.

You have an idea why this is happening?

Thank you very much for this great tutorial!! The resource-account got a phone number with direct routing!!! *party* This article saved my weekend!!

Wonderful. So glad it could help you. Enjoy the party 🎉

I was wondering whether you had any insight into when and if Microsoft will list phone numbers assigned to Call Q and Auto-Attendant as Service numbers. By not listing the numbers it is not possible to create a caller ID plociy and assign to a user that would send caller ID of the phone number assigned to the call queue.

No insights I’m afraid. But I am definitely hoping that will become the case. It’s less about resource account numbers being listed as service numbers and more about privately owned or Direct Routing numbers being manageable by admins in the TAC. As an MVP I’m definitely pushing for this.

Thanks Randy – push hard as you can please!

Thanks for the article. You could Update the License needed for Resource User. Microsoft released “Phone-system – Virtual User License” Best Regards

Hi Randy When we use the AutoAttendant in microsoft TEAMS, very often the autoattendant is only playing half or less of the menu, seems there is a delay here. It happens so often that I would say it is not useable. Is this normal behavior on Microsoft Teams?

Never heard that before. Are people selecting options before the announcement is done?

If there is a problem then I would raise a case with Microsoft. Definitely not normal

Hi no this is an example AA is saying “welcome to our firm, press 1 for Sales, press 2 for support, press 3 for reception”

maybe 2 out of 3 times, this message will be cut off. So maybe we only hear

“press 2 for support, press 3 for reception”

or maybe only “for reception”

Sounds like a big. Raise a ticket with Microsoft.

By now the Teams comandlets are changed: Set-CsPhoneNumberAssignment -Identity [email protected] -PhoneNumber +442071234567 -PhoneNumberType DirectRouting

Yep. I need to update quite a lot

Leave a comment Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed .

' src=

  • Already have a WordPress.com account? Log in now.
  • Subscribe Subscribed
  • Copy shortlink
  • Report this content
  • View post in Reader
  • Manage subscriptions
  • Collapse this bar

Plan and implement your Microsoft Teams Phone deployment

Do you want to plan for teams phone, or are you ready to deploy it, what to expect.

  • Creating an inventory of your current telephony system, such as existing sites, locations (countries or regions), phone numbers, and equipment.
  • Identifying telephony requirements for your company.
  • Capturing user personas and usage scenarios.
  • Public Switched Telephone Network (PSTN) connectivity features : Calling plans, Operator Connect, Teams Phone Mobile, and Direct Routing
  • Phone System features : Caller ID, auto attendants, call queues, and Audio Conferencing

Do you have an on-premises Skype telephony solution that you want to migrate to Teams? *

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Configure Teams Phone Mobile

  • 4 contributors
  • Applies to: Microsoft Teams

For a list of operators participating in the Microsoft Teams Phone Mobile program and the countries or regions where their service is available, see Microsoft 365 Teams Phone Mobile .

This article describes how to configure Teams Phone Mobile. Before configuring Teams Phone Mobile, be sure to read Plan for Teams Phone Mobile for information about benefits, prerequisites, and licensing.

Enable an operator

You can enable, edit, and remove operators in the Teams admin center. In the left navigation pane, go to Voice > Operators .

To enable an operator:

Choose an operator that supports Teams Phone Mobile. Under the All operators tab, filter available operators by region or service to find the right operator supporting Teams Phone Mobile. Then select the operator you want to enable.

Under Operator settings , select the countries/regions you want to enable with your selected operator.

Provide contact information. Your contact information, including your full name and email address, will be shared automatically with your operator. You can change this information later. Additionally, you'll need to provide company size, and you'll have the option to provide your phone number. Operators will use this information to contact you with more details about Teams Phone Mobile.

Accept the data transfer notice.

Select Add as my operator to save.

Set up phone numbers

If you want to add your existing company paid SIM-enabled phone numbers to Teams, contact your operator to ensure you have the eligible Teams Phone Mobile subscription, and they can upload your numbers to Teams. After your operator completes the order, you can assign those numbers to users.

To find your operator's website, see the Microsoft 365 Teams Phone Mobile directory .

You'll need to provide your tenant ID. If you don't know your tenant ID, see Find your Microsoft 365 tenant ID . You may be porting an existing desk phone number or wireline number to a wireless voice subscription if it's supported in your region and by your operator.

How you set up phone numbers depends on whether you're setting up numbers for new users, or moving existing numbers from either Microsoft Calling Plans, Operator Connect, or Direct Routing.

Acquire numbers for new Teams users .

Move numbers from Calling Plans to Teams Phone Mobile .

Move numbers from Operator Connect to Teams Phone Mobile .

Move numbers from Direct Routing to Teams Phone Mobile .

Assign numbers to emergency addresses

The emergency address is a static location associated with a number when accessible through Microsoft Teams endpoints/clients. Once you create emergency addresses in the Teams admin center, how you assign the addresses, or change them later, will depend on your operator.

To assign numbers to emergency addresses being used by Microsoft Teams endpoints, your operator will implement one of three scenarios:

The operator assigns emergency addresses to the phone numbers and allows you to change them later in the Teams admin center.

The operator doesn't assign addresses and allows you to assign emergency addresses to the phone numbers in the Teams admin center.

The operator assigns emergency addresses to the phone numbers, and doesn't allow you to change them. In this scenario, you'll need to contact your operator to make changes to phone numbers and their assigned emergency address.

When calls are made through the native dialer of the SIM-enabled smartphone, your operator may use the geographic coordinates or cell tower handling the call to approximate emergency location for assistance.

For more information on emergency calling, see Manage emergency calling and Plan and configure dynamic emergency calling .

Acquire numbers for new Teams users

To acquire numbers for new Teams users, follow these steps:

Assign a Phone System license and an Teams Phone Mobile add-on license. You can assign a Phone System license and a Teams Phone Mobile add-on license to your users from the Microsoft 365 admin center or by using PowerShell. For more information, see Assign Teams add-on licenses to users .

Users who will be assigned phone numbers acquired with Teams Phone Mobile need to be in TeamsOnly mode. If your organization is in TeamsOnly mode, then all your users are in TeamsOnly mode.

To check, in the Teams admin center, go to Teams > Teams upgrade settings . If your organization is in Islands mode, check if specific users are in TeamsOnly mode. Go to Users and select a user account. In the Account tab, under Teams upgrade, the coexistence mode should be set to TeamsOnly.

Acquire numbers. Go to your operator's website or contact them to order and acquire mobile SIM-enabled phone numbers with the Teams Phone Mobile service enabled.

After your operator completes the order, they'll upload SIM-enabled mobile numbers to your tenant. You can view the numbers and the provider in the Teams admin center by going to Voice > Phone numbers .

Assign numbers. You can assign numbers to users from the Teams admin center or by using PowerShell. For more information, see Assign numbers .

Move numbers from Calling Plans to Teams Phone Mobile

Ensure you have eligible Microsoft 365 subscriptions for Teams Phone Mobile and the Teams Phone Mobile add-on license. You need to remove the phone number to be moved for respective users .

Contact your operator to port your numbers to Teams Phone Mobile on an eligible wireless voice plan which is SIM-enabled.

After your operator completes the porting order, your operator will upload the numbers to your tenant. You can view the numbers and the provider in the Teams admin center by going to Voice > Phone numbers .

You can assign numbers to users by using the Teams admin center or by using PowerShell. For more information, see Assign numbers .

Move numbers from Operator Connect to Teams Phone Mobile

Ensure you have eligible Microsoft 365 subscriptions for Teams Phone Mobile and the Teams Phone Mobile add-on license. You need to remove the phone number to be moved for respective users . Contact your existing Operator Connect provider to remove the phone numbers from your tenant.

Move numbers from Direct Routing to Teams Phone Mobile

To move numbers from Direct Routing to Teams Phone Mobile, you'll need to complete the following steps:

Determine if the existing Direct Routing numbers are assigned online or on-premises .

Migrate the numbers from Direct Routing to Teams Phone Mobile .

Remove the online voice routing policy associated with your user .

Acquire phone numbers .

Assign phone numbers .

These steps are described in greater detail in the following sections.

Determine if the existing Direct Routing numbers are assigned online or on-premises.

How you remove your existing Direct Routing numbers depends on whether the number is assigned on-premises or online.

First, check that the user is assigned a Direct Routing number by running the following Teams PowerShell command. NumberType should be DirectRouting:

Determine if the number is assigned online or on-premises by running the following Teams PowerShell command:

If OnPremLineUri is populated with an E.164 phone number, the phone number was assigned on-premises and synchronized to Microsoft 365.

Migrate the numbers from Direct Routing to Teams Phone Mobile

To migrate numbers, follow the steps below.

During migration, the phone number will be out of service. Coordinate with your Teams Phone Mobile operator before you begin the migration.

To migrate existing Direct Routing numbers assigned online to Teams Phone Mobile , contact your operator. To find your operator's website, see Microsoft 365 Teams Phone Mobile directory . On the agreed date and time, your operator will migrate your numbers from Direct Routing to Teams Phone Mobile. This may involve removing the phone number being migrated from your tenant and add it again as a new phone number associated with Teams Phone Mobile.

To migrate Direct Routing numbers assigned on-premises to Teams Phone Mobile , run the following Skype for Business Server PowerShell command:

To check if the on-premises number was removed and the changes have been synced from on-premises to Microsoft 365, run the following Teams PowerShell command:

After the changes have synced to Microsoft 365 online directory, the expected output is:

To check if the phone number was removed, run the following Teams PowerShell command:

The amount of time it takes for the removal to take effect depends on your configuration. Removing the phone number may take up to 10 minutes, in rare cases, it can take up to 24 hours.

Remove the online voice routing policy associated with your user

After the number is unassigned, remove the online voice routing policy associated with your user by running the following Teams PowerShell command:

Acquire phone numbers

After your operator completes the order, they'll upload numbers to your tenant. You can view the numbers and the provider in the Teams admin center by going to Voice > Phone numbers .

Assign phone numbers

You can assign Teams Phone Mobile numbers to users by using the Teams admin center or by using PowerShell. For more information, see Assign numbers .

Manage your operators

From the My operators tab, you can view your operators and their status, and make the following changes to your selections:

  • Manage operator services by country/region
  • Suspend an operator
  • Remove an operator

Before removing an operator from your organization or from a country/region, you must remove all phone numbers assigned to users in the organization or country/region and contact the operator to release the numbers.

Release numbers

To release phone numbers from the Teams admin center, go to the Phone numbers page and select a number.

If the phone number isn't assigned to a user, select Release .

If the phone number is assigned to a user, you'll need to unassign the number. Select Edit , then Remove user . After you save your changes, select Release .

Manage user incoming calling policies

You can manage a user's incoming calling policies by using the Teams admin center or by using PowerShell. By default, incoming calls for Teams Phone Mobile users will ring the Teams app first on the user's SIM-enabled mobile device.

If a user's incoming calling preference is set to the Teams app, all incoming calls will ring the Teams app on the SIM-enabled smartphone and any other Teams endpoints on other devices simultaneously.

If a user's incoming calling preference is set to the native dialer, all incoming calls ring the native dialer on the SIM-enabled smartphone and simultaneously rings all other Teams endpoints on other devices.

Use the Teams admin center

To manage a user's incoming calling policies by using the Teams admin center:

Under the voice tab, select Mobility Policies .

To add a new mobile policy, click Add .

Select a name, add a description of the policy, and choose one of the following from the Select a mobile dialer dropdown option:

Microsoft Teams to ring the Teams app on the SIM-enabled smartphone first.

Native Dialer to ring the Native Dialer on the SIM-enabled smartphone first.

Assign the policies to users. See Assign policies .

Use PowerShell

Connect to your tenant: Connect-MicrosoftTeams.

Create policies for incoming calls to ring either the Native dialer or the Teams app first. (You can choose the policy name; this example uses TeamsFirst and NativeFirst.)

Grant policies to users:

Check user policies:

Check all mobility policy options:

Was this page helpful?

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback .

Submit and view feedback for

Additional resources

teams assign on premise phone number

Top Contributors in Microsoft Teams: EmilyS_726   ✅

February 14, 2024

Top Contributors in Microsoft Teams:

EmilyS_726   ✅

  • Search the community and support articles
  • Microsoft Teams
  • Teams for business
  • Search Community member

Ask a new question

Inactive profile

I NEED YOUR HELP: Teams phone number assigned to another user

Hello Teams Community,

Please i need your help on this issue.

We are users of MS Teams phone solutions (Microsoft 365 Business Voice) which by Monday 7.2.2022. functioned neatly. On the specified date, we should have changed the person who is forwarding the calls and we receive the following error:

Microsoft.Teams.ConfigAPI.Cmdlets.internalSet-CsUserGenerated : 3xxxxxxxxxx is assigned to another user

For 4-5 months we've had the same treatment (there's a change of user on a regular basis) and everything's been neatly flicked.

The specified problem has already been reported to Microsoft by other users here:  https://github.com/MicrosoftDocs/office-docs-powershell/issues/8742

teams assign on premise phone number

Report abuse

Vaidya Darpan MSFT

  • Microsoft Agent |

Thank you for posting into the forum community. We will highly appreciated your kind cooperation and patience in our forum community.

Based on your mentioned concern description, I totally understand your concern and as we have dedicated Microsoft Q&A forum community for API related concern. So, I'd recommend you please kindly contact and raise your concern into this mentioned forum community. Our related expert forum community member will further assist you there accordingly and respectively.

Stay safe and healthy.

Was this reply helpful? Yes No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

Thanks for your feedback.

Replies (1) 

Question info.

  • Meetings and calls
  • Norsk Bokmål
  • Ελληνικά
  • Русский
  • עברית
  • العربية
  • ไทย
  • 한국어
  • 中文(简体)
  • 中文(繁體)
  • 日本語

IMAGES

  1. How to assign a Phone Number in Microsoft Teams

    teams assign on premise phone number

  2. assign a phone number in teams

    teams assign on premise phone number

  3. Teams Calling Assigning Direct Routing Numbers To A User

    teams assign on premise phone number

  4. Microsoft Teams Phone, make and receive phone calls anywhere

    teams assign on premise phone number

  5. Microsoft Teams

    teams assign on premise phone number

  6. Microsoft Teams for conference calls and dial-in phone numbers

    teams assign on premise phone number

VIDEO

  1. O365Eh!

  2. How to assign teams to training sessions

  3. Microsoft Teams Call Recording

  4. YourSite Explorer: Security Roles and Lists: MiContact Center Business

  5. The Secret And Her Warden P2...[F4A][Crossed Lovers][Prisoner][Secrets][Ex][Roleplay Audio]

  6. We Fixed Microsoft Teams Phone Number Management!

COMMENTS

  1. Manage phone numbers for users

    To assign a number by using the Teams admin center: Open the Microsoft Teams admin center and log in with a user that is a Global admin. This is usually the account you used to sign up for Microsoft 365. In the left navigation, click Voice > Phone numbers. On the Phone numbers page, select an unassigned number in the list, and then click Edit.

  2. Manage phone numbers for your organization

    Skype for Business, Microsoft Teams Feedback In this article User telephone numbers Service telephone numbers Where phone numbers are managed Currently, Microsoft supports two telephone number types: User numbers, also called subscriber numbers, which can be assigned to users in your organization.

  3. Set up Teams Phone in your organization

    Feedback In this article Step 1: Buy and assign a Teams Phone license Step 2: Choose a PSTN connectivity option Step 3: Get and assign phone numbers for your users and services Step 4: Set up emergency calling Show 5 more

  4. Comprehensive Guide to Teams Phone Number Assignment in your Organization

    Step 1: Select country or region. An image demonstrating the Microsoft Teams Phone Advanced Deployment Guide Step 2: Use filters if desired. An image demonstrating the Microsoft Teams Phone Advanced Deployment Guide Step 3: Select the user you want the phone number assigned to.

  5. How To Automate Microsoft Teams Number Provisioning

    From the Admin Center, you can assign numbers to users and resource accounts using the web interface, or for automation purposes, PowerShell. Benefits of using the Teams Admin Center for number provisioning include: Uses native Microsoft functions to provision, reducing manual errors Numbers stored in the same portal as your Teams user settings

  6. How to Assign Phone Number for Calling in Microsoft Teams

    4 Share 1.4K views 4 months ago Microsoft Teams In this video, you will learn how to assign phone numbers to users using the Teams Admin Center. Clerk Chat utilizes the same phone...

  7. Microsoft Teams Phone (Voice) Configuration and Management

    Calling plans are a simple way to quickly procure, provision, and assign phone numbers to organization users. In the calling plan, Microsoft is the PSTN service provider. 2. ... You cannot see the on-premises phone number listed in the Teams admin center; however, you can manage it locally using an Excel file and assign the number using a ...

  8. Teams Phone Numbers: How to Sync with Active Directory

    1) Connect to your On-Premises AD server via Remote Desktop. 2) Create a user. 3) Provide the user account with write permission to the telephoneNumber attribute for the OU your users are located in. Right-click the OU which contains your Teams Calling users and select Delegate Control.

  9. Configuration of "Assigned phone number" in Microsoft Teams Admin

    2. Microsoft 365 Admin Center - https://admin.microsoft.com/Adminportal/Home#/users/:/UserDetails/<user-id> - add the phone number to the " Office Phone" field under Manage contact information section.

  10. Enable users for Direct Routing

    Step 1. Connect the SBC with Phone System and validate the connection Step 2. Enable users for Direct Routing (this article) Step 3. Configure voice routing Step 4. Translate numbers to an alternate format For information on all the steps required for setting up Direct Routing, see Configure Direct Routing.

  11. Microsoft Teams Phone

    Teams Essentials and Teams Phone with domestic calling. $20.00 $16.00. user/month. (Annual subscription-auto renews) 4. Price includes communication taxes and fees. 5. Buy now. See all bundles. Includes Teams Phone with Calling Plan and Teams Essentials, featuring: Phone number and PSTN service from Microsoft.

  12. I am unable to assign a licensed user to a phone number in teams. None

    If you are unable to find any licensed users to assign a phone number to in Microsoft Teams. The Teams Phone System license is available as an add-on license to Office 365 A1/E1, A3/E3 and I believe both Microsoft 365 Business Standard and Premium. It comes as part of the licensing package for Office 365 A5/E5.

  13. Manage resource accounts for service numbers

    Create a resource account Assign a license Assign a phone number Next steps Show 4 more In Microsoft Teams, a resource account is required for each auto attendant or call queue. Resource accounts may also be assigned telephone numbers.

  14. How to: Assign a Direct Routing Number to an Auto Attendant or Call

    Thank you for this, I will like to clarify, the on-premise number i'm assigning to the resource account, can it be an existing on-premise number currently terminated on a PBX (e.g Avaya). Since i will like to migrate my phone numbers to Teams, so when someone attempts to call the number assigned to the resoure account, it can route it to the ...

  15. Set-CsPhoneNumberAssignment (MicrosoftTeamsPowerShell)

    Example 1 PowerShell Set-CsPhoneNumberAssignment -Identity [email protected] -PhoneNumber +12065551234 -PhoneNumberType CallingPlan This example assigns the Microsoft Calling Plan phone number +1 (206) 555-1234 to the user [email protected].

  16. Plan for and deploy Microsoft Teams Phone

    This guide will help you transition from your existing voice solution to Microsoft Teams Phone. You'll be guided through discovery and planning phases, or you can go straight to deployment. You'll be able to configure a calling plan, Operator Connect, Teams Phone Mobile, Direct Routing, caller ID, and other features.

  17. Can you make a call from a phone to a Teams Channel?

    To enable this feature, you need to follow these steps: - Create a resource account and assign a phone number to it. - Create a call queue and assign the resource account to it. - Enable voice-enabled channels in the Teams admin center. - Create or select a channel in Teams and connect it to the call queue.

  18. Configure Teams Phone Mobile

    Feedback In this article Enable an operator Set up phone numbers Manage your operators Release numbers Manage user incoming calling policies For a list of operators participating in the Microsoft Teams Phone Mobile program and the countries or regions where their service is available, see Microsoft 365 Teams Phone Mobile.

  19. I NEED YOUR HELP: Teams phone number assigned to another user

    On the specified date, we should have changed the person who is forwarding the calls and we receive the following error: Microsoft.Teams.ConfigAPI.Cmdlets.internalSet-CsUserGenerated : 3xxxxxxxxxx is assigned to another user. For 4-5 months we've had the same treatment (there's a change of user on a regular basis) and everything's been neatly ...