Skip to content

Latest commit

 

History

History
39 lines (26 loc) · 2.12 KB

direct-lake-fixed-identity.md

File metadata and controls

39 lines (26 loc) · 2.12 KB
title description author ms.author ms.reviewer ms.service ms.subservice ms.topic ms.date LocalizationGroup
Learn how to specify a fixed identity for a Direct Lake semantic model in Power BI and Microsoft Fabric
Describes how to specify a fixed identity for a Direct Lake semantic model in Power BI and Microsoft Fabric.
kfollis
kfollis
powerbi
powerbi-premium
conceptual
04/24/2024
Admin

Specify a fixed identity for a Direct Lake semantic model

Follow these steps to specify a fixed identity connection for a Direct Lake semantic model.

  1. In your Direct Lake model's settings, expand Gateway and cloud connections. Note that your Direct Lake model has a SQL Server data source pointing to a lakehouse or data warehouse in Fabric.

    :::image type="content" source="media/direct-lake-fixed-identity/direct-lake-settings-fixed-identity.png" alt-text="Screenshot of Direct Lake model settings.":::

  2. In the Maps to listbox, select Create a connection. A New connection pane appears with some data source information already entered for you. Specify a connection name.

  3. In Authentication method, select OAuth 2.0 or Service Principal, and then specify credentials for the fixed identity you want to use.

    :::image type="content" source="media/direct-lake-fixed-identity/direct-lake-settings-fixed-identity-new-connection.png" alt-text="Screenshot of authentication credentials specified in new connection settings.":::

  4. In Single sign-on, ensure SSO via Microsoft Entra ID for DirectQuery queries is not selected.

    :::image type="content" source="media/direct-lake-fixed-identity/direct-lake-settings-fixed-identity-new-connection-single-sign-on.png" alt-text="Screenshot of Single sign-on where option is not selected.":::

  5. Configure any additional parameters if needed and then click Create.

  6. In the Direct Lake model settings, verify the data source is now associated with the non-SSO cloud connection.

Related content