Microsoft Fabric → AgentData → Power BI demo

This walkthrough creates a small but complete customer demo:

Wide World Importers sample → Microsoft Fabric Warehouse → AgentData Semantic
→ governed report → Power BI in the Fabric workspace

Allow 30–45 minutes once for setup. The rehearsed customer walkthrough takes five minutes. AgentData reads the Warehouse through its SQL analytics endpoint; it does not copy the source into another database.

Current publishing boundary

The Microsoft Fabric publish method creates or updates a Power BI semantic model and a report shell in the selected workspace. The model uses Import-mode TMSL; this is not a Direct Lake deployment. AgentData does not yet bind the semantic model's source credentials, and the generated report starts with an empty canvas. Complete the one-time credential/refresh step in Fabric and add visuals there (or use Standalone push when you need a data-filled demo with no model refresh).

What you need

• An organizational Microsoft account with access to Microsoft Fabric.
• A Fabric-capacity workspace. If needed, follow Microsoft's Fabric trial guide.
• Permission to register a Microsoft Entra application, or help from your tenant administrator.
• AgentData admin access at https://agentdata.ui.biskilled.com.
• A running AgentData deployment with ODBC Driver 18 for SQL Server. The hosted deployment already includes it.

Do not paste secrets into screenshots, tickets, chat, or source control.

Values to collect

Keep these values in your password manager while setting up the demo:

Value	Where to find it
TENANT_ID	Microsoft Entra ID → Overview → Tenant ID
CLIENT_ID	App registrations → your app → Application (client) ID
CLIENT_SECRET	App registrations → your app → Certificates & secrets
WORKSPACE_ID	The GUID after /groups/ in the Fabric workspace URL
SQL_ENDPOINT	Warehouse → Settings → SQL endpoint → SQL connection string
WAREHOUSE_NAME	The Fabric Warehouse item name; use it as the database name

The SQL endpoint resembles <unique-id>.datawarehouse.fabric.microsoft.com. Enter only that hostname in AgentData—do not include tcp:, a URL scheme, or the database name.

One-time setup

1. Create the Fabric sample

1. Open Microsoft Fabric, create a workspace, and assign it to Fabric capacity or your trial capacity.
2. Follow Microsoft's Data Warehouse tutorial to create a Warehouse.
3. Complete Ingest data into a Warehouse. The tutorial loads six Wide World Importers sample tables.
4. In Fabric's SQL query editor, run a small SELECT TOP (10) ... query against one of the loaded tables. This confirms that the sample is queryable before AgentData is involved.
5. Open Warehouse → Settings → SQL endpoint, copy the SQL connection string, and record the Warehouse item name. Microsoft's connection guide shows the same location and supported connection methods.

2. Create the service principal

1. In the Microsoft Entra admin center, create an app registration and a client secret.
2. In Fabric → Admin portal → Tenant settings → Developer settings, enable Service principals can call Fabric public APIs for a security group containing the app. See Microsoft's developer tenant settings.
3. Add the service principal to the demo workspace as Contributor.
4. Grant the service principal access to the Warehouse. Workspace Contributor access is the simplest demo setup; use narrower SQL permissions for production.

Use the same identity for the AgentData Fabric source and Power BI publishing in this sample. Production deployments can use separate least-privilege identities.

Connect and discover the sample in AgentData

1. Sign in to AgentData.

2. Open Connectors → Add → Cloud and select Microsoft Fabric.

3. Enter:

   AgentData field	Sample value
   SQL endpoint	<unique-id>.datawarehouse.fabric.microsoft.com
   Port	1433
   Warehouse / lakehouse name	your WAREHOUSE_NAME
   Tenant ID	your TENANT_ID
   Client ID	your CLIENT_ID
   Client secret	your CLIENT_SECRET

4. Select Test connection. Do not continue until it succeeds.

5. Save the connector and run discovery.

6. Open Semantic → Entities. Confirm the Wide World Importers tables/entities you want to use, review their attributes, and create or confirm relationships.

7. Add a simple measure such as total sales, total orders, or total profit using the exact column names discovered from your copy of the sample.

