Unable to provision Microsoft Fabric free trial on new Entra tenant
I created an Azure free account, created a Microsoft Entra ID user, and signed in to Microsoft Fabric using that Entra user. My Power BI trial is active, but Fabric trial activation fails from both the profile menu and when I try to create a Lakehouse. Error: Sorry, we are unable to start trial at this time. Activity ID: f9dbb4c3-cd07-4523-b98c-70de6a3425d7 Request ID: baafbc5f-f1e4-4f3a-91fd-ec69a8324d67 Correlation ID: f5ed1d5d-32f9-6c97-bb26-78f2b88535a2 Time: Tue Aug 25 2026 13:37:57 GMT+0530 Cluster: India Central Could anyone confirm whether Fabric trials are blocked for newly created Entra tenants, and whether there is an eligibility path or waiting period for activation?
Has anyone seen deleted Fabric Plans continue consuming capacity?
Hi all, I'm hoping someone else has run into this because I'm struggling to figure out whether this is expected behaviour or a bug in the Planning Preview workload. We recently created a Plan in Fabric Planning (Preview) to test the feature and later deleted it. The Plan is definitely gone from the workspace, but more than 24 hours later it still appears to be consuming capacity. When I look in the Capacity Metrics app, I can see three "Planner Session" entries under Background Operations. What's odd is that: None of them have a Start or End time. The User column contains GUIDs rather than actual user accounts. Each one is showing 86,400 seconds duration and around 100k CU consumption. If I pause and resume the capacity, the sessions come straight back. The other thing that's concerning is that the Planning workload's cumulative percentage keeps growing. At the moment it's sitting at around 3,694%, which is making up the majority of the cumulative utilization on our F4 capacity. A few questions for anyone who has been testing Planning: Is this normal behaviour for the 30-day Planning session model? Do Planner Sessions continue to exist after a Plan has been deleted? Has anyone seen these GUID-based sessions before? Is there any way to force the sessions to terminate or clean themselves up? Has Microsoft acknowledged this as a known issue in Preview? At first I thought this might just be a delay in cleanup, but it's now been over a week and the sessions are still there. The lack of Start/End times and the fact that they survive a capacity pause/resume makes me think something may be stuck in the backend. Would be interested to hear if anyone else has seen similar behaviour or if someone from the Fabric team can shed some light on it. Thanks!
Fabric Trial F64 stuck in Overloaded / AllRejected
I’m using a Microsoft Fabric Trial capacity (F64 / 64 CU) for learning and testing. Since August 18, 2026, I have been unable to access my Fabric Lakehouse and Warehouse because of CapacityLimitExceeded. I have disabled all scheduled workloads. Capacity Metrics shows: Most recent System Event: 2026-08-20 09:55:40 — Overloaded — AllRejected There has been no subsequent Active / NotOverloaded event. No significant CU spike occurred around 09:55 on August 20. No Interactive Rejection from August 20 until now. No Background Rejection from August 20 until now. Current CU utilization has been near 0% for several hours. The issue is also affecting OneLake directly. OneLake File Explorer cannot synchronize either my Lakehouse or Warehouse. On August 22, 2026 at 15:26:22, OneLake File Explorer returned: RejectedDueToResourceConstraints and HTTP: 503 ServiceUnavailable Request IDs: 114200cd-59b1-4079-b2a6-f69ce9a55a9f 6988d4b8-4d70-4544-9285-db202f02fcc0 RAID IDs: 1d2a06ba-026f-40ca-aa6c-95b2defd7f77 ab3c3d45-de6b-47d1-8716-6586002d0be0 The OneLake diagnostic log specifically says: Unable to complete the action because your organization’s Fabric compute capacity has exceeded its limits. Try again later. (RejectedDueToResourceConstraints) Could someone from Microsoft/Fabric support investigate whether this Fabric Trial capacity is stuck in an AllRejected / RejectedDueToResourceConstraints state? The Capacity Metrics data does not show current CU consumption or ongoing interactive/background rejection that explains the continued rejection. This is preventing access to my Lakehouse and Warehouse data. Please see attachments: Thanks.
Guest user is workspace admin, but cannot see Microsoft Fabric workspace
Hello, I'm facing an issue with Microsoft Fabric guest access. Environment Tenant, Data Analysis, my own tenant. Capacity is Fabric Trial, FTL64, Region is Central India. What I did. Created the trial and a workspace called WS Vedant Kharwade Personal. Invited my Raybiztech account as an Entra guest. The invite was accepted. Assigned that guest as admin on the workspace. Verified in the admin portal that the workspace is active and on the FTL64 trial. Problem. When signed in as that guest and switched to the data analysis tenant, no workspaces appear, only the 'Welcome to Fabric' page.
Unable to invoke UDFs when Power BI report is embedded in SharePoint
Hello, I have built a Power BI report which triggers a Fabric user data function via click of a button. The report works fine when published to the service (viewed in the report or via an app), but when the app is embedded within a SharePoint site, the UDF fails to trigger and I receive the attached 401 error. Can you please confirm whether Power BI reports embedded within SharePoint support UDFs and if not please confirm when this will be available?Fabric Dataflow Gen2 – MetadataEvaluationGatewayTimeout
Hi everyone, We have a Fabric Dataflow Gen2 that is consistently failing with the following error: MetadataEvaluationGatewayTimeout We have already checked the following: On-premises Data Gateway is Online Gateway Windows service is Running Gateway VM is healthy Manual refresh was attempted, but it failed again with the same error Since the gateway and VM appear to be working normally, we would like to understand what could be causing the metadata evaluation timeout and what would be the recommended permanent fix. Has anyone faced this issue before? Could this be related to the source metadata evaluation, gateway processing, or Fabric service-side processing? Any guidance or troubleshooting steps would be appreciated. Thank you!
Datagateway stuck at "Failed to sign in. Please Verify your credentials and try again."
Im droping this here as i didnt see anywhere where this had been addressed. When trying to signin to the data gateway the app freezes and says "Failed to sign in. Please Verify your credentials and try again." The credentials are good and everything was fine prior to update. I got this after updateing the datagateway. The app freezes up and you have to force close. The work around is that you click signin options prior to entering email select these options and it will redirect you to your browser to login and wont lock up hope this someone
Fabric Apps + semantic models: Build permission required just to view a report?
Hi team, We've started building POCs of our existing workspace Power BI apps as the new Fabric Apps, to support requirements our current apps can't — mainly data annotation and "soft" writeback. Our semantic models are solid, so we've built the Fabric App on top of our existing semantic models (RLS and all), with a sidecar SQL database as the annotation/writeback vehicle. Currently, our semantic models sit on F64-backed workspaces, meaning our users don't need a per-user license (Pro/PPU). But it seems Fabric Apps work differently: the app appears to execute queries on behalf of the signed-in user via the XMLA endpoint, which requires Build permission on the semantic model — and Build in turn requires an end-user license (Pro/PPU). Am I missing something obvious, or is this simply how Fabric Apps are meant to work? There seem to be two existing paths for this exact problem: Fabric data agents let consumers query a semantic model with Read-only access, no Build required: https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/update-to-required-permissions-for-semantic-models-in-fabric-data-agents/5172274 For multi-user applications on Premium/Fabric capacity, you already document that an app can use a service account or app identity to query on behalf of end users, without each one signing in individually (see "Multi-user application"): https://learn.microsoft.com/en-us/fabric/enterprise/powerbi/service-premium-connect-tools If either of those is viable, why does a Fabric App need each signed-in user to hold Build (and therefore a paid license) just to view a report? As it stands, requiring an end-user license for 1,000+ internal users who might open a report once a quarter is a hard sell. Thanks!Design pattern for an architecture for +20 offices
hey everyone, quick question I want to know what the options are for scaling up an infrastructure on MS Fabric to +20 countires in one region. should each country have their own workspace and then we deploy the same architecture across those +20 workspaces, or we have a single regional workspace to host all of them (i assume it's be messy at some point)?? considering security and governance, as the data of each country can be sensitive to some extent I would like to learn from any best practices out there Appreciated
