Own Azure Resources (OAR)

2026/06/19 • 3 min. to read

In this topic

When to Use OAR
Prerequisites
Provisioning Process
Resources Created
Monitoring Progress
Re-Provisioning
Finding Required Parameters in Azure
Related information

The OAR (Own Azure Resources) plan allows customers to host their own Azure Cosmos DB and Azure OpenAI resources. NAVAX hosts only the Function App for compute; all data remains in the customer's own Azure subscription.

When to Use OAR

Your organization requires data residency in a specific Azure region.
You need full control over your Azure OpenAI quota and costs.
Compliance or security policies require data to stay within your own Azure tenant.

Prerequisites

Before provisioning, the following must be prepared in Azure:

An Azure subscription where resources will be created.
An App Registration (Service Principal) in Microsoft Entra ID with the Contributor role on the target subscription.
A client secret for the Service Principal.

Important

The Service Principal client secret is used only during provisioning and is never stored. It is transmitted securely to the NAVAX backend and discarded after the provisioning job completes.

Important

The Data Processing Agreement (DPA) must be signed before Azure resources can be provisioned.

For more information, see Setup, Data Processing Agreement.

Provisioning Process

The provisioning is fully automated. After filling in the Azure fields on the Knowledge Assistant Setup page and choosing Provision Azure Resources, the following resources are created in your Azure subscription:

Resources Created
Resource	Details
Resource Group	rg-{cosmosAccountName} in the selected region.
Azure Cosmos DB (Serverless)	Account with database and three containers: kb_sources, kb_chunks, kb_feedback.
Azure OpenAI (S0)	Account named oai-{cosmosAccountName}.
Chat model deployment	navax-chat — gpt-4o-mini (GlobalStandard).
Embedding model deployment	navax-embedding — text-embedding-3-small (GlobalStandard).

The provisioning runs asynchronously and typically takes 20–35 minutes. The status is reported back to Business Central via the Check Provision Status action.

Monitoring Progress

After starting provisioning:

The Provision Status field changes to Provisioning.
Use Check Provision Status every few minutes to poll for updates.
When complete, the status changes to Ready and the chatbot switches to your Azure resources automatically.
If something goes wrong, the status changes to Failed and the error is shown in the Provision Error field.

Re-Provisioning

If provisioning fails or resources are missing, you can re-run it by choosing Provision Azure Resources again. Existing resources are reused — only missing ones are created. No data is lost.

Finding Required Parameters in Azure


BC Field	Where to Find It in Azure
Azure Subscription ID	Portal → Subscriptions → Subscription ID column.
Azure AAD Tenant ID	Portal → Microsoft Entra ID → Overview → Tenant ID.
Service Principal Client ID	Portal → Microsoft Entra ID → App registrations → [your app] → Application (client) ID.
Service Principal Secret	Portal → Microsoft Entra ID → App registrations → [your app] → Certificates & secrets → Value (copy immediately after creation).
Azure Region	Use the internal Azure region name, e.g. westeurope, swedencentral, eastus.
Cosmos DB Account Name	Choose a globally unique name (3–44 lowercase letters, digits, hyphens). E.g. mycompany-chatbot.
Database Name	Any valid name. Default: ChatbotDB.