--- sourceDocument: Yokohama Enable AI sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/intelligent-experiences Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama 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: Yokohama 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 use their own API credentials from supported third-party cloud AI providers such as Azure OpenAI, Amazon Bedrock (Anthropic Claude on AWS), and Google Gemini to power Now Assist skills and AI agents. Instead of routing AI model requests through the ServiceNow AI Platform infrastructure, BYOK sends requests through the customer's cloud AI provider account. This enables customers to maintain control over their AI configuration, security, and data processing environment while benefiting from Now Assist capabilities. Show full answer Show less BYOK supports the same AI models available on the ServiceNow AI Platform but runs workloads within the customer's cloud environment. Customers should be aware that using their cloud AI provider account might incur additional charges based on the provider's pricing. ## Key Features * **Support for multiple cloud AI providers:** Azure OpenAI, Amazon Bedrock (Anthropic Claude), and Google Gemini. * **Control over API credentials and security:** Customers keep their own API keys and maintain their data processing within their cloud provider's environment. * **Model mapping:** ServiceNow model aliases can be mapped to specific provider model versions (e.g., mapping geminilarge to version 2.5 Pro). * **Customization options:** Ability to override model variants per skill in Version Management and customize prompts for the AI models. * **Validation tools:** Customers can verify that AI requests use their cloud provider account by reviewing outbound HTTPS logs. ## How to Configure BYOK To integrate a cloud AI provider with ServiceNow using BYOK, customers must: * Create the connection and credentials with the cloud AI provider (including endpoint, API key, and region). * Enable BYOK for the selected provider within Now Assist Admin. * Map ServiceNow model aliases to the provider's deployed model versions. * Optionally customize model variants and prompts for more tailored AI interactions. * Validate the integration by checking outbound HTTPS logs to confirm requests use the customer's AI account. For detailed, provider-specific configuration steps, customers should refer to the official ServiceNow Knowledge Base article "Configure Bring Your Own Key (BYOK) for Now Assist and AI Agents." ## Azure OpenAI Specific Configuration When configuring BYOK with Azure OpenAI, customers will: * Set up an Azure OpenAI connection using their own API key. * Configure the model and deployment names in the Generative AI Controller for recognition within ServiceNow. * Customize prompts sent to Azure OpenAI large language models by modifying prompt configurations. * Switch the provider setting within Now Assist Admin to route AI processing through Azure OpenAI using BYOK. ## Why This Matters BYOK empowers ServiceNow customers to leverage the AI models they trust within their own cloud security and compliance frameworks, ensuring greater control over sensitive data and AI processing. It also enables integration flexibility by supporting multiple leading cloud AI providers, helping organizations align AI usage with their existing cloud investments and governance policies. 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-for-azure-open-ai__section_njw_gt2_zhc} BYOK supports the following cloud AI providers: * Azure OpenAI * Anthropic Claude on AWS, 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 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. {#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://servicenow-prod.fluidtopics.net/m3umLzCHdcluClbWTFfFmg "Configure your API credentials to use Azure OpenAI in custom workflows and Virtual Agent Designer topics."). 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=yokohama&pubname=yokohama-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://servicenow-prod.fluidtopics.net/sN1XMt0i~V1okhSroilOzw "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 . {#byok-for-azure-open-ai__ol_r2y_zbj_yhc} **Related tasks** * [Configure a custom resource path for BYOK models](https://servicenow-prod.fluidtopics.net/0eTKSo_dBZuGBT~zolB80w "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, such as Azure OpenAI, that use a different web address than the default.")