DemoContoso Ltd is a fictional company. The grade, the findings and the attack paths came from Tenant Strike’s engine reading made-up data.

Run it on your own tenant →

Sharing & Collaboration

Who can see your files

SharePoint, OneDrive and Teams sharing

Measured score

91

Partial assessment · 1 left out of the score

13Total
3Need attention
8In good shape
1Do not apply
1Not verified
0Suppressed

Needs attention (3)

  • Should fixNeeds fixingWho can see your files

    Restrict OneDrive sync to domain-joined devices

    What this means

    OneDrive sync is permitted on ANY device. Users can install OneDrive on personal laptops, home desktops, or borrowed machines and pull a full local copy of all files they can access. That data then escapes all tenant controls — BitLocker, remote wipe, CA, audit logging.

    What to do

    Limit OneDrive sync to devices joined to your on-premises domains, or hold sync to compliant devices with a Conditional Access policy.

    Who does it
    Your IT person or provider
    How long
    About 15 minutes
    Before you change it
    Users on personal/BYOD devices will lose the ability to sync OneDrive locally. They can still access files via OneDrive web. For BYOD-heavy organizations, consider Intune App Protection Policies as an alternative.
    1 evidence row
    Technical detailssetting, steps, evidence

    The setting

    OneDrive sync restriction to domain-joined computers

    SharePoint admin center → Settings → Sync → 'Allow syncing only on computers joined to specific domains'

    Now: Disabled (any device can sync)→Should be: Enabled (listed domains only)

    Open in the admin portal ↗

    Steps

    1. admin.microsoft.com → SharePoint admin center → Settings → Sync
    2. 'Allow syncing only on computers joined to specific domains' OR
    3. Set 'isUnmanagedSyncAppForTenantRestricted' via Graph PATCH

    Microsoft Graph

    PATCH /beta/admin/sharepoint/settings
    { "isUnmanagedSyncAppForTenantRestricted": true }

    Evidence · 1 recorded item

    • Sync limited to domain-joined computers — Disabled

    How an attacker would use it

    Disgruntled or departing employee installs OneDrive on their personal MacBook, signs in, syncs their entire OneDrive locally (which often includes shared SharePoint libraries they have access to). When they leave the company and their account is disabled, the cloud access is cut — but the local copy on their personal device remains, untouchable.

    Learn more ↗
  • Should fixNeeds a lookWho can see your files

    Restrict Teams external access

    What this means

    Judged: Global. Global: AllowFederatedUsers is true and AllowedDomains is empty, so Teams external access is open to every Teams organization. 1 to tighten.

    What to do

    Limit Teams external access to the partner domains you work with, and block trial organizations.

    Who does it
    Your IT person or provider
    How long
    About 15 minutes
    1 evidence row
    Technical detailssetting, steps, evidence

    The setting

    Teams external access: allowed domains

    Teams admin center → Users → External access → Teams and Skype for Business users in external organizations

    Now: AllowFederatedUsers is true and AllowedDomains is empty, so Teams external access is open to every Teams organization→Should be: Allow only specific external domains; ExternalAccessWithTrialTenants = Blocked

    Open in the admin portal ↗

    PowerShell

    Connect-MicrosoftTeams
    Get-CsTenantFederationConfiguration | Format-List AllowFederatedUsers, AllowedDomains, ExternalAccessWithTrialTenants
    # Choose the partner domains in the Teams admin center, then:
    Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants Blocked

    Evidence · 1 recorded item

    • Global — AllowFederatedUsers is true and AllowedDomains is empty, so Teams external access is open to every Teams organization
  • MinorNeeds a lookWho can see your files

    Block guest re-sharing

    What this means

    Guests may pass on items shared with them, but only to guests who already exist in your directory (you have none).

    What to do

    Disable guest re-sharing tenant-wide. Guests can still ask the document owner to invite additional collaborators directly.

    Who does it
    Your IT person or provider
    How long
    About 5 minutes
    Before you change it
    Workflows where a guest forwards a shared document to another contact at their own org will break. They'll need to request an additional direct invite from the document owner.
    2 evidence rows
    Technical detailssetting, steps, evidence

    The setting

    SharePoint guest re-sharing

    SharePoint admin center → Policies → Sharing → More external sharing settings → 'Allow guests to share items they don't own'

    Now: On (guests can re-share)→Should be: Off

    Open in the admin portal ↗

    Steps

    1. admin.microsoft.com → SharePoint admin center → Policies → Sharing
    2. Under 'External sharing' → 'More external sharing settings'
    3. 'Allow guests to share items they don't own' → Off
    4. Save

    Microsoft Graph

    PATCH /beta/admin/sharepoint/settings
    { "isResharingByExternalUsersEnabled": false }

    Evidence · 2 recorded items

    • isResharingByExternalUsersEnabled — true
    • External sharing setting — existingExternalUserSharingOnly
    Learn more ↗

