Replies: 2 comments
-
You will have to be a SharePointAdministrator to be able to Connect to PNP to run the commands. You would need a Tenant-level account for each automation. Could use a service account for it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
hey @braadinny , thanks for raising this. Going to move it to a discussion |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Notice
As per new requirement, Pnp powershell needs to be registered with AllSites.Read permission.
https://pnp.github.io/powershell/articles/registerapplication.html
I work for a small agency that shares a Microsoft 365 tenant with several other agencies. My access is limited to being a Site Collection Administrator for the sites specific to my agency.
Given these constraints, is there a way to leverage PnP PowerShell to automate tasks within my agency’s site collections without requiring intervention from the Tenant-level SharePoint Administrators for each automation?
AllSites.Read expose read access to the sites that are not part of my agency and it is a huge security risk.
Beta Was this translation helpful? Give feedback.
All reactions