Azure AI Content Safety (Prompt Shields) vs NVIDIA NeMo Guardrails

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.

NVIDIA NeMo Guardrails

Apache-2.0, 7,200 stars and nine releases between 9 October 2025 and 16 September 2026. Usage telemetry and a heartbeat every 10 minutes to NVIDIA by default.

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

NVIDIA NeMo Guardrails

1. Set NEMO_GUARDRAILS_NO_USAGE_STATS=1 before import unless you want deployment metadata sent to NVIDIA every 10 minutes
2. Use IORails for plain input and output checks. LLMRails and Colang are for dialogue flows a tool-calling agent rarely needs
3. Pin nemoguardrails==0.24.1. 0.24.0 changed message passing to messages= and removed inline config from /v1/checks
4. Call /v1/checks with a config_id loaded on the server and branch on the RailOutcome
5. Put the server behind your own gateway. It has no auth or rate limiting