Deploy a GPT model in your Azure account to power AI question-answering.
Azure OpenAI is Microsoft's hosted version of OpenAI's GPT models (GPT-4o, GPT-4o-mini, etc.). Chordalia products send relevant document excerpts plus your question to Azure OpenAI, which returns a written answer with citations.
Crucially, the traffic goes to your own Azure account, not a shared Chordalia endpoint. Your documents and queries never touch our servers, and Microsoft's enterprise privacy terms apply to the content.
Azure OpenAI charges per token (~750 words of input or output). For a typical Chordalia user asking a few questions a day:
In the past, Azure OpenAI was gated behind an application form. Microsoft has removed that requirement for most accounts — you can now create the resource directly. But if you're using a brand-new subscription, an Enterprise Agreement, or an account in certain regions, you may still hit a one-time access-request form.
If prompted, fill in the form honestly (intended use: "private document search and Q&A with my own data"). Approvals are usually granted within a day.
In the Azure portal, use the search bar at the top and type Azure OpenAI. Click the result.
chordalia-rg).chordalia-openai).chordalia-openai-project). This is the
AI Foundry project the resource gets linked to.
Provisioning takes a minute or two. When it's done, the portal shows a Go to resource button — click it.
Creating the Azure OpenAI resource is only half the work. The resource is a container; the actual models (GPT-4o, GPT-4o-mini, etc.) have to be explicitly deployed inside it before you can use them.
From the resource overview page, click Go to Foundry portal (also called Azure AI Studio). This opens a new tab.
gpt-4o-mini or chordalia-gpt.
my-gpt
but try to use gpt-4o-mini in Arion's settings, you'll
get a "deployment not found" error. Copy your deployment name
exactly when you configure the product.
Back in the Azure portal, open your Azure OpenAI resource. In the left sidebar, click Keys and Endpoint.
You'll see three things you need to copy:
https://keirnifia-eastus2.cognitiveservices.azure.com/Open Settings → Azure (Tier 2). Scroll to the Azure OpenAI group box (lower half of the tab) — not the Azure AI Search group above it, which is for a different service. Paste:
Also set Arion's tier to Tier 2 on the Search Tier tab.
Edit chordium.yml or use the admin UI:
azure.openai.endpointazure.openai.api_keyazure.openai.deploymentOpen Settings → AI, pick Azure OpenAI as the provider, and paste the three values above.
You're referring to a deployment name that doesn't match anything deployed in the resource. Open Azure AI Foundry → Deployments and copy the exact name shown there — it's case-sensitive.
The API key is wrong, expired, or was regenerated. Go back to Keys and Endpoint, copy KEY 1 freshly (the eye icon shows it, the copy icon puts it on your clipboard), and paste it into the product settings again.
Not every Azure region offers every model. GPT-4o variants are usually available in East US, East US 2, and Sweden Central; newer or preview models may be in only one region at a time. Either pick a different model, or create a new Azure OpenAI resource in a region that offers what you want.
Common on free-trial subscriptions: the model you picked has 0 TPM allocated to your subscription in that region, so the deployment slider is stuck at zero and the Deploy button is disabled.
To diagnose and resolve, in priority order:
The model hit its output-token limit. Chordalia products set sensible defaults (~1000 tokens), enough for a page or two of prose. If you need longer answers, raise the limit in the product's settings (Arion: Settings → AI Prompt → tuning options, when available).
Most "surprise" Azure OpenAI bills come from applications left running in a loop by mistake. In the Azure portal, go to Cost Management + Billing → Cost analysis to see which resource is spending the most, and set a Budget with an email alert at 80% of your monthly cap.
Open the resource in the portal, click Delete at
the top. To remove everything at once (OpenAI resource, deployments,
logs), delete the whole resource group instead — that's why
we used a dedicated chordalia-rg.