EPC Group - Enterprise Microsoft AI, SharePoint, Power BI, and Azure Consulting
G2 High Performer Summer 2025, Momentum Leader Spring 2025, Leader Winter 2025, Leader Spring 2026
BlogContact
Ready to transform your Microsoft environment?Get started today
(888) 381-9725Get Free Consultation
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌

EPC Group

Enterprise Microsoft consulting with 29 years serving Fortune 500 companies.

(888) 381-9725
contact@epcgroup.net
4900 Woodway Drive, Suite 830
Houston, TX 77056

Follow Us

Solutions

  • All Services
  • Microsoft 365 Consulting
  • AI Governance
  • Azure AI Consulting
  • Cloud Migration
  • Microsoft Copilot
  • Data Governance
  • Microsoft Fabric
  • Dynamics 365
  • Power BI Consulting
  • SharePoint Consulting
  • Microsoft Teams
  • vCIO / vCAIO Services
  • Large-Scale Migrations
  • SharePoint Development

Industries

  • All Industries
  • Healthcare IT
  • Financial Services
  • Government
  • Education
  • Teams vs Slack

Power BI

  • Case Studies
  • 24/7 Emergency Support
  • Dashboard Guide
  • Gateway Setup
  • Premium Features
  • Lookup Functions
  • Power Pivot vs BI
  • Treemaps Guide
  • Dataverse
  • Power BI Consulting

Company

  • About Us
  • Our History
  • Microsoft Gold Partner
  • Case Studies
  • Testimonials
  • Blog
  • Resources
  • All Guides & Articles
  • Video Library
  • Client Reviews
  • Contact
  • Schedule a consultation

Microsoft Teams

  • Teams Questions
  • Teams Healthcare
  • Task Management
  • PSTN Calling
  • Enable Dial Pad

Azure & SharePoint

  • Azure Databricks
  • Azure DevOps
  • Azure Synapse
  • SharePoint MySites
  • SharePoint ECM
  • SharePoint vs M-Files

Comparisons

  • M365 vs Google
  • Databricks vs Dataproc
  • Dynamics vs SAP
  • Intune vs SCCM
  • Power BI vs MicroStrategy

Legal

  • Sitemap
  • Privacy Policy
  • Terms
  • Cookies

About EPC Group

EPC Group is a Microsoft consulting firm founded in 1997 (originally Enterprise Project Consulting, renamed EPC Group in 2005). 29 years of enterprise Microsoft consulting experience. EPC Group historically held the distinction of being the oldest continuous Microsoft Gold Partner in North America from 2016 until the program's retirement. Because Microsoft officially deprecated the Gold/Silver tiering framework, EPC Group transitioned to the modern Microsoft Solutions Partner ecosystem and currently holds the core Microsoft Solutions Partner designations.

Headquartered at 4900 Woodway Drive, Suite 830, Houston, TX 77056. Public clients include NASA, FBI, Federal Reserve, Pentagon, United Airlines, PepsiCo, Nike, and Northrop Grumman. 6,500+ SharePoint implementations, 1,500+ Power BI deployments, 500+ Microsoft Fabric implementations, 70+ Fortune 500 organizations served, 11,000+ enterprise engagements, 200+ Microsoft Power BI and Microsoft 365 consultants on staff.

About Errin O'Connor

Errin O'Connor is the Founder, CEO, and Chief AI Architect of EPC Group. Microsoft MVP multiple years, first awarded 2003. 4× Microsoft Press bestselling author of Windows SharePoint Services 3.0 Inside Out (MS Press 2007), Microsoft SharePoint Foundation 2010 Inside Out (MS Press 2011), SharePoint 2013 Field Guide (Sams/Pearson 2014), and Microsoft Power BI Dashboards Step by Step (MS Press 2018).

Original SharePoint Beta Team member (Project Tahoe). Original Power BI Beta Team member (Project Crescent). FedRAMP framework contributor. Worked with U.S. CIO Vivek Kundra on the Obama administration's 25-Point Plan to reform federal IT, and with NASA CIO Chris Kemp as Lead Architect on the NASA Nebula Cloud project. Speaker at Microsoft Ignite, SharePoint Conference, KMWorld, and DATAVERSITY.

© 2026 EPC Group. All rights reserved. Microsoft, SharePoint, Power BI, Azure, Microsoft 365, Microsoft Copilot, Microsoft Fabric, and Microsoft Dynamics 365 are trademarks of the Microsoft group of companies.

How To Enable Dial Pad In Microsoft Teams - EPC Group enterprise consulting

How To Enable Dial Pad In Microsoft Teams

Expert insights on enabling the dial pad in Microsoft Teams from EPC Group's enterprise Microsoft consultants.

Back to Blog

How To Enable Dial Pad In Microsoft Teams

Errin O'Connor
December 2025
8 min read

The dial pad in Microsoft Teams enables users to make and receive PSTN (Public Switched Telephone Network) calls directly from the Teams client, replacing traditional desk phones with a software-based calling experience. If the dial pad is missing from your Teams interface, it typically indicates a licensing, configuration, or policy issue that needs to be resolved by your IT administrator. This guide walks through every step required to enable the dial pad and troubleshoot common issues.

