How do you manage all the guest accounts created by file sharing?

November 19, 2026 4 answers
Asked by n.782~plovriko

We have more guest accounts than internal users, and a lot of external sharing is just for viewing individual files. How can we reduce new guest creation and clean up existing accounts without breaking access people still need?

Answers

_v57!nexlavo.8

Start by checking how people share from SharePoint and OneDrive. Links addressed to specific people can result in guest identities. For files that are suitable for unauthenticated access, an Anyone link avoids requiring a guest account.

That is a security tradeoff, not just a cleanup setting. Anyone with the link can use it, so consider view-only permissions and an expiration where available. Check both the organization and site sharing settings before changing anything.

r.526+torqueno:

Anyone links won't be appropriate for every PDF. The content and the consequences of a forwarded link should drive that choice.

Reply to this answer
5b+parcelcrank_694

Treat existing guests as an access review problem, not a bulk deletion problem. Decide on an inactivity period, identify accounts that may no longer be needed, and check with the people responsible for the sharing before removing access.

Entra ID Governance may offer access review options if your licensing covers them. Otherwise, an automation that asks the person responsible whether access is still needed could help, though it adds something else to maintain. Test the process on a small group first.

n.782~plovriko:

Checking with the person responsible before cleanup sounds more practical than just deleting old guests on a schedule.

Reply to this answer
8q~fennelcaddy_371

Look at the Entra external collaboration settings too. You can restrict who is allowed to invite guests and use domain allow or deny lists if that fits your organization. The Guest Inviter role can be limited to selected accounts, with PIM as an option if you have it.

Be careful with a blanket restriction, though. It may affect ordinary external sharing workflows, so test what happens when a user shares a file before rolling it out widely.

Reply to this answer
_y83+zordali.5

I'd separate the two goals first. If recipients need authenticated access to sensitive material, having an external identity may be part of the design rather than a problem to eliminate. If the file is genuinely suitable for anyone with a link, avoiding the guest object may make more sense.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions