Azure Active Directory - Query users

What it does

This action communicates with people or looks up Microsoft 365 user data. Migration review should focus on recipients, dynamic identities, message content, and connector permissions.

How Flow Migrator maps it

Flow Migrator maps this to Microsoft Graph filtered/paged users + native result object using HTTP with Microsoft Entra ID (Premium) / Data Operations. Queries Microsoft Graph through a separate Premium HTTP with Microsoft Entra ID connection. Preserves supported exact predicates and nested AND/OR groups, follows nextLink to the source maximum, and produces users, emails and count from the same matched set. Configure Graph base/resource URLs, delegated User.Read.All and admin consent after import. Unsupported predicates or consumed source-only properties require explicit mapping. Malformed pages and missing/null mail fail before publishing a partial result; live tenant/identity/paging validation remains necessary. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• Review HTTP method, URI, headers, authentication, retry behavior, premium licensing, and response parsing.
• Confirm recipients, sender behavior, HTML body rendering, attachments, and tenant connector permissions.
• Run a test instance and compare outputs against the original Nintex workflow before production migration.

Validation checklist

1. Open the generated flow and confirm the action card imported correctly.
2. Validate connection references and required settings before running the flow.
3. Test with representative source data from the original workflow.