> ## Documentation Index
> Fetch the complete documentation index at: https://cubed3-docs-dashboard-link-target-honored.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# NTLM authentication

> NTLM is an authentication method developed by Microsoft that can be used to authenticate requests to the DAX API and MDX API.

[NTLM][link-ntlm] is an authentication method developed by Microsoft that can be used to
authenticate requests to the [DAX API][ref-dax-api] and [MDX API][ref-mdx-api].

<Note>
  Available on [Enterprise plan](https://cube.dev/pricing).
</Note>

On the diagram below, NTLM is used to authenticate requests from Power BI Service that
come through the [on-premises data gateway][link-power-bi-opdg] (step 6):

![](https://ucarecdn.com/a1928cd7-51b5-4d0c-b6b3-7f97eb94b41e/)

## Authentication flow

The NTLM authentication can be used with Power BI Desktop or with Power BI Service and
the [on-premises data gateway][link-power-bi-opdg].

### Power BI Desktop

Initiated by Power BI Desktop, NTLM authentication works as follows:

* Power BI Desktop is launched under a specific user account via the `runas` command.
* Power BI Desktop performs an NTLM challenge-response authentication and passes the
  credentials of that account to the Cube Cloud deployment.
* The Cube Cloud deployment [verifies the credentials](#verifying-the-credentials).

In the following example, Power BI Desktop is launched under the `cube` user:

```bash theme={null}
# Run Power BI Desktop as the `cube` user
runas /netonly /user:cube "C:\Program Files\Microsoft Power BI Desktop\bin\PBIDesktop.exe"

# Run a specific report in Power BI Desktop as the `cube` user 
runas /netonly /user:cube "C:\Program Files\Microsoft Power BI Desktop\bin\PBIDesktop.exe \"C:\Users\Administrator\Desktop\Dashboard.pbix\""
```

**This flow should only be used for testing purposes.** Note that, when Power BI Desktop
is started as a user different from the currently logged-in Windows account, it may
encounter permission issues, e.g., when saving files on network drives.

In a production environment, Power BI Desktop should be used with [Kerberos
authentication][ref-kerberos].

### Power BI Service

Initiated by Power BI Service, NTLM authentication works as follows:

* [The gateway is configured](#installing-the-gateway) with a master user account.
* When users interact with a Power BI report in Power BI Service, their *user principal
  name* (UPN) is passed to the gateway.
* The gateway performs an NTLM challenge-response authentication and passes the the
  credentials of the master user account to the Cube Cloud deployment. It also passes the
  UPN of the interacting user.
* The Cube Cloud deployment [verifies the credentials](#verifying-the-credentials) and
  changes the user name to the UPN of the interacting user.

**This is the recommended way to authenticate Power BI Service requests.**

## Configuration

Using NTLM authentication requires configuring the deployment to [verify the
credentials](#verifying-the-credentials).

To use NTLM authentication with Power BI Service, you also need to [install the on-premises
data gateway](#installing-the-gateway) first.

### Installing the gateway

You need to have the [on-premises data gateway][link-power-bi-opdg] installed
on a Windows Server machine.

It should be configured to authenticate with a *master user* account. It can be a
local user on the machine or a domain user. Its credentials must match the [XMLA
service account](#verifying-the-credentials) configured in Cube — the user name must
match exactly, including the format and letter case (e.g., `svc-account@example.com`).

The Windows machine running the gateway should be joined to the corporate Active
Directory or Entra ID where your business users have their accounts. The service account running
the gateway needs minimal permissions but must exist in that same directory.

### Verifying the credentials

NTLM connections are verified against the **XMLA service account** credentials set on
the **Settings → Power BI** page of your deployment. They are stored in the
`CUBE_XMLA_API_USER` and `CUBE_XMLA_API_PASSWORD` environment variables and default to
the deployment’s SQL API credentials.

All NTLM connections are validated against this single shared password — per-user
passwords are not supported with NTLM. Users other than the service account must exist
as Cube users. A mismatch fails with
`Authentication failed due to invalid username or password`.

Cube changes the session user to the UPN of the interacting user only if the connection
authenticated as the XMLA service account. The UPN must resolve to a Cube user — see
[provisioning users with SCIM][ref-kerberos-scim]. The [`can_switch_sql_user`
configuration option][ref-config-can-switch-sql-user] can be used to customize this
check.

[link-ntlm]: https://en.wikipedia.org/wiki/NTLM

[ref-dax-api]: /reference/core-data-apis/dax-api

[ref-mdx-api]: /reference/core-data-apis/mdx-api

[link-power-bi-opdg]: https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem

[ref-kerberos]: /docs/integrations/power-bi/kerberos

[ref-kerberos-scim]: /docs/integrations/power-bi/kerberos#provisioning-users-with-scim

[ref-config-can-switch-sql-user]: /reference/configuration/config#can_switch_sql_user