Report shared links
Find and export sharing links
Every sharing link on the sites or libraries you choose, exported. Anyone-with-the-link, organisation-wide, and specific-people links all come back with their URL, scope, type and expiry. This is how you find out whether a file that should never have left the building has an anonymous link on it.
What it tells you
- Which items are shared by link, and what kind of link it is.
- Whether a link is anonymous, organisation-wide or limited to named people.
- Who each link was granted to, and what it lets them do.
- Whether a link has an expiry date or a password on it.
- Which items could not be read, listed on their own sheet.
How it runs
- Sign in and choose what to scan. Clicking the tile asks which account to use and how to connect, signs you in if you are not already, and drops you straight on the site list. No feature page asks you to connect a second time. Sites, or individual libraries.
- Narrow it down if you want to. Filter by link scope, by link type, by name, or to expired links only.
- It scans. Item by item, reporting as it goes rather than going quiet on a long library.
- Save the workbook. If you then want to remove links, the Shared links menu has separate tiles for that, and they never run from here.
How it works
Only document libraries are scanned, hidden ones left out. With subsites included, every subsite below is scanned at any depth; a OneDrive is never asked for subsites. Libraries are scanned one at a time. A site whose libraries or subsites cannot be listed becomes a not read row.
Links are found in two steps. First each library's items are read in pages, which works past the 5,000 item threshold, keeping only items that have their own permissions, because an item carrying a sharing link no longer inherits. Then each of those items is looked up through Microsoft Graph and its permissions are read there. A permission is kept when it is a link and is not inherited from a parent. The link scope (anonymous, organisation or specific people), the type (view or edit), the expiry, the password and the people it was granted to all come from the link itself.
A browser-session sign-in carries no Graph access, so each library gets one row explaining that no links were read. If Graph refuses the sign-in many times in a row, link reads stop for the rest of the run instead of failing item by item. A fault in one library is recorded and the scan moves to the next. The workbook goes into History when the run ends, provided the run found something to report.
What you get
An Excel workbook, named like shared-links-contoso-projects-20260901-1422.xlsx, kept in Report History whether or not you save it. Link scope is the column to sort on. Anonymous links are the ones most audits are actually asking about.
Sharing Links sheet
Every link found.
| Column | Example |
|---|---|
| Library | Shared Documents |
| Item path | Clients/Northwind/Contract.pdf |
| Item type | File |
| Link type | Edit |
| Link scope | Anonymous |
| Expires (UTC) | 2026-12-01 |
| Password | No |
| Granted to | anyone with the link |
| Roles | Write |
Errors sheet
Items that could not be read, with the reason.
| Column | Example |
|---|---|
| Library | Policies |
| Item path | Handbook.docx |
| Error | Access denied |
Summary sheet
Scope, filters, counts and timings.
What you need
- Read access to the sites or libraries in scope.
- Sharing links are read through Microsoft Graph, so this report needs a sign-in that carries a Graph token. Where a cookie-only sign-in cannot do that, the app says so instead of returning an empty report.
What it will not do
- It changes nothing. Removing a link, or removing one person from a link, are separate tiles with their own confirmations.
- Scanning is per item, so a large library is a long run. Filters cut it down considerably.
- A link that has already expired still exists until it is cleaned up. Filter to expired links only if that is what you are after.