<?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 Brad's Blog</title><link>https://blog.bjdean.id.au/tags/azure/</link><description>Recent content in Azure on Brad's Blog</description><generator>Hugo -- 0.152.2</generator><language>en-au</language><copyright>Bradley Dean</copyright><lastBuildDate>Thu, 20 Nov 2025 17:30:51 +1100</lastBuildDate><atom:link href="https://blog.bjdean.id.au/tags/azure/index.xml" rel="self" type="application/rss+xml"/><item><title>Fine-Tuning in Azure AI Foundry: Practical Lessons from a Weekend Experiment</title><link>https://blog.bjdean.id.au/2025/11/fine-tuning-azure-ai-foundry-practical-lessons/</link><pubDate>Thu, 20 Nov 2025 17:30:51 +1100</pubDate><guid>https://blog.bjdean.id.au/2025/11/fine-tuning-azure-ai-foundry-practical-lessons/</guid><description>&lt;h2 id="tldr"&gt;TL;DR&lt;/h2&gt;
&lt;p&gt;Azure AI Foundry makes fine-tuning accessible with straightforward data preparation requirements, but costs can accumulate quickly during experimentation. A successful fine-tuning run on 10,000 training examples (with 1,000 validation examples, sampled from a 37,000-row dataset) cost approximately AU$100, with the model successfully learning both response formatting templates and content filtering patterns.&lt;/p&gt;
&lt;p&gt;Lessons learned: understand the model and training technique settings and data requirements, monitor your training metrics early to avoid over-training and watch your spending closely since billing data lags by 24-48 hours.&lt;/p&gt;</description></item></channel></rss>