Microsoft Teams - Get teams

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 HTTP call to Microsoft Graph joinedTeams using HTTP / Microsoft Graph. Preserves NAC Microsoft Teams get_teams_v_2 actions as an importable Microsoft Graph HTTP handoff and shapes the returned collection for downstream Nintex variable references. Replace placeholder authentication and validate Graph Teams permissions before production activation. 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.