Microsoft 365 External Sharing: How to Control Guest Access to Business Data

Person in a red sweatshirt typing on a laptop in a dark room.
This entry was posted in Office 365 and tagged on by .

What Is Microsoft 365 External Sharing?

Microsoft 365 external sharing lets people in your organization share files, folders, sites, and collaboration spaces with people outside it. Depending on the service and sharing method, recipients may use an anonymous link, authenticate to a named-recipient link, or collaborate through a guest identity or a Teams shared channel.

The right controls depend on what is being shared, who needs access, and how long that access should last. File-sharing links, guest accounts, and Teams external access are related, but they are not interchangeable.

If you know this topic as Office 365 external sharing, the central task is the same: allow useful collaboration with clients, vendors, and partners without giving them unnecessary access to business data.

How External Sharing Works Across SharePoint, OneDrive, and Teams

External sharing is not a single Microsoft 365 switch. SharePoint and OneDrive settings, Microsoft 365 group membership, Teams policies, and Microsoft Entra identity controls work together.

SharePoint External Sharing

SharePoint supports sharing individual files and folders as well as giving guests access to sites. Sharing one file does not necessarily grant access to the entire site. Adding someone to a site or its connected Microsoft 365 group can provide broader access, depending on the permissions assigned.

Organization-level SharePoint settings establish the maximum sharing level. An individual site can be more restrictive, but cannot exceed that maximum. Administrators can also restrict which users are allowed to share externally.

OneDrive External Sharing

OneDrive uses the SharePoint sharing framework for an individual user’s files. The organization-level OneDrive setting cannot be more permissive than the SharePoint setting, and an individual OneDrive can be restricted further. Moving a sensitive file to OneDrive does not make its sharing permissions safe automatically.

Two coworkers smiling while looking at a desktop monitor.

External collaboration works best when access is limited to the people and resources a project requires.

Teams Guest Access, External Access, and Shared Channels

Guest access adds an external collaborator to a team through a Microsoft Entra B2B guest identity. Team members, including guests, can participate in standard channels. A private channel has a separate membership list, so joining the team does not automatically grant access to every private channel.

External access supports communication such as chat, calls, and meetings with people outside the organization. It is not the same as membership in a team and does not by itself grant access to that team’s SharePoint files.

Shared channels support a different collaboration model. External participants use Microsoft Entra B2B direct connect rather than being added as guest accounts in the host team. Both organizations’ cross-tenant settings need to support the collaboration. Guest accounts cannot be added to shared channels.

Teams channel files are stored in SharePoint. Standard channels use the team’s site, while private and shared channels have separate sites. Microsoft’s channel comparison and shared-channel guidance explain the different membership boundaries.

Which External Sharing Control Should You Use?

Choose the access model before choosing a link. The following decision table is a practical starting point, not a Microsoft default policy.

Business Need Suitable Starting Point Important Boundary
Distribute genuinely public, low-sensitivity material An Anyone link, if anonymous sharing is permitted. Recipients do not authenticate. The link can be forwarded; apply an expiry and appropriate permissions.
Share a file or folder with named clients or vendors A Specific people link, with view or edit permissions matched to the task. Recipients must authenticate through a supported method. Review existing permissions as well as the new link.
Provide ongoing access to a project site or team Guest collaboration through Microsoft Entra B2B, with a business owner and a review process. Site or group membership can grant access to more than one file. Private-channel membership remains separate.
Collaborate in a channel with another organization without adding its users to the whole team A Teams shared channel using B2B direct connect, where supported. This is not ordinary guest access. Confirm cross-tenant policies and channel membership.
Send a convenient link to people who already have permission A People with existing access link. This link does not grant new access, so it cannot solve a missing-permission problem.

Anyone and Specific people are link types. Guest collaboration and shared channels are collaboration models. Keeping those concepts separate makes it easier to understand what a setting actually controls.

The Risks of Unmanaged External Sharing

Anonymous links can travel beyond their intended audience. Anyone with a valid link may be able to open the content, subject to the link’s permissions and the service’s controls. Do not use anonymous sharing for sensitive material simply because it is convenient.

