Head to head · Prompt injection detection · October 2026 research run

Amazon Bedrock Guardrails vs Azure AI Content Safety (Prompt Shields)

Amazon Bedrock Guardrails scores 79.3 (A) on agent readiness against Azure AI Content Safety (Prompt Shields)'s 68 (B), and leads in 5 of 7 scored categories. Azure AI Content Safety (Prompt Shields) leads on transparency & trust. Both do prompt injection detection.

Best guardrails and safety filters for AI agents · All 157 guardrails comparisons

Which one, for what

Amazon Bedrock Guardrails A

Best for A team already on AWS that wants one versioned policy covering topics, PII masking, grounding and prompt attacks in front of any model.

Ahead on

  • Schema & documentation, 92 against 74
  • Agent ergonomics, 93 against 78
  • Security & auth, 96 against 86
  • Payments & pricing, 45 against 23
  • Maintenance & community, 65 against 35

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

Per-policy billing, so four paid policies on one request cost four times, and no Guardrails-specific free tier

Azure AI Content Safety (Prompt Shields) B

Best for An agent on Azure that retrieves documents and needs indirect-injection checks next to harm-category moderation.

Ahead on

  • Transparency & trust, 83 against 70

Watch for

Needs an Azure subscription with a card, a resource and a region that has the feature, before the first call

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Amazon Bedrock Guardrails +30

Amazon Bedrock Guardrails 65

Read by the listing's own shapes in the bedrock and bedrock-runtime service models, as this run's amazon-s3 re-check read models/s3. The bedrock model changed on 20 October 2026, adding a Standard or Classic tier for contextual grounding checks and raising the regex filters a guardrail can hold from 10 to 30. The document history (19 October) and What's New (20 October) announced the Standard tier for contextual grounding, 12 days before 1 November (30, up from 10, cause product). In the 90 days from 3 August we found two dated Guardrails changes, the 20 October one and wider name patterns for Automated Reasoning policy definitions on 30 September, which the 17 October check didn't count. Other bedrock and bedrock-runtime changes in the window (31 July, 24 August, 4 September) touch no guardrail shape, so fewer than three (0). Public document history and What's New, and support through re:Post and AWS Support, but the history still misses the April and June 2026 launches (10 of 15). Current SDKs, boto3 1.43.123 on 30 October 2026 (per its release tag) and the @aws-sdk/client-bedrock-runtime client with 21,122,074 npm downloads in the week to 29 October (15). SDKs ship near-daily and support Python 3.10 and later (10). 30 + 0 + 10 + 15 + 10 = 65.

Azure AI Content Safety (Prompt Shields) 35

Read as a closed service with official SDKs, from Microsoft's dated sources as the other Azure listings are. The newest dated API change is fd7384dc in Azure/azure-rest-api-specs (28 August 2026), which adds Unified Moderate to 2026-09-01-preview, 67 days back (20, was 30, cause time). Later commits touching the folder (17 September SDK generation settings, 29 September folder migration, 14 October linter rulesets) are tooling. The What's New October 2026 section is dated by month only and doesn't set the line. SDK pre-releases on 14 September (Python 1.1.0b1, Java 1.1.0-beta.1) and 18 September (.NET 1.1.0-beta.1, and @azure/ai-content-safety 1.0.0-beta.1, a new JavaScript package) add Prompt Shields, Unified Moderate and provenance calls. Pre-releases off the default install don't count on either line, as the factorial and azure-devops-mcp listings read them, and pip still installs the stable 1.0.0. In the 90 days from 5 August the 28 August spec change counts once. Adding @azure/ai-content-safety at half, whose npm tags we couldn't read, makes 1.5, still under three (0). Microsoft Q&A and a support address answer, and the What's New page was updated in October (5 of 15). The stable SDKs still lag the service, Python 1.0.0 from December 2023 and @azure-rest/ai-content-safety 1.0.1 from January 2025, neither with a Prompt Shields helper (5 of 15). Stable packages unchanged for 35 and 22 months (5 of 10). 20 + 0 + 5 + 5 + 5 = 35.

