You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by renewtx November 6, 2024
Hello,
For the below we use:
PowerShell v7.4.5
PnP PowerShell v2.99.35-nightly (had to use this due to another issue)
We have a PnP PowerShell script that basically queries the Power Automate environment for flows ... this was working fine until Sept when the PnP team implemented the change that now requires an App Reg to authenticate. We've implemented this change and set up two different PnP PowerShell App Reg instances -- one to use with interactive logins and another to use for non-interactive (app only) logins. The interactive app reg appears to be working fine.
For the script that interacts with the PowerAutomate env (without an interactive login), we previously used
and immediately after connection we ran this statement ...
$flows = Get-PnPFlow -Environment $environmentName -SharingStatus Personal
At the time this all worked as expected.
To support the new connection requirements pushed out in September, and after creating the necessary app reg instances, we have now modified the script to connect as follows:
This appears to set up a valid connection which I can verify using Get-PnPContext (which returns valid context information) and I can execute other PnP commands under this context. However, when we now call
we get the error "Get-PnPFlow: Authentication failed." Is this a new issue? Or is other information required to now execute this Get-PnPFlow call??
Also, we used to use a parameter -SharingStatus, as in
Get-PnPFlow: A parameter cannot be found that matches parameter name 'SharingStatus'.
which now no longer seems to be recognized -- did that change as well?? Is there updated documentation for this and other PowerAutomate-related PnP commands?
This discussion was converted from issue #4526 on November 09, 2024 17:06.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Discussed in #4521
Originally posted by renewtx November 6, 2024
Hello,
For the below we use:
We have a PnP PowerShell script that basically queries the Power Automate environment for flows ... this was working fine until Sept when the PnP team implemented the change that now requires an App Reg to authenticate. We've implemented this change and set up two different PnP PowerShell App Reg instances -- one to use with interactive logins and another to use for non-interactive (app only) logins. The interactive app reg appears to be working fine.
For the script that interacts with the PowerAutomate env (without an interactive login), we previously used
and immediately after connection we ran this statement ...
At the time this all worked as expected.
To support the new connection requirements pushed out in September, and after creating the necessary app reg instances, we have now modified the script to connect as follows:
This appears to set up a valid connection which I can verify using Get-PnPContext (which returns valid context information) and I can execute other PnP commands under this context. However, when we now call
we get the error "Get-PnPFlow: Authentication failed." Is this a new issue? Or is other information required to now execute this Get-PnPFlow call??
Also, we used to use a parameter -SharingStatus, as in
which now no longer seems to be recognized -- did that change as well?? Is there updated documentation for this and other PowerAutomate-related PnP commands?
Beta Was this translation helpful? Give feedback.
All reactions