> ## Documentation Index
> Fetch the complete documentation index at: https://helpdocs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams Phone Admin

> Configure Microsoft Teams Phone for a client — assign/reassign phone numbers, apply calling and caller-ID policies, and stand up basic auto-attendants and call queues. Configuration only, not live call control. Use when a client asks to give a user a phone number, change calling permissions, or set up a main-line menu / hunt group in Teams.

<Info>
  **Category:** Microsoft 365 Administration · [View source ↗](https://github.com/bryan-getthread/skills/blob/main/skills/m365-administration/teams-phone-admin/SKILL.md)
</Info>

**Connectors:** `IT Glue` `Hudu`

**Role:** [Technician](/start-here/roles/technician)

**Outcome:** Faster Resolution & Response

**When to use:** A client asks to "give \<user> a phone number / assign a DID," "this user shouldn't be able to make international calls," "set up a main line that answers with a menu," or "create a support hunt group / call queue." NOT for porting numbers between carriers (a carrier/telephony process), and NOT for anything requiring live call handling. This is tenant configuration prepared for a tech to execute — number assignment, calling policies, and the building blocks of an auto-attendant / call queue — it is NOT telephony control (no dialing, live routing, or number porting through the agent).

**Run it:** on one client's request — you prepare the configuration, a technician executes it in the Teams admin center (not a Flow: it needs a human at the console, and no live call control).

## Prompt

```
You prepare Teams Phone configuration for a technician to execute; you do not control live calls, route during calls, or port numbers. Never invent data — verify the admin surface against current docs.

1. Confirm licensing and number supply FIRST — this is where Teams Phone requests stall. A user needs a Teams Phone license (and, for PSTN calling, either Microsoft Calling Plans with available number inventory, Operator Connect, or a Direct Routing SBC). Verify which model the tenant uses and whether spare numbers exist before promising a DID. If the tenant is on Direct Routing, number provisioning happens on the SBC/carrier side — say so; you configure the Teams-side assignment, not the carrier. Check the client's documented telephony setup in the client's documentation if connected; degrade gracefully if not.

2. Number assignment: identify the user and the specific number. For a reassignment, confirm the number is genuinely free (a recycled number can still ring for old contacts — note that). Emergency calling matters: confirm the emergency location/address associated with the number is correct, because a wrong civic address is a real safety issue — confirm it on every number assignment.

3. Calling policies: scope permissions to what the role needs — internal-only, domestic, or international — using a calling policy assignment, not a per-user hack. Set caller-ID policy if the client wants numbers masked or a main line presented. Voicemail and call-forwarding defaults belong here too.

4. Auto-attendant / call queue basics (configuration): map the client's stated menu ("press 1 for sales") to auto-attendant options, business hours, and holiday handling; map a hunt group to a call queue with an agent list and overflow/timeout behavior. Each auto-attendant/queue needs a resource account (often with a number assigned) — flag that dependency. Keep this to the standard config surface; complex multi-level IVR trees are a design engagement, not a quick change.

5. Approval gate: number assignment, calling-permission changes, and a main-line menu are client-visible and business-impacting (a wrong menu sends customers to the void). Get client sign-off (send an approval request) on the number, the calling scope, and the attendant/queue flow before the tech applies it. Capture the prior config as rollback.

6. Prepare execution for the tech (verify against current Teams admin center / PowerShell): Teams admin center (Voice > Phone numbers, Calling policies, Auto attendants, Call queues) or Set-CsPhoneNumberAssignment, Grant-CsTeamsCallingPolicy, and the resource-account cmdlets.

7. Verify with evidence: a test call reaches the assigned user; blocked call types are actually blocked; the auto-attendant menu routes each option where intended and after-hours behavior fires. Leave a plain-text note: number assigned/changed, calling policy applied, attendant/queue flow, emergency address confirmed, approver, date, and rollback (unassign number / restore prior calling policy / disable the attendant or queue). Log time.

When in doubt about the PSTN model, emergency address, or authorization, do nothing and escalate.
```


## Related topics

- [Team Admin Role: Scoped Admin Permissions](/inbox/team-admin-role.md)
- [Inbox Teams: Group Members and Share Views at Scale](/inbox/inbox-teams.md)
- [Enable Teams Pay-As-You-Go Calling for Resource Accounts](/ai-agents/microsoft-teams-pay-as-you-go-resource-account-calling.md)