Description:

This step retrieves information for an existing Microsoft Entra ID user.

The Read EntraID User workflow step connects to Microsoft Entra ID (formerly Azure Active Directory) and retrieves the properties of a specified user account.

The step identifies the user by the User Principal Name (UPN) and maps the selected Microsoft Entra ID attributes into FlowWright workflow variables for use by subsequent workflow steps.

The step supports:

• Microsoft Entra ID user lookup
• Configurable Entra ID connections
• User attribute mapping
• Dynamic workflow variable population
• Integration with Microsoft Graph through FlowWright connections

This step can be used for:

• Employee information lookup
• HR system synchronization
• Identity verification
• Workflow personalization
• Access review processes
• Identity lifecycle management
• Business process automation

Usage:

The Read EntraID User step is typically placed after user information has been collected or selected within a workflow.

The workflow can dynamically populate the username using workflow variables, form fields, HR systems, or data retrieved from external applications.

Once the user information has been retrieved, later workflow steps can:

• Populate forms
• Generate reports
• Update workflow variables
• Make workflow decisions
• Synchronize external systems
• Continue employee lifecycle workflows

You need to set up an EntraID connection. Go to Integration > Connections > Generic Connections. On the Manage Generic Connections page, click Actions > Create. A sample connection is included here for reference. 

Example:

Let’s build and execute the “clsReadEntraIDUserDef” example:

• Create a new process definition named “clsReadEntraIDUserDef” and open it in designer mode. 
• Drag a “clsReadEntraIDUser” step to the canvas.
• Connect the dots between the “Start” and “clsReadEntraIDUser” steps.
• Define a variable or a global to store the user attributes.
• Click the "clsReadEntraIDUser" step to configure its "Required" properties. Provide a name for the step. Select the EntraID connection from the drop-down list. Provide the “Username”. Click the button to map user attributes. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the button to map user attributes. A pop-up is rendered for configuration. Click the Add Row (+) button to insert an empty row. Provide the variable name and value. Click the Save button. You may insert multiple attribute mappings by using the Add Row button.  

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Read User step, FlowWright connects to the configured Microsoft Entra ID tenant and retrieves the requested user information. The configured attributes are stored in the specified FlowWright workflow variables. If the user information is successfully retrieved, the workflow follows the True return path. If the user cannot be found, the connection is unavailable, or the requested attributes cannot be retrieved, the workflow follows the False return path.

Tips:

• Verify that the Microsoft Entra ID connection has been configured before using this step.
• Use workflow variables to dynamically specify the username.
• Retrieve only the attributes required by the workflow to simplify configuration.
• Verify that the specified User Principal Name (UPN) exists before executing the workflow.
• Use the True and False return paths to implement appropriate success and error handling.
• Combine this step with update, approval, or provisioning steps to automate identity management workflows.

Notes:

• A valid Microsoft Entra ID connection must exist before this step can execute.
• The configured connection must have sufficient Microsoft Graph permissions to read user information.
• The specified User Principal Name (UPN) must already exist in Microsoft Entra ID.
• Invalid usernames or attribute mappings may cause the operation to fail.
• Network connectivity or authentication issues may prevent successful retrieval.
• The workflow should include appropriate error handling for the False return path.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

Note: Verify and complete any missing configuration after importing the sample, including:

• Microsoft Entra ID connection
• Username mapping
• User attribute mappings
• Workflow variable mappings
• Microsoft Graph permissions
• Environment-specific settings

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.