SharePoint Link Analyzer

The PowerShell script scans SharePoint Online and exports sharing links for files and folders in document libraries.

• Connects interactively using your Microsoft account
• Temporarily grants Site Collection Admin access when required
• Scans files and folders for sharing links
• Writes a CSV export plus state, log, cleanup, and summary files

First run for a tenant:

Later runs normally only need:

Upload the generated CSV into this page. All parsing and analysis happen locally in your browser.

Once loaded, use the page in this order:

• Summary for quick scale and expiration counts
• Urgent Review for the riskiest candidate links first
• Charts for trends by type, expiration, and site
• Tree View plus Detail to inspect where the links live
• Raw Rows when you want exact row-level selection

This page does not upload your CSV to a backend.

Urgent Review surfaces the links that should usually be checked first. The score is a heuristic, not an automatic decision.

• No expiration
• Anonymous or broad organization scope
• Folder-level sharing
• Edit or review permissions
• Many recipients
• Unique permissions
• Folders that expose many items underneath them

Use the tree to understand location and inheritance, then jump to Raw Rows when you want to act on a specific link.

The page gives you two safe ways to prepare remediation:

• Critical Links: use the automatically generated script for links that currently score as Critical
• Selected Links: select rows manually in Urgent Review or Raw Rows

Selection does not execute anything. It only prepares a PowerShell script that you can review and copy.

Open Remediation to generate PowerShell for either critical links or your manual selection.

• The page never removes links by itself
• You copy the generated script and run it yourself in PowerShell
• The removal commands are generated per CSV row and deduplicated where needed

Treat the generated script as a starting point: review the targets, validate business context, and only then execute it.

If you need a smaller or more targeted export, use optional parameters on the PowerShell side.