> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/user/phone/grant-teams-user-policies.md).

# Grant Teams User Policies

Assign Teams voice and meeting policies to this user

### Description

Assigns Teams policies to this user: voice routing, dial plan, calling, IP phone, voicemail, meeting and live event policies. Only the policies you fill in are changed. Enter Global (Org Wide Default) to remove an assignment and fall back to the tenant default.

### Location

User → Phone → Grant Teams User Policies

**Full Runbook name**

rjgit-user\_phone\_grant-teams-user-policies

### Details

| Property         | Value                                                                   |
| ---------------- | ----------------------------------------------------------------------- |
| Version          | 1.0.2                                                                   |
| Required modules | <p>RealmJoin.RunbookHelper (>= 0.8.10)<br>MicrosoftTeams (>= 7.9.0)</p> |
| Schedulable      | no                                                                      |

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * Organization.Read.All
    * *Required by the app-based Teams PowerShell sign-in to read tenant information*

#### RBAC roles

* Teams Administrator
  * *Required to assign Teams policies to the user via the Grant-Cs policy cmdlets*

### Parameters

#### UserName

User principal name of the user the runbook acts on. Set by the portal from the selected user.

| Property         | Value                                  |
| ---------------- | -------------------------------------- |
| Required         | true                                   |
| Default Value    |                                        |
| Type             | String                                 |
| Hidden in portal | yes (preset via runbook customization) |

#### OnlineVoiceRoutingPolicy

Voice routing policy to assign. Leave empty to keep the current one, or enter Global (Org Wide Default) to reset it.

| Property            | Value                       |
| ------------------- | --------------------------- |
| Required            | false                       |
| Default Value       |                             |
| Type                | String                      |
| Portal display name | Online voice routing policy |

#### TenantDialPlan

Dial plan to assign. Leave empty to keep the current one, or enter Global (Org Wide Default) to reset it.

| Property            | Value            |
| ------------------- | ---------------- |
| Required            | false            |
| Default Value       |                  |
| Type                | String           |
| Portal display name | Tenant dial plan |

#### TeamsCallingPolicy

Calling policy to assign. Leave empty to keep the current one, or enter Global (Org Wide Default) to reset it.

| Property            | Value          |
| ------------------- | -------------- |
| Required            | false          |
| Default Value       |                |
| Type                | String         |
| Portal display name | Calling policy |

#### TeamsIPPhonePolicy

IP phone policy to assign, typically for common area phones. Leave empty to keep the current one, or enter Global (Org Wide Default) to reset it.

| Property            | Value           |
| ------------------- | --------------- |
| Required            | false           |
| Default Value       |                 |
| Type                | String          |
| Portal display name | IP phone policy |

#### OnlineVoicemailPolicy

Voicemail policy to assign. Leave empty to keep the current one, or enter Global (Org Wide Default) to reset it.

| Property            | Value            |
| ------------------- | ---------------- |
| Required            | false            |
| Default Value       |                  |
| Type                | String           |
| Portal display name | Voicemail policy |

#### TeamsMeetingPolicy

Meeting policy to assign. Leave empty to keep the current one, or enter Global (Org Wide Default) to reset it.

| Property            | Value          |
| ------------------- | -------------- |
| Required            | false          |
| Default Value       |                |
| Type                | String         |
| Portal display name | Meeting policy |

#### TeamsMeetingBroadcastPolicy

Live event (meeting broadcast) policy to assign. Leave empty to keep the current one, or enter Global (Org Wide Default) to reset it.

| Property            | Value             |
| ------------------- | ----------------- |
| Required            | false             |
| Default Value       |                   |
| Type                | String            |
| Portal display name | Live event policy |

[Back to Runbook Reference overview](/automation/runbooks/runbook-references.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmjoin.com/automation/runbooks/runbook-references/user/phone/grant-teams-user-policies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.