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
Hello,
Hoping someone has some ideas ... we have a PowerShell-based site provisioning process that has been working fine for some time now (close to 2 years) using PnP PowerShell 1.12. Among other things the code deploys an app from the SharePoint App Catalog into any of our new sites as part of this process. We are now updating this process and (among other things) have moved to a more recent version of PnP PowerShell (currently using the latest v3.1) for a variety of reasons. Fundamentally it’s the same process/script, just with some tweaks/updates related to the site configurations. We are still using the same code to deploy the app as before (that has not changed).
However, what we have found is that, while the provisioning script initiates adding the app to the site, the app will sit there for a while attempting to install
**
… but eventually the status is updated, and it then shows
At that point, if I click the Retry link, it installs immediately and all is well … Question is why is it never completing the install until a user manually clicks the Retry link?
I know that back in September there was a permission change that was required to continue to use PowerShell against SPO which required that we implement an app reg for PowerShell (as described in this link).
As you can see from our connect call above, we use the corresponding App Reg App Id to initiate our connections. That’s been working fine so far Including for all the actions that are performed by our provisioning script. Is there maybe another ‘specific’ permission that might need to be added to the app reg for PowerShell for the script to be able to deploy the SPOC app? Our current app reg for PowerShell is shown in the below screenshot.
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
-
Hello,
Hoping someone has some ideas ... we have a PowerShell-based site provisioning process that has been working fine for some time now (close to 2 years) using PnP PowerShell 1.12. Among other things the code deploys an app from the SharePoint App Catalog into any of our new sites as part of this process. We are now updating this process and (among other things) have moved to a more recent version of PnP PowerShell (currently using the latest v3.1) for a variety of reasons. Fundamentally it’s the same process/script, just with some tweaks/updates related to the site configurations. We are still using the same code to deploy the app as before (that has not changed).
$ctxSp = Connect-PnPOnline -url $curSiteParams["trgtUrl"] -ClientId $appId -Tenant $tenantId -Thumbprint $certThumbprint -ReturnConnection
Get-PnPApp -Identity $App.Id -Connection $ctxSp | Install-PnPApp -Connection $ctxSp
However, what we have found is that, while the provisioning script initiates adding the app to the site, the app will sit there for a while attempting to install
… but eventually the status is updated, and it then shows
At that point, if I click the Retry link, it installs immediately and all is well … Question is why is it never completing the install until a user manually clicks the Retry link?
I know that back in September there was a permission change that was required to continue to use PowerShell against SPO which required that we implement an app reg for PowerShell (as described in this link).
As you can see from our connect call above, we use the corresponding App Reg App Id to initiate our connections. That’s been working fine so far Including for all the actions that are performed by our provisioning script. Is there maybe another ‘specific’ permission that might need to be added to the app reg for PowerShell for the script to be able to deploy the SPOC app? Our current app reg for PowerShell is shown in the below screenshot.
Any ideas welcome
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions