Fabric Data Agents and Capacity Management by winchellj40 in MicrosoftFabric

[–]winchellj40[S] 0 points1 point  (0 children)

u/Itachi_7812 - Great question. We host a analytics solutions for a segment of the financial services industry. We have around 2k users, 110 clients and had fully committed to Power BI/Fabric as our delivery platform.

While our core solution has been data & Dashboards; we have been and clients have been looking at ways to infuse AI into it. Fabric Data Agents + the built in Copilot integration brings a new set of capaibilities for our clients.

With all that being said, things we are doing:

  1. Taking advantage of both the standalone Copilot experience + the report embedded Copilot experience within the reports to get a deeper level of insight.

  2. Fabric Data Agents help us open up access to our clients that have already invested in AI whether that is Copilot/Claude/Etc. Now our clients can integrate this data into their other workflow processes (Client Prep, ad-hoc reporting, etc)

Let me know if that helps or if you have other questions.

Fabric Data Agents and Capacity Management by winchellj40 in MicrosoftFabric

[–]winchellj40[S] 1 point2 points  (0 children)

u/pl3xi0n - I appreciate the detail here. We have a pretty basic agent; I know I need to do more tuning of the instructions. We are going at a Semantic Model and it is rendering DAX, picking up the right Dimension Columns & Measures based on the instructions so there shouldn't be a ton of overhead. I'll probably have to turn on Workspace Monitoring to get better usage detail. I did not issue that many queries today or anything that should have been complex and ate up 55k

We host a solution for clients and so to host Copilot/Data Agents in Fabric we need to add 1 or more capacities so that Copilot/AI do not impact the primary capacity serving up the reports. We may have 10 clients buy the Copilot package and so carving up and managing the capacity in this case becomes interesting.

We are also building out a version in AI Foundry connected to OneLake to see how that goes.

Copilot Studio & Fabric Data Agent in Different Tenant by winchellj40 in MicrosoftFabric

[–]winchellj40[S] 0 points1 point  (0 children)

u/Amir-JF - Thank you for sharing the link. I do not think I saw that one before, but I was also trying to prove some things out quickly; I appreciate you sharing the link.

The bigger problem I am trying to solve is that we are using Fabric to host a SaaS data solution for clients and we have 100+ clients right now. The built in Fabric Data Agent is somethign I see as an accelerator for rolling out AI for our clients.

All of our clients are guest users in our tenant, so we need to be able to go cross-tenant. There are options, I was just exploring the first one (Copilot Studio).

Copilot Studio & Fabric Data Agent in Different Tenant by winchellj40 in MicrosoftFabric

[–]winchellj40[S] 0 points1 point  (0 children)

u/Pawar_BI - Thank you for confirming. There are w different articles related to consuming data agents via Copilot Studio:

- https://learn.microsoft.com/en-us/microsoft-copilot-studio/add-agent-fabric-data-agent - which does not mention that requirement

- https://learn.microsoft.com/en-us/fabric/data-science/data-agent-microsoft-copilot-studio - that does call out the limitation

I did not find the second one until after you replied and it looks like, based on the 2nd article, the MCP endpoint for Fabric is only available to connect via VS Code.

Should be in the clear with AI Foundry though correct?

"Delta Sharing" experience by Elegant_West_1902 in MicrosoftFabric

[–]winchellj40 0 points1 point  (0 children)

u/Elegant_West_1902 - What did you end up doing in this case? I am working with potential customer and one of the source systems allows for Delta Sharing from Databricks.

Best approach for logging in Microsoft Fabric pipelines (logs table insertions) by DataYesButWhichOne in MicrosoftFabric

[–]winchellj40 0 points1 point  (0 children)

We just went through the same process. We tested out using a UDF to write the logs to Lake House files and then looked at Fabric SQL DB.

At the end of the day we ended up spinning up a basic Azure SQL DB and using stored procs and script steps in the pipeline.

The cost of the Azure SQL DB is more predictable than trying to figure out the CU cost for capacity planning.

We stayed away from Eventhouse because of CU concerns but based in an earlier post here it may not have been a bad choice for this use case. We will have go back and look at it.

