SharePoint Online - Query user profile

What it does

This action works with SharePoint list items, files, folders, metadata, content approval, or permissions. The key migration inputs are the target site, list or library, field mappings, and any dynamic item identifiers.

How Flow Migrator maps it

Flow Migrator maps this to Send an HTTP request + native profile-property projection using SharePoint / Data Operations. Reads the destination SharePoint profile store, preserving exact property keys and the Manager account identifier rather than substituting Entra user fields. Requires an unambiguous SharePoint destination, supported membership identity, profile access and consumed source properties. Lookup errors and missing consumed properties fail; validate permissions, email aliases and destination profile schemas in UAT. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• Validate SharePoint site, list/library, content type, required fields, person fields, lookup fields, and attachment or file path behavior.
• 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.

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.
4. Confirm site/list/library names and complex field mappings in the target tenant.