<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
      <title>Alek&#x27;s Blog - microsoft</title>
      <link>https://blog.none.at</link>
      <description>My Blog to share my knowledge</description>
      <generator>Zola</generator>
      <language>en</language>
      <atom:link href="https://blog.none.at/tags/microsoft/rss.xml" rel="self" type="application/rss+xml"/>
      <lastBuildDate>Thu, 09 Jul 2026 00:00:00 +0000</lastBuildDate>
      <item>
          <title>Who Builds the Platform? Ownership vs. Stack</title>
          <pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate>
          <author>aleks</author>
          <link>https://blog.none.at/blog/2026/2026-07-09-sovereignty-technology-stack/</link>
          <guid>https://blog.none.at/blog/2026/2026-07-09-sovereignty-technology-stack/</guid>
          <description xml:base="https://blog.none.at/blog/2026/2026-07-09-sovereignty-technology-stack/">&lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;blog.none.at&#x2F;blog&#x2F;2026&#x2F;2026-07-09-sovereign-cloud-washing&#x2F;&quot;&gt;Part 1&lt;&#x2F;a&gt; raised the technology-supply-chain
question with one case: Open Telekom Cloud, legally owned by Deutsche Telekom, running on a
Huawei-licensed platform. Five more prominent, more recent cases turn out to follow the same
pattern — checked here against primary sources, not just repeated from secondary coverage —
alongside three providers where ownership and technology stack come closer to aligning, each with
its own gaps left intact rather than smoothed over.&lt;&#x2F;p&gt;</description>
      </item>
    </channel>
</rss>
