Microsoft Foundry: Where can I see all content-filter-blocked prompts and the reason for each (category or blocklist term)?

Microsoft Foundry content filters and custom blocklists do not provide a built-in view that lists each blocked prompt together with the exact triggering harm category or specific blocklist term.

What is available:

1. Content filter metrics in Risks & Safety monitoring (classic)
   • Risks & Safety monitoring shows aggregated metrics about content filtering, not individual prompts. The report surfaces:
     1. Total blocked request count and block rate over time.
     2. Blocked requests by category (hate, sexual, self-harm, violence).
     3. Block rate over time by category.
     4. Severity distribution by category (for all flagged content, not only blocked).
     5. Severity rate distribution over time by category.
   • These metrics are intended to help understand trends and adjust configuration, not to inspect specific prompts or matched terms.
   • The documentation explicitly recommends: “Adjust your content filter configuration to further align with business needs and Responsible AI principles.”
2. Data handling and limitations
   • Prompts and completions are not stored for the purposes of content filtering, and are not used to train, retrain, or improve the content filtering system without user consent.
   • The system runs prompts and completions through classification models to detect harmful content in the four harm categories (hate, sexual, violence, self-harm) with severity levels (safe, low, medium, high), but the documentation does not describe any feature that exposes full prompt text plus the exact matched term or rule per request.
3. Prompt Shields and indirect attacks
   • Prompt Shields detect user prompt attacks and indirect prompt attacks (for example, attempts to change system rules, role-play attacks, encoding attacks, or malicious instructions embedded in documents). These are categorized (manipulated content, fraud, malware, attempt to change system rules, encoding attacks, etc.), but again the documentation describes classification categories, not a per-request log of blocked prompts and matched terms.
4. Microsoft Defender or Purview
   • The provided documentation does not describe any integration with Microsoft Defender or Microsoft Purview that would expose:
     • Full blocked prompt text, or
     • The exact custom blocklist term that triggered a block.
   • No setup steps are documented for using Defender or Purview to view blocked prompts for Foundry content filters.
5. Diagnostic logs
   • Within the provided documentation, there is no description of diagnostic logging that captures:
     • The full prompt text, and
     • The specific blocklist term or harm category per individual request.
   • Only aggregated metrics and category/severity distributions are documented.

Given the available documentation:

• There is no documented view (in Foundry, Defender, or Purview) that lists each blocked prompt with the exact reason (harm category or blocklist term).
• Risks & Safety monitoring can be used to monitor aggregate block counts, categories, and severities over time and then tune content filter configuration accordingly.
• The system is explicitly designed not to store prompts/completions for content filtering purposes, which limits the availability of per-prompt inspection in the platform.

References:

• Content filtering for Microsoft Foundry Models (classic)
• Prompt Shields in Microsoft Foundry
• Use Risks & Safety monitoring in Microsoft Foundry (preview) (classic)