Setting Up Your LLM
Last updated: August 23, 2026
| Tier | Deployment |
|
|
Bring your own LLM is the advanced privacy option for Sisense Intelligence. Instead of using the model that Sisense manages for you, you connect your own LLM provider account, so the AI features run on a model you control, in your own cloud and region, under your provider's data terms.
The managed LLM is the simplest way to run these features: Sisense hosts the model for you, so there is no provider account to set up and nothing to maintain, which makes it the best default for most deployments. You reach for bring your own LLM when privacy, compliance, or data-residency requirements mean AI requests should stay inside an environment you own. You supply the provider, the model, and the credentials, and Sisense uses your model to generate queries, charts, and narrative insights. A custom LLM supplements the managed services rather than replacing them.
Sisense supports three providers for this: Azure OpenAI, OpenAI, and AWS Bedrock.
Managed or bring your own?
The managed LLM is the recommended default. It requires a Sisense credit package and needs no provider setup. Bring your own LLM is the advanced privacy option this page covers. For the managed option, see Generative AI (Cloud-Linked Features).
Advanced Privacy and Control
Bringing your own LLM gives you control that the managed option does not:
-
Your data stays in your environment. AI requests go to your own provider account, in the region you choose, so prompts and results are processed under your cloud and your provider's data terms, not a model managed by Sisense.
-
You meet privacy and compliance requirements. When your organization requires that AI processing happen inside infrastructure you own, this is how you satisfy that.
-
You control cost and quota. Usage is billed through your own provider account, so you set the budgets and limits directly.
-
You choose the model. Pick a provider and a model in the tier that fits: a strong model for the best quality, or a lightweight one for lower cost and latency.
The trade-off is setup and billing on your side. If you have no specific requirement to run AI in your own environment, the managed LLM is simpler.
How It Works
Sisense Intelligence --request--> Your LLM provider --response--> Sisense
(Assistant, narrative, (Azure OpenAI, OpenAI, (applies your
semantic enrichment) or AWS Bedrock, in governance, shows
your account & region) the result)
-
You configure your provider once, under Provider Configuration.
-
When an AI feature needs the model, Sisense sends the request to your provider, using the credentials you supplied.
-
Your provider processes the request in your own account and region, and returns the result.
-
Sisense applies your data permissions and governance, then shows the result in the feature.
Because the model runs in your own provider account, your prompts and results are handled under your cloud and your provider's data terms. That is the privacy benefit of bringing your own.
Supported Providers and Models
Sisense recommends models in two tiers. A strong model gives the best answer quality for complex assistant tasks. A lightweight model costs less and responds faster, which suits simpler computations.
The tier you need depends on the feature. The Assistant requires a strong model. Narrative and Semantic Enrichment can run on a lightweight model. If you use the Assistant, configure a strong model. If you only use narrative insights or semantic enrichment, a lightweight model is enough.
OpenAI model deprecations (November 2026)
OpenAI is deprecating GPT-4.1, GPT-4o, GPT-4.1 Mini, and GPT-4o Mini, and will stop supporting them in November 2026. If you use one of these on Azure OpenAI or OpenAI, plan to move off it before then. For the strong tier, Sisense now also supports GPT-5.1.
Recommended Models
|
Tier |
Azure OpenAI / OpenAI |
AWS Bedrock |
|---|---|---|
|
Strong (best quality) |
GPT-5.1 |
Claude Sonnet 4.6 |
|
Lightweight (lower cost and latency) |
GPT-4.1 Mini |
Claude Haiku 4.5 |
Sisense is optimized for the GPT family, hosted on Azure OpenAI or OpenAI. Claude models are available through AWS Bedrock.
All Supported Models
These are the models you can choose in Provider Configuration today. It is your responsibility to manage your model version.
|
Provider |
Model |
Version |
Tier |
Notes |
|---|---|---|---|---|
|
Azure OpenAI / OpenAI |
GPT-4.1 |
gpt-4.1-0414 |
Strong |
Being deprecated by OpenAI in November 2026. Migrate to GPT-5.1. |
|
Azure OpenAI / OpenAI |
GPT-4o |
gpt-4o-1120 |
Strong |
Being deprecated by OpenAI in November 2026. Migrate to GPT-5.1. |
|
Azure OpenAI / OpenAI |
GPT-5.1 |
— |
Strong |
Recommended for the strong tier |
|
Azure OpenAI / OpenAI |
GPT-4.1 Mini |
gpt-4.1-mini-0414 |
Lightweight |
Being deprecated by OpenAI in November 2026. |
|
Azure OpenAI / OpenAI |
GPT-4o Mini |
gpt-4o-mini-0718 |
Lightweight |
Being deprecated by OpenAI in November 2026. |
|
AWS Bedrock |
Claude Sonnet 4.6 |
— |
Strong |
Recommended for the strong tier on Bedrock |
|
AWS Bedrock |
Claude Haiku 4.5 |
— |
Lightweight |
Recommended for the lightweight tier on Bedrock |
Sisense supports Bedrock with these two models only; other Bedrock models are not available through Provider Configuration.
Some models offer extended reasoning and bill those reasoning steps as output tokens, which can raise cost significantly. Review your provider pricing before selecting one.
These models appeared in earlier versions and are no longer offered in Provider Configuration. If you still have one configured, move to a supported model.
|
Provider |
Model |
Version |
Notes |
|---|---|---|---|
|
Azure OpenAI / OpenAI |
GPT-3.5 |
gpt-35-turbo-0125 |
Not supported by the Assistant. Superseded by the GPT-4 family. |
|
AWS Bedrock |
Claude Opus 4.6 |
— |
No longer offered through Bedrock in Provider Configuration. Sisense supports Claude Sonnet 4.6 and Claude Haiku 4.5 on Bedrock. |
Before You Begin
You need all of the following before the setup steps will work:
Note:
-
Cloud-Linked Features enabled on your instance. An administrator enables this under Admin > Sisense Intelligence > Feature Management. The AI features that use the LLM do not appear until this is on. For more information, see Generative AI (Cloud-Linked Features) - Empowering Your Analytics Experience.
-
Access to Sisense Intelligence settings. You configure providers under Admin > Sisense Intelligence > Provider Configuration, which requires administrator access.
-
A provider account with a deployed model. You set up the model in your own provider (Azure OpenAI, OpenAI, or AWS Bedrock) before connecting it here. Each provider section below lists what to prepare.
-
Acceptance of the terms. The first time you open Provider Configuration, click I agree to accept the terms and conditions before you can add a provider.
Set Up a Provider
Under Provider Configuration, the Bring your own LLM section lists your custom providers. The flow is the same for every provider: add a provider, choose its type, and enter the connection details. The fields differ by provider type, so follow the section that matches yours.
-
In Sisense, in the Admin tab, select Sisense Intelligence > Provider Configuration.
-
If this is your first time here, read and accept the terms by clicking I agree to approve the terms and conditions in order to proceed with using the cloud-linked features.
-
Under Bring your own LLM, click + Add Provider.
-
In Provider Type, choose Azure OpenAI, OpenAI, or Amazon Bedrock, and enter the connection details for that provider (see below).
-
Click Save, then verify the connection.
Prepare in Azure first: deploy a supported model in an Azure OpenAI Service resource, in a region that offers that model version. Note the resource's endpoint and an API key.
-
From the Region drop-down, select a region that supports the model version.
-
In the Name field, type an instance name. The instance name will be part of the endpoint name (Base URL).
For more information, see Create and Deploy an Azure resource and Azure OpenAI Service Models.
-
Follow the Azure documentation to deploy a base model on the resource you created. For more information, see Azure OpenAI Service Models.
Once your model is deployed, go to Admin > Sisense Intelligence > Provider Configuration, click + Add Provider, and in Provider Type choose Azure OpenAI. Set the following fields:
|
Field |
What to enter |
|---|---|
|
Provider Type |
Azure OpenAI |
|
Display Name |
A name to identify this provider in Sisense (an alias for the deployment) |
|
Model |
The model your deployment serves (for example, |
|
Deployment Name |
The deployment name you gave the model in Azure |
|
Base URL |
Your Azure OpenAI resource endpoint (the API base URL), for example |
|
API Key |
An API key for the resource, used to authenticate and authorize your requests to the model's API |
Prepare in OpenAI first: create an API key whose permissions allow model access.
-
Create an API key to access the OpenAI API.
-
The Sisense API requires Write access for your Model capabilities. Therefore, when creating/editing your secret key, set the Permissions to either All or Restricted. If you set the permissions to "Read only" your Sisense GenAI features will not work.
Note:
Ensure that the key permissions are set to All (not Restricted/Read only). A read-only key will not work.
If you set the Permissions to "Restricted", you must also set the Permissions for the "Model capabilities" to Write.
-
Save your key.
Then, go to Admin > Sisense Intelligence > Provider Configuration, click + Add Provider, and in Provider Type choose OpenAI. Set the following fields:
|
Field |
What to enter |
|---|---|
|
Provider Type |
OpenAI |
|
Display Name |
A name to identify this provider in Sisense |
|
Model |
A model from your OpenAI account (for example, |
|
API Base |
The OpenAI API base URL |
|
API Key |
Your OpenAI API key, used to authenticate and authorize your requests to the model's API |
|
Organization |
Optional. Your OpenAI organization ID, for billing attribution (if left blank, the default is used) |
Prepare in AWS first: enable access to the model you want in Amazon Bedrock, in a region where it is available, and create credentials (an access key, or a role) that can invoke it.
Then, go to Admin > Sisense Intelligence > Provider Configuration, click + Add Provider, and in Provider Type choose Amazon Bedrock. Set the following fields:
|
Field |
What to enter |
|---|---|
|
Provider Type |
Amazon Bedrock |
|
Display Name |
A name to identify this provider in Sisense |
|
Model |
Select the Bedrock model to use (Claude Sonnet 4.6 or Claude Haiku 4.5) |
|
Region |
The AWS region your model runs in (for example, |
|
Access Key ID |
The AWS access key ID for the credentials that can invoke the model |
|
Secret Access Key |
The matching AWS secret access key |
Note:
Sisense supports Claude Sonnet 4.6 (strong tier) and Claude Haiku 4.5 (lightweight tier) on Bedrock. Some models offer extended reasoning and bill those reasoning steps as output tokens, which can raise cost significantly. Review your AWS pricing before selecting one.
Verify the Connection
After you save a provider, Sisense checks the connection. In the Bring your own LLM list, a green dot next to the provider means the model connected properly with the key you entered. If the dot does not appear, open the provider again and check the model, the base URL, and the API key.
You can also confirm it end to end:
-
Open an AI feature that uses the LLM, such as the assistant.
-
Ask a simple natural-language question against a model you have access to.
-
A successful query or chart response means the provider is working. If the request fails, check the credentials, the model name, and that the model is reachable from your account.
Cost and Quota
You are billed by your provider for every request Sisense sends to your model, under your own account and pricing. Sisense does not add a charge for bring-your-own usage. Set usage limits or budgets in your provider console if you want to cap spend, and be aware that reasoning-capable models can use far more output tokens than standard models.
Limitations
-
You can add only one custom LLM at a time. Support for configuring multiple models together (a strong model and a lightweight one) is on the roadmap.
-
Bring your own LLM supports Azure OpenAI, OpenAI, and AWS Bedrock only. Other providers are not available through this configuration.
-
The assistant requires a strong model. Lightweight models suit narrative insights and semantic enrichment.
-
On AWS Bedrock, Sisense supports only Claude Sonnet 4.6 (strong) and Claude Haiku 4.5 (lightweight). Other Bedrock models, including Claude Opus 4.6, are not available through Provider Configuration.
-
OpenAI is deprecating GPT-4.1, GPT-4o, GPT-4.1 Mini, and GPT-4o Mini, and will stop supporting them in November 2026. Move to GPT-5.1 for the strong tier on Azure OpenAI or OpenAI before then.
-
Availability of a given model depends on your provider account and region, not on Sisense.
Frequently Asked Questions
Use the managed LLM unless you have a specific privacy, compliance, or data-residency requirement to keep AI processing in your own environment. The managed LLM requires a Sisense credit package and has nothing for you to configure. Bring your own LLM is the advanced privacy option: it runs AI requests through your own provider account, region, and keys, at the cost of setup and provider billing on your side.
Pick a tier first. For the strong tier, use GPT-5.1 on Azure OpenAI or OpenAI, or Claude Sonnet 4.6 on AWS Bedrock. For the lightweight tier, use GPT-4.1 Mini on Azure OpenAI or OpenAI, or Claude Haiku 4.5 on AWS Bedrock. Note that GPT-4.1, GPT-4o, GPT-4.1 Mini, and GPT-4o Mini are being deprecated by OpenAI in November 2026. See the recommended models table above.
Claude is available through AWS Bedrock, not as a direct Anthropic provider. Set up Bedrock and select a Claude model.
In the Bring your own LLM list, a green dot next to the provider means the model connected properly. If it does not appear, re-check the model, the base URL, and the API key.
Yes. The LLM only powers AI features once Cloud-Linked Features is enabled under Admin > Sisense Intelligence > Feature Management.