Skip to content

New: How We Design Technology - our seven-layer architecture model, explained in full. See the architecture

general

SharePoint External Sharing That Expires: No Permanent Links

10/28/2026

The annual access review turns up the usual surprises. An outside auditor from two engagements ago can still open the finance site. A folder of draft contracts went out on an "Anyone" link last spring, and nobody can say where that link traveled. A consultant's guest account is still active, with access to three project sites the consultant hasn't opened in a year.

Each of those shares made sense on the day it happened. Nothing was set up to end it. SharePoint external sharing is a good way to get files to auditors, vendors, counsel, and partners, and the missing piece in most tenants is an end date. When expiration is built into the defaults, stale access stops piling up between reviews, and the people doing the sharing barely notice the change.

At a glance

  • Microsoft 365 can put an end date on both kinds of external access: "Anyone" links and guest accounts.
  • Set sensible organization defaults first, then tighten the sites that hold sensitive work with site settings or sensitivity labels.
  • Review whatever remains on a schedule, using the audit log and, where your licensing allows, Microsoft Entra access reviews.

Why external access outlives the work

Sharing is easy to start and easy to forget. A project manager invites a vendor to a site. Someone in finance sends a link to the outside CPA. A Teams channel picks up a guest for a joint project. Each grant stays in place until someone removes it, and the person who created it has usually moved on to the next deadline.

Over time, that adds up to access nobody can fully account for. The problem surfaces in an audit, when someone asks a plain question about a sensitive folder: who outside the organization can open this, and why? If the answer takes a week of digging, the controls are working against you.

How SharePoint external sharing settings fit together

Microsoft sets external sharing in layers. At the organization level, SharePoint offers four levels, from most to least permissive: Anyone, New and existing guests, Existing guests, and Only people in your organization. OneDrive has its own setting, which can match SharePoint or be more restrictive, but never more permissive.

Each site also has a sharing setting. It can match the organization level or be stricter, so a board site or HR site can be locked down even when project sites allow guests. That layering is useful. You can keep the organization setting practical for everyday collaboration and reserve the tightest limits for the places that need them.

The same admin settings shape everyday behavior in smaller ways. You can limit sharing to or from specific domains, require guests who sign in with a one-time verification code to reauthenticate after a set number of days, and choose which link type appears first when someone selects Share.

Link types and what each one leaves behind

When people share a file or folder, they pick a link type:

  • Anyone with the link. No sign-in is required. Microsoft notes that people using an Anyone link don't authenticate, so their access can't be audited. This option exists only when the organization allows Anyone sharing.
  • People in your organization. Works for members of your organization if the link is forwarded. It doesn't work for guests.
  • Specific people. The recipient has to authenticate as the person named in the link, whether they work for you or not.
  • People with existing access. Sends a link to people who already have permission, without changing who has access.

The default link type deserves more attention than it usually gets, because it's what people accept when they're in a hurry. Microsoft's guidance is to make the default more restrictive while still letting people choose another type when they need one. For most organizations, Specific people is a sensible default for SharePoint and OneDrive.

Put an end date on access

Two settings do most of the work.

Anyone link expiration. If you allow Anyone links, you can require them to expire and set the maximum number of days. If you later shorten that limit, existing links update to the shorter period. If you lengthen it, existing links keep their original dates. You can also restrict Anyone links to view-only.

Guest access expiration. SharePoint and OneDrive can end guest access automatically after a set number of days. The policy covers guests invited to a site and guests with whom individual files or folders were shared. Site admins see a banner a few weeks before a guest expires and can extend access for someone who still needs it. Once access lapses, the guest is locked out even if they still hold the link.

One caution: guests who belong to a Microsoft 365 group or team get access through that membership, and Microsoft notes that a guest can keep access to the team after losing direct access to the site. Treat team and group membership as its own review, covered below.

  • Organization external sharing
    • Recommended starting point: New and existing guests
    • Why it helps: Outside people sign in, so every grant is tied to a person
  • Anyone links
    • Recommended starting point: Off, or on with a short expiration and view-only access
    • Why it helps: Limits links that can be forwarded with no record of who opened them
  • Guest access expiration
    • Recommended starting point: On, with a period that matches a typical engagement
    • Why it helps: Ends access automatically when the work usually ends
  • Default link type
    • Recommended starting point: Specific people
    • Why it helps: Makes the safest choice the quickest one
  • Sensitive sites
    • Recommended starting point: Existing guests only, or internal only
    • Why it helps: Keeps the strictest limits where the risk is highest

Tighten the sites that hold sensitive work

Site-level sharing settings are the simplest way to protect board materials, HR files, and legal matters. Set those sites to existing guests only, or to internal only, and the more open organization default no longer applies to them.

For a more consistent approach, Microsoft Purview sensitivity labels can apply settings to a whole team or site at once. A label can set the site's external sharing level, control whether owners can add guests, and limit access from unmanaged devices (that last option only works alongside a matching Conditional Access policy). Microsoft warns that site owners can change these settings by applying or changing a label, so decide who may apply which labels before you rely on them.

Review what's still open

Expiration shrinks the cleanup, and a regular review catches the rest. The Microsoft Purview audit log records sharing activity, including when someone creates an Anyone link, when that link is used, when a Specific people link is created, and when an external user accepts an invitation. Each sharing record shows which user shared which resource with whom, and when, so you can filter for guests and see what has gone outside. An Anyone link appears in the log when it's created and used, but the log can't tell you who opened it.

Microsoft Entra access reviews add a second check. Resource owners, or another person you designate, confirm whether each guest still needs access, and you can remove those who don't. Access reviews require Microsoft Entra ID P2 or Microsoft Entra ID Governance licensing, and some guest review features, such as reviews of inactive guests, are billed per guest through a governance add-on. Confirm the cost before you plan a large program.

Without that licensing, a quarterly export of guest accounts and sharing activity, sent to each site owner for a keep-or-remove answer, covers much of the same ground by hand.

Roll it out without slowing people down

People share externally because their work requires it. If the approved path is slower than emailing an attachment, they'll email the attachment. A rollout that holds up usually follows a simple order:

  1. Turn on expiration and the safer default link type first, since they change the least for users.
  2. Give people an easy approved path, such as a clear home for each client or vendor relationship and a named owner who can extend a guest.
  3. Tell staff what changes before it happens: links will expire, guests will sign in, and here is who to ask for an extension.
  4. Lock down sensitive sites with site settings or labels.
  5. Review guest access and sharing activity on a set schedule, and remove anything that no longer has an owner.

Some teams will ask for exceptions, such as a long-running partner relationship that needs open-ended access. Give each one an owner and an end date, and keep the list short. Unmanaged security exceptions have a way of becoming permanent.

Make expiration the default

Access that ends on its own is easier to defend in an audit and easier to live with day to day. Set sensible defaults, protect the sites that matter most, and review the rest on a calendar instead of after a finding.

At CTP, we design collaboration settings around how your organization shares work, and we document each choice so the next review starts with answers. See our approach to collaboration, or schedule a conversation about the external access in your tenant today.

Sources and further reading

Ask about something important for you.

Curious about our take on an industry or technology topic? Let us know.

Contact Us