Why Is Microsoft Foundry’s Content Filter Blocking Legitimate Medical Questions?

Last Updated on October 6, 2026 by Editorial Team Author(s): Dave R | Microsoft Azure & AI MVP ☁️ Originally published on Towards AI. An AB-100 case study: read the guardrail annotation, find the category and severity, and relax one threshold while Self-harm stays strict. An oncologist asks a clinical notes assistant built on Microsoft Foundry to summarize the risks of a high-dose chemotherapy plan, and the app gets back an HTTP 400 with the error code content_filter. The same assistant still declines off-topic questions exactly as intended. This scenario is the false positive that teams running AI in medicine, law, or security eventually meet. Here's how to find the exact category and severity behind the block, and how to fix it with a custom guardrail while Self-harm stays at the strictest setting. Why Is Microsoft Foundry’s Content Filter Blocking Legitimate Medical QuestionsThe article walks through a four-step approach to fix a medical-system false positive in Microsoft Foundry: first, diagnose by reading guardrail annotations returned with API calls (including distinguishing input-block vs completion-block vs model refusal), then identify the specific harm category, severity…

≈