Skip to content
    IT Support

    Microsoft 365 External Sharing Review: A Practical Checklist

    5 min read
    Microsoft 365 External Sharing Review: A Practical Checklist - Petatec blog article image

    A Microsoft 365 external sharing review checks whether people outside your organisation can reach the right content for the right period. Do not begin by switching every sharing feature off. Start with the collaboration need, identify the actual access path and test whether ownership, links and guest accounts still match that need.

    Define the collaboration need first

    Choose the partner, project or business process in scope. Record what external people need to do, which information they need and when the work should end. A supplier uploading one document needs a different arrangement from a project team editing files for six months.

    Name a business owner for the shared workspace or content. The owner should be able to confirm who still needs access and what should happen when the work finishes. IT can provide evidence and controls, but it should not guess the business purpose of every guest.

    Distinguish chat from access to content

    Microsoft Teams uses different collaboration models. External access supports finding, calling, meeting and chatting with people in other organisations, but it does not give them access to a team or its files. Guest access adds an external person to the organisation as a Microsoft Entra B2B guest and can provide access to team resources and files.

    Confirm which model supports the task before changing a tenant-wide setting. If people only need meetings and chat, adding them as guests may create access and lifecycle work that the process does not require.

    Review the control layers together

    External sharing is affected by Microsoft Entra, Microsoft 365 Groups, Teams, SharePoint and OneDrive settings. A Teams workspace also uses a connected SharePoint site for files. Review the complete path rather than checking one admin centre and assuming the result applies everywhere.

    Microsoft's SharePoint and OneDrive sharing guidance explains that each site can be set to the same or a more restrictive level than the organisation. OneDrive can be more restrictive than SharePoint, but not more permissive. Record the organisation setting, site setting, default link type and default permission for the workspaces in scope.

    Know what each link permits

    • Specific people: access is limited to the named recipients and requires the intended identity to verify access.
    • People in your organisation: anyone inside the organisation with the link may gain access, depending on the selected permission.
    • Anyone: the link can provide anonymous access and may work when forwarded to another person.

    Where Anyone links are enabled, review their expiry and whether they allow viewing or editing. A convenient default can become an oversharing route when users do not understand the difference between link types. Microsoft's sharing and collaboration planning guidance describes the available restrictions, expiry controls and link defaults.

    Run a representative access test

    1. Select a non-sensitive test file or controlled test workspace.
    2. Record the intended external identity, link type and permission.
    3. Open the invitation as the external recipient, using the same identity and sign-in route they will use.
    4. Confirm that the intended file or workspace is available.
    5. Try a task that should be denied, such as editing when access is view-only or opening a neighbouring workspace.
    6. Remove or expire the test access, then confirm that the previous route no longer works.
    7. Save the result, exception and responsible owner.

    Use a controlled test account where possible. Do not send live confidential content merely to prove that a sharing setting works.

    An illustrative project-site review

    Assume a project site contains files shared with three supplier guests. The project owner confirms that two people still work on the project and one left the supplier. A separate Anyone link was created for a workshop pack.

    The review should remove the obsolete guest through the approved process, confirm the remaining guests' permissions and decide whether the workshop link still has a purpose. If the link is retained, the owner should accept its permission and expiry. This example is hypothetical and does not describe a Petatec customer.

    Include guest lifecycle and ownership

    Review guest accounts that no longer belong to an active collaboration. Check group and team membership as well as direct file, folder and site access. Removing a guest from one team does not prove that every other permission has ended.

    Microsoft Entra access reviews for guests can support recurring recertification where the required governance capabilities and licences are available. Whether the review is manual or automated, define the reviewer, evidence, decision and action after a denial or non-response.

    Avoid common review mistakes

    • Checking only guest accounts: anonymous links may not appear as a named guest relationship.
    • Changing the tenant setting first: a broad restriction can interrupt valid collaboration without resolving existing ownership.
    • Assuming a link expiry removes every permission: the person may have access through a group, team or direct assignment.
    • Using activity as the only decision: low use does not prove access is unnecessary, and recent use does not prove it remains authorised.
    • Ignoring connected sites: Teams file access depends on SharePoint and may include private or shared channel sites.
    • Recording approval without implementation: verify that the requested access change actually took effect.

    Use a short review record

    • Workspace, content owner and collaboration purpose.
    • External identity, organisation and access route.
    • Link type, permission, expiry and relevant site setting.
    • Decision: retain, reduce, remove or investigate.
    • Implementer, completion evidence and next review trigger.

    Connect the review to the Microsoft 365 joiner, mover and leaver process, privileged access reviews and shadow IT controls. For help assessing Microsoft 365 collaboration, identity and operating responsibilities, see Petatec's infrastructure and cloud services. Discuss a Microsoft 365 sharing review with Petatec.

    Cloud and security

    Strengthen the setup behind the advice.

    Petatec supports cloud migration, cybersecurity, infrastructure optimisation, Microsoft 365, backup, monitoring and operational support.

    We will confirm a suitable time with you.

    30-minute introductory conversationUK GDPR awareService-led advice
    Share this article:

    Related Articles

    Get a second opinion on your IT.

    A short call is enough for a first assessment, free of charge and with no obligation. We reply within one working day.

    Petatec GmbH (Switzerland)

    Mülibach 4, CH-8852 Altendorf, Switzerland

    +41 43 888 07 30

    info@petatec-schweiz.ch

    Petatec Ltd (UK)

    13 Sotheron Road, Watford, WD17 2QB, United Kingdom

    +44 20 8050 1189

    info@petatec.uk