SharePoint Hero Links need separate governance from legacy sharing links
Diesen Beitrag auf Deutsch lesen
Hero Links use secure defaults, but legacy links remain active and existing expiration policies do not govern the new primary link.
TL;DR
SharePoint Hero Links default to a selected audience through DefaultMainLinkScope, while existing sharing links remain under Other links and continue working separately. Legacy expiration policies do not govern Hero Links. Administrators should configure and verify the site-specific setting, and manage legacy links independently because automatic migration is not documented.
Original on reshmeeauckloo.com. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Set and verify DefaultMainLinkScope on each relevant site, because the setting is site-specific and establishes the initial Hero Link audience.
- Security/Compliance: Assess Hero Link expiration separately, because existing expiration policies govern legacy links but do not govern Hero Links.
- Leadership/Business: Account for both link experiences during rollout, because legacy links remain accessible under their existing arrangements and are not automatically replaced.
Frequently asked questions
How does DefaultMainLinkScope control SharePoint Hero Link access?
DefaultMainLinkScope selects the initial audience for a site’s main Hero Link. It is a default, not an enforced restriction where policy permits broader sharing.
Do existing SharePoint sharing links migrate automatically to Hero Links?
Existing sharing links are not automatically replaced, and no documented automatic migration path is provided. They remain separately available under Other links.
Do SharePoint link expiration policies apply to Hero Links?
Existing expiration policies continue to apply to legacy links but do not govern Hero Links. Administrators must assess Hero Link expiration separately.