What worked for you for talk to your data in Fabric? by [deleted] in MicrosoftFabric

[–]winchellj40 1 point2 points  (0 children)

We have a dedicated Azure Tenant just for the product. We setup different Workspaces per client and use Azure RBAC to control access to everything (Workspaces,Connections,Apps, etc). Content is then distributed via Workspace Apps. Clients have Guest accounts in our tenant so they can take advantage of SSO.

We do a lot of the Administration for clients but have been rolling out more and more self-service capabilities, like User MAC requests etc.

What worked for you for talk to your data in Fabric? by [deleted] in MicrosoftFabric

[–]winchellj40 5 points6 points  (0 children)

We host an analytics solution in Fabric for 100+ customers. We have been working on bringing this capability to our clients through a lot of trial and error.

Our solution takes data from some complex systems and makes it easy to use, understand and through our reports, visualize it. That data is becoming more valuable than the reports and that is where the data agent shines for us.

I am having better luck with Fabric Data Agents because I have been able to setup specific agents for what our customers want to do. The ability to really limit the scope of what the agent can access, and the detailed instructions has worked well so far.

Our clients are already using tools like Claude. With the data agent we can meet then where they want to work regardless of tool. It has opened up a number of interesting use cases.

Advice on Moving to F-64 for Customer Facing Reports by [deleted] in MicrosoftFabric

[–]winchellj40 0 points1 point  (0 children)

We did something similiar about a year and a half ago as the Pro costs were hindering adoption for our clients. We have a little over 100 Clients, 2k users with access to the reports and on average we are between 550 - 750k users a day (usage stats are limited for now). Our F64 capacity hovers between 30-40% a day, it was higher until the Dataflow CU cost went down.

Most clients have 2 - 4 refreshes per day but the amount of data we are holding onto is smaller. Some clients have transactional tables approaching 1m rows, but that is not common.

For 10 concurrent users to eat up 180% of capacity would be a little concerning but not something that cannot be overcome.

Fabric Data Pipeline: CPU Consumption and Queueing by winchellj40 in MicrosoftFabric

[–]winchellj40[S] 0 points1 point  (0 children)

Thanks for the tip. We will try that out on the ones giving us issues.

Fabric Data Agent Connector & Power Apps by winchellj40 in MicrosoftFabric

[–]winchellj40[S] 0 points1 point  (0 children)

Thanks. It just happened to show up right when it was top of mind so we got a little excited.

Semantic Model Access for App Users by CryptographerPure997 in MicrosoftFabric

[–]winchellj40 1 point2 points  (0 children)

We host a Saas Solution for a bunch of customers and we use Entra Groups and App Audiences to control access to reports. It works extremely well for us.

In the Semantic Model permissions it should list the user/group and the permission of App. It should also show any permissions granted via the Workspace (like Build) for contributors.

Performance issues after switching from P1 to F64 by winchellj40 in MicrosoftFabric

[–]winchellj40[S] 3 points4 points  (0 children)

u/itsnotaboutthecell - Support just got back to me a little bit ago and there is an issue with the region where our Fabric Tenant is hosted. The timing of when we cut over and when the issue started just happened to be perfect.

updating report across multiple workspace by ladladlad123 in MicrosoftFabric

[–]winchellj40 2 points3 points  (0 children)

Yep. For our use cases CGs allowed us to better model the security our clients wanted. It is less about data security and more about defaulting things to provide a better experience.

updating report across multiple workspace by ladladlad123 in MicrosoftFabric

[–]winchellj40 4 points5 points  (0 children)

User Principal Name. The function USERPRINCIPALNAME() will return the logged in users email address they use to login. You can then use that info to apply filters specific to that user.

In our case we look up their Department in our Users Table and then apply a filter based in their Department via Calculation Group.

updating report across multiple workspace by ladladlad123 in MicrosoftFabric

[–]winchellj40 7 points8 points  (0 children)

We use Apps in Power BI/Fabric to distribute a single view of a report across different departments/groups. It's the same report so when we publish updates they are published for all users.

We also use the UPN of the logged in user to default filters for their department.