Skip to main content
Microsoft Foundry supports third-party safety and security integrations. You can connect external solutions to your AI models and agents at runtime to enhance Foundry Guardrails & Controls with best-in-class security capabilities from trusted partners.

Prerequisites

Before you set up the integration, ensure you have:
The Foundry RBAC roles were recently renamed. Foundry User, Foundry Owner, Foundry Account Owner, and Foundry Project Manager were previously named Azure AI User, Azure AI Owner, Azure AI Account Owner, and Azure AI Project Manager. You might still see the previous names in some places while the rename rolls out. The role IDs and core permissions are unchanged by the rename.
  • Managed Identity: Create at least one user-assigned Managed Identity and attach it to the Foundry resource in the Azure portal under Resource Management > Identity.

Enablement and data processing

Third-party integrations are enabled via a Bring Your Own License (BYOL) approach, allowing you to utilize existing third-party software licenses from supported partners. Your data is processed outside of Azure AI Foundry using the service you selected. The terms and privacy commitments for your other service is applied to this processing.

Steps to connect integration

  1. Follow the third-party integrations steps and retrieve your API key linked to your custom security profile. We recommend that your Foundry project is in the same region as the third-party endpoint. View supported regions here.
  2. Go to AI Foundry and select Guardrails.
  3. Select the Integrations tab, and add a third-party integration. Then, select your desired third-party integration.
  4. Select a Keyvault and Managed Identity.
  5. Add the endpoint and API keys. To get the endpoint-API key pair, follow the third-party integrations steps.

Third-party integrations

This section links resources to third-party instructions on retrieving API keys and creating custom profiles. In the steps to connect integration section, you can use these links to continue connecting your integration.
ModelOnboarding step
Palo Alto NetworksPrisma AIRS
ZenityAI Detection and Response.

Attach Integrations to Foundry Guardrails

  1. Select one or more Foundry Guardrails to attach the integration.
  2. Select Save and confirm integration and guardrail attachment in the integrations table.
  3. Confirm the status. Running indicates that a connection has been successfully established.
  4. Error messages point to concrete recommendations (for example, missing Managed Identity).
  5. Follow the main Foundry Guardrail flow to assign a custom guardrail with an active third-party integration to a model or agent.
  6. Test in Playground.

Code Examples

from openai import OpenAI

# Replace with your endpoint and API key
endpoint = "<your-endpoint>"
deployment_name = "gpt-5.2-chat"
api_key = "<your-api-key>"

client = OpenAI(
    base_url=endpoint,
    api_key=api_key
)

response = client.chat.completions.create(
    model=deployment_name,
    messages=[
        {
            "role": "user",
            "content": "<prompt-that-violates-rai-policy>",
        }
    ],
    temperature=0.7,
)

print(response)

Output

openai.BadRequestError: Error code: 400 - 
{
  "error": {
    "message": "The response was filtered due to the prompt triggering Azure OpenAI's content management policy. Please modify your prompt and retry. To learn more about our content filtering policies please read our documentation: https://go.microsoft.com/fwlink/?linkid=2198766",
    "type": null,
    "param": "prompt",
    "code": "content_filter",
    "status": 400
  }
}

{
  "innererror": {
    "code": "ResponsibleAIPolicyViolation",
    "content_filter_result": {
      "external_safety_provider": {
        "detected": true,
        "filtered": true,
        "results": [
          {
            "provider_name": "Palo Alto Networks Prisma AIRS",
            "error": false,
            "detected": true,
            "filtered": true,
            "role": "User",
            "source": "AI-Runtime-Azure-AI-Foundry",
            "details": {
              "created_at": "2026-02-18T01:11:29.3949427Z",
              "completed_at": "2026-02-18T01:11:29.436312651Z",
              "detections": {
                "action": "block",
                "category": "malicious",
                "content_detected": {
                  "injection": false,
                  "toxic_content": true
                }
              }
            },
            "profile_id": "b44235eb-2960-49f9-bc44-13c69cb3f5f6",
            "profile_name": "safety-provider-do-not-use",
            "scan_id": "c41ac678-c675-4180-9f74-a109a25457cc",
            "report_id": "Rc41ac678-c675-4180-9f74-a109a25457cc",
            "session_id": "182e5add-f49a-4a63-931f-30c864866dd6",
            "tr_id": "182e5add-f49a-4a63-931f-30c864866dd6"
          }
        ]
      },
      "hate": {
        "filtered": false,
        "severity": "safe"
      },
      "self_harm": {
        "filtered": false,
        "severity": "safe"
      },
      "sexual": {
        "filtered": false,
        "severity": "safe"
      },
      "violence": {
        "filtered": false,
        "severity": "safe"
      },
      "jailbreak": {
        "detected": false,
        "filtered": false
      }
    }
  }
}

Region availability

The following table shows supported regions. We recommend that your Foundry project is in the same region as the third-party endpoint. Different regions can cause higher latency and potential timeouts.
Azure RegionRecommended EndpointThird-party Integration
West USUSZenity, Palo Alto Networks Prisma AIRS
West US 2USZenity
West US 3USZenity, Palo Alto Networks Prisma AIRS
West Central USUSZenity, Palo Alto Networks Prisma AIRS
Central USUSZenity
North Central USUSZenity
South Central USUSZenity
East USUSZenity
East US 2USZenity
Canada CentralUSZenity
Canada EastUSZenity
West EuropeEuropeZenity, Palo Alto Networks Prisma AIRS
North EuropeEuropeZenity, Palo Alto Networks Prisma AIRS
France CentralEuropeZenity, Palo Alto Networks Prisma AIRS
Germany West CentralEuropeZenity, Palo Alto Networks Prisma AIRS
Italy NorthEuropeZenity, Palo Alto Networks Prisma AIRS
Spain CentralEuropeZenity
Sweden CentralEuropeZenity, Palo Alto Networks Prisma AIRS
Norway EastEuropeZenity, Palo Alto Networks Prisma AIRS
Switzerland NorthEuropeZenity, Palo Alto Networks Prisma AIRS
Switzerland WestEuropeZenity, Palo Alto Networks Prisma AIRS
UK SouthEuropeZenity, Palo Alto Networks Prisma AIRS
UK WestEuropeZenity, Palo Alto Networks Prisma AIRS
South IndiaIndiaPalo Alto Networks Prisma AIRS
Southeast AsiaSingaporePalo Alto Networks Prisma AIRS
East AsiaSingaporePalo Alto Networks Prisma AIRS

Next steps