Permissions can outlast the business relationship. A guest may retain access after a project ends if nobody removes the relevant permissions or group membership. Inventory both guest identities and the resources they can access.

Workspace membership can be broader than a file invitation. Adding a partner to a site or team can expose additional content within that membership boundary. Check the resource and permission level before granting access.

Permissive settings allow risky choices but do not erase stricter restrictions. A tenant that permits Anyone links may still have sensitive sites that prohibit them. Review the effective combination of organization, site, user, and resource settings instead of treating the tenant slider as the whole policy.

Office employees working at computers, with code visible on a foreground monitor.

Review sharing settings and effective permissions together, rather than relying on a single Microsoft 365 setting.

Microsoft Purview data loss prevention can help identify sensitive information and enforce policies in supported locations. DLP and access permissions complement each other. Backup and recovery serve a different purpose and do not substitute for preventing unauthorized sharing.

Tenant-Level, Site-Level, and Identity Controls

In the SharePoint admin center, Policies > Sharing controls organization-level sharing. The available levels are Anyone, New and existing guests, Existing guests, and Only people in your organization. OneDrive cannot be set more permissively than SharePoint.

To change a site’s external-sharing level, a SharePoint Administrator or another appropriately authorized administrator uses Active sites > select the site > Settings > More sharing settings. Site owners can manage permissions and sharing within the permitted boundaries; the site-owner role alone should not be confused with authority to change the administrative sharing level.

Microsoft documents the organization-level options in Manage sharing settings and the site-specific process in Change the sharing settings for a site.

Domain Restrictions and Who Can Share

SharePoint can allow or block sharing with specified domains. An allowlist is useful when collaboration is limited to known partners, but a permitted domain is not proof that a particular person should see a particular file.

Review SharePoint domain rules alongside Microsoft Entra external collaboration and cross-tenant access settings. They govern different parts of the process. Teams communication policies and shared-channel controls also need their own review; a SharePoint domain rule is not a universal Microsoft 365 block.

The SharePoint organization-level sharing settings also support allowing only users in specified security groups to share externally. This provides a more direct sharing control than relying on guest-invitation permissions alone.

See Microsoft’s guidance on restricting SharePoint and OneDrive sharing by domain and Microsoft Entra B2B collaboration when coordinating these policies.

What Changed with SharePoint OTP in October 2026?

Microsoft says retirement of legacy SharePoint Online one-time passcode authentication rolls out to commercial tenants during October 2026. This is not retirement of Microsoft Entra B2B email one-time passcode, which remains a supported fallback authentication method when enabled.

When the retirement reaches a tenant, external users need a matching Entra B2B guest account to access previously shared Specific people links. Users who already have a matching account retain access. If the account is missing, an administrator can create it, or a user with sharing permission can share or reshare at least one file, folder, or site to create it.

It is not necessary to reshare every item individually. Check the tenant’s rollout status and affected recipients rather than assuming that all guests or all links have stopped working. Microsoft’s external-sharing transition FAQ explains the distinction and remediation.

Link Expiration, Guest Access Expiration, and Access Reviews

These controls solve different problems:

  • Link expiration limits the validity of a sharing link where supported. SharePoint allows administrators to require expiry for Anyone links. Do not assume the same expiry control applies identically to every link type.
  • Guest access expiration limits guest access to a site or OneDrive under the applicable settings. It is not the same as deleting the guest’s directory account or ending every access path across Microsoft 365.
  • Access reviews ask designated reviewers to confirm whether access to selected groups or applications is still needed. Removing access through a review does not necessarily delete the guest identity.
  • Account lifecycle management addresses the identity itself, including who owns it, when it should be disabled or removed, and what resources still depend on it.

For automated reviews, configure both the decision to apply when a reviewer does not respond and whether results are applied automatically. Enabling auto-apply alone does not mean every unanswered review will remove access.

Check licensing before promising automation. Access-review capabilities depend on the relevant Microsoft Entra ID Governance, Entra Suite, or supported Entra ID P2 features. Conditional Access, DLP, and audit capabilities also have licensing and configuration requirements. Do not assume every Microsoft 365 subscription includes the same controls. Microsoft’s access-review overview provides the licensing starting point.

