<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hero Link on Blog about anything related to my learnings</title><link>https://reshmeeauckloo.com/tags/hero-link/</link><description>Recent content in Hero Link on Blog about anything related to my learnings</description><generator>Hugo -- gohugo.io</generator><language>en-uk</language><lastBuildDate>Sun, 11 Oct 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://reshmeeauckloo.com/tags/hero-link/index.xml" rel="self" type="application/rss+xml"/><item><title>SharePoint Hero Links: What admins need to know</title><link>https://reshmeeauckloo.com/posts/sharepoint-herolink-powershell/</link><pubDate>Sun, 11 Oct 2026 10:00:00 +0000</pubDate><guid>https://reshmeeauckloo.com/posts/sharepoint-herolink-powershell/</guid><description>Microsoft&amp;rsquo;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 are straightforward:
What happens to existing sharing links during rollout? Can old links be migrated into Hero Links? How should both experiences be managed in parallel?</description></item></channel></rss>