Azure AI Content Safety (Prompt Shields) vs OpenAI Moderation API

Azure AI Content Safety (Prompt Shields)

Prompt Shields checks up to five retrieved documents for indirect injection, not only the user prompt. Needs an Azure subscription with a card, a resource and a region that has the feature, before the first call.

OpenAI Moderation API

Free, on any OpenAI project key. No prompt-injection, jailbreak or PII detection.

Azure AI Content Safety (Prompt Shields)

1. Send retrieved pages and tool results in the documents array of shieldPrompt, not in userPrompt, so document attacks are reported separately
2. Call text:shieldPrompt over REST with api-version=2024-09-01. The Python SDK 1.0.0 has no method for it
3. Keep each request under 10,000 characters across prompt and documents, and split long tool results
4. Create the resource in a region that lists Prompt Shields, since not every region has it
5. On F0 you get 5 requests a second. Queue checks or move to S0 before load testing

OpenAI Moderation API

1. Read category_scores rather than flagged alone. The default thresholds are OpenAI's
2. Pin omni-moderation-2024-09-26 if the scores feed a decision you audit. The latest alias will move
3. Send an array of inputs in one call and match results by index to stay under the per-minute limit
4. Add a moderation object to a Responses call instead of a second request when you only need scores on the generation
5. Pair it with a separate injection detector. A clean result says nothing about a hidden instruction in a tool result