The purpose of this article is to have a clear picture about the permissions required on each Atlas customer Microsoft 365/Azure tenants in order to complete a successful Atlas deployment.
To start the deployment, the customer would need to execute some scripts following the Atlas Runbook for Admin and send to ClearPeople the output files to configure and execute the pipeline in Azure DevOps.
Additional to the above, there are some actions in the Atlas deployment that can be carried out by ClearPeople (If full Global Administrator role is given) or by the customer's administrator described in the table below:
Product |
Role/Permissions |
Actions |
Microsoft Teams |
Teams Administrator |
|
SharePoint |
Global Administrator |
|
Azure |
Global Administrator |
|
For a more detailed breakdown of permissions required for the whole deployment you can check the table below:
Task or Activity | Global Tenant Admin | Azure Subscription Contributor | Resource Group Owner | SharePoint Admin | Teams Admin | SharePoint Member / Visitor |
Upload Teams apps and change settings | Required | |||||
Install resource providers | Required | |||||
Create Azure Resource Group | Required | |||||
Deploy Azure Infrastructure | Required | |||||
SharePoint components/settings | Required | |||||
Grant Permissions (SPFx and Azure AD Apps) | Required | |||||
Set-up tyGraph Analytics | Required | |||||
CSM Tasks and Activities | Required | |||||
Tech CSM / Consultant | Required | |||||
Support Tasks and Activities | Required | Required |
For more information please check the documents Atlas Prerequisites for Customer and the Atlas Runbook for Admins that were provided as part of the Atlas delivery process (You can find links to them in the Process Street link provided by your CSM or otherwise reach out to your CSM directly to request a copy.
Comments
0 comments
Please sign in to leave a comment.