<?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>Litellm on BalkanDevOps</title><link>https://www.balkandevops.com/tags/litellm/</link><description>Recent content in Litellm on BalkanDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.balkandevops.com/tags/litellm/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming Azure AI Foundry with LiteLLM: budgets and key rotation</title><link>https://www.balkandevops.com/posts/taming-azure-ai-foundry-with-litellm/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.balkandevops.com/posts/taming-azure-ai-foundry-with-litellm/</guid><description>Azure AI Foundry is amazing until you have to manage it for more than one team. Here is how LiteLLM became the gateway that fixed my key sprawl, capped everyone&amp;rsquo;s spend, and turned key rotation from a fire drill into a thirty second job.</description></item></channel></rss>