Azure: Workflow and journey actions

When you integrate Atomicwork with identity access platforms like Okta, Azure Active Directory, and Google Workspace, you can add automated actions to a journey or a workflow, like creating a user, adding a user to a group, suspending a user, and deactivating a user.

When you’re configuring an onboarding or offboarding journey (or even a team change journey), you can use these automated actions to automatically perform these operations instead of having to note it down on your to-do list and manually log into these platforms to perform these operations every single time.

To add Azure actions to a journey or a workflow, you must connect Atomicwork with Azure.

Note: In a journey, all Azure actions are automated actions that cannot be assigned to employees. This also means that Azure AD actions will be visible to journey collaborators but not to employees assigned to this journey, so make sure to give it a clear name.

You can only specify when an action needs to be executed. You can specify whether you want the action to be executed the day the employee moves to this stage or a day relative to the day the employee moves to this stage. You can only specify day triggers and not hours or minutes. For example, you cannot specify that an action should be executed at 10:35 PM on a Sunday night.