<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Identity on Sovereign Shift</title>
    <link>https://sovereignshift.eu/tags/identity/</link>
    <description>Recent content in Identity on Sovereign Shift</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sovereignshift.eu/tags/identity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Anatomy of a Google Workspace Dependency: What Keeps You Locked to Google</title>
      <link>https://sovereignshift.eu/blog/google-workspace-dependency-audit/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/google-workspace-dependency-audit/</guid>
      <description>&lt;p&gt;Google Workspace is often seen as the lighter-weight alternative to Microsoft 365. Fewer products, simpler licensing, less enterprise complexity. Organisations that chose Google early tend to believe they could switch to something else in a few weeks if they needed to.&lt;/p&gt;&#xA;&lt;p&gt;That belief rarely survives contact with reality. Google Workspace creates dependencies that are structurally different from Microsoft&amp;rsquo;s, but just as deep. Some are harder to escape because they are less visible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Anatomy of a Microsoft 365 Dependency: What Actually Locks You In</title>
      <link>https://sovereignshift.eu/blog/microsoft-365-dependency-anatomy/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/microsoft-365-dependency-anatomy/</guid>
      <description>&lt;p&gt;When organisations talk about replacing Microsoft 365, the conversation usually starts with email and ends with &amp;ldquo;it&amp;rsquo;s too hard.&amp;rdquo; But the difficulty is rarely about email. The real lock-in lives in layers most teams never think about until they try to leave.&lt;/p&gt;&#xA;&lt;p&gt;This post maps the actual anatomy of a Microsoft 365 dependency: the layers that make migration hard, the ones that make it easy, and the ones nobody documents until it is too late.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