Keep the demo deterministic

Prepare one confirmed entity, one measure, and one dimension before the meeting. For example: Total sales by city. Sample schemas can change, so use AgentData's discovered names instead of assuming a particular table or column spelling.

Create the Power BI publishing connection

1. Open Connectors → Add → Cloud → BI & Reporting → Power BI.

2. Choose the live Azure AD app connection and enter the credentials in the format:

   TENANT_ID:CLIENT_ID:CLIENT_SECRET

3. Test and save the connection. A .pbit/model.bim file import cannot publish; publishing requires this live connection.

Build and publish the report

1. Open Conversation → Reporting → Builder.

2. Create a report named Fabric Sales Demo.

3. Add one KPI and one chart based on the confirmed Fabric entity—for example, Total sales and Sales by city.

4. Run each preview and verify that rows and generated SQL are returned.

5. In Publish live → Power BI, select the live Power BI connection.

6. Choose one publish method:

   Method	Use it when	Required value
   Microsoft Fabric	You want a semantic model plus a bound report in a Fabric workspace	WORKSPACE_ID
   SharePoint	You want a portable PBIP ZIP stored in a document library	Site ID, Drive ID, optional folder
   Standalone push	You want AgentData to execute the report parts and push their result rows to a Power BI push dataset	No Fabric workspace ID

7. For this demo choose Microsoft Fabric, paste WORKSPACE_ID, and publish. AgentData returns a Power BI report URL and creates/updates same-named semantic model and report items.

8. Open the returned URL. If Fabric requests source credentials, configure the Warehouse connection for the semantic model and run a refresh.

9. Add the KPI and chart visuals to the initially empty report canvas, save them, and leave the report open before the customer session.

Publishing the same report name to the same workspace updates the existing items; it does not intentionally create a duplicate on every run.

Five-minute customer script

Time	Show	Say
0:00–0:45	Fabric Warehouse sample tables	“The customer data remains in Microsoft Fabric.”
0:45–1:45	AgentData Microsoft Fabric connector and successful test	“AgentData connects read-only through the SQL analytics endpoint with an Entra service principal.”
1:45–2:45	Semantic → Entities and lineage	“AgentData turns physical tables into reviewed business entities, measures, and relationships.”
2:45–3:45	Report preview and generated SQL	“The report is grounded in that governed model and can be checked before publication.”
3:45–5:00	Publish method selector, then the prepared Power BI report	“The same definition can be pushed as result data, stored as PBIP in SharePoint, or deployed as a Fabric semantic model and report.”

Acceptance checklist

Run this checklist immediately before the demo:

• Fabric trial/capacity is active and the workspace opens.
• The Warehouse query editor returns Wide World Importers rows.
• AgentData Test connection succeeds.
• Discovery shows the expected tables and Semantic → Entities is confirmed.
• The KPI and chart previews return non-empty results.
• The Power BI live connection is selected—not a file import.
• Fabric publish returns a report URL.
• The semantic model refresh succeeds after credentials are configured.
• The saved Power BI report shows its KPI and chart.
• No client secret is visible in browser history, screenshots, or presenter notes.

Troubleshooting

Symptom	Check
Fabric connector cannot load the driver	AgentData must have Microsoft ODBC Driver 18 for SQL Server installed.
Login or token failure	Recheck Tenant ID, Client ID, secret expiry, and URL-encoding of special characters.
Test connects but no tables appear	Confirm the service principal can access the Warehouse and that WAREHOUSE_NAME is the item name, not the endpoint hostname.
Fabric publish returns 403	Enable service principals for Fabric public APIs and add the app to the target workspace as Contributor.
AgentData says a workspace ID is required	Copy the GUID after /groups/ from the workspace URL, not the report ID.
Published report opens but has no data	Configure the semantic model's Warehouse credentials and refresh it.
Published report canvas is blank	This is the current generated shell; add visuals once in Fabric, or use Standalone push for a populated result dataset.

For the broader reporting workflow, see Build & publish reports and Reporting & BI intelligence.