<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SharePoint External Sharing on Secure Techies</title><link>https://securetechie.com/tags/sharepoint-external-sharing/</link><description>Recent content in SharePoint External Sharing on Secure Techies</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 14 Sep 2026 00:00:00 -0700</lastBuildDate><atom:link href="https://securetechie.com/tags/sharepoint-external-sharing/index.xml" rel="self" type="application/rss+xml"/><item><title>SharePoint External Sharing: Anyone-Links Are Not a Workflow</title><link>https://securetechie.com/blog/sharepoint-external-sharing/</link><pubDate>Mon, 14 Sep 2026 00:00:00 -0700</pubDate><guid>https://securetechie.com/blog/sharepoint-external-sharing/</guid><description>&lt;p&gt;Here&amp;rsquo;s the short version: &lt;strong&gt;SharePoint external sharing is a ceiling you set on purpose, not a convenience toggle.&lt;/strong&gt; Anyone-links and immortal guests are how client files leave the firm. Disable Anyone, expire guests, and make finance sites stricter than the marketing library.&lt;/p&gt;</description></item><item><title>SharePoint Oversharing Cleanup for a Media Agency</title><link>https://securetechie.com/case-studies/sharepoint-external-sharing-cleanup/</link><pubDate>Fri, 14 Aug 2026 00:00:00 -0700</pubDate><guid>https://securetechie.com/case-studies/sharepoint-external-sharing-cleanup/</guid><description>A Los Angeles media agency asked Secure Techies to clean SharePoint external sharing after a client asked who outside the firm could still open last year&amp;rsquo;s campaign files. Anyone links were on. Guests from old freelancers were live. We inventoried sites, turned Anyone links off, named owners, and left a written sharing rule producers would actually follow.</description></item></channel></rss>