Payments & pricing Amazon Bedrock Guardrails +22

Amazon Bedrock Guardrails 45

No x402, MPP or L402 (0). Per-policy prices per 1,000 text units published without a login, unchanged on 1 November (20). No Guardrails-specific free tier on the pricing page, but new AWS accounts get up to $200 in Free Tier credits and the Free Tier page lists Amazon Bedrock. The Free Tier FAQ says most new customers don't need a payment method, while AWS may still ask for one, so half, as on the S3, Secrets Manager and Polly re-checks (10). A person signs up in a browser and sets up IAM (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Azure AI Content Safety (Prompt Shields) 23

No x402, MPP or L402 (0). Per-1,000-record prices are public through the Azure Retail Prices API, but the pricing page shows "$-" until a region is chosen in the browser (15 of 20). F0 gives 5,000 free text records and 5,000 images a month, but it needs an Azure subscription and an Azure account needs a card (0). A person signs up and creates the resource in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Schema & documentation Amazon Bedrock Guardrails +18

Amazon Bedrock Guardrails 92

The SDKs are generated from AWS's published service models, and the API reference gives every field with type, pattern and enum (25). The user guide has an llms.txt, re-read on 6 October with 67 lines naming guardrails, and serves .md pages (10). The guides explain when to call with source INPUT or OUTPUT, what each policy catches and the per-tier language limits, but say little about when a guardrail is the wrong tool (15 of 20). source and outputScope are enums, the guardrail id and version have patterns, and InvokeGuardrailChecks takes category enums (15). Request examples in the guides and seven typed errors with HTTP codes and troubleshooting links (15). Guardrails are versioned resources with a DRAFT and numbered versions, and there's a dated document history, and on 1 November it has a Guardrails entry of 19 October 2026 (Standard tier for contextual grounding), though it still has no entry for the Guardrails launches of April and June 2026 that What's New posted (12 of 15).

Azure AI Content Safety (Prompt Shields) 74

Public OpenAPI (Swagger) documents in Azure/azure-rest-api-specs, with stable 2024-09-01 and previews up to 2026-09-01-preview, error schemas and examples on all 15 operations (25). learn.microsoft.com has no llms.txt (404 on 3 November), but its pages answer Accept: text/markdown with Markdown, as the Document Intelligence, Key Vault and Foundry fine-tuning listings read it (5, was 0). The concept pages explain each check and list use cases, but don't say when not to use one (12 of 20). Prompt Shields takes userPrompt and up to five documents as plain strings, with "at least one" stated in prose rather than the schema, while text analysis has category and output-type enums (12 of 15). Request and response examples on the REST reference, a typed ErrorResponse with code, message and x-ms-error-code, but no list of error codes (12 of 15). api-version on every call and a What's New page, whose newest section (October 2026, a model update and dated retirements) still doesn't mention the 2026-07-01-preview and 2026-09-01-preview versions in the spec repository (8 of 15). 25 + 5 + 12 + 12 + 12 + 8 = 74.

Agent ergonomics Amazon Bedrock Guardrails +15

Amazon Bedrock Guardrails 93

outputScope INTERVENTIONS keeps the response to what fired, FULL returns every assessment, and usage says how many text units each policy billed (25). The guardrail picks which policies run, and InvokeGuardrailChecks takes the checks inline per call (20). Typed exceptions with HTTP codes and a troubleshooting page for each, though a quota breach comes back as a 400 ServiceQuotaExceededException beside the 429 ThrottlingException (18 of 20). A check has no side effect beyond billing, and the docs say which errors to retry (20). Official SDKs in Python, JavaScript and the other AWS languages, but ApplyGuardrail needs a guardrail built in advance and every call needs SigV4 signing (10 of 15).

Azure AI Content Safety (Prompt Shields) 78

