Fix Teams Dial Pad Is Missing for a Remote User

When a remote user opens Teams and tries to make a call, the dial pad may be missing entirely. This usually happens after a policy change, a licensing issue, or a network restriction. The dial pad is not a separate app; it appears only when the user has the correct calling plan and policy assignments. This article explains why the dial pad disappears and provides step-by-step fixes you can apply from the Teams admin center.

You will learn how to check licensing, verify calling policies, and confirm network settings. The fixes work for both Teams desktop and Teams on the web. By the end, you will be able to restore the dial pad for the affected user.

Why the Dial Pad Disappears in Teams for a Remote User

The dial pad in Teams is not a standalone feature. It appears only when the user has the correct combination of licenses, policies, and network access. The most common cause is that the user does not have a Phone System license and a Microsoft Calling Plan assigned. Without these, the Calls tab shows no dial pad.

Another frequent cause is a calling policy that restricts private calls. If the policy setting Make private calls is set to Off, the dial pad is hidden. Remote users often connect through VPN or a home network, which may block the required ports for Teams calling. If the network cannot reach the Microsoft Teams signaling endpoints, the dial pad may not load.

Finally, the user might be signed in with a personal account or a guest account that does not have calling permissions. In that case, the dial pad is intentionally hidden. The following sections explain how to check each of these areas.

Steps to Diagnose and Fix the Missing Dial Pad

Before making any changes, gather the user’s full name and email address. You will need admin access to the Teams admin center and the Microsoft 365 admin center. Perform the checks in the order listed below.

Step 1: Verify the User Has the Required Licenses

1. Open the Microsoft 365 admin center
   Go to admin.microsoft.com and sign in with an account that has Global Admin or User Management Admin permissions.
2. Find the user
   Select Users > Active users, then search for the remote user’s name. Click the user to open their profile.
3. Check the license assignments
   Select the Licenses and apps tab. Confirm that the user has a Phone System license and a Microsoft Calling Plan license assigned. If either is missing, assign the licenses by checking the boxes and clicking Save changes.
4. Wait for the license to propagate
   License changes can take up to 24 hours to take effect. Ask the user to sign out of Teams and sign back in after a few minutes.

Step 2: Confirm the Calling Policy Allows Private Calls

1. Open the Teams admin center
   Go to admin.teams.microsoft.com and sign in with a Teams Administrator or Global Admin account.
2. Navigate to calling policies
   In the left navigation, select Voice > Calling policies.
3. Check the policy assigned to the user
   Find the policy that applies to the remote user. The default policy is Global (Org-wide default). Click the policy to open it.
4. Verify the private call setting
   Look for Make private calls. If it is set to Off, change it to On and click Save.
5. Check the cloud recording setting
   Some policies also hide the dial pad if Cloud recording is disabled. Confirm this setting is set to On if you want full calling features.

Step 3: Verify the Effective Policy for the User

1. Go to Users in Teams admin center
   In the Teams admin center, select Users > Manage users.
2. Select the remote user
   Click the user’s name to open their settings.
3. Check the Policies tab
   Select the Policies tab. Look at the Calling policy field. Confirm it shows the policy you edited in Step 2. If it shows Global (Org-wide default), the change should apply.
4. Apply the policy if needed
   If the user has a specific policy assigned that you did not edit, click Edit and select the correct policy, then click Apply.

Step 4: Check Network and Firewall Requirements

1. Verify the user can reach Microsoft endpoints
   Ask the user to open a browser and go to endpoints.office.com. They should see a JSON file with IP ranges. If the page does not load, the network may block access.
2. Check the required ports
   Teams uses UDP ports 3478 through 3481 for media. The user’s firewall or VPN must allow these ports. If the VPN blocks UDP, the dial pad may not appear.
3. Test without VPN
   Ask the user to disconnect from the VPN and try Teams again. If the dial pad appears, the VPN is the problem. Adjust the VPN settings to allow Teams traffic.

Step 5: Sign Out and Restart Teams

1. Sign out of Teams
   Click the profile picture at the top right, then select Sign out.
2. Close Teams completely
   Right-click the Teams icon in the system tray and select Quit.
3. Restart Teams
   Open Teams again and sign in. Check if the dial pad appears on the Calls tab.

If Teams Still Has No Dial Pad After the Main Fix

Sometimes the dial pad is still missing after you apply the fixes. The following issues are common in remote work environments.

Teams Shows a Blank Calls Tab

If the Calls tab is blank, the user may be using an outdated Teams client. Ask the user to update Teams by clicking the ellipsis next to their profile picture, then select Check for updates. If the update does not help, uninstall Teams and reinstall the latest version from teams.microsoft.com/downloads.

The Dial Pad Works on the Web but Not the Desktop

This indicates a local cache issue in the desktop app. Clear the Teams cache by deleting the folder %appdata%\Microsoft\Teams on Windows. Then restart Teams. The app will rebuild the cache and the dial pad should appear.

The User Has a Phone System License but No Calling Plan

A Phone System license alone does not give the user a dial pad. They also need a calling plan or a direct routing setup. If your organization uses direct routing, ensure the user is assigned a voice routing policy. Without a calling plan, the dial pad is hidden.

Teams Desktop vs Teams on the Web for Calling: Key Differences

Item	Teams Desktop	Teams on the Web
Dial pad availability	Full dial pad with number keypad	Dial pad available but may lack some keys
Media quality	Optimized for audio and video	Depends on browser and network
Cache issues	Local cache can cause missing UI	Browser cache can be cleared easily
Update frequency	Automatic updates via app	Updates with the browser
Call transfer and forwarding	Full feature set	Limited but supports basic calls

Both versions require the same licenses and policies. If the dial pad works in one but not the other, the issue is usually local to the desktop app or the browser.

Restoring the Dial Pad for Your Remote User

You now know the main causes of a missing dial pad in Teams for a remote user. Start by verifying licenses, then check the calling policy, and finally test the network. The fixes are straightforward and can be done from the admin centers.

After applying the fixes, ask the user to sign out and back in. If the dial pad still does not appear, check the direct routing configuration or contact Microsoft support. As a next step, review your organization’s calling policies to ensure all remote users have the same settings.