- sara.next
- Integrations
- Microsoft 365, SharePoint and Teams
Integrations · Systems
Microsoft 365, SharePoint and Teams
Access to teams, groups and document libraries changes very often and has a direct impact on information security — which makes it a frequent candidate for an integration pilot. The scope of automation is confirmed in the project.
- Microsoft Graph
- Microsoft 365 groups
- security groups
- scope to be confirmed in the project
Scope
What can be covered by the process
The request, approval and review process works regardless of how the change is executed. Permissions granted outside groups — direct sharing and links — require a separate decision on whether and how they will be covered by the process.
Project teams
Controlled adding and removing of users in Teams teams.
SharePoint resources
Libraries, folders and document spaces — through groups.
Time-bound access
For the duration of a project, with an automatic revocation process.
Access reviews
Periodic confirmation of access to designated resources.
Example
Access to a project team
In Microsoft 365 access changes when
- joining projects
- team changes
- the end of collaboration
- periodic clean-ups
Scope
Limits of the integration
NoteYou should not claim full synchronisation or complete discovery of M365 permissions without testing the connector, the API scope, the integration application's permissions and exception handling.
Group governance is not automatically governance of all files: before deployment you need to establish which kinds of permissions the system actually reads, enforces and covers by reviews.
sara.next does not replace the native DLP, Conditional Access or Microsoft Purview information classification mechanisms.
See sara.next on your own scenarios
During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.