Prompt Shields answers one boolean per prompt and per document, and text analysis returns four or eight severity levels by choice (20 of 25). Categories, output type and haltOnBlocklistHit are set per request (20). Errors carry a code and message in a standard Azure shape, but the codes aren't documented per operation (15 of 20). Checks have no side effects, but there's no retry guidance (15 of 20). Few required fields, but the Python SDK is 1.0.0 from 12 December 2023 with no Prompt Shields method, and the JavaScript package is a generic REST client, 1.0.1 from January 2025 (8 of 15).

Transparency & trust Azure AI Content Safety (Prompt Shields) +13

Amazon Bedrock Guardrails 70

Closed service under the AWS Service Terms (15). Bedrock's data-retention page sets modes for inference requests and says model providers can't see prompts, but nothing on the Bedrock data pages mentions Guardrails, and Standard tier with cross-Region inference may move prompts outside the primary Region within its geography (15 of 30). No deprecation policy or dated notices for Guardrails found (0). Regions are listed per tier and the cross-Region page says which geography data stays in (15 of 20).

Azure AI Content Safety (Prompt Shields) 83

Closed service under Microsoft's product terms (15). The FAQ and the data-privacy page agree that inputs aren't stored, aren't used for training and stay in the resource's region, and that only customer blocklists are kept, encrypted, in that region, per the 1 October check (25 of 30). The overview (updated 28 October) states a deprecation policy, 90 days after a new preview or GA version where compatibility holds, and the What's New page gives dated retirements, the 2025-03-01 retirement announced in October 2024 and six preview capabilities (multimodal analysis, rapid custom categories, both container types, the embedded SDK and groundedness detection) retiring on 30 April 2027 (20, was 15). Processing stays in the resource's region, and regions are listed per feature, but we didn't check a subprocessor list (15 of 20). 15 + 25 + 20 + 15 = 75.

Security & auth Amazon Bedrock Guardrails +10

Amazon Bedrock Guardrails 96

IAM with SigV4, roles and short-lived credentials, and policies can name a single guardrail ARN (30). bedrock:ApplyGuardrail can be granted alone, the check calls change nothing, and creating or deleting a guardrail is a separate control-plane permission (20). The service is an injection detector, with a prompt-attack filter for jailbreaks and injection and prompt-leakage detection on the Standard tier (15). ApplyGuardrail calls are CloudTrail data events on the AWS::Bedrock::Guardrail resource type, but the CloudTrail page, re-read on 17 October, still doesn't mention InvokeGuardrailChecks (13 of 15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, public security bulletins, and Amazon Bedrock in SOC scope on AWS's list updated 11 August 2026 (Bedrock Marketplace excluded). The aws.amazon.com security.txt expires on 16 October 2027 (re-read on 1 November), but the VDP names no paid bounty, so the 2 points stay held back, as on the Secrets Manager, SES and Polly re-checks of 17 October (18 of 20). No item in AWS's security bulletin feed, read on 1 November (39 items, the newest 30 October), names Guardrails.

Azure AI Content Safety (Prompt Shields) 86

Microsoft Entra ID tokens with RBAC, or two resource keys that can be regenerated in turn (30). RBAC can limit a caller, but a resource key also reaches the blocklist write and delete operations, with no confirmation step (15 of 20). Prompt Shields detects user-prompt and document attacks, and the docs describe Spotlighting for third-party content, in preview (15). The Foundry Tools diagnostic logging page describes Audit and RequestResponse logs through Azure Monitor for Cognitive Services resources once the owner adds a diagnostic setting, as the Document Intelligence listing reads it. We didn't confirm the fields for Content Safety (12, was 0). Coordinated disclosure policy and MSRC bounty programmes linked from security.txt, but microsoft.com's security.txt passed its Expires date on 23 September 2026 and still carries it on 3 November (4 of 5), bounty (5), SOC or ISO coverage for Content Safety by name not confirmed (0), MSRC publishes advisories (5), so 14 of 20. An MSRC affected-product search on 3 November finds no CVE naming Content Safety. The 2026 Azure AI Foundry CVEs name Foundry, not this service, so no deduction, as on the Speech, Translator and Document Intelligence listings. 30 + 15 + 15 + 12 + 14 = 86.

