Does SharePoint Have a 180-Day Sharing Link Expiration Default? What Admins Should Know

Why sharing link expiration keeps coming up

If you administer Microsoft 365 for a small or mid-sized organization, you’ve likely seen discussion online about a “new” 180-day default expiration for SharePoint and OneDrive sharing links. It’s a reasonable thing to want clarity on — sharing link lifecycles directly affect how long external or internal recipients can access shared files, and unexpected changes to that behavior can disrupt workflows or create security gaps.

Based on the official Microsoft documentation reviewed for this article, there is no confirmed statement of a specific 180-day default expiration value, nor a documented rollout timeline for such a change. What is documented is how sharing link expiration works conceptually, and the specific admin controls available to configure or override expiration settings. This article focuses on what’s actually confirmed, so you can plan your own configuration instead of reacting to unverified claims.

What Microsoft documents about sharing link expiration

Three link types, different expiration behavior

Microsoft 365 sharing links generally fall into three categories:

• Anyone links – accessible to anyone who has the link, without authentication.
• People in your organization links – usable only by authenticated members of your own tenant (not guests).
• Specific people links – restricted to named individuals, whether inside or outside your organization.

Expiration settings are documented separately for these link types, and they are not identical.

Anyone link expiration

According to Microsoft’s sharing settings documentation, admins can require all Anyone links to expire and specify the maximum number of days allowed. This is configured in the SharePoint admin center, under sharing policies, in the advanced settings for Anyone links.

An important documented detail: if you change the expiration time after links already exist, existing links keep their current expiration time if the new setting is longer, or they update to the new (shorter) setting if you reduce the allowed number of days. In other words, tightening the policy can retroactively shorten the life of links that were already created, while loosening it does not extend links beyond what was already set.

People in your organization link expiration

Separately, Microsoft documents that admins can configure expiration policies specifically for People in your organization links. When such a policy is enabled:

• Newly created links receive an expiration date and stop working after that date.
• Existing links aren’t automatically modified the moment the policy is turned on.
• However, when an existing link is next accessed, it’s evaluated against the configured expiration limit using its original creation date — so a link created long before the policy existed can be treated as expired immediately if it already exceeds the new limit.
• When a link expires, only the link itself stops working. The underlying file or folder isn’t deleted, and anyone with access through other permissions (such as direct permissions or group membership) retains access.

This is a useful distinction for admins to understand: expiration affects the link, not the content or any other access path to it.

No documented 180-day default in these sources

None of the reviewed Microsoft sources state that a 180-day expiration is now applied by default to new sharing links, nor do they describe a phased rollout schedule for such a change. If your organization is seeing sharing links expire around the 180-day mark, that behavior may be the result of a policy that was explicitly configured — either by your own admins, by a prior configuration, or by a setting inherited from a related policy — rather than a newly imposed Microsoft default. Admins who want certainty about their own tenant’s current expiration settings should check the SharePoint admin center’s sharing policy page and any site-level overrides directly, rather than relying on assumptions about defaults.

How to configure or override sharing link expiration

Organization-level configuration (SharePoint admin center)

Admins with the SharePoint Administrator role can manage sharing settings at the organization level:

1. In the SharePoint admin center, go to Policies and then Sharing.
2. Under External sharing, set the overall sharing level (Anyone, New and existing guests, Existing guests, or Only people in your organization).
3. Expand More external sharing settings to find the Advanced settings for Anyone links, where you can require expiration and set the maximum number of days.

Microsoft’s documentation notes that the OneDrive sharing setting can be more restrictive than the SharePoint setting, but not more permissive — useful to keep in mind if you’re trying to apply different expiration behavior across SharePoint sites versus individual users’ OneDrive.

Site-level overrides with PowerShell

For organizations that need different expiration rules on specific sites rather than tenant-wide, the Set-SPOSite cmdlet (part of the SharePoint Online Management Shell) exposes several relevant parameters at the site collection level, including:

• AnonymousLinkExpirationInDays – sets the number of days after which Anyone (anonymous) links created for that site expire. Per the cmdlet reference, valid values range from 1 to 730 days, and setting it to 0 removes the expiration requirement. This parameter only applies if OverrideTenantAnonymousLinkExpirationPolicy is set to true for that site.
• OverrideTenantAnonymousLinkExpirationPolicy – a boolean that determines whether the site-level expiration setting takes precedence over the tenant-wide policy.
• AnyoneSharingLinkRecommendedExpirationInDays – sets a recommended (rather than enforced) expiration period shown to users when they create Anyone links, again only active when the override is enabled, and must be less than or equal to the maximum set by AnonymousLinkExpirationInDays.
• OrganizationSharingLinkMaxExpirationInDays and OrganizationSharingLinkRecommendedExpirationInDays – analogous controls for People in your organization links, allowing a maximum and a recommended expiration period to be set per site, along with a corresponding override flag.

Running Set-SPOSite requires being a SharePoint Online administrator and a site collection administrator, as documented in the cmdlet reference. Note that for OneDrive for Business site collections and Microsoft 365 Groups-connected sites, only a specific subset of Set-SPOSite parameters is valid — not the full parameter list used for standard SharePoint sites.

Practical recommendation: audit before you assume

Because the supplied documentation doesn’t confirm a universal 180-day default, a practical step for SMB admins is to directly check your tenant’s current sharing policy configuration rather than assuming a particular value is in effect. This is a governance recommendation, not a documented Microsoft requirement:

• Review the Sharing policy page in the SharePoint admin center to see whether Anyone link expiration is enabled, and what value is set.
• Check whether a People in your organization expiration policy has been enabled separately, since it is configured and behaves differently from Anyone link expiration.
• For sites with unique sharing needs, consider whether a site-level override via Set-SPOSite is warranted, documenting why that site deviates from the tenant-wide policy.
• When tightening expiration policy, remember that existing links may be shortened automatically (for Anyone links) or re-evaluated against their original creation date (for People in your organization links) — plan user communication accordingly.

What this means for your tenant

The practical takeaway is that sharing link expiration in SharePoint and OneDrive is a configurable control, not a fixed, universal timer. Microsoft’s documentation describes the mechanics clearly — how Anyone link and People in your organization link expiration policies work, how changes affect existing links, and the specific PowerShell parameters available for site-level overrides — but it does not, in the sources reviewed here, establish a specific 180-day default or a rollout timeline for one.

If your organization needs predictable sharing link lifespans, the most reliable approach is to explicitly configure expiration at the tenant or site level rather than relying on assumptions about current defaults. Given that Microsoft documentation in this space can be updated over time, it’s worth periodically revisiting your tenant’s sharing settings, especially before making governance decisions based on expiration behavior you haven’t directly verified.

This article is a draft prepared for review and should be confirmed against your own tenant’s current configuration before being used as the basis for policy decisions.