Create a Service user to make calls from Microsoft Teams

task australia Updated Sep 10, 2026 2 min read provide-app-access-policy-nc-st.md
Raw file servicenow.com

Create a service user role to be able to start online meetings on behalf of users in Microsoft Teams.

Before you begin

Role required: Microsoft Teams admin

Procedure

  1. Log in to Microsoft Azure portal.

  2. Create a Service user.

    1. Navigate to Azure services > User.

    2. Select New user.

    3. On the form, fill the fields.

      Field Description
      User name Option to provide the user name for the user.
      Name Option to provide the name of the user.
    4. Select Create.

    5. Select the created user to view the details.

      Note: Ensure that the Service User has the required license/subscription and a valid usage location set to make conference calls from Microsoft Teams.

  3. Run the PowerShell command from Terminal on macOS or from the Command prompt on Windows OS.

    1. Type the command pwsh and press Enter.

    2. Connect your Microsoft tenant with PowerShell.

    3. Run the following command in PowerShell.

      Text
      connect-microsoftteams

      [Omitted image "powershell-connect-teams-command.png"] Alt text: PowerShell connect Teams command

      Upon successful connection, a confirmation message is displayed in the browser.

      [Omitted image "authentication-message-browser.png"] Alt text: Authentication message in browser

      PowerShell will also display the tenant details.

      [Omitted image "powershell-confirmation.png"] Alt text: Powershell confirmation

  4. Run the command below to create a new Application Access Policy in PowerShell.

    Use the bot ID created in step 3 in the section Create an app in Microsoft Teams to enable making calls as the AppId for the command.

    For more information on the application access policy, see Configure application access to online meetings.

    SQL
    Syntax:
    New-CsApplicationAccessPolicy -Identity "<PolicyName (can be anything)>" -AppIds "<AppIds>" -Description "<Policy Description>"
    Example:If you have a Self-configured (single tenant) setup, use the application ID from Azure portal.
    For Example: New-CsApplicationAccessPolicy -Identity "OnlineMeetingsAccessPolicy" -AppIds "aaaaaaaa-1234-er4r-8dc9-123456789012" -Description "Grant OnlineMeeting Application Permission"

    [Omitted image "app-access-policy.png"] Alt text: App access policy in Powershell

    Upon successfully creating the policy, the details are displayed in PowerShell.

    [Omitted image "powershell-app-access-success.png"] Alt text: App access policy success message in Powershell

  5. Run the user permission policy in PowerShell.

    1. Go to the Microsoft Azure portal.

    2. Navigate to Home > Users.

    3. Select the user created.

    4. Copy the Object ID of the user to notepad.

    5. Use the policy name created in the previous step as the PolicyName of the command and the Object ID as the UserAzureID respectively in the command to execute in PowerShell.

      SQL
      Syntax:
      Grant-CsApplicationAccessPolicy -Identity "<UserAzureID>" -PolicyName "<PolicyName>"
      Example:
      Grant-CsApplicationAccessPolicy -Identity "fdcd9c17-ceae-468f-906f-2er76b4dd0f4" -PolicyName "OnlineMeetingsAccessPolicy"

      [Omitted image "powershell-user-permissions.png"] Alt text: User permissions

Parent Topic:Integrating Notify connector self-configured app with Microsoft Teams

Search documentation
Search document titles and file paths on the australia branch