██FR█████ █INTELL███████████

Assign Users to Teams and Queues in Power Automate Using Perform a Bound Action


This content originally appeared on DEV Community and was authored by Nikhil Sarpatwari

In one of my recent projects, I built a canvas-based Security App to streamline user access management in Dynamics 365 CE. As part of this solution, I needed to assign users to relevant teams and queues based on the access request submitted.

Rather than calling custom APIs or writing plugins, I decided to use Power Automate’s native “Perform a bound action” functionality to do this. This post outlines how the flow works and how you can implement the same approach in your own environment.

Use Case

When an access request is submitted via the app, the backend Power Automate flow takes over to:

  • Assign the user to one or more Dataverse teams
  • Assign the user to one or more queues

The goal was to keep everything within the Power Platform stack, avoid custom code, and ensure the assignments are scalable and repeatable.

Why use “Perform a bound action”?

Dataverse exposes a set of native bound actions for core tables. These actions are designed to operate on specific records. For example:

  • AddMembersTeam lets you add one or more users to a given team
  • AddPrincipalToQueue allows a record (like a user) to be added to a queue

These can be invoked using the “Perform a bound action” step in Power Automate, making them ideal for this type of automation.

Flow Implementation

1. Triggering the flow

The flow can be triggered by:

  • A button in Power Apps
  • A new row creation in a custom Dataverse table (such as “Access Requests”)
  • Any other trigger based on your app design

In my case, the flow was triggered by a Power Apps button.

2. Assigning the user to teams

If multiple teams are involved, loop through each team ID using an “Apply to each” control.

Inside the loop, use the “Perform a bound action” step with the following settings:

  • Entity name: teams
  • Action name: AddMembersTeam
  • Item ID: Team ID
  • System user

Team

3. Assigning the user to queues

Similarly, loop through each queue ID and use the “Perform a bound action” step.

  • Entity name: queues
  • Action name: AddToQueue
  • Item ID: Queue ID from the loop
  • System user

Queue

Security Considerations

Make sure that:

  • The flow runs under a service account or application user with appropriate permissions
  • Only authorised users can trigger the flow
  • Access logs or audit trails are maintained if required

You can also add approval logic before any team or queue assignment is performed.

Summary

Using the Perform a bound action step in Power Automate has allowed me to:

  • Eliminate the need for plugin-based user assignments
  • Automate access provisioning directly from a canvas app
  • Keep the entire solution low-code and maintainable

This technique is simple but highly effective when working with native actions like team and queue assignments. It’s a good example of how we can get more done inside the platform without resorting to custom code.


This content originally appeared on DEV Community and was authored by Nikhil Sarpatwari