Set-PnPSiteScript doesn't accept new Power Automate triggerFlow URLs

[Callum-Munro]

Reporting an Issue or Missing Feature

This is both an issue and a missing feature - as per this change we need to update our triggerFlow URL values from logic.azure.com to the new Power Automate HTTP trigger URL.

Expected behavior

When using Set-PnPSiteScript to update SiteScript content, we are expecting to replace the old and soon to be deprecated URL with a new Power Automate trigger URL.

Actual behavior

We receive the following error: Set-PnPSiteScript: Action 1 (triggerFlow) is invalid. Parameter url has an invalid value.

Steps to reproduce behavior

• Retrieve the content of a Site Script.
• Convert the JSON to a PS Object for amending.
• Update the triggerFlow URL to a Power Automate trigger HTTP response URL
• Use Set-PnPSiteScript to apply the updated content.

What is the version of the Cmdlet module you are running?

3.1.0

Which operating system/environment are you running PnP PowerShell on?

• Windows

[msznwska]

We also run into that issue. Customers get notified about the need to update URLs for their flows, but we are unable to do this using PnP or SPO cmdlets.

[StephenBoydSG]

Same issue here. Microsoft forcing change of Flow Trigger URL, but receive error above when attempting to change URL using Set-SPOSiteScript. Using Window 11 (latest updates) and Powershell Admin. i.e. No known ability to make the required change