Genesys Cloud - Main

 View Only

Sign Up

  • 1.  Teams Integration || Presence and Sync Issues

    Posted 10-04-2026 17:27

    Hello Dears,

    I would appreciate your expert feedback regarding a case I encountered while integrating Genesys Cloud with Microsoft Teams.

    I noticed the following behavior:

    1. Teams users' presence/status does not sync unless the administrator navigates to the Apps tab in Genesys Cloud and clicks Sign in to Microsoft.
    2. Before completing the above step, the Microsoft Teams badges are displayed in Genesys Cloud, but all users appear as Offline, which does not reflect their actual Teams presence.

    I found several articles in the Genesys Resource Center indicating that, even after granting Admin Consent (tenant-wide permissions) from the Microsoft Entra ID side, users may still need to click Sign in to Microsoft. However, providing Admin Consent supposedly makes the sign-in process quicker.

    This raised a few questions for me:

    • Is this an expected limitation of the integration?
    • Is the Sign in to Microsoft step required in order for Genesys Cloud to obtain a user-context token that is necessary for presence/status synchronization?
    • If Admin Consent has already been granted at the tenant level, why is an individual user sign-in still required?

    I also came across the following Genesys Blueprint:

    Genesys Cloud – Presence Update from Microsoft Teams Blueprint

    My understanding is that the Blueprint can synchronize presence based on Microsoft Teams presence events. Although this approach is unidirectional, I assume that it does not eliminate the need for the user to complete the Sign in to Microsoft process within Genesys Cloud.

    Additionally, in the Genesys Arena demonstration, the sign-in step appears to be required even when SSO is enabled:

    Genesys Arena – Microsoft Teams Scenarios

    Could you please share your feedback on the following points?

    1. Is the sign-in process within Genesys Cloud, or within the embeddable application on the Microsoft Teams side, mandatory for synchronizing Teams presence/status?
    2. Is there any supported workaround to bypass this individual sign-in process, particularly when tenant-wide Admin Consent and SSO are already configured?
    3. Regarding the Presence Update from Microsoft Teams Blueprint, would the solution still work if users do not complete the Sign in to Microsoft process in Genesys Cloud?
    4. If the sign-in is mandatory, could you please clarify what specific authentication/token requirement makes this step necessary, despite tenant-wide Admin Consent?

    Thanks in advance for your support and clarification.

    Best regards,
    Mohamed


    #API/Integrations
    #ArchitectandDesign
    #System/PlatformAdministration


  • 2.  RE: Teams Integration || Presence and Sync Issues

    Posted 10-05-2026 02:27
    Edited by Christian Sedlmeier 10-05-2026 02:32

    Hello Mohamed,

    My name is Christian, and we recently implemented Microsoft Teams presence synchronization in our company. Microsoft Teams is an important collaboration platform for us and is widely used across the organization.

    During the implementation, we realized that the standard presence synchronization mainly covers the direction from Genesys to Microsoft Teams, rather than providing the synchronization capabilities we would ideally like to have between both platforms.

    We also identified some limitations regarding the mapping of different Genesys presence and agent states to Microsoft Teams.

    The implementation itself required quite some effort on our side. Together with our partner and our internal Azure team, we had to prepare the required configuration in Entra ID, configure the presence mappings and Architect flows, and complete the application setup before the synchronization worked as expected.

    The synchronization from Genesys to Microsoft Teams is now working. However, we are still missing more granular mapping options. For example, we would like to differentiate between an agent who is On Queue but not currently on a call and an agent who is On Queue and actively talking.

    In addition, we are interested in synchronization in the other direction, from Microsoft Teams to Genesys.

    For this reason, we are currently looking for an add-on or solution in the Genesys Marketplace that could provide more flexible presence mapping and potentially bi-directional synchronization between Microsoft Teams and Genesys.

    I would be very interested to hear whether your solution could address these requirements.

    Best regards,
    Christian



    ------------------------------
    Christian
    Lead Infrastructure Analyst
    ------------------------------



  • 3.  RE: Teams Integration || Presence and Sync Issues

    Posted 23 days ago

    Hi Mohamed,

    Thanks for the detailed write-up. Short answer: yes, this is expected behavior.

    1. Is sign-in mandatory for presence sync?
    Yes. For Genesys Cloud to subscribe to a user's Microsoft Teams presence events and receive them, that user must authenticate their Microsoft Teams account with Genesys Cloud. The sign-in can happen in Genesys Cloud or through the embedded app in Teams. Until then, the Teams badge shows but presence defaults to Offline, because no presence data is flowing for that user.

    2. Is there a supported workaround?
    Not that I'm aware of. Tenant-wide Admin Consent and SSO don't replace the per-user authentication.

    3. Does the Presence Update from Microsoft Teams Blueprint still require sign-in?
    Yes. The Blueprint relies on the same Teams presence events, so each user must still be authenticated. It adds a one-way presence update from Teams to Genesys Cloud, but it doesn't remove the sign-in requirement. Without sign-in, there are no presence events to act on.

    4. Why is sign-in required if Admin Consent is granted?
    Admin Consent and user sign-in do different jobs:

    • Admin Consent authorizes the Genesys Cloud application to request specific Microsoft permissions on behalf of users in your tenant. It also means users don't see an individual consent prompt, which is why sign-in goes faster.
    • User sign-in is what produces a token tied to that specific user. Presence subscriptions are made in the context of an individual user, so Genesys Cloud needs that user's authenticated session to subscribe to and receive their presence events.

    Consent grants permission to ask. It doesn't create a user session or token. That's why the Sign in to Microsoft step is still needed for each user, including after Admin Consent and with SSO enabled. SSO authenticates the user to Genesys Cloud, but it doesn't link their Microsoft Teams account to the integration.

    In practice, plan for every user to complete the sign-in once. Admin Consent will keep that step quick, with no consent prompt.

    Best regards,
    Jason Wolfgang
    Genesys



    ------------------------------
    Jason
    Senior Manager, Product Management
    ------------------------------