A project approvals dashboard shows request statuses, notifications, and background processing progress.
Project Operations users who submit big batches of approvals no longer have to guess when the work finishes. A roadmap item now lists approval sets among the processes that send a completion notification. The status is "Launched," with general availability in October 2026 on the Web client in Worldwide (Standard Multi-Tenant). The Microsoft roadmap describes the feature, but its page text didn't expose the item itself. The "Launched" status and the October 2026 date therefore come from the submitted metadata. Microsoft also says roadmap information is subject to change.

A project approvals dashboard shows request statuses, notifications, and background processing progress. What the feature does​

Project Operations approvals can run in the background through a scheduled cloud flow. The new feature lets the person who started an approval set find out when it is done.

  • Who gets notified: the user who started the operation, and only for operations they triggered.
  • On success: a brief pop-up names the approval set, says it completed, and links to the record. The notification stays in the notifications pane until you clear it.
  • On failure: if one or more approvals in the set fail, the notification says the set completed with failures. It gives the failure reason and links to the failing record. Multiple failures produce separate notifications, not one summary.
  • What it doesn't do: it sends no "processing started" notice, no email, and no Teams message. It adds no retry or remediation workflow.

In short, this is a completion alert delivered inside the app. It is not a monitoring or repair system.

How to enable it​

The feature builds on Microsoft's existing notification framework for long-running processes. Microsoft Learn says the Enable notifications for long-running processes setting in Project parameters controls the behavior. With it set to No, a spinner blocks the UI until the job finishes or the UI times out after two minutes. A timeout doesn't cancel the job, which keeps running in the background.

With the setting on, a job that is enabled for notifications shows a ribbon message when it starts. An in-app notification appears when it finishes. Turning the setting on unlocks Select jobs for notification, and the roadmap says to add approvals to that list. You have two options:

  1. Pick explicitly. Add approvals to the list. Learn's current list covers closing a quote as won or lost, confirming a project-contract order, confirming an invoice, creating or correcting an invoice, adding invoice line details, copying a price list, and updating estimate prices. If the list isn't blank, any newly added process must be included by hand.
  2. Leave it blank. All available processes use notifications, and new ones are picked up automatically.

The sources don't say that selecting approvals overrides a disabled master setting. The safe reading is that the two layers work together. Check Enable notifications for long-running processes first, then the job list.

Approval sets and why failure alerts matter​

Learn describes approval sets as groups that split approval requests into smaller units. They allow processing by project, in sequence, with retries. A record that processes successfully moves from Submitted to Approved and is unlinked from the set. A record that fails stays Submitted. The set is marked failed and logs the error message.

Processing can be asynchronous. The Asynchronous Threshold field decides when:

  • Zero: every request is processed asynchronously.
  • Above zero: processing goes to the background only when the number of submitted approvals exceeds the value.

The notification fits that background model. Without it, a user would have to watch the Processing Approvals view or check the logs.

What the notification doesn't replace​

Learn documents a separate Failed Approvals view for items that need user intervention. You open the approval-set logs to find the cause. Selecting Retry adds to the set's lifetime count, puts it back in Processing, and tries the remaining records.

The notification gives you a failure reason and a link to the failing record. It doesn't fix or retry anything. Administrators should keep the Failed Approvals view and the logs in their runbooks.

Admin checklist​

Background processing depends on a scheduled flow, so check it too:

  1. Sign in to Power Automate as an administrator.
  2. Switch to the environment that runs Project Operations.
  3. Open Solutions, select Project Operations, and filter to Cloud Flows.
  4. Confirm that Project Service – Recurrently Schedule Project Approval Sets is On. If it isn't, turn it on.
  5. Check the System Jobs list in the Dataverse environment. Learn says processing should occur every five minutes.

The D365 Demystified blog documented this in 2022. It said the flow is off by default in a newly provisioned environment. If it is off, approvals are processed while the user waits. A freshly provisioned environment may therefore show no background behavior at all, and no notifications, until the flow is on.

Open questions​

The sources don't give a minimum build number, a per-tenant rollout schedule, or the permissions needed. They don't say how long notifications are kept or which approval categories are covered. Check these in a test environment before telling users to rely on the alerts.

Takeaway​

This is a small quality-of-life change that matters mainly to finance and project teams processing approvals in bulk. A failure now announces itself, with a reason and a link. A blank "Select jobs for notification" list is convenient, but it also changes how every other eligible job behaves, so choose between a blank list and an explicit one on purpose.

 

References

  1. Dynamics 365 Project Operations: Notify users when approval sets finish processing Microsoft 365 Roadmap 2026-10-22T22:58:40.939110Z
  2. Approval sets | Microsoft Learn learn.microsoft.com
  3. Enable notifications for long-running processes | Microsoft Learn learn.microsoft.com