What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Microsoft Teams can show “You are not set up to use this calling feature” when a user tries to place a PSTN call, use the Calls app, dial a phone number, or access a calling option that is not enabled for their account. The message usually means Teams does not see the required voice configuration, license, policy, or telephony connection for that user.
In many cases, the fix is straightforward: confirm the user has the right Teams Phone licensing, is allowed to make calls by policy, and is assigned a valid Calling Plan, Operator Connect setup, or Direct Routing configuration. It can also appear because of stale client sign-in data, the wrong account being used, or recent admin changes that have not finished provisioning.
As an Amazon Associate I earn from qualifying purchases.
Resolving the issue starts with separating user-side problems from tenant or admin configuration problems. Basic checks such as signing out, updating Teams, and confirming the correct account can help, but persistent errors usually require an administrator to review licensing, voice routing, emergency calling, and PSTN connectivity settings.
What This Microsoft Teams Calling Error Means
The Microsoft Teams message “You are not set up to use this calling feature” appears when Teams recognizes that the user is trying to place or manage a phone call, but the account does not currently have everything required to use that specific calling capability. In most cases, this is not a problem with the microphone, headset, or internet connection. It usually means Teams cannot confirm that the user is enabled for enterprise voice, assigned the right license, allowed by policy, or connected to a working PSTN calling configuration.
#1 Best Overall
This error is most often seen when a user clicks the Calls app, tries to dial an external phone number, selects a phone number from a contact card, or attempts to use dial pad features. It can also appear for users who can join Teams meetings and make Teams-to-Teams audio calls successfully, but cannot call mobile numbers, landlines, or external PSTN numbers. That distinction matters: regular Teams audio in meetings is different from Microsoft Teams Phone calling. A user may be fully licensed for Microsoft 365 collaboration while still lacking the services needed for external calling.
Teams calling depends on several layers being correctly configured. The user account must have a compatible Teams Phone license, such as Microsoft Teams Phone Standard or a license bundle that includes Phone System capabilities. The user must also be assigned a calling method, such as Microsoft Calling Plan, Operator Connect, or Direct Routing. On top of that, Teams policies must allow the user to make calls, and the tenant’s voice routing or phone number assignment must be complete. If any one of these layers is missing or mismatched, Teams may block the calling action and show the setup message.
The wording can be confusing because it does not always identify the exact missing component. For example, the same message may appear if a user has no Teams Phone license, if the dial pad is hidden due to policy, if the account has not been assigned a phone number, or if Direct Routing voice routes are incomplete. It may also occur temporarily after a license or policy change because Teams services can take time to update across Microsoft 365. Signing out and back in, switching accounts, or testing in the web client can help confirm whether the issue is local to the Teams client or tied to the account configuration.
In practical terms, the error means the user’s Teams account is not currently authorized or provisioned for the calling action being attempted. End users can check simple account and client issues first, but administrators usually need to verify licensing, calling policies, number assignment, emergency location settings, and PSTN connectivity. Once the missing entitlement or configuration is corrected, the dial pad and calling features typically become available without reinstalling Teams.
Common Causes of the “You Are Not Set Up” Message
The Microsoft Teams message “You are not set up to use this calling feature” usually appears when Teams can open the Calls area, but the user account is not fully enabled for the specific calling action being attempted. This may happen when placing a PSTN call, using the dial pad, calling an external phone number, or accessing a feature that depends on Teams Phone configuration. In most cases, the problem is tied to licensing, policy assignment, phone number setup, voice routing, or the account currently signed in to the client.
Missing or incorrect Teams Phone licensing
One of the most common causes is that the user does not have the required Microsoft Teams Phone license, formerly known as Phone System. A standard Microsoft 365 or Office 365 license can allow Teams chat, meetings, and peer-to-peer Teams calls, but it does not automatically enable PSTN calling. For external phone calls, the user typically needs a Teams Phone license plus a calling option such as Microsoft Calling Plan, Operator Connect, or Direct Routing.
- No Teams Phone license: The user can join meetings and call other Teams users, but cannot use full telephony features.
- License assigned recently: Teams may need time to reflect licensing changes across Microsoft services.
- Wrong service plan disabled: The license may be present, but the Teams Phone-related service plan may be turned off.
- Conflicting license setup: Trial, add-on, or bundled licenses may not provide the expected calling capability if not assigned correctly.
Calling policy or voice policy restrictions
Teams administrators can control which users are allowed to make private calls, use PSTN calling, forward calls, or access other calling features. If a calling policy disables private calling, the user may see this message when trying to place calls. Similarly, if the user is missing the correct voice routing policy or dial plan, Teams may not know how to process the number being dialed.
Recommended Free Tools
Policy assignment issues are especially common after a user changes department, moves to a different region, is migrated from Skype for Business, or is newly enabled for Teams Phone. A user may have the correct license but still be blocked because the assigned policy does not permit the intended action. In large tenants, group-based policy assignments can also override or delay expected settings.
Calling Plan, Direct Routing, or Operator Connect setup problems
For PSTN calls to work, the tenant needs a valid calling path. With Microsoft Calling Plan, the user must have a Calling Plan license and an assigned phone number. With Operator Connect, the carrier connection, number assignment, and operator configuration must be active. With Direct Routing, the session border controller, voice routes, PSTN usages, and online voice routing policy must all be configured correctly.
| Calling method | Common configuration issue |
|---|---|
| Microsoft Calling Plan | User has Teams Phone but no Calling Plan license or phone number assigned. |
| Operator Connect | Operator service is not fully activated, or the number is not assigned to the user. |
| Direct Routing | User lacks an online voice routing policy, or routes to the SBC are misconfigured. |
Client, sign-in, and account mismatches
The Teams desktop or mobile client can also contribute to the error. A user may be signed in with the wrong work account, using a guest account in another tenant, or running an outdated client that has not refreshed new licensing and policy changes. Cached credentials can make Teams continue showing the error even after an admin has corrected the account configuration. This is common when users have mulle Microsoft accounts, switch between tenants, or were recently assigned calling features.
Rank #2
- 100 Count Perfect Fit for Toploaders & Sleeves – Sized at 3 3/8" x 5" with a 1" resealable flap, these trading card team bags are ideal for protecting standard-size cards in toploaders, soft sleeves, semi rigid or magnetic holders.
- Strong Resealable Closure – Each resealable team set bag features a reliable adhesive strip that seals securely, opens cleanly, and retains its stickiness for multiple uses — perfect for sellers and collectors.
- Crystal Clear Protection – Made from ultra-transparent polypropylene, these TCG bags let your cards shine while keeping them safe from dust, fingerprints, and scratches.
- Archival-Grade Materials – 100% acid-free and PVC-free to ensure your baseball card team bags protect your collection long-term without yellowing, clouding, or chemical damage.
- Collector-Trusted Quality – Whether you’re shipping, storing, or presenting, these team bags for cards are the go-to choice across sports, TCG, and pop culture categories — a staple for anyone using team bags for top loaders.
In some cases, the message appears because the user is attempting a calling feature that is unavailable in their current context. For example, guest users generally cannot use another organization’s PSTN calling setup as if they were native users. The dial pad may also be missing or nonfunctional if the account is not homed correctly in Teams, the tenant is in the middle of a migration, or the user’s phone number assignment has not finished provisioning.
Checks End Users Should Try First
Before opening an admin ticket, users can rule out several local and account-related issues that often make Microsoft Teams show “You are not set up to use this calling feature.” These checks are most useful when calling worked previously, when the issue affects only one person, or when the Calls app is visible but dialing fails. If every user in a department or tenant is affected, the cause is more likely licensing, calling policy, Direct Routing, Calling Plan, or Operator Connect configuration.
Confirm you are using the correct Teams account
Many calling problems happen because Teams is signed in with the wrong identity. For example, a user may be logged in with a guest account, personal Microsoft account, test account, or an old work account that does not have enterprise voice enabled. In Teams, select your profile picture and verify that the signed-in account is the same work or school account assigned to your phone number and calling license. If you belong to mulle organizations in Teams, switch back to your home organization and try the call again.
Check whether calling is available in Teams
Open Teams and look for the Calls app on the left rail. If it is missing, select Apps and search for Calls, or select the three-dot menu to see whether it is hidden. If the Calls app is present, check whether you can see a dial pad. A missing dial pad usually means the account is not enabled for PSTN calling, is restricted by policy, or has no assigned phone number. Users cannot fix those tenant-side settings themselves, but confirming what is missing helps the help desk route the issue correctly.
- No Calls app: Teams app setup policy may hide it, or the client may need to refresh.
- Calls app exists but no dial pad: licensing, phone number assignment, or voice policy may be incomplete.
- Dial pad exists but calls fail: the issue may involve routing, Calling Plan credit, Direct Routing, Operator Connect, or network access.
- Only one contact cannot be called: the contact may not have voice enabled, may be external, or may be blocked by federation or calling policy.
Restart, update, and clear the Teams session
A stale Teams session can continue to show old policy or license information after an admin makes a change. Fully quit Teams rather than just closing the window. On Windows, right-click the Teams icon in the system tray and select Quit. On macOS, use Quit Microsoft Teams from the menu bar or dock. Reopen Teams and try again. If the problem remains, sign out of Teams, close the app, reopen it, and sign back in.
Users should also check for client updates. In the new Teams client, select Settings and more, then check for updates if the option is available. If you use Teams in a browser, try a supported browser such as Microsoft Edge or Chrome, then test in a private browsing window. This helps separate a Teams account problem from cached browser data, extensions, or an outdated desktop client.
Test from another device or network
If possible, try Teams calling from another device, such as the Teams mobile app or a different computer. A call that works on mobile but not on the desktop usually points to a local client, operating system, headset, firewall, or network issue. A call that fails everywhere for the same user points more strongly to account provisioning. When testing, avoid VPN if company policy allows, or try a trusted corporate network. Some VPNs and restrictive networks block media or signaling paths used by Teams calling.
Collect details before contacting support
If the error continues, gather practical details for your IT team: the exact wording of the message, the time it occurred, the number or contact you tried to call, whether the dial pad appears, whether Teams calls to coworkers work, and whether PSTN calls to external numbers fail. Include screenshots where appropriate. These details help admins quickly determine whether they need to review your Phone System license, calling policy, emergency location, phone number assignment, voice routing, or provider configuration.
Admin Licensing and Calling Policy Fixes
If basic user-side checks do not clear the message, an administrator should confirm that the affected account is licensed and allowed to place calls in Teams. The error often appears when Teams can open the Calls app, but the user does not have the required voice entitlement or is blocked by a policy. This is especially common after new user onboarding, license changes, department moves, or migrations from Skype for Business to Teams Phone.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesConfirm the required Teams Phone licensing
In the Microsoft 365 admin center, open the affected user and review the assigned licenses. A user who needs public switched telephone network calling must have a base Microsoft 365 or Office 365 license that includes Teams, plus the appropriate Teams Phone entitlement. Depending on the tenant and subscription model, this may be shown as Microsoft Teams Phone Standard, Phone System, or included in certain enterprise plans. If the user is expected to dial external phone numbers, they also need a PSTN connectivity method such as a Calling Plan, Operator Connect, or Direct Routing configuration.
Rank #3
- 7'x 7' Baseball & Softball Practice Net perfect for baseball and softball training to improve your baseball Pro level. It has a big mouth to help you catch and collect the ball whether you are practicing batting or pitching. So you can spend less time chasing balls and much time improving your skills, also ideal for youth, children and adults hitting pitching batting practice
- Baseball hitting net sets up in less than 5 minutes; No tools required; Includes ground stakes for added stability, can withstand even the hardest hits; Collapsible training nets assemble quickly and easily for easy setup; Lightweight for easy portability and placement during practice sessions, Breaks down to fit in carrying bag for easy long-term storage and portability in any where
- The baseball net is designed to take the abuse of the hardest hits and throws; The steel frame and flexible fiberglass bow poles provide a steady base; each leg has rubber feet for added stability. Includes metal stakes to secure the net to grass or dirt infield. and the metal supports, and ground stakes hold the frame firmly whatever the weather
- Versatile practice net is an ideal baseball training tool for batting practice, pitching, fielding, and catching, and backstop use. It works great in the backyard, sports ground, garage, Ideal for coaches, college players, baseball and softball beginners, family members, and all age groups
- Offered a better opportunity to you to get to build up your body and strengthen your friendship or parent-child relationships, and This baseball pitching net can increase stamina, attention, and action ability. Whatever the skill level of the players, can make everyone active, let you feel very relaxed
- Internal Teams-to-Teams calling only: Confirm the user has access to Microsoft Teams and is not blocked from chat or calling by policy.
- External PSTN calling: Confirm Teams Phone is assigned and enabled for the user.
- Domestic or international dialing: Confirm the user has the correct Calling Plan, Operator Connect number, or Direct Routing voice route access.
- Shared or common-area phones: Confirm the account has the correct common area phone or resource account licensing, where applicable.
After assigning or correcting licenses, allow time for provisioning to complete. In many tenants, changes appear within minutes, but voice features can take longer to become available across Teams services. Ask the user to sign out of Teams completely and sign back in, or test from the Teams web client to confirm whether the account has picked up the updated entitlement.
Review Teams calling policies
Licensing alone is not enough if the user’s Teams policies prevent calling. In the Teams admin center, check the user under Users, then review assigned policies such as Calling policy, Teams upgrade policy, and any voice-related policy packages. The calling policy should allow private calling if the user needs person-to-person Teams calls. If this setting is disabled, users may see calling options missing or receive an error when trying to start a call.
| Admin area | What to check | Expected setting |
|---|---|---|
| Microsoft 365 admin center | Teams and Teams Phone license assignment | Assigned and enabled for the user |
| Teams admin center | Calling policy | Private calling allowed, if required |
| Teams admin center | Teams upgrade mode | Teams Only for most modern Teams Phone deployments |
| Teams admin center | Policy assignment source | No conflicting group or package assignment |
Also check whether the user is receiving policies through group assignment. A direct policy assignment may be overwritten or made ineffective by a policy package or group-based policy with higher precedence. If only one department or security group is affected, compare its assigned calling policy with a known working user. For organizations that recently changed voice settings, review whether the affected user has fully moved to Teams Only mode; hybrid or legacy coexistence settings can interfere with how calling is surfaced in the client.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Once licensing and policy changes are made, validate with a known test path: have the user sign out and back in, place a Teams-to-Teams call, then test PSTN dialing if applicable. If Teams-to-Teams calling works but dialing external numbers still fails, the remaining issue is likely in the PSTN configuration rather than the basic calling policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Direct Routing, Calling Plan, and Operator Connect Configuration Checks
If the user has the correct Teams Phone license and a policy that allows calling, the next place to check is the voice connectivity method assigned to the user. Microsoft Teams calling can be delivered through Microsoft Calling Plans, Direct Routing, Operator Connect, or Teams Phone Mobile. A mismatch between the user’s phone number, voice route, emergency location, or carrier setup can cause Teams to show “You are not set up to use this calling feature,” even when the Calls app appears in the client.
Microsoft Calling Plan checks
For Microsoft Calling Plans, confirm that the user has both a Teams Phone entitlement and the appropriate Calling Plan license for their country or region. The user also needs a telephone number assigned in the Teams admin center under Users > Manage users > Account > General information. If the number is missing, unassigned, or still in a pending port state, outbound and inbound PSTN calling may fail.
- Verify the user’s Usage location in Microsoft Entra ID matches a supported Calling Plan market.
- Confirm a Microsoft service number was not accidentally assigned where a user number is required.
- Check that emergency calling information is configured where required, including emergency address and location details.
- Allow time for provisioning after assigning a number or license; changes can take several hours to appear consistently.
Direct Routing checks
With Direct Routing, the Teams tenant must be able to route calls through a certified Session Border Controller. In the Teams admin center, check Voice > Direct Routing and confirm the SBC shows as healthy, enabled, and using a valid TLS certificate. A certificate name mismatch, expired certificate, firewall block, or SIP options failure can prevent Teams from completing PSTN setup for affected users.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Admins should also review the user’s voice routing configuration. The user needs an assigned phone number in the correct format, usually E.164 such as +15551234567, plus a voice routing policy that includes a PSTN usage linked to a valid voice route. That voice route must point to the correct SBC and match the dialed number pattern. If the policy is missing, assigned to the wrong user group, or references an inactive route, Teams may not find a valid path for the call.
- Check the user with Teams PowerShell commands such as Get-CsOnlineUser to confirm LineURI, EnterpriseVoiceEnabled, and assigned voice policy values.
- Confirm the SBC is listed and responding with Get-CsOnlinePSTNGateway.
- Review voice routes, PSTN usages, and voice routing policies for number pattern mismatches.
- Test with another Direct Routing-enabled user to determine whether the problem is user-specific or tenant/SBC-wide.
Operator Connect checks
For Operator Connect, the carrier relationship and number assignment are managed through the Teams admin center and the provider’s portal. Confirm the operator is active under Voice > Operators, the user’s number has completed provisioning, and the number is assigned to the correct account. If the carrier has not finished activation or the number is still pending, Teams may not recognize the user as ready for PSTN calling.
| Calling method | Configuration to verify |
|---|---|
| Calling Plan | Calling Plan license, supported usage location, assigned user number, emergency address |
| Direct Routing | SBC health, TLS certificate, LineURI, voice routing policy, PSTN usage, route pattern |
| Operator Connect | Operator status, completed number provisioning, assigned user number, emergency details |
After making changes, ask the user to sign out of Teams, fully quit the client, and sign back in. If the configuration looks correct but the error remains, compare the affected user with a working user in the same calling model. Differences in number format, policy assignment, emergency location, or carrier provisioning status usually reveal the source of the problem.
Rank #4
- SIMPLE HEADSET SETUP: Forget complex installations – simply plug in and this noise cancelling headset is ready to go, creating a stress-free start to every day
- LIGHTEN THE LOAD: Enjoy easy-breezy phone calls and work meetings with a compact, minimalist USB headset with microphone that feels as light as a feather for all day comfort
- LOUD AND CLEAR: Loud and Clear Communication: Evolve 10 wired headset includes a noise-cancelling microphone for crystal-clear conversations in busy or loud work environments
- WEAR IT YOUR WAY: PC and laptop headset with microphone comes with an adjustable boom arm so you can wear the microphone on either the left or the right
- KINDER TO THE PLANET: USB headset with microphone is TCO certified and made from more than 50% recycled plastic; it’s the eco-friendly choice for every call
When to Escalate to Microsoft Support
Escalate the Teams calling issue to Microsoft Support when the tenant appears to be configured correctly but users still see “You are not set up to use this calling feature.” Before opening a case, confirm that the affected user has the required Teams Phone or Phone System entitlement, a valid calling policy, the correct voice routing assignment, and a provisioned phone number where applicable. If those checks are clean and the error persists across Teams desktop, web, and mobile, the problem may be related to backend provisioning, service health, or account state synchronization.
Support is also appropriate when mulle users are affected at the same time after a license change, migration, policy update, or carrier configuration change. For example, if users were recently moved from Skype for Business to Teams Only mode, migrated from Calling Plan to Direct Routing, or enabled for Operator Connect, there may be delayed or stuck provisioning in Microsoft’s service. In these cases, repeated client reinstalls or cache clearing will not resolve the issue because the account is not being recognized correctly by the Teams calling service.
Escalate when these conditions apply
- Licensing looks correct but calling remains unavailable: The user has Teams Phone or an eligible bundle, but the Calls app, dial pad, or PSTN calling capability does not appear after several hours.
- Policies are assigned correctly: The user has an allowed Teams calling policy and, where required, a voice routing policy, emergency calling policy, and dial plan.
- Phone number assignment is valid: The user has a properly assigned Calling Plan, Operator Connect, or Direct Routing number, but Teams still blocks outbound or inbound calling.
- The issue affects a group of users: Several users in the same location, license group, policy package, or migration batch report the same message.
- Provisioning appears stuck: Admin changes show correctly in the Teams admin center or PowerShell, but Teams behavior does not update after sign-out, cache reset, and waiting for replication.
- Service health shows related incidents: The Microsoft 365 admin center reports an advisory or incident involving Teams calling, PSTN connectivity, Teams Phone, or user provisioning.
When creating the support request, include concrete evidence so Microsoft can investigate without repeated back-and-forth. Provide the affected user principal names, tenant ID, approximate start time, licensing details, assigned policies, phone number type, and whether the issue occurs in the Teams web client as well as the desktop client. If Direct Routing is involved, include the Session Border Controller domain, affected routes, PSTN usage records, and examples of failed call attempts. For Operator Connect or Calling Plan, include the assigned number, country or region, carrier if applicable, and whether inbound, outbound, or both call directions fail.
For faster triage, capture screenshots of the Teams error, the user’s calling settings in the Teams admin center, and any relevant Microsoft 365 service health advisories. Admins can also export PowerShell results for the affected account, such as license assignment, Teams upgrade mode, calling policy, voice routing policy, dial plan, and phone number assignment. If Microsoft confirms that configuration is correct, they can check backend provisioning states that are not visible in the admin portals and trigger remediation where needed.
Frequently Asked Questions
Does this error mean I do not have a Teams phone number?
Not always. The message can appear if you do not have a Teams Phone license, if your calling policy blocks PSTN calling, or if your number assignment is incomplete. Ask your Teams admin to confirm that your account has the correct license, voice policy, and either a Calling Plan, Operator Connect, or Direct Routing setup.
Free tools Windows power users keep installed
One-click scans. No signup required.
Can I fix “You are not set up to use this calling feature” myself?
You can try signing out of Teams, restarting the app, checking for updates, and confirming you are using the correct work or school account. Also test in the Teams web app to see whether the issue is limited to your desktop client. If the Calls tab or dial pad is still missing, an admin likely needs to check your licensing and voice configuration.
Which Microsoft license is required for Teams calling?
For external phone calls, your account usually needs Teams Phone, either as an add-on or included in certain Microsoft 365 plans. You also need a PSTN connectivity option such as Microsoft Calling Plan, Operator Connect, or Direct Routing. Having standard Teams chat and meeting access is not enough to make calls to regular phone numbers.
How long does it take after an admin assigns Teams Phone settings?
Some changes appear within minutes, but voice licensing, number assignment, and policy updates can take several hours to fully apply. Users should sign out of Teams and sign back in after the admin makes changes. In larger tenants or complex Direct Routing environments, it may take up to 24 hours for everything to work consistently.
What should admins check if Direct Routing users see this message?
Admins should verify that the user has a Teams Phone license, is enabled for Enterprise Voice, and has the correct voice routing policy assigned. They should also check the SBC status, PSTN usage records, voice routes, dial plans, and normalization rules. If only some users are affected, compare a working user’s policies and number format with the affected account.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Bottom Line
The “You are not set up to use this calling feature” message usually means Teams cannot confirm that your account is licensed, allowed, or properly configured to place the type of call you are trying to make. For users, the fastest next steps are to sign out and back in, confirm you are using the correct account, update Teams, and ask your admin to check your voice setup.
Admins should verify Phone System licensing, calling policies, emergency settings, number assignment, and either Calling Plan, Operator Connect, or Direct Routing configuration. Once the account has the right license, policy, number, and voice route, calling should become available after Teams and Microsoft 365 finish syncing the changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
