<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Azure on Yogesh Thanvi</title>
    <link>https://yogeshthanvi.com/tags/azure/</link>
    <description>Recent content in Azure on Yogesh Thanvi</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://yogeshthanvi.com/tags/azure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enforcing Pod Security on AKS with Azure Policy and OPA Gatekeeper</title>
      <link>https://yogeshthanvi.com/posts/enforcing-pod-security-aks-azure-policy/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://yogeshthanvi.com/posts/enforcing-pod-security-aks-azure-policy/</guid>
      <description>Detecting insecure pods on Azure Kubernetes Service is not the same as preventing them. Here is how Azure Policy and OPA Gatekeeper move enforcement to admission time, so a misconfigured workload never reaches the cluster.</description>
    </item>
    <item>
      <title>Securing AI Workloads on Azure: Governance Patterns for Azure OpenAI and AI Foundry</title>
      <link>https://yogeshthanvi.com/posts/securing-ai-workloads-on-azure/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://yogeshthanvi.com/posts/securing-ai-workloads-on-azure/</guid>
      <description>Generative AI on Azure introduces control points that traditional application security never had to handle. Here are practical governance patterns for Azure OpenAI and AI Foundry workloads, mapped to where the real risks live.</description>
    </item>
  </channel>
</rss>
