Hello Community,
We’re exploring ways to increase automation within our access management processes, specifically whether assyst workflows can be used to trigger outbound actions such as adding users to Microsoft Entra ID (Azure AD) groups based on ticket or workflow outcomes.
We already make use of inbound integrations (for example, Intune feeding data into assyst). However, our focus here is on using assyst as a driver for outbound actions, rather than purely as a consumer of external data.
Our current understanding is that this type of integration would most likely be achieved using AssystETM (e.g. via workflow steps and external calls), but we’re keen to understand how others have approached this.
We’d be interested in hearing from the community:
- Have you implemented outbound integrations from assyst to Entra ID (such as managing group membership)?
- Was this done using AssystETM, and if so, how was it structured (e.g. workflow design, triggers, error handling)?
- Did you use ETM alone, or in combination with APIs, middleware, or other integration components?
- Are there any patterns, challenges, or lessons learned you’d recommend considering early on?
We’re at an exploratory stage and would value learning from real‑world implementations and experiences.
Many Thanks,
Jessica Lee van Pelt (She/Her)
Service Analyst
IT Service Operations, Architecture & Design
IFSCloud - Assyst Version 11.8.4