Microsoft Graph Presence Source (Get) Configuration

Introduction

The Microsoft Graph Cloud Communications Presence APIs are used by AnywhereNow for two distinct presence actions, Get Presence states of agents and Set Presence state of agents:

Read more

1. This article: Microsoft Graph Presence Source enables the UCC A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location. to continuously get (collect) presence of Teams users, and

2. See other article: Microsoft Graph Presence Publisher which enables the UCC to set presence of Teams users on-demand by AnywhereNow components.

For more information on the Graph API, see Microsoft’s documentation on https://learn.microsoft.com/en-us/graph/api/resources/presence?view=graph-rest-1.0

Important

We recommend registering the Microsoft Graph Presence Publisher (set) and the Microsoft Presence Source (get) as two separate apps in your Microsoft Entra ID Formerly known as Azure Active Directory (or Azure AD, or AAD).

Firstly, either the Presence Publisher app or the Presence Source app , could generate a higher load/volume in the Microsoft Graph API than expected, which could lead to throttling Throttling, in the context of a software cloud delivery service, is the practice of temporarily suspending or diminishing access to a service offering to a cloud customer. Because cloud platforms are mostly multi-tenant, shared platforms and the usage at any moment of many customers is unpredictable, throttling is a normal and logical procedure of retaining a cloud service for all customers, sometimes at the expense of one or a handful of customers who are at that time using too many resources for the backend platform. Not only a customer itself, but also a "noisy neighbour" on the same platform can be the cause of throttling. Usually service will be resumed at a normal level after a short cool-down period, but can even take up to 24 hours or more. In Microsoft 365 throttling is usually indicated by "429 errors" or "server too busy" messages in logfiles or replies. or other issues.

Secondly, Publishing other users' Presence with the Publisher app may not be desired or legally permitted in your company, region or country, making this an optional feature.

High Level Steps

In order to start collecting presence for Microsoft Teams users, there are two requirements per tenant:

1. Microsoft Entra ID Formerly known as Azure Active Directory (or Azure AD, or AAD) App Registration:

   1. Register an app in Microsoft Entra ID to query the Microsoft Graph APIs.

2. Choose Authentication Method:

   1. Delegated Permissions:

      Authenticate using a user account (username and password).

   2. Application Permissions:

      Authenticate using a Client ID and Client Secret.

      Note

      Introduced in DC2024.02

Microsoft Entra Id App Registration setup

Please find below the steps to setup an App Registration in Azure.

1. Navigate to: https://entra.microsoft.com/

2. Under Applications -> App registrations create a new App registration

   1. Provide a Name for the application, for example: AnywhereNow Graph Get Presence Application

   2. Select the account type “Accounts in this organizational directory only”

   3. Click “Register”

   

3. On the API permissions tab,

   • Delegated Permissions
   • Application Permissions

   Add the following Delegated Microsoft Graph permissions:

   User.ReadBasic.All - Read all users' basic profiles

   Description: Allows the app to read a basic set of profile properties of other users in your organization on your behalf. Includes display name, first and last name, email address and photo.

   Why is this required? To allow the Graph Presence Source to translate UPN In Windows Active Directory, a User Principal Name (UPN) is the name of a system user in an email address 'like' format. A UPN (for example: john.doe@domain.com) consists of the user name (logon name), separator (the @ symbol), and domain name (UPN suffix). to ID, ID is required to retrieve presence from user.

   Permission name: Microsoft Graph / User.ReadBasic.All

   Directory.Read.All - Read directory data

   Description: Allows the app to read data in your organization's directory.

   Why is this required? To allow the Graph Presence Source to cache user details (display name, sip address, id, UPN) from all employees, in order to minimize the number of request to graph.

   Permission name: Microsoft Graph / Directory.Read.All

   Presence.Read.All - Read presence information of all users in your organization

   Description: Allows the app to read presence information of all users in the directory on your behalf. Presence information includes activity, availability, status note, calendar out-of-office message, timezone and location.

   Why is this required? To allow the Graph Presence Source to retrieve current presence from users utilizing a single service account.

   Permission name: Microsoft Graph / Presence.Read.All

   Note

   Introduced in DC2024.02

   Add the following Application Microsoft Graph permissions:

   Presence.Read.All - Read presence information of all users in your organization

   Description: Allows the app to read presence information of all users in the directory without a signed-in user. Presence information includes activity, availability, status note, calendar out-of-office message, timezone and location.

   Why is this required? To allow the Graph Presence Source to retrieve current presence from users.

   Permission name: Microsoft Graph / Presence.Read.All

   Domain.Read.All - Read domains

   Description: Allows the app to read all domain properties without a signed-in user.

   Why is this required? To allow the Graph Presence Source to retrieve the domains from the tenant.

   Permission name: Microsoft Graph / Domain.Read.All

   User.Read.All - Read all users' full profiles

   Description: Allows the app to read user profiles without a signed in user.

   Why is this required? To allow the Graph Presence Source to translate UPN to ID, ID is required to retrieve presence from user.

   Permission name: Microsoft Graph / User.Read.All

4. Since the Admin consent are required, click the button “Grant admin consent for <tenant>”.
   

   Note

   Only a tenant administrator can grant the admin consent

5. On the Authentication tab, change “Allow public client flows” to “Yes”.

   • Click “Save”
     

   

6. On the Overview tab, copy both the Application (client) ID and the Directory (tenant) ID

   • These IDs need to be used for Configure the Presence Source.

Authentication Methods

• Delegated Permissions
• Application Permissions

Configure Agents for presence collection via MS Graph

In order to collect presence for Agents using Microsoft Graph, make sure that the UPN field in the SharePoint Agent list is populated with the correct UPN of the Agent.

Configure the Presence Source

<MsGraphPresenceSource enabled="true">
<Accounts>
<Account Id="my-presence-account1" ClientId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" TenantId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" />
</Accounts>
</MsGraphPresenceSource>

MsGraphPresenceSource GraphPresenceManager::Graph API needs authentication for account with ID 'my-presence-account1' (tenant: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Please login on the following w

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

<MsGraphPresenceSource enabled="true">
<Accounts>
<Account Id="my-presence-account1" ClientId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" TenantId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" EncryptedSecret="xxxx"/ />
</Accounts>
</MsGraphPresenceSource>