Microsoft Power BI® XMLA

The following page discusses the Microsoft Power BI® XMLA connector for data integration. If you are searching for information on the Power BI® connector to access Foundry resources from the Power Query interface, review our analytics connectivity documentation.

The Microsoft Power BI® XMLA connector is a Palantir-provided driver for Microsoft Power BI® XMLA.

To create a new Microsoft Power BI® XMLA source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Microsoft Power BI® XMLA-specific configuration and networking. For the complete property reference, see the official Microsoft Power BI® XMLA driver documentation ↗.

Configuration

The properties below are mandatory or recommended.

PropertyRequired?DescriptionDefault
AuthSchemeRecommendedThe type of authentication to use when connecting to Microsoft Power BI XMLA.AzureServicePrincipal
AzureTenantRecommendedIdentifies the Microsoft Power BI XMLA tenant being used to access data. Accepts either the tenant's domain name (for example, contoso.onmicrosoft.com ) or its directory (tenant) ID.
InitiateOAuthRecommendedSpecifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working.GETANDREFRESH
OAuthClientIdRecommendedSpecifies the client ID (also known as the consumer key) assigned to your custom OAuth application. This ID is required to identify the application to the OAuth authorization server during authentication.
OAuthClientSecretRecommendedSpecifies the client secret assigned to your custom OAuth application. This confidential value is used to authenticate the application to the OAuth authorization server. (Custom OAuth applications only.)
PowerBIEnvironmentRecommendedSpecifies the PowerBI environment to use for API requests.NONE
WorkspaceRecommendedSpecifies the Premium Power BI workspace(s) to connect to, using a comma-separated list of workspace names.

Networking

The table below lists the domains that the source needs to be able to access in order to successfully run.

For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.

DomainRequired
api.powerbi.comIF AzureEnvironment=GLOBAL(default)
*.pbidedicated.windows.netIF AzureEnvironment=GLOBAL(default); The exact cluster used (added in the *) is determined by calling the api.powerbi.com
login.microsoftonline.comIf AuthScheme=AzureAD (default), AzureServicePrincipal, AzureServicePrincipalCert AND AzureEnvironment=GLOBAL (default)
login.chinacloudapi.cnIf AuthScheme=AzureAD (default), AzureServicePrincipal , AzureServicePrincipalCert AND AzureEnvironment=CHINA
login.microsoftonline.usIf AuthScheme=AzureAD (default), AzureServicePrincipal, AzureServicePrincipalCert AND AzureEnvironment=USGOVT,USGOVTHIGH USGOVTDOD
api.powerbigov.usIF AzureEnvironment=USGOVT
api.high.powerbigov.usIF AzureEnvironment=USGOVTHIGH
api.mil.powerbigov.usIF AzureEnvironment=USGOVTDOD
*.pbidedicated.usgovcloudapi.netIF AzureEnvironment=USGOVT,USGOVTHIGH,USGOVTDOD