--- sourceDocument: Australia Enable AI sourceDocumentLink: https://www.servicenow.com/docs/r/australia/intelligent-experiences Release : - australia ft:locale : - en-US ft:publication_title : - Australia Enable AI ft:clusterId : - platai bundleId : - platai workflow : - Platform --- # Bring your own key for third-party AI provider integration # Bring your own key for third-party AI provider integration {#ariaid-title1} Release version: Australia Updated January 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 integrate their own API credentials from supported cloud AI providers---such as Azure OpenAI, Amazon Bedrock (Anthropic Claude), and Google Gemini---to run generative AI skills and AI agents. Instead of routing AI model requests through the ServiceNow AI Platform infrastructure, BYOK enables these requests to be processed directly within the customer's cloud AI provider environment. Show full answer Show less This ensures that customers retain ownership and control over their AI configuration, security policies, and data processing environments while still leveraging ServiceNow's AI capabilities. BYOK supports the same AI models available through the ServiceNow AI Platform but routes the workloads via the customer's cloud provider account. **Important:** Using your organization's cloud AI provider account may incur additional charges according to the provider's pricing and terms. Customers should review these before enabling BYOK. ## Supported Cloud AI Providers * Azure OpenAI * Amazon Bedrock (Anthropic Claude) * Google Gemini ## Configuring BYOK To enable BYOK, customers must establish a connection between their ServiceNow instance and the chosen cloud AI provider. Although configuration details vary by provider, the general workflow includes: * Creating connection credentials (e.g., API key, endpoint, region) * Enabling BYOK for the provider within the ServiceNow AI Admin Hub * Mapping ServiceNow model aliases to specific provider model versions (for example, mapping `geminilarge` to version 2.5 Pro) * Overriding skill variants in Version Management as needed * Validating that AI requests use the customer's provider account by reviewing outbound HTTPS logs Step-by-step configuration instructions for each supported provider are available in the Now Support Knowledge Base article. ## Azure OpenAI BYOK Configuration Highlights * Set up the Azure OpenAI connection with your API key within your ServiceNow instance. * Configure your Azure OpenAI model and deployment name in the Generative AI Controller to enable recognition and use by ServiceNow. * Modify prompt configurations to customize prompts sent to Azure OpenAI large language models. * Switch AI processing to use BYOK instead of the default ServiceNow AI provider. ## Benefits for ServiceNow Customers * Maintain full control over AI keys, configuration, and data processing environment within your cloud provider account. * Leverage ServiceNow AI Platform capabilities while using your preferred cloud AI models and infrastructure. * Ensure security and compliance by using your organization's cloud security controls. * Flexibility to switch AI providers and manage AI model versions explicitly. 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 generative AI skills and AI agents. When BYOK is enabled, AI model requests are sent 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 ServiceNow AI Platform capabilities. BYOK supports the same AI models that the ServiceNow AI Platform supports. After you configure your API credentials, your provider resources are used to process requests instead of 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-for-azure-open-ai__section_njw_gt2_zhc} BYOK supports the following cloud AI providers: * Azure OpenAI * Anthropic Claude, which is accessible through Amazon Bedrock * Google Gemini {#byok-for-azure-open-ai__ul_pxb_kt2_zhc} ## Configuring a BYOK connection with a cloud AI provider {#byok-for-azure-open-ai__section_yqb_py3_yhc} 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, such as the following: 1. Create connection and credentials for the provider, such as endpoint, API key, and region. 2. Enable BYOK for the provider in AI Admin Hub. 3. Map ServiceNow model aliases to provider model versions. For example, map `gemini_large` → 2.5 Pro. 4. Override variants in each skill in Version Management. 5. Validate that requests are using your AI provider account by reviewing outbound HTTPS logs. {#byok-for-azure-open-ai__ol_fdb_kwh_b3c} 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\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2666298) article in the Now Support Knowledge Base. ## High-level BYOK configuration for Azure OpenAI {#byok-for-azure-open-ai__example_grf_rb3_b3c} 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](https://www.servicenow.com/docs/mNtoXIjXt6QEYqYHQNGU4Q "Configure your API credentials to use Azure OpenAI as your LLM provider for Generative AI Controller capabilities."). 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](https://www.servicenow.com/docs/access?context=create-byom&version=australia&pubname=australia-platform-administration&ft:locale=en-US). 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](https://www.servicenow.com/docs/bXEv~zQQXi1UzAOMLl4Erg "Connect an external LLM to the ServiceNow AI Platform by using a generic LLM connector. With a connector, you can write your own prompts to send to the LLM and create your own generative AI capabilities."). 4. Switch providers to use BYOK for AI processing.For more information, see [Manage Integration](https://www.servicenow.com/docs/gSFG~sO0r198t~Ls_tluzg "Choose the preferred integration type for configuring the available model providers. There are two ways to configure a model provider in AI Admin Hub. You can either select Original Equipment Manufacturer (OEM) or Bring Your Own Key (BYOK)."). {#byok-for-azure-open-ai__ol_r2y_zbj_yhc} **Related tasks** * [Configure a custom resource path for BYOK models](https://www.servicenow.com/docs/N_TMp11XQQQJ1NMuOPckVw "Enter a custom resource path in your bring-your-own-key (BYOK) model configuration so that Generative AI Controller can connect to AI service providers that use a different web address than the default.")