Best practices for managing (adding user to group) entra ID users with flows?

Tone1
Tera Contributor

Hello,

We are looking to use the Entra ID Spoke to allow users to have their group memberships managed via requests and workflows in ServiceNow.

 

The primary use case for this is managing membership in Microsoft Teams groups.

We are having an internal discussion about whether the Entra ID Spoke is a practical way to handle this. Some team members are concerned that multiple API hits could negatively impact usability and create latency for the end-user during the request process.

 

Does anyone here have experience with this?

 

As a potential solution for latency problems with synchronous API calls, we've considered storing the entire Entra ID structure—with all users and groups—in our CMDB. We would then read the current state from the CMDB for any checks and only push the final changes to Entra ID via the API.

 

Would this be necessary, or is the latency from using the API directly generally negligible?

 

Thanks in advance.

0 REPLIES 0