<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Terraform on Azure Citadel</title>
    <link>https://www.azurecitadel.com/tags/terraform/</link>
    <description>Recent content in Terraform on Azure Citadel</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Tue, 02 Jun 2026 12:43:36 +0100</lastBuildDate>
    <atom:link href="https://www.azurecitadel.com/tags/terraform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Terraform MCP Server update</title>
      <link>https://www.azurecitadel.com/blog/2026-06-02-terraform-mcp-server-update/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.azurecitadel.com/blog/2026-06-02-terraform-mcp-server-update/</guid>
      <description>The Terraform MCP Server has evolved significantly since I covered it in the Fabric Terraform series. It has moved well beyond a simple registry lookup tool and is now at v0.5.2. Here is a summary of what has changed and how to think about which configuration is right for you.&#xA;Note that this post was largely generated using GitHub Copilot CLI (Claude Opus 4.6) as I used it to compare my previous post with the new functionality rolled into the Terraform MCP server.</description>
    </item>
  </channel>
</rss>
