Bring your own key for third-party AI provider integration

  • Release version: Australia
  • Updated January 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Bring Your Own Key for Third-Party AI Provider Integration

    The Bring Your Own Key (BYOK) feature allows ServiceNow customers to use their own API credentials from supported cloud AI providers—such as Azure OpenAI, Amazon Bedrock (Anthropic Claude on AWS), and Google Gemini—to run Now Assist skills and AI agents. Instead of routing AI model requests through ServiceNow’s AI Platform infrastructure, BYOK sends requests through the customer’s cloud AI provider account, enabling customers to maintain ownership of their AI configurations, security controls, and data processing environments.

    Show full answer Show less

    BYOK supports the same AI models available through the ServiceNow AI Platform, ensuring compatibility while keeping AI workloads and keys under customer control within their cloud environment.

    Important: Using your organization’s cloud AI provider account may incur additional costs; review pricing and terms before enabling BYOK.

    Supported Cloud AI Providers

    • Azure OpenAI
    • Anthropic Claude on AWS via Amazon Bedrock
    • Google Gemini

    Configuring BYOK

    To integrate your cloud AI provider with ServiceNow using BYOK, you must configure a connection between your ServiceNow instance and the provider. While configuration steps vary by provider, the general workflow includes:

    • Creating connection credentials (endpoint, API key, region) for the cloud AI provider
    • Enabling BYOK for the provider within the Now Assist Admin interface
    • Mapping ServiceNow model aliases to the provider’s model versions (e.g., mapping geminilarge → 2.5 Pro)
    • Optionally overriding skill variants in Version Management
    • Validating that AI requests use your provider account by reviewing outbound HTTPS logs

    For detailed, provider-specific setup instructions, ServiceNow provides a knowledge base article titled Configure Bring Your Own Key (BYOK) for Now Assist and AI Agents.

    Azure OpenAI Specific Configuration

    When configuring Azure OpenAI with BYOK:

    • Set up the Azure OpenAI connection using your API key within your ServiceNow instance
    • Configure your Azure OpenAI model and deployment name in the Generative AI Controller to enable ServiceNow recognition and usage
    • Modify prompt configurations to customize prompts sent to Azure OpenAI large language models (LLMs)
    • Switch your AI provider settings to leverage BYOK for processing

    Practical Benefits for ServiceNow Customers

    • Maintains full control over AI keys and data processing environments
    • Enables use of preferred cloud AI providers while continuing to benefit from Now Assist capabilities
    • Supports existing ServiceNow AI models for seamless integration
    • Allows customization of AI model mappings and prompts for tailored AI interactions

    The bring your own key (BYOK) feature enables you to use your own API credentials from supported cloud AI providers, such as Azure OpenAI, Amazon Bedrock, and Google Gemini, to run Now Assist skills and AI agents.

    When BYOK is enabled, Now Assist sends model requests through your cloud AI provider account instead of ServiceNow AI Platform infrastructure. This approach lets you maintain ownership of your AI configuration, security controls, and data processing environment while continuing to use Now Assist capabilities.

    BYOK supports the same AI models that the ServiceNow AI Platform supports. After you configure your API credentials, Now Assist uses your provider resources to process requests instead of using the default ServiceNow AI provider. BYOK keeps your keys under your control and AI workloads running within your cloud environment.
    Note:
    Using your organization’s cloud AI provider account might result in additional charges from that provider. Review the provider’s pricing and terms of service before enabling BYOK.

    ServiceNow integrated model providers

    BYOK supports the following cloud AI providers:
    • Azure OpenAI
    • Anthropic Claude on AWS, which is accessible through Amazon Bedrock
    • Google Gemini

    Configuring a BYOK connection with a cloud AI provider

    To use your cloud AI provider resources within your ServiceNow instance, configure a connection between ServiceNow and your provider. Configuration steps vary by provider, but follow a similar high-level configuration workflow as the following steps:
    1. Create connection and credentials for the provider, such as endpoint, API key, and region.
    2. Enable BYOK for the provider in Now Assist Admin.
    3. Map ServiceNow model aliases to provider model versions. For example, map gemini_large → 2.5 Pro.
    4. Optionally, override variants in each skill in Version Management.
    5. Validate that requests are using your AI provider account by reviewing outbound HTTPS logs.

    For step-by-step instructions for each supported cloud AI provider, see Configure Bring Your Own Key (BYOK) for Now Assist and AI Agents [KB2666298] article in the Now Support Knowledge Base.

    High-level BYOK configuration for Azure OpenAI

    1. Set up Azure OpenAI connection with your own key to use Azure OpenAI within your ServiceNow instance.

      For more information, see Configure API credentials for Azure OpenAI.

    2. Configure your Azure OpenAI model and deployment name in Generative AI Controller so your ServiceNow instance can recognize and use it.

      For more information, see Create a custom embedding model.

    3. Modify the prompt configuration to write your own prompts to send to the Azure OpenAI LLMs.

      For more information, see Configure a generic large language model (LLM) connector.

    4. Switch providers to use BYOK for AI processing.

      For more information, see Manage Integration.