<?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 PAUL'S BLOG</title><link>https://paulyu.dev/categories/identity/</link><description>Recent content in Identity on PAUL'S BLOG</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 25 Aug 2023 13:00:00 +0000</lastBuildDate><atom:link href="https://paulyu.dev/categories/identity/index.xml" rel="self" type="application/rss+xml"/><item><title>Does Workload Identity on AKS work across tenants?</title><link>https://paulyu.dev/article/cross-tenant-workload-identity-on-aks/</link><pubDate>Fri, 25 Aug 2023 13:00:00 +0000</pubDate><guid>https://paulyu.dev/article/cross-tenant-workload-identity-on-aks/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;An interesting use case for Workload Identity came up recently. I was asked if a Pod in an AKS cluster that was deployed in one tenant can access Azure resources within another tenant.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve configured Workload Identity on AKS many times, and I thought &amp;ldquo;in theory&amp;rdquo; it should &amp;ldquo;just work&amp;rdquo;, but I never tested it across tenants. So I decided to give it a try.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;TL;DR: Yes, it does work.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>