azure-ai-contentsafety-py

Topics in the source

• Azure AI Content Safety SDK for Python
• Installation
• Environment Variables
• Authentication & Lifecycle
• Legacy: API Key (existing keyed deployments)
• Analyze Text
• Analyze Image
• Image from URL

Detect harmful user-generated and AI-generated content in applications. 🔑 Two rules apply to every code sample below: 1. Prefer DefaultAzureCredential. It works locally (Azure CLI / VS Code / Developer CLI) and in Azure (managed identity, workload identity) with no code change. Avoid connection strings, account/API keys — they bypass Entra audit and rotation. - Local dev: DefaultAzureCredential works as-is. - Production: set AZURETOKENCREDENTIALS=prod (or AZURETOKENCREDENTIALS= ) to constrain the credential chain to production-safe credentials. 2. Wrap every client in a context manager so HTTP transports, sockets, and token caches are released deterministically: - Sync: with (...) as client: - Async: async with (...) as client: and async with DefaultAzureCredential() as credential: (from azure.identity.aio) Snippets may abbreviate this setup, but production code should always follow both rules. New code should use DefaultAzureCredential above. Use AzureKeyCredential only if you have an existing keyed deployment that hasn't been migrated to Entra ID yet — for example, regulated environments still completing their Entra rollout. The BlocklistClient accepts the same AzureKeyCredentia

This is an excerpt. Refer to the complete source and its current requirements.