The process of submitting and distributing custom apps across Microsoft 365 platforms, including Outlook, Teams, and the Microsoft 365 app store.
Even if I use the same/current environment as the agent, it still fails to publish -
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Error - "Dataverse connector preview actions with environment parameter cannot yet connect outside of the current environment with connections provided by run-only users."
The same tool worked perfectly fine just yesterday, and I had an entire workflow created and published. The change I was trying to make it change the row count from 10 to 1000. This tool or workflow does not show a preview tag so I need to understand what changed.
The process of submitting and distributing custom apps across Microsoft 365 platforms, including Outlook, Teams, and the Microsoft 365 app store.
Even if I use the same/current environment as the agent, it still fails to publish -
Hi Meera,
Thank you for reaching out.
The error you’re seeing is caused by a known limitation with certain Dataverse connector actions, specifically preview actions that use an environment parameter. When the connection for those actions is provided by a run-only user, publishing can be blocked, even if the action is pointed to the current environment. The row count change likely triggered a full re-validation of the workflow, which surfaced this existing configuration issue.
To resolve this, please try the following:
For more information, please refer to: Manage connections to Dataverse - Power Automate | Microsoft Learn
I hope your issue gets resolved soon. Any updates would be greatly appreciated.