Fabric Capacity Metrics app vs Chargeback app
Hi, using Fabric Capacity Metrics app and Chargeback app I've noticed that they seem to overlap about the exposed data, even if their goal is different: the Capacity Metrics is useful for operational and performance monitoring, while the Chargeback app is useful for attribution/allocation of capacity consumption. I think it's very difficult not to use them together in a Fabric solution: why not have a single app? They should share the same data that feeds the two semantic models. What do you think? Thanks
Unable to activate Microsoft Fabric free trial — Error code 200
Hi everyone, I created a new Microsoft Entra ID tenant and Azure account today. My Power BI 60-day trial is active, but I cannot activate the Microsoft Fabric capacity trial. When I click Start Fabric trial or try to create a Lakehouse, I receive this message: "A Fabric trial isn't available for your account." The activation error says: "Sorry, we are unable to start trial at this time." I have tried both Safari and Chrome, and the issue persists. I also tried submitting a Microsoft support request, but the form failed with "HttpRequestWorker.requestInternal error create ticket 400." I selected Southeast Asia as my region. Has anyone encountered this issue with a newly created tenant? Is there a waiting period before a new tenant becomes eligible for the Fabric trial, or is there another workaround? Thank you!
Fabric 60-day trial unavailable for new Entra ID tenant despite admin settings enabled
Hello Microsoft Fabric Community, I'm preparing for the DP-700 certification exam on November 3, 2026, and I'm unable to activate the Microsoft Fabric 60-day free trial. My environment: Newly created Microsoft Entra ID tenant Organizational account with the Fabric Administrator role Microsoft Fabric Free account Power BI 60-day trial activated successfully Region: East US (shown during trial signup) What I have already verified: "Users can try Microsoft Fabric paid features" is enabled for the entire organization. "Users can create Fabric items" is enabled for the entire organization. The Fabric Administrator role is assigned correctly. Admin portal > Capacity settings > Trial shows no trial capacity. When creating a workspace, the "Fabric Trial" option is disabled. Error message: "Your Power BI trial is active. A Fabric trial isn't available for your account." I created this tenant specifically for Microsoft Fabric training and hands-on practice. My questions: Why is a newly created Entra ID tenant ineligible for the Fabric 60-day trial despite having the correct administrator permissions and tenant settings? Is there a way to request an eligibility review or resolve a trial provisioning issue? Is there an official method to activate the Fabric trial for a new individual learner without purchasing an Azure Fabric capacity? I would appreciate guidance from the Microsoft Fabric team. Thank you!Unable to activate Microsoft Fabric free trial
Hi everyone, I'm preparing for the DP-700 exam and having trouble activating the Microsoft Fabric 60-day free trial. I created a new Entra ID tenant and enabled both "Users can create Fabric items" and "Users can try Microsoft Fabric paid features." My tenant is in Central US, but I keep receiving the message: "A Fabric trial isn't available for your account." I've also confirmed that no trial capacity exists in the admin portal. Has anyone encountered this issue with a new tenant? Is there a way to resolve it? Thanks!
Fabric F8 to F32 resize: provisioningState Succeeded, but memory limit still at F8 level
Hello, We scale a Fabric capacity from F8 to F32 via ARM PATCH before a scheduled Power BI semantic model refresh, triggered through the Power BI REST API from Azure Data Factory. The ARM GET on the capacity confirms the resize immediately: {"sku":{"name":"F32"},"properties":{"state":"Active","provisioningState":"Succeeded"}} However, the semantic model refresh intermittently fails with: Resource Governance: not enough memory [...] consumed memory 802 MB, memory limit 749 MB We added a wait activity of 1 to 5 minutes after the upscale, but the refresh can still fail from time to time. The 749 MB limit matches what we see for F8, not F32. This suggests provisioningState “Succeeded” reflects only the ARM resize, while memory enforcement for the semantic model lags behind. Questions: Is there a supported way to detect when a capacity resize has fully propagated to semantic model memory enforcement, beyond ARM provisioningState? What's the expected max propagation delay, so we can size a safe wait? Is there a better-supported pattern for "scale up before refresh? Thanks!
FabricPipelineWorker.exe crash with SAP connection
Hello all, We are experiencing recurring crashes of FabricPipelineWorker.exe when using Microsoft Fabric Data pipelines to extract data from SAP through the SAP Table Application Server connector and an On-premises Data Gateway. The issue appears to be similar to the one reported in this discussion: https://community.fabric.microsoft.com/discussions/df_pipelines/faulting-application-fabricpipelineworker-exe/5364506 For some reason I cannot reply on mentioned post with message: "This content was not accepted by moderation." However, despite updating the relevant components and changing the gateway configuration, the issue persists. Issue description The interesting part is that Copy activities complete successfully in Microsoft Fabric, and we do not see any errors or failed pipeline executions in Fabric itself. In the On-premises Data Gateway logs, the Copy activities also return: Status: Succeeded However, FabricPipelineWorker.exe appears to crash after the data transfer has completed, potentially during the cleanup phase when existing SAP connections are being closed or disposed of. This is currently our assumption based on the observed behavior, rather than a confirmed root cause. Although the operations complete successfully, these crashes generate a very large number of error logs on the SAP side, creating additional operational overhead and making monitoring more difficult. Environment On-premises Data Gateway: 3000.334.4 Microsoft C++ Runtime 14.x: 14.50.35719.0 SAP .NET Connector (NCo): 3.1.8.0 Troubleshooting performed We have already taken the following steps: Updated the On-premises Data Gateway to version 3000.334.4. Updated the SAP .NET Connector to version 3.1.8.0. Verified the Microsoft C++ Runtime version. Disabled gateway load balancing to rule out potential issues with connections being distributed across gateway nodes. Reviewed the gateway logs and confirmed that Copy activities report successful completion. Unfortunately, none of these changes has resolved the issue. Since the data transfers themselves are successful, this appears to be more related to the gateway worker process lifecycle or SAP connection cleanup than to SAP connectivity or data extraction. Any insights from the Microsoft Fabric engineering team or others experiencing similar behavior would be greatly appreciated. Thank you!
Unable to Activate Microsoft Fabric Free Trial – Error Code 200
Hello Microsoft Fabric Support Team, I recently created a Microsoft Entra tenant and Azure subscription for learning Microsoft Fabric. My Power BI trial is active, but I cannot activate the Microsoft Fabric free trial. When I select Start trial, I receive: “Something went wrong. Sorry, we are unable to start trial at this time.” The error shows status code 200, but no trial capacity appears under Admin portal -> Capacity settings -> Trial. I have checked the relevant tenant settings, and they are enabled. I also attempted to submit a support request through the Fabric Admin Portal, but that submission fails with an HTTP 400 error. Could you please clarify whether my tenant is eligible for a Fabric trial and whether there is a restriction on newly created tenants? Activity ID: d18fd9e6-2f20-4ce8-8cb0-a9ffcd7d115f Request ID: 200c1c8d-bd95-4cb7-af33-0d612005bb99 Correlation ID: 049cbdd1-3eaa-975d-5b66-cbbd040a49c1 Thank you.
getting issue with Project osmos
I was recently testing the project osmos with an f2 capacity got this error after it executed for some 40 mins.I was just testing .Gave this prompt and got the error after execution : """ Create a Project Osmos task for the OSMOS_SupplyChain_Lakehouse. Build an end-to-end supplier performance data engineering solution. Create a small sample supplier order dataset containing supplier, material, ordered quantity, delivered quantity, promised delivery date, actual delivery date, defect rate, shipment mode, supplier rating and supplier remarks. Create a bronze layer that preserves the source data. Create a silver layer that: - standardizes data types - handles invalid or missing values - calculates delivery delay days - calculates delivery performance - validates ordered and delivered quantities - standardizes supplier ratings and defect rates Create a gold table named gold_supplier_performance containing: - supplier - total orders - total ordered quantity - total delivered quantity - average delivery delay - average defect rate - delivery performance - supplier rating - supplier risk category Create Spark notebooks required to implement the solution. Run the transformations in the correct order. Validate: - row counts - null values - duplicate supplier/order keys - data types - delivery calculations - quantity totals - gold table output Do not modify or delete existing user data. Use new tables and artifacts for this demonstration. """ I want to understand that what alternative we can have to use it on a f2 capacity or we need to upgrade to a bigger capacity. ERROR={"code":"CapacityLimitExceeded","subCode":0,"message":"Unable to complete the action because your organization�s Fabric compute capacity has exceeded its limits. Try again later.","timeStamp":"2026-10-09T10:40:07.882692Z","httpStatusCode":429,"hresult":-2147467259,"details":[{"code":"RootActivityId","message":"282fd3a5-6245-426e-b5cd-df7656b0025f"}],"exceptionCategory":1} Failed with exit code 1
