The Hero Link replaces the proliferation of sharing links with a single main link per file or folder, limited by default to people who have already been added. What remains to be seen is whether your tenant has received it and what it changes when permissions evolve after the link is sent. This test-tenant lab provides a reproducible method: check the feature, create links, change permissions, audit with PowerShell, compare.
Hero Link: what the single main link changes
Each file or folder has a single main link. According to the reference announcement on the new sharing model in Microsoft 365, this link is used for "Copy link", for email and for the address bar URL. Every Hero Link starts with the Only people added scope: only people who have already been added can access it.
Administrators can change this default per site collection or per OneDrive. Existing links keep working and appear in the "Other links" ("Other sharing links") section, with no action required for files that are already shared, according to the Tech Community post on the new sharing experience.
| Aspect | Links created before activation | Hero Link |
|---|---|---|
| Status | Still work, listed in Other links | Single main link per file or folder |
| Initial audience | The one chosen when the link was created | Only people added (can be changed per site or OneDrive) |
| Action required | None according to Microsoft | Set the desired default on the relevant sites |
| Expiration | Covered by existing policies | Not yet governed by these policies according to T-Minus365 |
The lab is there to measure these differences on your own settings rather than assume them.
A gradual rollout: check before launching the lab
The schedule has slipped. Originally announced for "end of 2025", Hero Links began rolling out in October 2026, according to a Tech Community discussion. The rollout is gradual and has not reached every tenant.
End of 2025
Originally announced deadline
First announcement of a Hero Links rollout at the end of 2025.
October 2026
Rollout begins
Gradual rollout: the feature may be missing from your test tenant.
Check that the feature is present first
A lab run on a tenant that does not yet have the feature produces worthless measurements. Open the sharing dialog on a test file and check the behaviour described above before going further.
Lab prerequisites
Before you start
- A test tenant, never the production tenant
- A dedicated SharePoint site (for example a disposable team site) and a test OneDrive
- Three accounts: an owner, an internal recipient, a second internal recipient
- The SharePoint Administrator role for site configuration
- Delegated consent for the Microsoft Graph Files.Read.All scope (read-only) for the audit
- Test files containing no real data
Implementation
The lab follows a simple thread: snapshot the state of the links, act, snapshot again, compare. The two modules below each install with a single command.
1Install-Module Microsoft.Online.SharePoint.PowerShell -Scope CurrentUser2Install-Module Microsoft.Graph.Authentication -Scope CurrentUserCheck that the module exposes the parameter
This test confirms that your version of the SharePoint module knows the DefaultMainLinkScope parameter of Set-SPOSite. It does not prove that the feature is active in the tenant: the sharing interface remains the final arbiter.
1# Returns True if the installed module exposes the parameter2(Get-Command Set-SPOSite).Parameters.ContainsKey('DefaultMainLinkScope')If the result is False, update the module before continuing.
Set the default audience of the test site
According to T-Minus365, DefaultMainLinkScope sets the default audience of the Hero Link, not the maximum access users can grant. The effective default value is OnlyPeopleAdded; Organization is also possible. The following script offers a simulation mode and touches only a single site.
1# Required role: SharePoint Administrator2param(3 [Parameter(Mandatory)][string]$AdminUrl, # e.g. https://contoso-admin.sharepoint.com4 [Parameter(Mandatory)][string]$SiteUrl, # test site only5 [ValidateSet('OnlyPeopleAdded','Organization')][string]$Scope = 'OnlyPeopleAdded',6 [switch]$DryRun7)8 9Connect-SPOService -Url $AdminUrl10 11if ($DryRun) {12 Write-Host ('SIMULATION: {0} would switch to DefaultMainLinkScope = {1}' -f $SiteUrl, $Scope)13 return14}15 16Set-SPOSite -Identity $SiteUrl -DefaultMainLinkScope $Scope17 18# Read back the applied value19Get-SPOSite -Identity $SiteUrl | Select-Object Url, DefaultMainLinkScopeDo not switch to Organization outside the lab
The Organization setting widens the audience offered by default to the whole organization on the targeted site collection. On a production site, it directly increases the risk of oversharing. The propagation delay is not documented in the available sources: measure it in the lab rather than assume it.
Audit permissions and links
This script reads the permissions of the items at the root of a site's default library, via Microsoft Graph, and exports them to CSV. It distinguishes links from direct access, which lets you see whether an added person appears as direct access or via a link. It performs no writes. Items in subfolders are not traversed: put your test files at the root.
1# Module: Microsoft.Graph.Authentication2# Delegated scope: Files.Read.All (read-only)3param(4 [Parameter(Mandatory)][string]$SiteHostname, # e.g. contoso.sharepoint.com5 [Parameter(Mandatory)][string]$SitePath, # e.g. /sites/LabHeroLinks6 [Parameter(Mandatory)][string]$Label, # e.g. before or after7 [string]$OutFile8)9 10if (-not $OutFile) { $OutFile = 'audit-{0}.csv' -f $Label }11 12Connect-MgGraph -Scopes 'Files.Read.All' -NoWelcome13 14# Resolve the site from its host name and path15$site = Invoke-MgGraphRequest -Method GET -Uri ('https://graph.microsoft.com/v1.0/sites/{0}:{1}' -f $SiteHostname, $SitePath)16 17# Items at the root of the default library, with paging18$uri = 'https://graph.microsoft.com/v1.0/sites/{0}/drive/root/children' -f $site.id19$items = @()20while ($uri) {21 $page = Invoke-MgGraphRequest -Method GET -Uri $uri22 $items += $page.value23 $uri = $page.'@odata.nextLink'24}25 26$rows = foreach ($item in $items) {27 $permUri = 'https://graph.microsoft.com/v1.0/drives/{0}/items/{1}/permissions' -f $item.parentReference.driveId, $item.id28 $perms = Invoke-MgGraphRequest -Method GET -Uri $permUri29 foreach ($perm in $perms.value) {30 $grantee = if ($perm.grantedToV2.user) { $perm.grantedToV2.user.email } else { ($perm.grantedToIdentitiesV2 | ForEach-Object { $_.user.email }) -join ';' }31 [pscustomobject]@{32 Item = $item.name33 Kind = if ($perm.link) { 'Lien' } else { 'Acces direct' }34 Scope = $perm.link.scope35 Type = $perm.link.type36 Roles = ($perm.roles -join ',')37 Grantee = $grantee38 Expiration = $perm.expirationDateTime39 LinkUrl = $perm.link.webUrl40 }41 }42}43 44$rows | Export-Csv -Path $OutFile -NoTypeInformation -Encoding UTF845Write-Host ('{0} permissions exported to {1}' -f @($rows).Count, $OutFile)The script produces an audit-<label>.csv file. The Scope and Type values depend on what Microsoft Graph returns for a Hero Link: the lab is precisely meant to establish how it appears in your tenant.
Compare two snapshots
After running the audit with -Label avant, then -Label apres, the comparison highlights what changed. The <= symbol marks a row present only before, => a row present only after.
1$avant = Import-Csv -Path .\audit-avant.csv2$apres = Import-Csv -Path .\audit-apres.csv3 4Compare-Object -ReferenceObject $avant -DifferenceObject $apres -Property Item, Kind, Scope, Type, Roles, Grantee, LinkUrl |5 Sort-Object Item |6 Format-Table -AutoSizeLab walkthrough
Validate the feature and set the default
Check that the parameter is present, then apply OnlyPeopleAdded on the test site with -DryRun, then without.
Snapshot the initial state
Run the audit with -Label avant. If some files have links created before activation, they serve as a reference for the Other links section.
Create Hero Links
From the sharing dialog, add the first recipient on three files. Note the main link URL of each.
Change permissions after sending
Add the second recipient on one file, remove the first on another, then uncheck "People with edit access can reshare" via the gear icon on the third. Then reopen each URL noted in step 3.
Snapshot again and compare
Run the audit with -Label apres, then the comparison, and record the differences.
What the lab must measure
The table below sets out the observations to record for each test. The reshare option deserves close attention: the o365reports team points out that it is enabled by default with Hero Links, which directly affects oversharing, as detailed in its guide to oversharing countermeasures.
| Test | Action | Observation to record |
|---|---|---|
| Default audience | Create a Hero Link without touching the settings | Is the link limited to the people added? |
| Addition after sending | Add a person to an already shared file | Same URL? New row in the audit? |
| Removal after sending | Remove a person | Access denied for them? Row removed from the audit? |
| Resharing | Uncheck the reshare option via the gear | Can the recipient still add someone? |
| Existing links | Compare links before and after activation | Present in Other links, access retained |
| Expiration | Apply an expiration policy | Is the Hero Link affected? |
An isolated report to verify, not to generalise
A user reports in the comments of the Microsoft article that links to updated and then reshared documents stop working. This is an isolated report, not an established behaviour. The "Addition after sending" test lets you confirm or rule it out in your environment by comparing the URL before and after.
Known limitations: expiration and scope of the default
According to T-Minus365, existing link expiration policies do not yet govern Hero Links. Microsoft's October 2026 announcement on what's new in OneDrive presents expiration controls for the organization's Hero Links as "Coming Soon": they are therefore not available. Separate links with expiration remain the workaround; our article on the new SharePoint link expiration limits covers this aspect in detail.
Second point of caution: DefaultMainLinkScope does not cap what users can grant. It guides the initial choice, nothing more.
Strengths
- A single main link per file or folder
- Restrictive default audience: Only people added
- Existing links keep working with no action
- Default can be changed per site collection or per OneDrive
Limitations
- Gradual rollout, missing from some tenants
- Hero Link expiration not yet available
- The default setting does not limit maximum access
- Reshare option enabled by default
Lab troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Unknown DefaultMainLinkScope parameter | Microsoft.Online.SharePoint.PowerShell module too old or feature not yet deployed | Update the module, then check again with Get-Command |
| No Hero Link in the dialog | Gradual rollout: tenant not yet reached | Postpone the lab and check the sharing interface again |
| 403 error on the Graph call | Files.Read.All scope consent missing | Sign in again with Connect-MgGraph -Scopes 'Files.Read.All' and grant consent |
| Empty audit for a shared file | File in a subfolder that is not traversed | Place test files at the root of the library |
| Expiration has no effect on a Hero Link | Expiration controls announced but not yet available | Use a separate link with expiration |
| Link not working after modification | Isolated report, cause not established | Compare URLs before and after, then document the case |
Frequently asked questions
Should I fix links that are already shared before enabling the feature?
No, Microsoft states that no action is required for files that are already shared. Existing links remain functional and appear in the Other links section. Auditing older links remains worthwhile, because they do not benefit from the new restrictive default.
Does the DefaultMainLinkScope parameter limit what my users can share?
No. According to T-Minus365, it sets the default audience of the Hero Link and not the maximum access users can grant. The documented values are OnlyPeopleAdded (effective default) and Organization.
Can a Hero Link be made to expire automatically?
Not yet. Existing expiration policies do not govern them, and the dedicated controls were announced as "Coming Soon" on 20 October 2026. In the meantime, separate links with expiration serve as a workaround.
Where to start
Action plan for the coming days
- Confirm that the test tenant displays the Hero Link in the sharing dialog
- Run the "before" audit on the test site
- Work through the six tests in the grid and record each result
- Decide the target default per site type (
OnlyPeopleAddedorOrganization) - Uncheck the reshare option during the tests and note the effect
- Plan user communication before any wider rollout
If your sites contain sensitive data or if Copilot relies on your content, keep OnlyPeopleAdded and treat expiration as a residual risk, to be covered with separate links. For the Copilot readiness aspect, see our analysis of ShareGate Protect and securing M365 before Copilot.
Further reading
- The new sharing experience is coming to SharePoint Online: What admins need to know: interface differences, FAQ and communication tips before rollout.
- Simple, Smart, and Secure: The next step in sharing files in Microsoft 365: the reference announcement of the Hero Link model.
- OneDrive Just Got a Major Upgrade: October 2026 announcements, including upcoming expiration and the SharePoint Admin Agent.
- 17 Effective Ways to Prevent Oversharing in Microsoft 365: practical measures against oversharing, including the reshare setting.
- Essential pillars of a successful SharePoint architecture: framing the site structure before configuring sharing.



