Hi Maya,
Hi,
Looking at the blueprints, they seem to be implemented as independent one-way flows, and I couldn't find any reference to running both directions together or handling bi-directional sync.
I also came across a couple of AppFoundry solutions that support presence synchronization:
These appear to include bi-directional synchronization with additional control logic, which suggests that simply combining the two blueprints may introduce a feedback loop or conflicting updates between systems.
This could explain the behaviour you're seeing after enabling both directions.
Keen to hear if anyone has successfully implemented this bi-directionally using just the blueprints, or if additional logic was required.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 03-30-2026 03:44
From: Maya Tsenova
Subject: Bi-directional presence sync Genesys <-> Teams
Hello,
Has anyone successfully implemented bi-directional presence synchronization using the following Genesys Cloud blueprints?
- https://developer.genesys.cloud/blueprints/update-ms-teams-user-presence-blueprint/
- https://developer.genesys.cloud/blueprints/gc-presence-update-from-ms-teams/
I initially configured the Genesys Cloud → Microsoft Teams presence update, and this was working as expected.
However, after adding the Microsoft Teams → Genesys Cloud presence update, the original synchronization stopped working as well. Specifically, the "Update Teams user presence" data action is now failing after implementing the Teams-to-Genesys sync.
At first glance, the configuration appears to be correct. I'm wondering whether it is actually supported to have both integrations running simultaneously, or if this setup is creating a loop that causes the integration to break.
Any insights or similar experiences would be greatly appreciated.
Thanks!
#API/Integrations
------------------------------
Maya Tsenova
UC engineer
------------------------------