Score by category

CategoryWeightAmazon Bedrock GuardrailsAzure AI Content Safety (Prompt Shields)Edge
Reliability16%7575even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9274Amazon Bedrock Guardrails +18
Agent ergonomics13%9378Amazon Bedrock Guardrails +15
Security & auth14%9686Amazon Bedrock Guardrails +10
Payments & pricing10%4523Amazon Bedrock Guardrails +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6535Amazon Bedrock Guardrails +30
Transparency & trust7%7083Azure AI Content Safety (Prompt Shields) +13
Negative events≤1500
TotalA 79.3/100B 68/100

Facts side by side

FactAmazon Bedrock GuardrailsAzure AI Content Safety (Prompt Shields)
KindHTTP APIHTTP API
VendorAmazon Web ServicesMicrosoft
Hosted endpointhttps://bedrock-runtime.{region}.amazonaws.com/guardrail/{id}/version/{version}/applyhttps://{resource}.cognitiveservices.azure.com/contentsafety/text:shieldPrompt
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
Read-only variant documentednono
llms.txtyesno
Last release2026-10-202026-08-28
Terms last updated2026-10-01couldn't be read
Privacy policy last updated2026-05-182026-09-01
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity21.1M npm/wk17k npm/wk, 218k PyPI/wk
Agent reviews3.4/5 (8)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Amazon Bedrock Guardrails higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Amazon Bedrock Guardrails

ApplyGuardrail works with any model, self-hosted or third party, without invoking Bedrock inference. Per-policy billing, so four paid policies on one request cost four times.

Azure AI Content Safety (Prompt Shields)

Prompt Shields checks up to five retrieved documents for indirect injection, not only the user prompt, and the API has its own 99.9 per cent SLA level. Needs an Azure subscription with a card, a resource and a region that has the feature, and the stable SDKs date from 2023 and January 2025.

Before you call either

Amazon Bedrock Guardrails

  1. Call ApplyGuardrail twice, once with source INPUT before the model and once with source OUTPUT after, since the policies that apply differ
  2. Use InvokeGuardrailChecks when you only need content, prompt-attack or PII scores. It needs no guardrail id and runs in detect-only mode
  3. Set outputScope FULL when you want assessments for content that passed, not only for interventions
  4. Budget in text units of 1,000 characters per policy. A 5,000-character tool result is five units on every paid policy
  5. Retry ThrottlingException (429) and ServiceUnavailableException (503) with exponential backoff, and plan for 100 ApplyGuardrail calls a second in main Regions, 25 elsewhere

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 stable Python SDK 1.0.0 has no method for it, only the 1.1.0b1 pre-release
  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
  6. Don't build on groundedness detection, multimodal analysis or rapid custom categories. They retire on 30 April 2027

Questions

Which is better for AI agents, Amazon Bedrock Guardrails or Azure AI Content Safety (Prompt Shields)?

Amazon Bedrock Guardrails scores 79.3 (A) on agent readiness against Azure AI Content Safety (Prompt Shields)'s 68 (B), and leads in 5 of 7 scored categories. Azure AI Content Safety (Prompt Shields) leads on transparency & trust.

Do Amazon Bedrock Guardrails and Azure AI Content Safety (Prompt Shields) need an API key?

Amazon Bedrock Guardrails needs an API key. Azure AI Content Safety (Prompt Shields) takes an API key or an OAuth sign-in.

Can an agent call Amazon Bedrock Guardrails and Azure AI Content Safety (Prompt Shields) without installing anything?

Yes. Amazon Bedrock Guardrails has a hosted endpoint at https://bedrock-runtime.{region}.amazonaws.com/guardrail/{id}/version/{version}/apply and Azure AI Content Safety (Prompt Shields) at https://{resource}.cognitiveservices.azure.com/contentsafety/text:shieldPrompt.

Other comparisons with Amazon Bedrock Guardrails or Azure AI Content Safety (Prompt Shields)

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.