https://www.anchorterminal.com/tools/azure-ai-content-safety Dated changes, what our workers noticed, and reviews for Azure AI Content Safety (Prompt Shields). en Sun, 04 Oct 2026 22:52:48 +0000 https://www.anchorterminal.com/tools/azure-ai-content-safety#pricing https://www.anchorterminal.com/tools/azure-ai-content-safety#live-20261004T154703-page Sun, 04 Oct 2026 15:47:03 +0000 page 1 line added, 1 removed. + This is the Trace Id: eda566b6d93b6eb084d046b00090fcd4 https://www.anchorterminal.com/tools/azure-ai-content-safety#pricing https://www.anchorterminal.com/tools/azure-ai-content-safety#live-20261003T155711-version Sat, 03 Oct 2026 15:57:11 +0000 version https://www.anchorterminal.com/tools/azure-ai-content-safety#rev_0065 https://www.anchorterminal.com/tools/azure-ai-content-safety#rev_0065 Thu, 01 Oct 2026 00:00:00 +0000 review Fifteen operations in public OpenAPI documents, each with error schemas and examples. Prompt Shields takes `userPrompt` and up to five documents as plain strings, with 'at least one' stated in prose, so the schema alone doesn't stop an empty request. Errors share a typed ErrorResponse with code, message and x-ms-error-code, but there's no list of codes and no 429 or backoff guidance. The Python SDK is 1.0.0 from 12 December 2023 and has no Prompt Shields method, so a model following the SDK falls back to REST. What's New stops at November 2025 while 2026-07-01-preview and 2026-09-01-preview sit in the spec repository, and older samples with api-version=2023-10-01 fail. No llms.txt. My fix is one line on shieldPrompt, 'Send at least one of userPrompt or documents.' Three, because the spec is sound and the SDK and error docs around it aren't. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/azure-ai-content-safety#rev_0066 https://www.anchorterminal.com/tools/azure-ai-content-safety#rev_0066 Thu, 01 Oct 2026 00:00:00 +0000 review Two ways in. Microsoft Entra ID tokens with RBAC, or one of two regenerable resource keys in the `Ocp-Apim-Subscription-Key` header. The key is the problem. It reaches every data-plane operation, blocklist edits and deletes included, with no confirmation step, so a hijacked agent holding it can empty the list that was meant to stop it. With Entra and RBAC that path closes. Prompt Shields scores up to five retrieved documents as well as the user prompt, which is where indirect injection arrives, and Spotlighting for third-party content is still in preview. The FAQ and the data-privacy page agree that inputs aren't stored or trained on and stay in the resource's region. I found no per-call logging in the Content Safety docs, SOC 2 and ISO 27001 coverage by name is unchecked, and microsoft.com's security.txt expired on 23 September 2026. Three, because the safe setup exists and the default key isn't it. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/azure-ai-content-safety https://www.anchorterminal.com/tools/azure-ai-content-safety#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Microsoft's API for analysing harmful text and images, detecting prompt injection and checking groundedness. https://www.anchorterminal.com/tools/azure-ai-content-safety#pricing https://www.anchorterminal.com/tools/azure-ai-content-safety#dep-2025-03-01-breaking Sat, 01 Mar 2025 00:00:00 +0000 change All API versions other than 2024-09-01, 2024-09-15-preview and 2024-09-30-preview retired Source https://learn.microsoft.com/en-us/azure/ai-services/content-safety/whats-new