Woman wearing a headset while working on a laptop, with a coworker in the background.

Assign owners for guest access, policy exceptions, and regular permission reviews.

Audit records help investigate how content was shared and accessed, but historical sharing events are not a complete current-permissions inventory. Use resource permissions, group membership, sharing reports, and relevant logs together. Anonymous-link use cannot be attributed to an authenticated guest in the same way as named-recipient access. See Microsoft’s sharing-audit documentation.

A Practical Starting Policy for Business Collaboration

The following is a recommended starting point to adapt to your organization, not a universal Microsoft policy:

  • Use named-recipient sharing for business documents and grant view or edit access only as needed.
  • Allow anonymous links only for an approved use case, with an appropriate expiry and minimal permissions.
  • Apply tighter settings to HR, legal, financial, and other sensitive sites. Avoid mixing public material and confidential project work in the same access boundary.
  • Assign a business owner and an expected end date or review date to each ongoing external collaboration.
  • Use MFA and suitable identity controls where available, and test the experience with partner identities before enforcing a new policy.
  • Review permissions regularly and after project completion, personnel changes, or a security incident. Choose the cadence based on risk rather than assuming quarterly reviews are always sufficient.

How to Configure and Audit Microsoft 365 External Sharing Permissions

Use a test site and an approved external test identity before applying broad changes. Record the current configuration so that changes can be reviewed and reversed if necessary.

  1. Inventory the collaboration need and sensitive locations. Identify which partners need access, the files or workspaces involved, the required permission level, and an accountable owner. Identify sensitive sites that should remain internal.
  2. Review organization-level sharing settings. As a SharePoint Administrator or another authorized administrator, open SharePoint admin center > Policies > Sharing. Choose the SharePoint and OneDrive levels that meet approved business needs; the OneDrive setting cannot be more permissive than SharePoint.
  3. Set default links and anonymous-link limits. Choose a default link type and permission level appropriate to your workflow. Where Anyone links are allowed, configure a suitable expiry and available permission restrictions. View-only does not automatically mean download is blocked, and download restrictions do not prevent every form of copying.
  4. Coordinate domain and sharer restrictions. Review SharePoint domain allow/block rules, any security groups permitted to share externally, and Microsoft Entra invitation and cross-tenant policies. Check the impact on existing partner workflows rather than treating one list as a complete control for every service.
  5. Apply tighter site-level settings. In SharePoint admin center > Active sites, select the site, then Settings > More sharing settings. Set appropriate sharing limits and relevant guest-expiration options. Confirm the effective permissions for sensitive content as well as the site’s sharing level.
  6. Verify guest identities and the OTP transition. In Microsoft Entra admin center, review guest users and their business purpose. For recipients affected by legacy SharePoint OTP retirement, confirm a matching B2B guest account exists or use Microsoft’s documented create-or-reshare process.
  7. Review Teams and channel membership separately. Check Teams guest and external access policies, Microsoft 365 group membership, private-channel membership, and shared-channel cross-tenant settings as applicable. Test file access in the associated SharePoint site rather than assuming chat access proves file access.
  8. Configure access reviews within available licensing. Select the groups or applications to review, name responsible reviewers, define the cadence and fallback decision for unanswered reviews, and decide whether results are applied automatically. If automated reviews are unavailable, maintain a documented manual process.
  9. Test access and inspect sharing activity. Use an authorized external test identity to confirm expected access and denial cases. Review Manage access and resource permissions alongside sharing reports and relevant Microsoft Purview audit events. Investigate unexpected links, recipients, or changes.
  10. Document the policy and remove obsolete access. Record approved settings, owners, exceptions, review dates, and the offboarding process. Remove unnecessary links and permissions, address guest identities through the lifecycle process, and verify the result. Follow service-specific session-revocation procedures when immediate containment is required.

Why Can’t an External User Open a Shared File?

