Forum Discussion
What O365 roles can run PowerShell scripts?
Global Admin is only needed for a few things, if you start crossing into OneDrive scripting, or things that require you to touch the -admin site collection for example.
Do you have to be a global admin to enable licenses (like SPO) via PowerShell?
Im guessing you need to be either a Global Admin or User Management Admin
You need the same role as you would need to do it in the portal.
https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc
- All, just the results of my tests:
(1) To use PowerShell at the SPO Tenant Level you need to be a Global Admin or a SPO Admin. This allows you to work with SharePoint Online Management Shell
(2) To use PowerShell at the Site Collection Level it's enough to be a site collection Admin as stated by Brent...but you have to run your PowerShell code using ISE or Visual Studio and you have to work with Client Side Object ModelWe found Friday that an individual who administers our Azure subscription subscription that connects to O365 can't do certain tasks within the Azure Portal without Global Admin rights in the O365 Portal. Specifically, he couldn't create a new App ID within Azure AD and also couln't move an Azure RMS subscription key. He did have User Managment and SPO Admin rights in our O365 Portal, but we had to give him Global Admin rights to perform those two tasks. I couldn't find any documentation that details out tasks done in Azure Portal that would require Global Admin rights in the O365 Portal. Does anyone know of such documentation or could explain why those actions done in Azure Portal require O365 Global Admin rights? What other tasks in Azure Portal would require Global Admin role in O365 Portal?
