BYOK Integration Guide for Azure¶
Bring Your Own Key (BYOK) encryption in Kore’s public cloud SaaS enables enterprises to retain complete control over their encryption keys while protecting sensitive data. With BYOK, organizations use their own Customer Master Keys (CMKs) to encrypt application and bot data, ensuring stronger security and compliance.
Kore’s BYOK solution integrates with external key management systems such as Azure Key Vault. Customers retain ownership of their encryption keys while leveraging Kore’s secure, scalable cloud platform with HSM-backed keys.
Prerequisites¶
- Active Kore.ai subscription (platform.kore.ai) with BYOK enabled.
- Azure account with administrative access to the Key Vault service.
- Permissions to create Key Vault.
Integration Process¶
The BYOK integration requires coordination between you (the customer) and the Kore.ai support team. The integration involves five main steps:
- Authorize the Kore Application in Your Tenant: Register our application in your Azure tenant for secure access to Key Vault.
- Prepare Key Vault and Key: Create an Azure Key Vault and generate an RSA key. Note the Key Vault URI and Key Identifier for integration purposes.
- Configure Key Vault Access: Assign the Key Vault Crypto User role to the Kore application in Key Vault IAM to enable cryptographic operations.
- Share Information: Share your Tenant ID, Key Vault URI, and Key Name with Kore.ai to complete the integration and approve network access.
- Configure Network Access: Enable a private endpoint, or allow trusted Microsoft services and Kore IP ranges.
Step 1: Authorize the Kore Application in Your Tenant¶
Option 1: Admin Consent URL
- Log in to the Azure portal as a Global Administrator.
- Navigate to the following URL (replace
<YOUR-TENANT-ID>and<KORE-CLIENT-ID>):https://login.microsoftonline.com/<YOUR-TENANT-ID>/adminconsent?client_id=<KORE-CLIENT-ID> - Review permissions and grant admin consent.
Option 2: Azure CLI
- Open Azure Cloud Shell or install Azure CLI locally.
- Login as Global Administrator:
az login - Create service principal:
az ad sp create --id '<KORE-CLIENT-ID>'
This step registers our application in your tenant, enabling it to securely interact with your Key Vault.
Step 2: Prepare Key Vault and Key¶
- In Azure Portal, create a Key Vault if one doesn’t exist.
- Configure:
- Resource group: Select or create
- Key vault name: Choose a unique name
- Region: Select appropriate region
- Pricing tier: Standard or Premium
- Note the Key Vault URI:
https://<vault-name>.vault.azure.net/
Create RSA Key (if needed)
- In your Key Vault, navigate to Keys
- Click Generate/Import
- Configure:
- Options: Generate
- Name: Choose a descriptive name
- Key type: RSA
- RSA key size: 2048 or 4096
- Note the Key Identifier URL.
Step 3: Configure Key Vault Access¶
Assign Key Vault Permissions
- Navigate to Access control (IAM) in your Key Vault.
- Click Add role assignment.
- Configure:
- Role: Key Vault Crypto User
- Assign access to: User, group, or service principal
- Members: Search for the Kore application name
- Click Review + assign
Step 4: Share Information with Kore.ai¶
Contact Kore.ai support and provide the following information:
- Your Tenant ID (found in Microsoft Entra ID > Properties in the Azure portal)
- The Key Vault URI
- The Key Name
Step 5: Configure Network Access¶
- Recommended: Enable a private endpoint for access to the Kore platform.
- Alternatively, allow trusted Microsoft services and Kore IP ranges.
Configure BYOK Encryption in AI for Service¶
You can enable BYOK encryption by configuring it within the AI for Service Admin Console. This process connects your Azure Key Vault to AI for Service. During configuration, you can choose which applications and bots will use it.
Configuration Steps¶
- In the Admin Console, go to Enterprise Key.
-
Enter Azure Details:
- Cloud Provider: Azure.
- Key identifier: Enter your Key Vault URL.
- Authentication credentials: Enter your Role ARN Tenant ID.
-
Set Enforcement Date: Choose when encryption will begin. This is the date your CMK starts encrypting data.
Note
You can modify the CMK and retest until the enforcement date. After this date, you can only rotate the key or update which apps/bots are encrypted.
-
Test Configuration: Click Test Configuration to validate the connection. The system will test the connection to your Azure, authentication, encryption, and decryption operations. Verify all tests pass before continuing.
-
Select Apps and Bots: Click Next to view all applications and bots in your workspace.
Validation (Optional)¶
After the enforcement date, verify that encryption is working by using one of the following methods:
Option 1: View Analytics¶
Check analytics data for recent chat interactions to confirm that encrypted data is accessible.
Option 2: Test Application Authorization¶
Open the application and run Authorization Profiles and Dialogs.
Example:
- Execute BasicAuthValidationDialog.
- When the bot displays the authorization link, click the link and enter the credentials (admin/password).

If successful, the system redirects you and displays "Basic authentication successful."
This confirms your encrypted credentials are correctly stored and retrieved using your CMK.