Work through the access layers instead of creating broader links as a quick workaround:

  • Confirm the signed-in identity. The recipient may be using a different work or personal account from the one named in the invitation.
  • Check the resource and link. Verify the correct file or site, whether the link still exists or has expired, and whether the recipient has the required permissions. An existing-access link does not add permissions.
  • Check organization and site settings. A restrictive site, domain rule, or sharer restriction may prevent the intended collaboration even when the organization permits external sharing generally.
  • Check guest and identity policies. Confirm the matching guest identity, invitation/redemption state, and applicable Conditional Access or cross-tenant policies. Review legacy OTP transition issues where relevant.
  • Check Teams membership boundaries. Guest access, private-channel membership, shared-channel participation, and the underlying SharePoint permissions are different checks.

Record the error, resource URL, recipient identity, and time of the failure for IT investigation. Do not respond to an access problem by switching confidential content to an Anyone link.

FAQs About Microsoft 365 External Sharing

Do external guests need a Microsoft account to access shared files?

Not always. Microsoft Entra B2B supports several identity methods, including work or school accounts and supported federation options. Email one-time passcode can provide a fallback when enabled. Legacy SharePoint OTP retirement is separate from Entra B2B email OTP, which remains supported. The method available depends on the organization’s configuration.

Can external sharing be disabled for specific users without disabling it organization-wide?

Yes. SharePoint administrators can limit external sharing to users in specified security groups, and resource permissions can further restrict sharing. Microsoft Entra invitation permissions are another control, but restricting who can invite a new guest is not identical to controlling every sharing action. Review the settings together and test both new and existing guests.

What happens to shared files when guest access is revoked?

The result depends on what is revoked: a link, resource permission, group membership, or the guest identity. Remove the relevant access paths and verify the outcome. Identity changes should not be treated as guaranteed immediate termination of every application session. Anyone links are not tied to a named guest, so they must be handled separately. Already downloaded copies are not recalled by removing access.

Can external guests access Microsoft 365 content on mobile devices?

Guests can access supported Microsoft 365 services on mobile devices when they have the required permissions and an accepted authentication method. Conditional Access can impose restrictions where available. Device-compliance and cross-tenant trust requirements need careful configuration and partner testing; guest-device policies should not simply be assumed to work identically to policies for managed internal devices.

What happens to guest access when a Microsoft 365 tenant is migrated or consolidated?

Guest identities, permissions, and sharing links need explicit migration planning. Whether they are preserved, remapped, recreated, or replaced depends on the migration method and tooling. Inventory existing access, confirm the supported behavior of the chosen process, communicate changes to partners, and test destination access before and after cutover.

Can guest users create or edit content, or are they limited to viewing?

Guest capabilities depend on the permissions granted to the file, folder, site, group, or team. Some guests can edit or upload; others can only view. Permissions to share with additional people are a separate consideration. Grant the minimum access needed and review existing memberships rather than assuming every guest has the same capabilities.

How can an organization tell which external users currently have access to its data?

Combine guest-directory information with current site, group, team, channel, and file permissions, relevant sharing reports, and audit logs. A guest list alone does not show every accessible resource, and historical sharing events are not a complete current-state inventory. Include active Anyone links and shared-channel external participants in the review because these are not represented by ordinary guest accounts alone.

Keep External Collaboration Useful and Controlled

Microsoft 365 external sharing works best when each collaboration has a clear purpose, a defined access boundary, and an owner responsible for reviewing it. The goal is not to stop employees from working with partners. It is to give the right people the access they need and remove it when the need ends.

Be Structured provides managed IT services to Los Angeles businesses, including Microsoft 365 configuration and ongoing administration. Our all-inclusive managed services can support routine policy and access reviews. If a tenant change is part of your project, include guest and link testing in your Microsoft 365 migration plan.

Contact Be Structured to discuss a Microsoft 365 security assessment.

About Chad Lauterbach

Founder & CTO at Be Structured Technology Group, Inc., a Los Angeles-based provider of Managed IT Services for small businesses. I desire to help small businesses better utilize technology by assisting in high-level planning to make sure that new systems will benefit them both operationally and financially. I am careful to implement and support systems using industry best practices. I am a CMMC Registered Practitioner Advanced (RPA) with the Cyber AB.