Configure Shared Calling

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/shared-calling-setup

Published

2026-07-28

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

Microsoft Learn content; CC BY 4.0 for docs text per MicrosoftDocs repository, verify before reuse; no-redistribution; short excerpts and locators only

Source notes citing this source

• If inbound calling is required, the resource account must be associated with a configured Auto attendant scoped to the users it needs to reach. in context
• Shared Calling policies are managed in PowerShell with New-, Get-, Set-, Remove- and Grant-CsTeamsSharedCallingRoutingPolicy, and in the Teams admin center under Voice > Shared calling policies. in context
• Calling Plan service numbers cannot be used for Shared Calling in Romania, the Czech Republic, Hungary, Singapore, New Zealand, Australia and Japan, or for a limited number of existing Calling Plan service numbers in other countries. in context
• If the resource account uses a Microsoft Calling Plan service number, the resource account needs a Pay-As-You-Go Calling Plan license. in context
• The Configure Shared Calling article says calls on a Calling Plan service number are funded with pay-as-you-go minutes, and that Communications Credits are needed only when the Calling Plan subscription is under a Microsoft Online Subscription Agreement. disputed in context
• If the resource account uses a Direct Routing number, the resource account must have an online voice routing policy with valid PSTN usages. in context
• If the resource account has a Calling Plan service number, the emergency callback numbers must be Calling Plan subscriber numbers, not service numbers. in context
• Emergency callback numbers are optional in a Shared Calling policy; with none defined, the resource account's number is used on emergency calls. in context
• An emergency number used in a Shared Calling policy cannot be deleted or reassigned until it has been removed from the policy, for example with Set-CsTeamsSharedCallingRoutingPolicy -EmergencyNumbers @{remove=...}. in context
• Emergency callback numbers must accept inbound PSTN calls, and for Calling Plan and Operator Connect they must be available within the tenant. in context
• Falling back to the resource account number as the emergency callback number is not supported when that number is a Calling Plan toll-free service number; in that case Calling Plan subscriber numbers must be added as emergency numbers. in context
• Every Shared Calling user must be assigned an emergency call routing policy, whether the resource account uses Calling Plan, Operator Connect or Direct Routing. in context
• For Shared Calling, the user's emergency call routing policy should have no online PSTN usages when the resource account uses Calling Plan or Operator Connect, and must have them when it uses Direct Routing. in context
• Emergency calling for Shared Calling is available globally, but outside North America the customer must contact each carrier to upload the emergency addresses of the resource account numbers into the carrier's emergency database. in context
• By default Shared Calling users call each other by dialing by name; optional extension dialing works by giving each user a Direct Routing number with a unique extension, for example the resource account's digits plus ;ext=. in context
• Some Calling Plan markets do not allow a location to be set on service numbers; Microsoft directs customers in those markets to the Telephone Number Services service desk. in context
• The emergency location sent for a Shared Calling user is the dynamic location from the Teams client if available, otherwise the static location assigned to the resource account's phone number. in context
• A user enabled for Shared Calling must not have a phone number assigned; they must hold a Teams Phone license and be Enterprise Voice enabled. in context
• If the resource account's number is removed, reassigned or ported, the Shared Calling policy stays in place but outbound calls fail for users still set to call from that number. in context
• When the resource account has an Operator Connect number, Microsoft says to confirm Shared Calling support with the operator; otherwise no funding step is needed for Operator Connect. in context
• The same resource account can be used in more than one Shared Calling policy. in context
• The shared resource account can hold a Calling Plan service number, an Operator Connect number or a Direct Routing number. in context
• All numbers in one Shared Calling policy, both the resource account number and the emergency callback numbers, must be of the same number type and country. in context
• Microsoft documents Shared Calling setup as ten ordered steps: license users and enable voice; give the resource account a number; associate the resource account with an Auto attendant; give it an emergency location; configure service-number funding or routing; create a voice routing policy with no PSTN usages; enable emergency calling for users; create the Shared Calling policy; assign it to users; and optionally configure extension dialing. in context
• If Shared Calling for Calling Plan or Operator Connect is configured in the same tenant as Direct Routing, site-assigned emergency call routing policies cannot be used. in context
• If no funding is available for a Shared Calling call on a Calling Plan service number, the caller hears a voice prompt saying they are not set up to use this calling feature and should contact their admin. in context
• Shared Calling users must not have a voice routing policy with valid PSTN usages; if the global policy has usages, create a policy with empty PSTN usages and assign it to them. in context
• If a user's voice routing policy contains PSTN usages, the user does not use Shared Calling and behaves as if they have an assigned phone number. in context

Cite this source record

APA

WarmTransfer. (2026, July 28). Configure Shared Calling. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-shared-calling-setup

BibTeX

@misc{warmtransfer-ms-learn-shared-calling-setup,
  title  = {Configure Shared Calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-shared-calling-setup},
  note   = {Microsoft, accessed 2026-09-25}
}