Overview

Benecloud Teams presence integration is a headless background service, which updates the terminal state (in a call/not in a call) of BeneCloud users based on user presence in teams.

Integration service creates and maintains presence subscription for a set of users and receives notification when the presence of the user is changed. If presence notification indicates that the user is having a Teams call, participating in Teams meeting or sharing a screen, user is set as ‘talking’ in BeneCloud.

Requirements and limitations

AzureAD App registration

AzureAD App registration must be created.

AzureAD service account

Presence - read permission, required by Microsoft GrapAPI presence endpoint permissions are currently available only for Delegated (worked or school account) permission Type. Application permission type is not available for Presence - read.

Because of this limitation, a presence subscription must be done as a user. A separate “service account” user must be created, which is used for creating a presence subscription. Service account credentials are configured in MS Teams Presence Integration service.

Requirements for the service account

MFA must be disabled, or BeneCloud IP addresses must be whitelisted
Password should not expire
Office licenses are not required

Limit of users

Current limit of GraphAPI presence subscription is 650 users.

Creating AzureAD app registration

Open AzureAD portal
Go to AzureAD → App registrations → New registration
1. Enter proper name
2. Accounts in this organizational directory only
3. click Register
Select API permissions and Add a permission