Not verified (1)

In good shape (8)
  • In good shapeWho can see your files

    Restrict SharePoint external sharing

    SharePoint external sharing is appropriately restricted (existingExternalUserSharingOnly).

    Technical detailsevidence

    Evidence · 1 recorded item

    • External sharing setting — existingExternalUserSharingOnly
  • In good shapeWho can see your files

    Disable SharePoint legacy authentication

    SharePoint legacy authentication protocols are disabled.

    Technical detailsevidence

    Evidence · 1 recorded item

    • SharePoint legacy auth protocols — Disabled
  • In good shapeWho can see your files

    Restrict OneDrive external sharing

    OneDrive external sharing is appropriately scoped. It is capped at your tenant-wide external sharing setting (existingExternalUserSharingOnly), and Microsoft enforces that OneDrive can only be equal to or more restrictive than SharePoint.

    Technical detailsevidence

    Evidence · 2 recorded items

    • Tenant external sharing (OneDrive ceiling) — existingExternalUserSharingOnly
    • OneDrive override — Microsoft enforces OneDrive ≤ SharePoint; the OneDrive-specific value is not exposed by the read-only Graph API.
  • In good shapeWho can see your files

    Restrict cross-tenant collaboration

    Cross-tenant collaboration is restricted in both directions.

    Technical detailsevidence

    Evidence · 3 recorded items

    • B2B Collaboration inbound — Restricted
    • B2B Collaboration outbound — Restricted
    • Policy source — Customized
  • In good shapeWho can see your files

    Block personal Teams accounts

    Judged: Global. Your people can start chats with personal Teams accounts, but personal accounts cannot start one with them.

    Technical detailssetting, steps

    The setting

    Teams external access: personal Teams accounts

    Teams admin center → Users → External access → Teams accounts not managed by an organization

    Now: Meets the standard→Should be: AllowTeamsConsumerInbound = false

    Open in the admin portal ↗

    PowerShell

    Connect-MicrosoftTeams
    Set-CsTenantFederationConfiguration -AllowTeamsConsumerInbound $false
  • In good shapeWho can see your files

    Restrict Teams shared channels

    B2B Direct Connect inbound is blocked tenant-wide (Microsoft default). Specific partner tenants can be allowlisted as needed.

    Technical detailsevidence

    Evidence · 2 recorded items

    • B2B Direct Connect inbound — Blocked (Microsoft default)
    • Inbound trust signals — MFA accepted: false · Compliant device accepted: false
  • In good shapeWho can see your files

    Restrict anonymous meeting join

    Judged: Global. In the Global meeting policy, anonymous people can join but wait in the lobby: they are not admitted automatically, cannot start a meeting, and phone callers do not bypass the lobby.

    Technical detailssetting, steps

    The setting

    Teams meeting policy: lobby and anonymous access

    Teams admin center → Meetings → Meeting policies → Global (Org-wide default)

    Now: Meets the standard→Should be: AutoAdmittedUsers = EveryoneInCompany; AllowAnonymousUsersToStartMeeting = false; AllowPSTNUsersToBypassLobby = false

    Open in the admin portal ↗

    PowerShell

    Connect-MicrosoftTeams
    Set-CsTeamsMeetingPolicy -Identity Global -AutoAdmittedUsers EveryoneInCompany -AllowAnonymousUsersToStartMeeting $false -AllowPSTNUsersToBypassLobby $false
  • In good shapeWho can see your files

    Restrict Teams custom apps

    Judged: Global. AllowSideLoading is false in the Global policy, so sideloading is off there. The tenant-wide switch for custom apps is not readable through Microsoft's configuration snapshots. All third-party apps are allowed unless blocked.

    Technical detailssetting, steps

    The setting

    Teams app setup policy: sideloading

    Teams admin center → Teams apps → Setup policies → Global (Org-wide default)

    Now: Meets the standard→Should be: AllowSideLoading = false

    Open in the admin portal ↗

    PowerShell

    Connect-MicrosoftTeams
    Set-CsTeamsAppSetupPolicy -Identity Global -AllowSideLoading $false
Does not apply (1)