Fabric App availability in UK South
The Fabric region availability link says UK South now has Fabric Apps (it's not listed in the `Unavailable Fabric features` column). However, when I go to my UK South Fabric capacity, where quite a while ago I set "Enable Fabric App Items (preview)" to be "Enabled for the entire organization", Fabric Apps still don't appear in my UK South workspace when I want to add a New Item. Any idea why it's not appeared yet? https://learn.microsoft.com/en-us/fabric/admin/region-availability
Fabric Data Agent visualization through MCP
I'm testing the new Fabric Data Agent visualization capability in the September 2026 update. In the native Fabric Data Agent experience, a question can return an interactive chart successfully. I'm consuming the same published Data Agent through its MCP endpoint from an external Next.js application. The MCP response gives me the answer/data, but I don't see the visualization specification needed for the external client to reproduce the chart. What is the supported way for an external MCP client to retrieve the visualization specification generated by the Data Agent and is this specification currently exposed through the MCP response/assistant run steps, or is visualization rendering currently limited to the native Data Agent experience?
DP-600 Voucher
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Hi everyone, I recently passed the DP-700 Microsoft Fabric Data Engineer Associate certification and am now planning to take DP-600 (Microsoft Certified: Fabric Analytics Engineer Associate) while the Fabric concepts are still fresh in my mind. Unfortunately, I wasn't able to use a previous DP-600 voucher when I first received it as I wasn't ready for the exam at the time. I was wondering if anyone is aware of any current voucher opportunities for DP-600, or has an unused voucher that they won't be using and is transferable (if permitted by the voucher terms). Any guidance would be greatly appreciated. Thanks in advance! Regards, Amanul
SPN gets 401 'not authenticated' on all Fabric REST APIs despite correct tenant setting & group
Setting up service principal auth for Fabric Data Agent MCP, following the official docs. Getting 401 even on the most basic APIs, before touching the Data Agent itself. Confirmed correct: Token acquired fine via ClientSecretCredential, scope https://api.fabric.microsoft.com/.default JWT decoded — aud, appid, tid, idtyp: app all correct Tenant setting "Service principals can call Fabric public APIs" enabled + SPN in scoped security group SPN has Contributor on workspace + Read on the semantic model Error (same on /v1/workspaces and /v1/capacities, not workspace-specific): HTTP 401 {"errorCode":"Unauthorized","message":"The caller is not authenticated to access this resource"} Request ID: d8cb8a65-6276-4629-a966-37a059198c3f What should I actually try next to fix this , is there a specific setting/step I'm missing? Thanks in advance!
Planning sheets show "No rows to display" with model measures since 30 Sep update
Since 30 Sep update, Fabric Planning sheets go blank with any model measure. Column sums still work. Symptoms All saved Planning sheets open as "No rows to display". Sync reports "Successfully fetched data and catalog details", but the grid stays empty. When I add any explicit semantic model measure to Values, the grid freezes: no value column appears and later changes aren't reflected. After saving and reopening, the sheet shows "No rows to display". Implicit column aggregations work, both "Sum of <column>" and data inputs. A sheet built only from these saves, reloads and writes back normally. It reproduces in a brand-new Plan item connected to the same model, with a long-standing measure (a simple Budget measure). What we've ruled out The model: An XMLA trace shows the Plan's grid query (SUMMARIZECOLUMNS with the measures and their [_<measure> FormatString] references) succeeding with no errors. Re-running the exact query returns the expected rows (79 rows in one case). Reports on the same model render normally. Connections: The App Database connection works. The Direct Lake sources are mapped to fixed-credential OAuth connections, not SSO. Model changes: measures and calculation groups are unchanged, and format strings are normal. Filters: none Environment Semantic model in Direct Lake mode on OneLake, plus calculated tables. Planning writeback to a Fabric SQL database. Australia East region. Questions Is anyone else seeing Planning sheets fail to display semantic model measures since this update? Is this a known issue, and is a fix or rollback planned?
Unable to activate Fabric trial. Is my tenant too new?
I attempted to start a Fabric free trial today following this article from Microsoft. I ended up getting an error telling me: Your free Power BI trial gives you 60-day access to Power BI paid features. A Fabric trial isn't available for your account. See the Microsoft documentation for eligibility requirements. I am new to Azure, Entra ID, and Fabric, so apologies if I don't use the terminology correctly. After doing some searching on these forums, it seems like the most likely cause is that my tenant is not 90 days old. My Azure account shows two users when I view the Entra ID section. The one I created today to try and get access to Fabric, and a default user that must have been created automatically when I was following the DP-900 labs. The default user is 72 days old. The clarification I would like: Is my assessment of the likely cause of my issue correct? How long will I have to wait to have access to Fabric, 89 days (based on the newly created user) or 18 days (based on the tenant) Is there any way around this restriction (especially if I have to wait 89 days) for someone preparing for the DP-600 certification? Should I cancel the activated Power BI trial in the meantime? I just finished reading through the DP-600 learning path yesterday and was hoping to start getting through the labs today. Hoping this doesn't set me behind too long. I have been studying with the intention of having a career pivot soon. Thanks in advance.Cannot log ticket on Since 30 Sep update, Fabric Planning sheets go blank with any model measure.
Cannot log ticket on Since 30 Sep update, Fabric Planning sheets go blank with any model measure. Column sums still work. Planning sheets blank ("No rows to display") when using semantic model measures. Started after the 30 Sept service update.Microsoft Fabric Materialized Lake Views (MLVs) – Looking for Confirmation on a Few Points
Microsoft Fabric Materialized Lake Views (MLVs) – Looking for Confirmation on a Few Points Hi everyone, I'm currently working with Materialized Lake Views (MLVs) in Microsoft Fabric and trying to establish the right approach for implementing them in a proper Dev → UAT → Production setup. I have gone through the available documentation, but I would appreciate confirmation from people who are already using MLVs in real projects. MLV Refresh Failure and Monitoring My current understanding is that if an MLV fails during its initial execution or during a scheduled refresh: The MLV run will be marked as Failed. The failure can be investigated through the MLV run history/monitoring experience. The error code, error message and execution details can be used for troubleshooting. If an upstream MLV fails, dependent MLVs may be skipped. Questions: Is there a recommended/native way to send an email or Teams notification whenever an MLV refresh fails? What is the recommended production monitoring approach for MLV refresh failures? Is anything else required in addition to configuring the MLV schedule? ON MISMATCH FAIL vs ON MISMATCH DROP My current understanding is that ON MISMATCH is related to handling schema/structure mismatches encountered during MLV processing, rather than being a general data-quality validation mechanism. For example: ON MISMATCH FAIL would cause the MLV operation to fail when the applicable mismatch occurs, whereas: ON MISMATCH DROP would allow processing to continue while dropping the affected/incompatible data. Questions: Is this understanding correct? What exactly constitutes a "mismatch" for an MLV? What are the recommended scenarios for using FAIL vs DROP? Does ON MISMATCH FAIL affect the entire MLV refresh or only the affected data/operation? Dev → UAT → Production Deployment This is probably my biggest area of uncertainty. Suppose I create and test the following in DEV: DEV Workspace Lakehouse Source tables MLV 1 MLV 2 My expectation is that I should not manually recreate the MLVs in UAT and Production. Instead, I would use Fabric lifecycle/deployment capabilities to promote the artifacts: DEV → UAT → PROD Questions: Are MLV definitions currently supported for this type of Dev → UAT → Prod deployment? Does Deployment Pipeline automatically handle the corresponding Lakehouse/item dependencies? If the workspace names, Lakehouse names and item IDs are different between environments, how are those references handled? Does Fabric automatically rebind supported dependencies to the corresponding target-environment resources? Which MLV-related properties/configurations need to be manually configured or validated after deployment? For example: DEV Workspace: BI_DEV Lakehouse: Sales_LH_DEV ↓ UAT Workspace: BI_UAT Lakehouse: Sales_LH_UAT ↓ PROD Workspace: BI_PROD Lakehouse: Sales_LH_PROD How much of this environment-specific mapping is automatically handled by Fabric? MLV Refresh Schedules Across Environments Suppose my DEV MLV has a refresh schedule of every 1 hour. When I deploy it to UAT and Production: Is the schedule also deployed? If it is, can or should it be different between environments? What is the recommended approach for managing MLV schedules separately in DEV, UAT and PROD? Is schedule configuration considered part of the deployable MLV artifact or environment-specific configuration? MLV Dependencies / MLV on top of MLV Can we create an MLV that references another MLV? For example: Source Tables → MLV 1 – Silver → MLV 2 – Gold → MLV 3 – Aggregation Is this a supported and recommended architecture? If yes: Are there any limitations on the number or depth of MLV dependencies? How does refresh orchestration work? If MLV 1 fails, are MLV 2 and MLV 3 automatically skipped? How is the dependency and lineage handled during deployment from DEV → UAT → PROD? SQL View on top of MLV Can we create a regular SQL View on top of an MLV? For example: Source Tables → Materialized Lake View → SQL View → Semantic Model / Power BI If this is supported: Are there any performance implications? Does the SQL View remain virtual while the MLV remains materialized? Is this a recommended pattern for exposing MLV data to downstream consumers? View → MLV Conversely, can an MLV be created on top of a regular SQL View? For example: Source Tables → SQL View → MLV If supported, are there any restrictions around the types of views or queries that can be used as an MLV source? Recommended Production Architecture For a production implementation, would the following architecture be considered a reasonable pattern? Source Tables → MLV Layer → Silver MLVs → Gold MLVs → SQL Views (if required) → Semantic Model → Power BI Or is it generally better to consume MLVs directly from the semantic model where possible? General Best Practices For anyone using MLVs in production: What are the main limitations you have encountered? What should be considered when designing MLV dependencies? How do you handle monitoring and alerting? How do you manage Dev/UAT/Prod deployment? Are there any MLV-specific CI/CD considerations that are easy to miss? What would you recommend avoiding when designing an MLV architecture? I'd particularly appreciate confirmation from anyone who has implemented MLVs across multiple Fabric environments such as DEV, UAT and PROD. Thanks in advance!
