10-11-2019 02:41 AM
10-11-2019 02:41 AM
One of our customer who wants to use Teams/Sharepoint/Exchange, but they want to manage it from 1 single point.
For example, they have 3 groups.
- Team Lead
So when they make 1 new user a member of Management, it should also get the rights from Team Lead and Sales.
And when we make 1 new user a member of Team lead, it should also get the rights of Sales.
Similarly there’ll be ‘n’ number of Groups to be managed.
Currently, they’re using Office 365 Security Groups to achieve the same, but it limits the control only to SharePoint resources and not for Teams and Exchange.
10-11-2019 04:45 AM
Hi, can you explain what you mean by this: "Currently, they’re using Office 365 Security Groups to achieve the same, but it limits the control only to SharePoint resources and not for Teams and Exchange"
Do you mean control to sharepoint is limited, while control to teams and exchange is not?
And what do you mean by control? Do you mean Sharepoint, Teams, and exchange administrator roles?
10-11-2019 08:29 AM
Thank you for your response. They've created Office 365 Security groups so that they can have specific users who can have an access to SharePoint resources. However, they will not have specific access to Teams and Exchange. Yes, I meant administrating SPO, EXO and Teams when my account is on different groups such as Management, Team Lead and Sales say for example.
10-11-2019 09:20 AM
We cannot use groups to delegate access to the Office 365 admin roles. Meaning you will be limited to the workload-specific admin controls. This will work OK for Exchange, where you can delegate every action to a Group (nesting included), but the other workloads are limited in this regards. It all boils down to which specific actions you want them to be able to perform. But you will probably end up having to look for a third-party "admin portal replacement" type of tool.
10-11-2019 11:11 AM
10-11-2019 11:19 AM
by Christine Goetz on November 30, 2016
by Martin Nothnagel on July 29, 2020
by Anne Michels on July 24, 2017
by Brian Levenson on April 11, 2017