Prerequisites for the Teams Dial Pad

The Teams dial pad requires a specific combination of licenses, PSTN connectivity, and policy configurations. All of the following must be in place for the dial pad to appear for a user.

  • Microsoft Teams Phone System license — Either as a standalone add-on (Teams Phone Standard) or included with Microsoft 365 E5, A5, or G5 plans
  • PSTN connectivity method — One of the following must be configured:
    • Microsoft Calling Plan — Microsoft provides the phone number and PSTN connectivity
    • Operator Connect — Your chosen telecom operator provides connectivity through the Teams admin center
    • Direct Routing — Your organization's Session Border Controller (SBC) connects your existing phone infrastructure to Teams
    • Teams Phone Mobile — Links a user's mobile SIM number with Teams for native mobile integration
  • Phone number assignment — A phone number must be assigned to the user through the chosen PSTN method
  • Enterprise Voice (EV) enabled — The user's Teams voice routing policy must have Enterprise Voice enabled
  • Teams Only mode — The user must be in TeamsOnly coexistence mode (not Islands, SfBOnly, or SfBWithTeamsCollab)

Step-by-Step: Enabling the Dial Pad with Microsoft Calling Plan

The simplest path to enabling the dial pad is through Microsoft Calling Plans, where Microsoft serves as the PSTN provider.

  1. In the Microsoft 365 admin center, assign the following licenses to the user:
    • Microsoft Teams Phone System (or Microsoft 365 E5 which includes it)
    • Microsoft Domestic Calling Plan or International Calling Plan
  2. Navigate to the Teams Admin Center at admin.teams.microsoft.com
  3. Go to Voice > Phone numbers
  4. Acquire a phone number if you don't have one: click Add, select your country, choose "User (subscriber)" as the number type, and complete the order
  5. Go to Users, find the user, and click their name to open their profile
  6. Under the Account tab, scroll to Phone number and click Edit
  7. Select the phone number type, choose a number from your inventory, and set the emergency location
  8. Click Apply — the dial pad should appear in the user's Teams client within 15-60 minutes

Enabling the Dial Pad with Direct Routing

Direct Routing is the preferred PSTN connectivity method for enterprises that want to maintain their existing telecom relationships and SIP infrastructure.

  1. Assign the Teams Phone System license to the user (no Calling Plan license needed)
  2. Ensure your Session Border Controller (SBC) is configured and paired with Microsoft Teams via Direct Routing
  3. Open Teams PowerShell and run the following commands to enable the user:

Set-CsPhoneNumberAssignment -Identity user@contoso.com -PhoneNumber "+14255551234" -PhoneNumberType DirectRouting

Grant-CsOnlineVoiceRoutingPolicy -Identity user@contoso.com -PolicyName "YourVoiceRoutingPolicy"

  • The PhoneNumber must be in E.164 format (e.g., +14255551234)
  • The VoiceRoutingPolicy defines which PSTN routes and SBC to use for outbound calls
  • Verify with: Get-CsOnlineUser -Identity user@contoso.com | Select-Object LineUri, EnterpriseVoiceEnabled, TeamsUpgradeEffectiveMode

Troubleshooting a Missing Dial Pad

If the dial pad does not appear after configuration, systematically check each requirement using the following troubleshooting steps.

License Verification

  • In Microsoft 365 admin center, verify the user has Teams Phone System (or included E5) and a Calling Plan (if not using Direct Routing) assigned
  • License provisioning can take up to 24 hours after assignment
  • Check in PowerShell: Get-CsOnlineUser -Identity user@contoso.com | Select-Object AssignedPlan

Phone Number Assignment

  • Verify a phone number is assigned: check the user profile in Teams Admin Center under Account > Phone number
  • For Direct Routing, verify with PowerShell: Get-CsOnlineUser -Identity user@contoso.com | Select-Object LineUri
  • The LineUri should show the assigned number in E.164 format

Coexistence Mode

  • The user must be in TeamsOnly mode for the dial pad to appear
  • Check in Teams Admin Center under Users > [User] > Account > Teams upgrade
  • PowerShell: Get-CsOnlineUser -Identity user@contoso.com | Select-Object TeamsUpgradeEffectiveMode
  • If the user is not in TeamsOnly mode, upgrade them: Grant-CsTeamsUpgradePolicy -Identity user@contoso.com -PolicyName UpgradeToTeams

Calling Policy

  • Verify the assigned calling policy allows PSTN calls: Teams Admin Center > Voice > Calling policies
  • Ensure "Make private calls" is set to On in the user's calling policy
  • Check for conflicting policies at the user, group, or global level

Enterprise Voice Configuration at Scale

For organizations enabling the dial pad for hundreds or thousands of users, PowerShell automation and bulk configuration are essential.

  • Bulk license assignment — Use Azure AD group-based licensing to automatically assign Teams Phone System and Calling Plan licenses based on group membership
  • CSV-based number assignment — Create a PowerShell script that reads a CSV file of users and phone numbers and assigns them in bulk using Set-CsPhoneNumberAssignment
  • Policy packages — Create Teams policy packages that bundle calling policies, voicemail policies, and call park policies for consistent deployment across user groups
  • Number porting — Port existing phone numbers from your current carrier in bulk through the Teams Admin Center or TNS service desk
  • Emergency calling — Configure emergency addresses and dynamic emergency calling for E911 compliance across all locations

