Teams dial pad access

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/dial-pad-configuration

Published

2025-05-08

Updated

unknown

Accessed

2026-10-01

HTTP status

200

License

Microsoft Learn terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

• To validate the licence, run (Get-CsOnlineUser -Identity $user).AssignedPlan and confirm a plan whose Capability starts with MCOEV (MCOEV, MCOEV1 and so on are all acceptable) has CapabilityStatus Enabled. in context
• To check the effective calling policy, Microsoft's script reads the user's TeamsCallingPolicy assignment with Get-CsUserPolicyAssignment, falls back to Get-CsTeamsCallingPolicy -Identity Global if none is assigned, and inspects AllowPrivateCalling. in context
• To confirm a user is homed online, the dial pad article requires that Get-CsOnlineUser shows a non-null RegistrarPool and a HostingProvider value beginning with sipfed.online. in context
• In the Teams admin center, Enterprise Voice is turned on under Users > Manage users > (user) > Account tab > Assigned phone number by setting Enterprise Voice to On and saving. in context
• If a user already has a phone number but EnterpriseVoiceEnabled reads False, the admin must set it to True manually in the Teams admin center or with PowerShell. in context
• Assigning a Teams Phone licence is what allows an account to be configured as Enterprise Voice enabled, so the licence check comes before the Enterprise Voice check. in context
• If the licence and the Microsoft 365 Phone System app are assigned but the user still has no dial pad, Microsoft says EnterpriseVoiceEnabled may be set to false. in context
• Users who have no custom calling policy inherit the Global calling policy, which has AllowPrivateCalling set to true by default. in context
• An assigned phone number isn't one of the four documented dial pad prerequisites, and Enterprise Voice can be enabled without a number. So a user with no number but a licence, Enterprise Voice, online homing and private calling may still see the dial pad, but can only place calls through Shared Calling or a voice route. inferred in context
• For the Teams dial pad to display, the user must be Enterprise Voice enabled. in context
• For the Teams dial pad to display, the user must be homed online and not in Skype for Business on-premises. in context
• For the Teams dial pad to display, the user must be assigned a Teams Phone licence, which appears as the MCOEV capability. in context
• For the Teams dial pad to display, the user's effective Teams calling policy must have Make private calls (AllowPrivateCalling) enabled. in context
• After a recent change to any dial pad prerequisite, it might take a few hours for the client to receive the new settings. in context
• To actually place a call from the dial pad, the user also needs a PSTN connectivity option: Microsoft Calling Plan, Operator Connect, Teams Phone Mobile, Direct Routing, or Shared Calling. in context
• After changing any of the dial pad prerequisites, the Teams client might need to be restarted. in context
• If problems continue more than 24 hours after the changes, Microsoft says to contact Support. in context
• If the dial pad still doesn't appear, Microsoft says to check for a provisioning error with Get-CsOnlineUser -Identity $user | Select UserValidationErrors. in context

Cite this source record

APA

WarmTransfer. (2025, May 8). Teams dial pad access. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-dial-pad-configuration

BibTeX

@misc{warmtransfer-ms-learn-dial-pad-configuration,
  title  = {Teams dial pad access},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-dial-pad-configuration},
  note   = {Microsoft, accessed 2026-10-01}
}