<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure OpenAI on Thomy Gölles</title><link>https://thomygoelles.com/tags/azure-openai/</link><description>Recent content in Azure OpenAI on Thomy Gölles</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 22 Feb 2024 09:15:01 +0000</lastBuildDate><atom:link href="https://thomygoelles.com/tags/azure-openai/index.xml" rel="self" type="application/rss+xml"/><item><title>How to fix Pi-hole blocking Azure OpenAI calls</title><link>https://thomygoelles.com/how-to-fix-pi-hole-blocking-azure-openai-calls/</link><pubDate>Thu, 22 Feb 2024 07:59:41 +0000</pubDate><guid>https://thomygoelles.com/how-to-fix-pi-hole-blocking-azure-openai-calls/</guid><description>&lt;p&gt;&lt;i&gt;A simple solution for a frustrating bug hunt&lt;/i&gt;&lt;/p&gt;
&lt;h2 id="tldr"&gt;TLDR;&lt;/h2&gt;
&lt;p&gt;If you’re using Pi-hole for ad-blocking and find that it’s preventing your access to Azure OpenAI Service, the solution is to whitelist Azure OpenAI domains in Pi-hole’s settings. This issue arises because Pi-hole, which blocks ad-serving domains at the DNS level, can also block legitimate services like Azure OpenAI. The fix involves accessing Pi-hole’s admin interface and adding openai.azure.com to the whitelist, ensuring uninterrupted access to Azure OpenAI for your services, which relies on Azure OpenAI for features like Semantic Kernel for natural language processing. Remember to share this workaround with anyone facing similar issues!&lt;/p&gt;</description></item></channel></rss>