Dialogue Cloud

Setting up an Azure App for Snapper

Snapper needs access to your Microsoft Graph API in order to collect details of your agents (users in your Active Directory, which have Display Names, Teams Presence States like "Available", "Busy", "Away" and Teams Activities, like "in-a-call"). To use Microsoft Graph API, an App must be created to allow access to these Teams related details.

Note: By default, Snapper will request the user that logs in for the first time to accept the delegated permissions. A User with Admin rights can accept on behalf of your entire Organisation. For more information see Microsoft’s description of the Consent experience on Learn More - Microsoft.

Users who have insufficient rights will need to obtain the required Microsoft 365 tenant consent rights to be allowed to proceed.

Snapper has 2 options for granting consent to your Graph API:

  1. Using the built-in A365 Snapper Teams - PROD global App Id pre-created by Anywhere365.

  2. Creating your own App Id with your own name and using that

Option 1:

Also here, two methods exist:

  1. When a Microsoft 365 tenant admin logs in to the Snapper for the first time a consent window will appear allowing the admin to grant consent on behalf of the entire Organization. (This requires the Admin to have the Snapper installed)

  2. Use a URL in a regular browser to access the Consent Window for the A365 Snapper Teams - PROD global App Id:




    After which a login screen will appear allowing a Microsoft 365 tenant admin to grant consent on behalf of the entire Organization.


Option 2:

Create your own privately named App Id to use in your Snapper install wizard or Snapper settings.


  • Your company must have Azure
  • The user account that creates the app must be present in the Azure AD directory of your company and have the rights to create apps (this is possible by default unless limited by an admin)
  • A global admin will have to go to an admin consent url in order to allow accounts of this Azure AD directory to use it, since Teams requires permissions normally reserved for admins. By consenting a global admin allow regular users to have these permissions in the app.

Create an Azure App

Our first step is to create the App in Azure.

  1. Navigate to https://portal.azure.com

  2. Select Azure Active Directory From the Azure Portal Menu (upper left).

  3. From here collect your tenant domain for later use (e.g. domain.com or domain.onmicrosoft.com)

  4. Select App registrations

  5. Click New Registration and do the following:

    • Give the application a name (e.g. A365-Azure-Application)

    • Under Supported account types, select Accounts in any organizational directory

    • Add the following redirect URI

      Type: Public client (mobile & desktop)

      Redirect URI: urn:ietf:wg:oauth:2.0:oob

  6. Click Register

  7. Select Authentication

    1. Add Web as a platform

    2. Under Web | Redirect URIs enter a url, for example http://localhost

    3. Under Implicit grant select both options:

      1. Access tokens

      2. Id tokens

    4. Under Mobile and desktop applications | Redirect URIs check all three options

      1. msal<application_client_id>://auth

      2. https://login.microsoftonline.com/common/oauth2/nativeclient

      3. https://login.live.com/oauth20_desktop.srf

    5. Double check if Supported account types is set to:

      1. Accounts in any organizational directory

  8. Click Save


Configure API Permissions

Before the App can be used, the right permissions need to be assigned. This varies per use of the App.

  1. Navigate to your Azure App

  2. Click ‘API Permissions

    Ad d the following 2 permissions:

    1. User.Read

      1. Click ‘Add a permission

      2. Click ‘Microsoft Graph

      3. Click ‘Delegated permissions

      4. Open 'User'

      5. If 'User.Read' is not selected, select it and click 'Add permissions'

    2. Presence.Read

      1. Click ‘Add a permission

      2. Click ‘Microsoft Graph

      3. Click ‘Delegated permissions

      4. Open 'Presence'

      5. If 'Presence.Read' is not selected, select it and click 'Add permissions'


Using the app

  1. Navigate to your App

  2. Click ‘Overview

    1. Collect the following value to be used in the Snapper client install wizard or settings.

      1. Application (client) id (aka App ID)

      2. Have a Microsoft 365 admin use a browser to grant consent:

      Please use the following link to grant admin consent to an Azure application (where "<client_id>" is your Microsoft 365 App ID):



      https://login.microsoftonline.com/common/adminconsent?client_id=<client id>