Remote Team Unable to Make Outbound Calls: The Licensing and Policy Gaps That Block Teams Phones
When your remote team is suddenly unable to make outbound calls, the problem is rarely the phone itself. In most cases, the issue stems from a mismatch between Microsoft Teams licensing, tenant calling policies, and the type of calling plan provisioned—or the absence of one entirely. Unlike traditional desk phones that fail visibly when unplugged, Teams calling failures often present no clear error message, leaving remote workers staring at grayed-out dial pads or silent call attempts while IT scrambles to trace permission layers across the Microsoft 365 admin center.
This guide draws on recurring themes in Microsoft Teams administrator discussions and small business IT troubleshooting forums on Reddit and the Microsoft Tech Community, gathered March 2025.
Key Takeaways
- Outbound calling in Teams requires either a Microsoft Calling Plan, Direct Routing, or Operator Connect—not just a Teams license.
- Most “unable to make outbound calls” errors trace to missing E5 or Teams Phone licenses, not tenant connectivity issues.
- Calling policies set at the tenant level can override user licenses, blocking outbound calls even when the dial pad appears active.
- Remote teams using personal devices or unmanaged networks may encounter carrier-level blocks that look like Teams failures.
- Testing outbound calls as the affected user, not as an admin, is the fastest way to surface policy inheritance problems.
- Emergency calling location assignment is required for outbound public switched telephone network (PSTN) calls in many jurisdictions; missing addresses block calls silently.
Table of Contents
- The Licensing Gap: When Teams Licenses Don’t Include Phone System
- Why a Calling Plan or Direct Routing Setup Is Non-Negotiable
- Tenant Calling Policies That Silently Block Outbound Calls
- Device and Network Conditions That Mimic Teams Failures
- Emergency Location Assignment and Regulatory Blocks
- Diagnostic Steps to Identify the Real Cause
- Frequently Asked Questions
The Licensing Gap: When Teams Licenses Don’t Include Phone System
The most common reason a remote team is unable to make outbound calls in Teams is that the users do not hold a Teams Phone license. Microsoft Teams comes in multiple licensing tiers, and the ability to place calls to external phone numbers—what Microsoft calls PSTN calling—requires a separate Phone System add-on or a plan bundle that includes it, such as Microsoft 365 E5.
A user with a Microsoft 365 Business Basic or Business Standard license can use Teams for chat, meetings, and internal voice calls between other Teams users. They can see the dial pad in the Teams client. But when they attempt to dial an external number, the call fails without explanation, or the dial pad remains inactive. From the user’s perspective, Teams looks fully functional. From the licensing perspective, the Phone System capability is simply absent.
According to Microsoft Learn’s guide on configuring Teams Phone, enabling outbound calling requires at minimum a Teams Phone license plus one of three connectivity options: a Microsoft Calling Plan, Direct Routing to a session border controller, or Operator Connect through a certified carrier partner. The Teams Phone license itself does not include dial tone; it unlocks the Phone System feature set, which must then be connected to the public telephone network through one of those three paths.
Small businesses and distributed teams often purchase Microsoft 365 subscriptions that bundle collaboration tools but do not include telephony. The gap becomes visible only when a remote employee needs to make their first outbound call. At that point, administrators must either assign a Teams Phone license to each affected user or upgrade the entire tenant to a plan that includes Phone System by default.
| License Type | Includes Teams Phone | Outbound PSTN Calling |
|---|---|---|
| Microsoft 365 Business Basic | No | Not available |
| Microsoft 365 Business Standard | No | Not available |
| Microsoft 365 E3 | No (add-on required) | Requires Teams Phone add-on + calling plan |
| Microsoft 365 E5 | Yes | Requires calling plan or Direct Routing |
| Teams Phone standalone | Yes | Requires calling plan or Direct Routing |
License assignment changes take effect within minutes for most features, but telephony routing can take up to 24 hours to propagate fully across Microsoft’s backend. If your remote team is unable to make outbound calls immediately after assigning new licenses, confirm the license appears in the user’s profile under the Microsoft 365 admin center, then allow time for provisioning before escalating to support.
Why a Calling Plan or Direct Routing Setup Is Non-Negotiable
Even when Teams Phone licenses are correctly assigned, outbound calls will fail if the tenant lacks a configured connection to the PSTN. Microsoft does not provide dial tone by default. The administrator must select and configure one of three PSTN connectivity options: a Microsoft Calling Plan, Direct Routing, or Operator Connect.
Microsoft Calling Plans are the simplest path for small and mid-sized businesses. They function like a traditional phone service subscription purchased directly from Microsoft, bundled with per-user monthly minutes for domestic or international calling. Plans are available only in specific countries, and pricing varies by region and included minutes. Once a Calling Plan is assigned to a user who already holds a Teams Phone license, that user gains the ability to dial external numbers immediately, assuming no tenant policies interfere.
Direct Routing is the enterprise alternative. It connects Microsoft Teams to an on-premises or cloud-hosted session border controller, which in turn connects to a carrier or SIP trunk of the organization’s choice. Direct Routing offers greater control over call routing, number porting, and cost management, but it requires technical configuration and ongoing maintenance. Many remote teams unable to make outbound calls on a newly deployed Direct Routing setup trace the problem to incomplete route policies, missing voice routing rules, or PSTN usage settings that were copied from documentation but never tested under the actual user’s context.
Operator Connect allows organizations to use certified carrier partners integrated directly into the Teams admin center. The carrier provisions phone numbers and PSTN connectivity while Microsoft handles the Teams client integration. Configuration is simpler than Direct Routing, but availability depends on geographic region and carrier participation. According to Microsoft’s guide on making and receiving calls in Teams, users must have both a valid phone number assigned and a functional PSTN connection before outbound calling becomes active.
Administrators sometimes assume that purchasing a Calling Plan automatically provisions all licensed users, but phone numbers must be assigned individually or via PowerShell scripting. A user with a Teams Phone license and a Calling Plan subscription but no assigned phone number will see the dial pad but cannot complete outbound calls. The Teams client may display the option to place calls, yet every attempt results in a silent failure or a generic “call could not be completed” message.
Tenant Calling Policies That Silently Block Outbound Calls
Licensing and calling plans control whether outbound calling is possible in principle. Calling policies control whether it is allowed in practice. Microsoft Teams administrators configure calling policies at the tenant level to restrict or permit specific telephony behaviors, including outbound PSTN calling, call forwarding, voicemail, and simultaneous ring. These policies apply to users or groups, and they override local client settings.
A recurring issue in administrator troubleshooting threads involves global calling policies set to block outbound calls during initial tenant setup or compliance reviews. The policy remains in effect even after users receive proper licenses and assigned phone numbers. The user sees an active dial pad and can initiate a call, but Teams blocks the connection before it reaches the carrier. No error appears in the client; the call simply ends.
The default Teams calling policy permits outbound PSTN calls, but custom policies created for security, cost control, or compliance often disable this setting. If a remote team is unable to make outbound calls while other users in the same tenant can, check whether the affected users are assigned to a restrictive calling policy. In the Teams admin center under Voice → Calling policies, verify that the policy assigned to each user includes “Make private calls” set to On.
Policy inheritance in Teams follows a hierarchy. If a user has no directly assigned policy, they inherit the global default. If a custom policy is assigned to a security group containing the user, that policy takes precedence. Administrators troubleshooting outbound call failures should review both individual user policy assignments and group-based policies, especially when onboarding remote employees into existing security structures copied from previous deployments.
Another common policy issue involves emergency calling policies. In some jurisdictions, Teams requires an emergency calling policy to be configured and associated with a valid emergency location before allowing any outbound PSTN calls. The logic here is regulatory: if a user cannot place an emergency call with a traceable location, the system blocks all outbound calls to prevent liability. This behavior is not always obvious from the admin interface, and affected users see no indication that location data is the root cause.
Device and Network Conditions That Mimic Teams Failures
Not every outbound calling failure originates in Microsoft’s tenant configuration. Remote teams working from home networks, mobile hotspots, or coworking spaces encounter device-level and network-level issues that present identical symptoms to licensing or policy problems.
On iPhones and Android devices, the Teams mobile app requires explicit microphone and network permissions to place calls. If a user previously denied microphone access or restricted background data, outbound calls fail silently. The dial pad appears functional, but the call never connects. Users troubleshooting why their remote team is unable to make outbound calls on iPhone should verify that Teams has microphone access enabled under Settings → Privacy → Microphone, and that cellular or Wi-Fi data is not restricted for the Teams app under Settings → Cellular or Settings → Teams → Background App Refresh.
Corporate VPN configurations sometimes block the UDP ports Teams uses for real-time media. When a remote worker connects through a VPN that restricts UDP traffic or applies aggressive firewall rules, outbound calls may fail or produce one-way audio where the caller cannot hear the recipient. The user sees the call connect, the timer starts, but no audio passes. Teams attempts to fall back to TCP transport, which adds latency and reduces call quality, but some VPN policies block the fallback entirely. Testing outbound calls while disconnected from the VPN helps isolate whether network policy is the cause.
Carrier-level restrictions also affect mobile users. Some mobile carriers block SIP traffic or VoIP applications on certain plans to preserve bandwidth for traditional voice services. If a remote team member is unable to make outbound calls while using a mobile data connection but can complete calls over Wi-Fi, the issue is likely carrier-imposed throttling or port blocking. Switching to a different network or enabling Wi-Fi calling within the carrier’s settings may resolve the issue, though this does not address the underlying Teams configuration.
Browser-based Teams clients have limited calling capabilities compared to desktop and mobile apps. Users accessing Teams through a web browser may see a dial pad but cannot place outbound PSTN calls unless the browser is fully supported and the user has granted microphone permissions through the browser’s site settings. Microsoft’s troubleshooting guide for calling in Teams recommends using the desktop app for telephony features whenever possible, as browser support varies across platforms and versions.
Emergency Location Assignment and Regulatory Blocks
Microsoft Teams enforces emergency location requirements for PSTN calling in many countries, including the United States, Canada, and the United Kingdom. Before a user can place outbound calls, an administrator must assign a valid emergency address to that user’s phone number. This address is transmitted to emergency services when the user dials an emergency number, and in some cases the system will not allow any outbound calls until the location is configured.
When a remote team is unable to make outbound calls and licenses appear correctly assigned, verify that each user has an emergency location configured in the Teams admin center under Voice → Phone numbers or Voice → Emergency addresses. The location must include a complete physical address, not a generic city or region. If the emergency address field is blank or invalid, outbound calling may be blocked entirely or limited to internal Teams-to-Teams calls.
For remote teams working from home or traveling frequently, maintaining accurate emergency locations creates an operational challenge. Microsoft supports dynamic emergency calling, where the Teams client detects the user’s location based on network information and updates the emergency address automatically. However, dynamic location requires network configuration—specifically, trusted IP addresses or subnet mappings in the Teams admin center—and does not work reliably on all networks. Small businesses often lack the IT infrastructure to map every remote worker’s home router, leaving manual address updates as the only option.
Failure to configure emergency locations carries both technical and legal consequences. From a technical perspective, users cannot place outbound calls. From a legal perspective, organizations may face regulatory penalties if emergency services cannot locate a caller during a crisis. Administrators should prioritize emergency location assignment during user onboarding and enforce periodic location audits for remote workers who change physical locations frequently.
Diagnostic Steps to Identify the Real Cause
When troubleshooting why a remote team is unable to make outbound calls, follow a structured diagnostic sequence to isolate the cause without guessing. Start with licensing, verify connectivity, test policies, and confirm device conditions in that order.
Step one: Confirm that each affected user holds both a Microsoft Teams license and a Teams Phone license. Open the Microsoft 365 admin center, navigate to Users → Active users, select the user, and review the Licenses and apps tab. If Teams Phone or Phone System is not listed, assign the license and wait 15 minutes for propagation before retesting.
Step two: Verify that the user has an assigned phone number and an active calling plan or Direct Routing connection. In the Teams admin center, go to Voice → Phone numbers and confirm the user’s number appears with a status of Assigned. If the number shows as Available or Unassigned, assign it to the user. If no numbers are available, purchase additional Calling Plan numbers or configure Direct Routing trunks.
Step three: Check the user’s calling policy. In the Teams admin center, navigate to Voice → Calling policies, locate the policy assigned to the user, and confirm that “Make private calls” is enabled. If the user inherits the global policy, open the global policy and verify the same setting. If a restrictive policy is in place, either modify the policy or assign the user to a less restrictive one.
Step four: Confirm that the user has an emergency address assigned. In the Teams admin center, go to Voice → Emergency addresses and verify that the user’s phone number is associated with a complete, validated address. If the address is missing or incomplete, add or update it and test outbound calling again.
Step five: Test the call as the affected user, not as an administrator. Many calling issues stem from policy inheritance that applies to standard users but not to tenant admins. Have the user attempt an outbound call to a known working number while you observe. If the call succeeds when you test it under your admin account but fails when the user tests it, the problem is almost certainly policy-based.
Step six: Review the Teams client diagnostics. In the Teams desktop app, the user can access call quality information under Settings → Calls → Call history. Failed calls appear with error codes. Common codes include 403 Forbidden (policy block), 404 Not Found (number not assigned), and 503 Service Unavailable (PSTN connectivity issue). Match the error code to Microsoft’s documentation to identify the specific failure point.
If all licensing, configuration, and policy settings appear correct but outbound calls still fail, test from a different device or network to rule out local issues. If the user can place calls from a personal mobile device over cellular data but not from their work laptop over the corporate VPN, the issue lies in network configuration rather than Teams setup. Work with your network team to verify that UDP ports 3478-3481 and TCP port 443 are open for Teams media traffic.
Conclusion
When a remote team is unable to make outbound calls, the problem is almost never a single misconfiguration. It is a chain of dependencies—licensing, calling plans, policies, emergency locations, and network conditions—that must align before Teams can route a call to the public telephone network. The dial pad appearing in the client does not guarantee calling capability; it reflects only the license level, not the full stack of telephony prerequisites.
Start troubleshooting with the most common causes: verify that affected users hold Teams Phone licenses, confirm that phone numbers are assigned, check calling policies for restrictions, and ensure emergency addresses are configured. Test as the user, not as an admin, to catch policy inheritance issues. If licensing and policies are correct, shift focus to network and device conditions, particularly for remote workers on VPNs, mobile data, or unsupported browsers. Business owners managing distributed teams should audit telephony configurations during onboarding and after any Microsoft 365 license changes to prevent silent failures that look like user error but stem from incomplete backend setup. For detailed configuration guidance and error code reference, consult Microsoft’s official Teams Phone planning documentation and test every change in a controlled environment before rolling it out to the entire team.
Frequently Asked Questions
Why can’t I make outbound calls in Teams?
The most common reason you cannot make outbound calls in Teams is that your account lacks a Teams Phone license or an assigned calling plan. Even if you have a Microsoft 365 license that includes Teams collaboration features, outbound calling to phone numbers requires a separate Phone System license and either a Microsoft Calling Plan, Direct Routing connection, or Operator Connect setup. Check with your administrator to confirm your licenses and phone number assignment.
Why is my phone saying I’m not allowed to make outbound calls?
If your phone or Teams client displays a message that you are not allowed to make outbound calls, the issue is typically a calling policy restriction set by your organization’s IT administrator. Calling policies in Teams can block outbound PSTN calls, forwarding, or voicemail for specific users or groups. Your administrator can review your assigned calling policy in the Teams admin center and enable the “Make private calls” setting if it is currently restricted.
Why am I not able to make an outgoing call?
Inability to make outgoing calls can stem from several causes: missing licenses, unassigned phone numbers, restrictive calling policies, missing emergency addresses, or network and device issues. Start by confirming that you have an active Teams Phone license and an assigned phone number in your Microsoft 365 account. Then verify that your calling policy permits outbound calls and that an emergency address is configured. If all settings appear correct, test from a different device or network to rule out local connectivity problems.
Why won’t my outbound calls work?
Outbound calls may fail to work even when the dial pad appears active because of missing backend configuration. The Teams client shows calling features based on your license, but the actual ability to connect calls depends on tenant-level PSTN connectivity—either a Calling Plan, Direct Routing, or Operator Connect setup. If your organization recently migrated to Teams or added Phone System licenses, the administrator may not yet have configured the calling infrastructure. Contact your IT team to confirm that PSTN connectivity is fully provisioned.
How do I make an outbound call on Teams?
To make an outbound call in Microsoft Teams, open the Teams app and select the Calls icon in the left navigation. Click the dial pad icon, enter the phone number including country code if calling internationally, and press the Call button. For the call to connect successfully, you must have a Teams Phone license, an assigned phone number, an active calling plan or Direct Routing connection, appropriate calling policies, and a configured emergency address. If any of these elements is missing, the call will fail or the dial pad may be disabled.
The Business Authority 360 Editorial Team studies business software and services through the lens of what actually happens after purchase. Our comparisons are built by identifying recurring themes across business reviews and community discussions on platforms like G2, TrustRadius, and Reddit. We surface the support experiences, billing patterns, and daily friction that feature checklists leave out. Every article notes when and where its insights were gathered. Learn more about how we research.
How PayPal's relentless focus on growth over profits created the
Read more
Key Takeaways Automation by accounting software saves time and reduces
Read more
Recession Panic: Are SMBs Ditching Marketing Budgets First – And
Read more
Post Malone's billion-dollar success reveals why the richest musicians diversify
Read more
