AI Models

AI Models are the language, vision, and OCR models that Agent steps and other model-driven steps run on. Studio ships with global models that are available to every tenant, and Tenant Admins can add their own tenant models when they need a specific deployment, provider, or set of credentials.

Where to Find AI Models

Open AI Models from the Agents group in the left navigation. The page is visible to Tenant Admins. It lists the models available to the tenant — both global models (read-only) and any tenant models you have added — and a form for configuring the selected model.

Global vs Tenant Models

• Global models are provided centrally and can be selected in steps as-is. You cannot edit or delete them.
• Tenant models are ones you add for your tenant. Use these when you want to point at your own deployment, use your own API credentials, or expose a model that is not available globally.

Model Types

Each model has a type that determines where it can be used:

• LLM — large language models for text reasoning and generation in Agent steps.
• VLM — vision language models that can also interpret images.
• OCR — optical character recognition for reading text from documents and images.

Adding a Tenant Model

1. Go to AI Models and select New.
2. Fill in the model details:
   • Model Key — a unique identifier (lowercase letters, numbers, and dashes). It cannot be changed after the model is created.
   • Name — the display name shown when selecting a model in a step.
   • Model Type — LLM, VLM, or OCR.
   • Notes — an optional description.
3. Fill in the deployment details:
   • Deployment Type — the provider or service, such as Azure OpenAI, OpenAI, Azure Document Intelligence, Azure Content Understanding, Ollama, or Datalab.
   • Provider Model Name — the model identifier at the provider, for example gpt-4o.
   • Deployment Name — the provider's deployment identifier (used by providers such as Azure OpenAI).
   • Endpoint — the service endpoint URL.
   • Access Key — the API key or credential. Leave empty when the deployment authenticates with a managed identity.
   • API Version — the provider API version where one is required.
   • Configuration — optional additional settings.
4. Select Test connection to verify Studio can reach the deployment.
5. Select Save.

You can reference Variables and Secrets in credential fields rather than pasting raw values — for example {{SECRET.OPENAI_API_KEY}}.

How Steps Use Models

Agent steps and other model-driven steps select a model from the list of models available to the tenant. When you promote an Action between environments, the model it referenced in the source tenant may not exist by the same name in the target tenant; the import wizard lets you map it to a model that does. See Promoting from UAT to Production.

Things to Know

• Model exports do not include access keys. After importing models into another tenant, re-enter their credentials.
• Deleting a tenant model affects any step that selects it, so check usage before removing one.
• Use Test connection after changing endpoints or credentials to confirm the deployment is reachable before a real run depends on it.

Related Pages

• Agent Steps — selecting and using models in steps.
• Variables and Secrets — storing model credentials safely.
• Credits — how model usage is charged.

---