Connect Microsoft Fabric to Odie so your customer data can become part of the Odie Customer Knowledge Graph. This connection authorizes Odie to access your Fabric database. It does not begin importing data.

After you authenticate, our Activation team will guide the ingestion setup. Together, you will decide which data to bring in, how it maps to Odie, and how often it should refresh.

Prepare your Microsoft Fabric credentials

Work with your Microsoft administrator to prepare a dedicated application for this connection.

1. Create or select an application registration in the Microsoft Entra admin center.
2. From the application’s Overview page, copy the Directory (tenant) ID and Application (client) ID.
3. Open Certificates & secrets and create a client secret.
4. Copy the secret’s Value and record its expiration date. Microsoft displays the value only when you create the secret.

For more information, see Microsoft’s application setup guidance.

Grant access to your Fabric data

Your Fabric administrator must give the application permission to connect and read the data you plan to bring into Odie.

1. In Fabric tenant settings, confirm that Service principals can use Fabric APIs is enabled for the application.
2. Grant the service principal Read permission on the selected Warehouse or Lakehouse SQL analytics endpoint. This item permission allows it to connect.
3. Grant SQL SELECT permission on each table or view Odie should read. Item Read permission alone does not grant permission to query those tables or views.

For least privilege, use item Read access together with SELECT permission on the intended tables or views. Workspace Contributor or Admin access is not required just to read data.

See Microsoft’s guidance for Fabric authentication and service principal permissions.

Gather your connection details

Have these values ready before you start:

• SQL Endpoint Server: The server hostname from your Fabric SQL connection string.
• Database: The database name for the Warehouse or SQL analytics endpoint you want to connect.
• Tenant ID: The Directory (tenant) ID for your application.
• Client ID: The Application (client) ID for your application.
• Client Secret: The current client secret value for your application.

Use the SQL endpoint hostname, rather than a Fabric browser URL or a complete connection string. See Microsoft’s Fabric connectivity guidance.

Connect Microsoft Fabric

In Odie, open Settings > Integrations, add a connection, and select Microsoft Fabric.

1. Enter your database details. In the Connect Microsoft Fabric dialog, enter:

   • SQL Endpoint Server: The server hostname from your Fabric SQL connection string.
   • Database: The database Odie should connect to.

   Select Connect Microsoft Fabric to open the secure setup window.

2. Enter your application credentials. In the Link Microsoft Fabric Account window, enter:

   • Tenant ID: Your application’s Directory (tenant) ID.
   • Client ID: Your application’s Application (client) ID.
   • Client Secret: Your application’s client secret value, not the secret ID.

   Scroll down and select Connect to complete authentication.

Complete the ingestion setup

Our Activation team will work with you to:

• Choose the tables and views Odie should use.
• Map your source data to Odie objects and properties.
• Confirm the keys and relationships that connect your customer data.
• Set the refresh schedule.
• Validate the data before ongoing ingestion begins.

FAQs

Can I use my personal Microsoft password?

This connection uses an application’s tenant ID, client ID, and client secret. Have your Microsoft administrator prepare those credentials.

Does authentication start importing data?

No. Source mappings and ingestion must be configured separately.

What should I check if the connection fails?

Confirm the tenant ID, client ID, secret value, SQL endpoint server, and database. Ask your Fabric administrator to verify item Read permission and SQL SELECT permission on the intended tables or views.

Odie must also be able to reach the Fabric SQL endpoint over TCP port 1433. If your organization uses private endpoints or restricted networks, coordinate connectivity with your Activation team. A successful connection from your laptop does not confirm that Odie can reach the endpoint. See Microsoft’s Fabric connectivity guidance.

What happens when the client secret expires?

The expired secret can no longer authenticate the application. Before it expires, create a replacement secret and contact your Activation team to update and reauthenticate the existing Odie connection. Keep the old secret active until the team verifies that the replacement credentials work and that Odie can connect to the database and read the selected tables. Revoke the old secret only after that verification.