Dialogue Cloud

Microsoft Graph Presence Source Configuration

Warning: The MS Graph Presence APIs are still in BETA at Microsoft.

Please note, if Microsoft decides to change this part of the Graph API, Anywhere365 might no longer be able to retrieve presence.

Introduction

The Microsoft Graph Presence Source (hereafter 'presence source') enables the UCC to use Teams user presences. It makes use of the Microsoft Graph Communications Presence APIs. Read more about Presence Resource Type at Microsoft Documentation.

Per a AD account the UCC can poll up to 200 unique users. In scenario's with more then 200 unique, you can add additional AD accounts.

The UCC will poll the presence each 500ms with a maximum of 100 users at a time. For UCCs with large amounts of agents, it is possible to add multiple AD accounts. For example when 500 unique agents are configured in the UCC (service wide) 3 accounts are needed to have the presence of all users polled every second.

 

Prerequisites

  • Core 8.1 or higher.

 

Account requirements

The accounts to retrieve presence must be Azure Active Directory user accounts, these accounts will be able to retrieve presence from users that arein the same tenant. When subscribing users across different tenants, at least one account is needed from each tenant. The accounts do not need any permissions as they are granted globally by tenant admin, nor do they need any licenses. Simply create an new user account without licenses.

To grant admin consent for the Anywhere365 UCC Presence Source, simply replace {tenant-id} with your tenant ID in the following URL and launch it in a web browser. After the admin consent is granted, you will be able to sign in with non-admin user accounts in the presence source

Example https://login.microsoftonline.com/common/adminconsent?client_id=99077b9e-cb11-4fb7-b493-fbc6907245e6

Note A user with the Global Admin Role can perform this action.

Make sure to create dedicated accounts in the Azure Tenant as the API limits are account specific (see FAQ for API limits).

 

Permissions

 

Verify

To verify if the application is successfully added, you can perform the following steps:

  1. Sign into the Azure Portal, with a Azure Admin

  2. Navigate to Azure Active Directory

  3. Navigate to Enterprise applications tab

  4. In here you can find an application named "Anywhere365 UCC Teams Presence Source"

 

Password policy

When the password of an account changes, the tokens of the account will also expire. Make sure to set a password policy that will never expire passwords. Also make sure that the password isn't changed while in use by MS Graph Presence Provider. To ensure safety, make sure to use a long and safe password.

 

UCC cache policy

When the complete cache of a UCC is removed, the tokens of the account will also be removed and a new device token must be granted access to start collecting presence information again. This can be prevented by not removed the following folder:

%programdata%\Anywhere365\Core\Service\<servicename>\cache\_presence-provider-msgraph

 

Add Teams users as agents

To use Teams presence

Teams users are matched by their User Principal Name (UPN). In most cases this is the e-mail address of the user. The UCC will create a Teams UPN field in the SharePoint list. The field can be added to the overview page with 'Modify view' button. When the field is not empty, this presence source will be selected over any other presence source. So if the Attendant presence source is desired, make sure this field is left blank.

To use Teams presence, fill in the Teams UPN field with the desired UPN of the user.

To use other presence sources

This presence source has the highest priority over other presence sources, but only when the Teams UPN SharePoint field is populated. This is also the case when this presence source is disabled. The UCC will raise errors that Graph Presence source is not enabled.

 

Related Topics

Additional Configuration Core

Using Microsoft Teams client with Anywhere365