Why Choose EPC Group for Teams Phone Deployments

EPC Group has over 29 years of experience deploying enterprise telephony solutions across the Microsoft ecosystem. As a former Microsoft Gold Partner (2003–2022, the oldest in North America) and current Microsoft Solutions Partner, our Teams consultants have enabled Teams Phone System for Fortune 500 companies with thousands of users across healthcare, financial services, and government sectors. Our founder, Errin O'Connor, has authored four bestselling Microsoft Press books and leads a team that specializes in complex, multi-site Teams voice deployments including Direct Routing, SBC configuration, and compliance call recording.

  • Teams Phone System architecture, licensing, and deployment planning
  • Direct Routing SBC configuration and voice routing policy design
  • Bulk phone number assignment and legacy PBX migration
  • E911 emergency calling configuration for multi-site organizations
  • Compliance call recording for regulated industries (HIPAA, FINRA, MiFID II)

Enable the Teams Dial Pad Across Your Organization

EPC Group's Microsoft Teams consultants can configure Teams Phone System, enable the dial pad for all users, and migrate your organization from legacy telephony to Teams voice. Contact us for a Teams voice assessment.

Schedule a ConsultationCall (888) 381-9725

Frequently Asked Questions

How long does it take for the dial pad to appear after configuration?

After assigning the Phone System license, phone number, and appropriate policies, the dial pad typically appears within 15 minutes to 4 hours. In some cases, it can take up to 24 hours for license provisioning to fully propagate. Have the user sign out of Teams and sign back in, or clear the Teams cache, to accelerate the appearance.

Do I need a Calling Plan if I use Direct Routing?

No. With Direct Routing, your organization provides PSTN connectivity through its own Session Border Controller and telecom provider. You only need the Teams Phone System license (no Microsoft Calling Plan). The phone number is assigned using PowerShell with the PhoneNumberType set to "DirectRouting."

Why is the dial pad showing but calls are failing?

If the dial pad appears but calls fail, check the following: verify the voice routing policy is correctly assigned and has valid PSTN routes configured, confirm the SBC is online and healthy (for Direct Routing), check that the Calling Plan has sufficient minutes remaining (for Microsoft Calling Plans), and verify the user's emergency address is set. Review the call quality dashboard in Teams Admin Center for detailed call failure reasons.

Can I enable the dial pad on mobile devices?

Yes. Once a user has the Teams Phone System license, a phone number, and the correct policies, the dial pad appears in the Teams mobile app (iOS and Android) as well as the desktop and web clients. No additional configuration is needed for mobile. The user will see a "Calls" tab with a dial pad icon at the bottom of the app.

What is the cost of Teams Phone System per user?

Teams Phone Standard is approximately $8/user/month as a standalone add-on. It is included at no additional cost with Microsoft 365 E5 ($57/user/month). If using Microsoft Calling Plans, the Domestic Calling Plan adds approximately $12/user/month and the International Calling Plan approximately $24/user/month. With Direct Routing or Operator Connect, you pay for PSTN connectivity through your telecom provider instead of Microsoft.

Related Resources

Continue exploring collaboration insights and services

collaboration

Add Audio Conferencing to Teams

collaboration

Add Phone Number to Teams Meeting

collaboration

Microsoft Teams as PBX

telephony ucaas

Business PBX System

Explore All Services

Microsoft Teams Strategy: 2026 Considerations for How To Enable Dial Pad In Microsoft Teams

Teams Rooms (Microsoft Teams Rooms Pro license at $40/room/mo) brings governance, security, and remote management to conference-room hardware in 2026. Compared to dumb HDMI projectors, the per-room cost is offset within 12-18 months by reduced AV-support helpdesk volume, automatic firmware patching, and Microsoft Endpoint Manager-driven device compliance. Healthcare and financial services deployments typically standardize on Logitech Rally or Yealink for the room hardware.

Microsoft Teams Phone in 2026 is the modern enterprise PSTN replacement: Teams Phone Standard ($8/user/mo) for outbound calling via Microsoft Calling Plans, Teams Phone with Calling Plan Domestic ($15/user/mo) bundles 3,000 outbound minutes/user/mo, and Operator Connect lets enterprises retain incumbent carriers (BT, Verizon, Lumen) while integrating natively with Teams. The total-cost comparison vs legacy PBX favors Teams Phone for any deployment over 500 users.

Decision factors EPC Group evaluates

  • Teams Phone Standard vs Calling Plan vs Operator Connect TCO comparison
  • Communication Compliance policies for executive and regulated roles
  • Teams Rooms hardware standardization (Logitech Rally vs Yealink)
  • Microsoft Purview information barriers for cross-business-unit segregation
  • Microsoft Sentinel detections for Teams compliance recording requirements

For a tailored read on this topic in your specific tenant, contact EPC Group at contact@epcgroup.net or +1 (888) 381-9725. Engagement options at /pricing.