Automate Case Resolution (Power Automate + Process)

Since Power Automate alone can’t directly resolve a case using the standard “Set Status” call due to limitations, we’ll create a classic process with the necessary steps and then call that process using the Perform a Bound Action step.

Why use a Bound Action?

Bound actions are powerful because they allow you to execute specific business logic tied to a single record, like resolving a case, through a custom process. In this scenario, since the native "Set Status" action in Power Automate doesn't support resolving a case, a bound action gives us a clean and supported workaround.

First, navigate to your Dynamics 365 solution and create a new Process.

Choose:

• Category: Action
  

• Entity: Case

• Name: ResolveCaseBoundAction (or your preferred name)

This process will later be exposed as a bound action that we’ll call from Power Automate.

Add Step to Change Status:

Save and Activate:

Make sure to save and activate this workflow.

Once activated, it will automatically be registered as a bound action and become available for use in Power Automate.

Create a Cloud Flow:

Now switch to Power Automate, and create a new flow. In this example, we use a Automated flow or trigger of your choice.

List Rows and Filter Specific Owner:

Use the List Rows action for the Case table, and optionally filter on owner, status, or other conditions to select only open cases that meet your logic.