Hero links are part of the new sharing experience in SharePoint Online. For an overview, see The new sharing experience is coming to SharePoint Online: What admins need to know. If a hero link is compromised—for example, its audience is changed to Anyone and the link is overshared—you may need to revoke it. Unlike a traditional sharing link, a hero link cannot be deleted directly. Microsoft provides the Reset link option instead.

Hero links are part of the new sharing experience in SharePoint Online. For an overview, see The new sharing experience is coming to SharePoint Online: What admins need to know. If a hero link is compromised for example, its audience was changed to Anyone and the link is now overshared you may need to change its audience or role. The supported values include: Audience Anyone Organization OnlyPeopleAdded Role view (Can view) restrictedview (Can’t download) review (Can review) edit (Can edit) Example request bodies to the endpoint:

This post follows on from SharePoint Hero Links: What admins/adoption teams need to know? and focuses on the technical difference between legacy sharing links and hero links. To validate what SharePoint is now generating behind the scenes, I adapted my earlier script from Converting SharePoint Sharing Links to Canonical URLs to validate whether Hero link exists or not even there are no unique permissions on the file/folder. The key behaviour change is this: legacy sharing links were typically created only when a user accidentally shared an item (e.

Microsoft’s third-generation sharing experience, Hero Links, introduces a simpler way to manage file-sharing access, with a stronger emphasis on secure defaults and granular permissions. The main administrative point is that Hero Links and legacy sharing links do not follow the same policy behavior. The immediate questions for administrators: What happens to existing sharing links during rollout? Can old links be migrated into Hero Links? How should both experiences be managed in parallel?