Identity Governance & Administration
sara.next
  1. sara.next
  2. Solutions
  3. Microsoft 365: access and group governance

Solutions · By need

Microsoft 365: access and group governance

A model for managing requests, groups and reviews of access to Teams, SharePoint and Microsoft 365 services.

  • Teams
  • SharePoint
  • groups
  • integration scope to be confirmed

Context

Access to M365 is spread across groups, teams and resources

In Microsoft 365 a user's access may result from membership of an Entra ID group, a Microsoft 365 group, a Teams team, SharePoint site permissions or direct sharing of a file. Managing the account in the directory alone does not show the full picture of access to information.

sara.next can act as the process layer: the user requests specific access, the resource owner approves it, and the change is made and later subject to review.

NoteIntegration with Microsoft Graph / Entra ID, mapping Teams and SharePoint permissions and automatic execution of changes are project scope to be confirmed, not a universal feature ready for every installation.

The big picture

Where access comes from and where the process works

01 · Sources of access in M365

  • Entra ID group
  • Microsoft 365 group
  • Teams team
  • SharePoint sitesite permissions
  • Filedirect sharing

02 · Process layer

  • Requestthe user specifies the access
  • Approvalresource owner
  • Making the changeAPI or an administrator task
  • Reviewperiodic review of assignments

sara.next

03 · Executing changes

  • Microsoft Graph / Entra IDintegration
  • Teams and SharePointpermission mapping
  • A task for the administratorwhen there is no automation

project scope to be confirmed

Illustrative diagram. Group governance is not automatically governance of all files.

Deployment

Proposed implementation model

  1. Inventory

    An inventory of groups, teams, sites and resource owners.

  2. Choosing resources

    Choosing resources with significant risk, e.g. repositories of financial documents.

  3. Roles and scopes

    Defining roles and access scopes in sara.next.

  4. Approval workflow

    Configuring an approval workflow by the business owner.

  5. Execution

    Connecting to the appropriate API or setting up a task for the administrator.

  6. Review

    Periodic review of assignments and handling of permission revocation.

Scenario

Project team

A new consultant needs access to a Teams team and the project's document library. The request specifies the project, the role and the validity period. The project owner approves the access.

When the contract ends, the relevant assignments are removed — provided the organisation has ensured a reliable end-of-collaboration event and the appropriate execution integration.

An implementation expert's view

Before anyone promises "full control of SharePoint"

The biggest challenge in M365 is permissions granted outside the central process: direct sharing, links and local decisions by resource owners.

Before promising "full control of SharePoint" you need to establish which kinds of permissions the system actually reads, enforces and covers by reviews. Group governance is not automatically governance of all files.

Scope

Limits of the solution

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.

sara.next does not replace the native DLP, Conditional Access or Microsoft Purview information classification mechanisms.

Verify a scenario for managing groups and access to a selected site

During a technical consultation we will go through your applications, roles and the scope of the first implementation stage.