how to user Expression Attributes to sync specific attributes only for one group of users.

Use scoping plus attribute expressions together:

1. Scope provisioning to the specific users/groups
   • In the Genesys Cloud for Azure enterprise app, go to Provisioning → Settings.
   • Under Scope, choose Sync only assigned users and groups.
   • Assign only the group(s) of users that should have Teams presence in Genesys to this app (Enterprise applications → Genesys Cloud for Azure → Users and groups → Add user/group).
   • Result: Only those users are provisioned at all, so the Teams-related SCIM attributes are sent only for them.
   If the app must remain assigned to all users, use an attribute-based scoping filter instead:
   • In Provisioning → Edit provisioning → Mappings → Users → Source object scope, add a scoping filter (for example, department EQUALS ContactCenter or a custom flag attribute) so only the intended users are in scope.
   • See examples in the Common scoping filters section.
2. Keep the Teams attributes mapped only for in-scope users
   • The attributes
     • phoneNumbers[type eq "microsoftteams"].value
     • urn:ietf:params:scim:schemas:extension:genesys:purecloud:2.0:User:externalIds[authority eq "microsoftteams"].value are standard, supported target attributes in the Genesys Cloud for Azure gallery app and can remain mapped as-is.
   • Once scoping is restricted (by assignment or scoping filters), those mappings will only be evaluated and sent for users that are in scope for provisioning. Out-of-scope users will not have these attributes provisioned to Genesys at all.
3. Optional: Use an expression to “blank out” attributes for non‑target users If the app must stay in scope for all users and a global scoping filter is not acceptable, an expression can be used on the source side:
   • Edit the user attribute mapping for phoneNumbers[type eq "microsoftteams"].value.
   • Replace the direct mapping with an expression that returns the phone number only when a condition is met (for example, a specific department or custom attribute), and returns null otherwise.
   • The same approach can be applied to externalIds[authority eq "microsoftteams"].value.
   Expressions are configured on the attribute-mapping page as described in the attribute customization article; they allow conditional logic so that only users matching the condition get a non‑null value provisioned.
4. Validate with on‑demand provisioning
   • Use Provision on demand for a test user inside the target group and one outside it to confirm:
     • In-scope user: Genesys receives the Teams phone and externalId attributes.
     • Out-of-scope user: Genesys does not receive those attributes (or receives them as null, depending on the expression).
5. Monitor
   • Use provisioning logs to verify which users are provisioned and what attributes are sent.

This approach ensures Teams presence–related attributes are only provisioned for the defined subset of users, either by scoping who is provisioned or by using expressions to conditionally populate the Teams attributes.

References:

• Configure Genesys Cloud for Azure for automatic user provisioning with Microsoft Entra ID
• Scoping users or groups to be provisioned with scoping filters (app-provisioning)
• Tutorial - Customize user provisioning attribute-mappings for SaaS applications in Microsoft Entra ID