Body
Category: Microsoft 365 > OneDrive / SharePoint
Audience: Client Services, Identity Management, OITS
Submitted: July 31, 2026
Purpose
This article explains how the location of a file or folder within OneDrive, SharePoint, or Microsoft Teams determines the sharing options available to users. Understanding ownership and the parent folder's permissions is critical when troubleshooting why a user cannot select "Anyone" or share content externally.
Overview
A file does not determine its own sharing capabilities. Instead, the parent library or folder controls what sharing options are available.
When troubleshooting sharing issues, always review the Sharing column in OneDrive or SharePoint before investigating permissions.
Example:
Possible values include:
- Private
- Shared
- Owner - Owner/Team Name
Each has different sharing behavior.
Private
If the Sharing column displays Private, the content belongs to the individual user.
Provided the organization's external sharing policies allow it, the user may share files or folders using the available sharing options, including Anyone links.
Shared
If the Sharing column displays Shared, the content exists in a location already intended for collaboration.
Users may generally share these files according to the permissions configured for that location.
If external sharing is enabled for the site, Anyone links may be available.
Owner - Owner/Team Name
If the Sharing column displays:
Owner - Owner/Team Name
the file or folder belongs to another owner or to a SharePoint site associated with Microsoft Teams.
In this scenario:
- The current user is not the owner.
- Sharing options are controlled by the SharePoint site owner.
- The Anyone option will typically not appear when attempting to share.
- The user cannot override the sharing restrictions inherited from the parent location.
This behavior is expected and is controlled by the ownership and sharing configuration of the SharePoint site.
Microsoft Teams Private Teams
Files stored within a Private Microsoft Team inherit the sharing configuration of that Team's SharePoint site.
Because of this:
- External Anyone links are not available.
- Files cannot be anonymously shared outside the organization.
- External collaborators must be configured through Microsoft Entra B2B guest access before they can access content.
If a department needs to collaborate with external organizations from a Private Team, the external domains must follow the university's external sharing approval process before guest access can be granted.
Public or Personally Owned Content
Files stored in:
- A user's own OneDrive
- Publicly shared SharePoint locations
- Sites configured to allow external sharing
may present the Anyone sharing option when organizational policies permit anonymous sharing.
Whether the option appears depends on:
- Organization-wide external sharing policies
- SharePoint site sharing configuration
- Ownership of the content
Troubleshooting Steps
When a user reports that they cannot share a file externally:
- Verify the value shown in the Sharing column.
- Determine whether the content is stored in:
- Personal OneDrive
- Shared SharePoint site
- Microsoft Teams site
- If the location shows Owner - Owner/Team Name, explain that the user is not the owner of the parent location and cannot create anonymous sharing links.
- If the content resides within a Private Team, confirm whether external collaboration has been configured through Microsoft Entra B2B.
- If external collaboration is required, follow the OITS process for external domain approval and B2B guest configuration.
Key Points for Client Services
- Always check the Sharing column first when troubleshooting.
- Owner - Owner/Team Name indicates the file inherits permissions from another owner or Team.
- Users cannot bypass permissions inherited from the parent SharePoint site.
- Private Microsoft Teams do not support anonymous (Anyone) sharing links.
- Personal OneDrive content generally allows the broadest sharing options, subject to organizational policy.
- The availability of the Anyone option is determined by the parent location's ownership and sharing configuration—not by the individual file itself.