...

The Enreach Voice Presence Sync enables the two-way integration of in-a-call status between Microsoft Teams and Enreach Voice.

When the user is having on a Teams call, participating in a Teams meeting or sharing a screen, the user is set as ‘talking’ in Enreach Voice. This has the following affect effects on Enreach Voice:

• Direct calls to the user in Enreach Voice use corresponding call handling (Busy on Busy, Call waiting, etc…)

• Service calls are not allocated to the user

• User The user is show shown as ‘talking’ in directory views

When a user is having on a call in Enreach Voice in any of his/her their terminals, the user in Microsoft Teams is set in to Busy/InACall status in Microsoft Teams.

Other parts of user presence are not synced between Enreach Voice and Microsoft Teams. This includes user Available, Offline, Do not Disturb etc presence statuses in Teams and user availability Enreach Voice (Available, Off work, DND, etc…).

...

A Microsoft Teams user can have multiple presence sessions because the user can be on multiple Teams clients. Similarly, an Enreach Voice have has its own application presence session for a user and be is able to update the state.

Each Teams client has an independent presence session and ; the final user 's presence is an aggregated state from all the sessions behind.

...

Presence Sync integration is implemented as a headless background service, which creates and maintains a presence subscription for a set of Microsoft Teams users and receives a notification when the presence of the user is changed.

...

Requirements and limitations

Usernames

Usernames The usernames of the users must match in AzureAD (UserPrincipalName) and in Enreach Voice (Email Address)

...

EnreachVoice Teams Presence Integration enterprise applications must be consented to by the customer’s Azure tenant administrator.

You can use this tool to generate the appropriate admin consent link: http://azure-consent.enreachvoice.com/teams-presence/

...

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

Same If Voice Portal provisioning integration is active, the same user can be used as a the presence sync service account as used for Voice Protal provisioning integration.

Requirements for the service account

• MFA must be disabled, or EnreachVoice IP addresses must be whitelisted

• Password The password should not expire

• Office licenses are not required

Limit of users

Current limit The current maximum number of GraphAPI presence subscription is 650 userssubscriptions is 650 users. This means that maximum of 650 users per organization can have the feature enabled.