[BUG] Dataflow Gen2 destination picker 404 — api.powerbi.com lakehouses UK region
Hi community, We have a complete blocker with Dataflow Gen2 (CI/CD) destination configuration in our UK-region Fabric tenant. The Error: When clicking "Add default destination" and selecting a Fabric Lakehouse from the OneLake catalog, this error fires immediately for ALL users including the workspace Admin: DataSource.Error: Downstream service call to url 'https://api.powerbi.com/v1/workspaces/{WORKSPACE_ID}/lakehouses' failed with status code 404. (Region: uk) The Lakehouse IS visible in the OneLake catalog — it appears in the picker. The 404 fires the moment it is clicked. Root cause hypothesis: The destination picker calls the legacy Power BI REST API: api.powerbi.com/v1/workspaces/{id}/lakehouses ← returns 404 For Fabric-native workspaces in the UK region, the correct endpoint should be: api.fabric.microsoft.com/v1/workspaces/{id}/lakehouses The OneLake catalog listing (which uses a different path) resolves the lakehouse correctly — it's only the destination configuration call that uses the wrong endpoint. Workarounds attempted — all failed: 1. UI — Admin user attempted same steps → same 404 2. queryMetadata.json via Git — Added destination fields, pushed to prod branch → Fabric silently strips loadEnabled/destination on every sync, creating a permanent conflict loop (workspace ≠ Git on every update) 3. Authentication methods — Before the error began firing immediately, a "Connect to default data destination" screen appeared offering two authentication options for the Lakehouse connection: - Organizational account (Sahil Singh / user account) - Service principal Both were attempted. Neither succeeded — the 404 followed in both cases. Subsequently, this connection credentials screen stopped appearing altogether. The 404 now fires immediately upon clicking lh_dhl_prod in the OneLake catalog, before the connection setup dialog is even shown. This regression suggests the failure point has moved earlier in the destination configuration flow. Questions: 1. Is this a known issue for UK-region tenants? 2. Is there a way to configure the Dataflow Gen2 destination via Fabric REST API directly to bypass the broken UI? 3. Are there other file-based approaches (mashup.pq metadata) for CI/CD Dataflow Gen2 destinations? Happy to provide Session IDs and further details to the Fabric team. I have attached the relevant images, PFA... Thanks
Unable to create sub connections in service
This is a dataflow that was working up until last night's refresh cycle. This particular part had been working for at least a year. The same PQ logic IS working in a local PBIX file w/o issue. My dataflow is connecting to a Dataverse environment. Connecting to "tables" works without issue. Where I am running into issues is attempting to access the metadata attributes that contain the values for multiple choice columns. To do so I'm using the function below: In both service and local PBIX. The first prompt for credentials is addressed with Anonymous In the PBIX the second prompt is addressed with my Org account. In the local PBIX this is recordable as two different credentials. The first is for https://org<number>.crm.dynamics.com the second is the expanded Attribute metadata url that RelativePath produces. Today I'm unable to create a second credential "specific" to the relative path url in the service which prevents refreshing this table. Is anyone else seeing this? Am I approaching this wrong? let Options = (TableName as text, OptionSetName as text) => let // Source = Json.Document(Web.Contents("https://" & ORGURL & "/api/data/v9.0/EntityDefinitions(LogicalName='" & TableName & "')/Attributes(LogicalName='" & OptionSetName & "')/Microsoft.Dynamics.CRM.MultiSelectPicklistAttributeMetadata?$select=LogicalName&$expand=OptionSet($select=Options)")), Source = Json.Document( Web.Contents(DataverseEnvironment, [ RelativePath = "/api/data/v9.0/EntityDefinitions(LogicalName='" & TableName & "')/Attributes(LogicalName='" & OptionSetName & "')/Microsoft.Dynamics.CRM.MultiSelectPicklistAttributeMetadata?$select=LogicalName&$expand=OptionSet($select=Options)" ] ) ), OptionSet = Source[OptionSet], Options = OptionSet[Options], #"Converted to Table" = Table.FromList(Options, Splitter.SplitByNothing(), null, null, ExtraValues.Error), #"Expanded Column1" = Table.ExpandRecordColumn(#"Converted to Table", "Column1", {"Value", "Label"}, {"Value", "Label"}), #"Expanded Label" = Table.ExpandRecordColumn(#"Expanded Column1", "Label", {"UserLocalizedLabel"}, {"UserLocalizedLabel"}), #"Expanded UserLocalizedLabel" = Table.ExpandRecordColumn(#"Expanded Label", "UserLocalizedLabel", {"Label"}, {"Description"}), #"Set Column Types" = Table.TransformColumnTypes(#"Expanded UserLocalizedLabel",{{"Value", Int64.Type}, {"Description", type text}}) in #"Set Column Types" in Options
Azure DevOps pipeline to replicate Power BI report changes for various repositories (PBI workspaces)
Hello, here is my business request: -> we are having data from various countries and would like to have dedicated Power BI workspace for data from each country -> it will help us with permissions management, will clearly separate the data,... And technical setup so far looks as the following: -> as semantic models will have the same schema (table names, metric names), it means, that semantic models within each workspace will be using slightly different SQL query (which will gather data for the respective country) -> it's true, that maintenance of semantic models for multiple workspaces may be then be a little bit longer (as we will have to adapt changes for each workspace), but changes for semantic models are not frequent and usually we do bulk of changes together But I am now dealing with the technical question and what would be the best practice for development of Power BI reports, where we would like to reduce amount of duplicated work. Below is my idea for technical implementation: -> PBI reports are developed for one workspace within Azure DevOps repository, then merged through Pull request and then published into PBI workspace through Source control integration in PBI -> and I would like to have Azure pipeline, which will listen to the Pull request merge (basically any change in the master branch of that repository) and then will create similar Pull request in another repository (which is linked to another Power BI workspace), while replicating all the adapted changes for reports -> as was mentioned, schema of semantic models is the same between workspace, so it's only important for replication of Pull request with changed reports to keep proper connection (from Power BI report to semantic model), everything else can be simply copied => and my question really is, if you think, that this could be the right approach (having Azure pipelines to replicated PBI report changes into multiple repositories) and if yes, whether you could suggest to me some working Azure DevOps YAML pipelines examples ? many thanks in advance for any thoughts or suggestions
how to change the service account in On Prem gateway
Hello everyone ! I am trying to connect a network directory using Power Automate . As you know the first step is to install and register gateway . I did the same but to connect to network folder/ directory - I got to know that we need to change the service account present in Service Settings ! I tried to change with my Windows User name and password , it is continuously throwing password / user incorrect error . Can you please guide me what needs to entered in Service Setting --> Change Service Account ? Please note that we have dedicated service account and I am trying to use the same ..
Severe Gateway Performance Degradation & High CPU Post-Migration (ASYNC_NETWORK_IO Waits)
Hello everyone, I am looking for some architectural and performance troubleshooting advice. Following a server migration on March 27, 2026, our On-Premises Data Gateway has experienced a massive and continuous spike in CPU usage and data processing duration. Standard refreshes are now taking twice as long to execute. Environment & Architecture: OS: Windows Server 2016 Standard. Hardware: AMD EPYC 9274F 24-Core (30 logical processors), 192 GB RAM. Co-hosted Services: The physical server hosts the Gateway, SQL Server 2019, and Remote Desktop sessions. Storage Configuration: Drive I (4KB allocation size), Drives E and D (64KB allocation size). SQL Shared Memory protocol is ON. Symptoms & Observations: Gateway Logs: We are seeing AsyncOperationStreamingCancelledException errors related to the spooler (No more this error after tuning applied on 24 April). SQL Server Waits: Running sp_WhoIsActive during Gateway execution shows a high volume of blocked sessions with ASYNC_NETWORK_IO wait types. This specifically impacts databases located on Drive D (logs on Drive E). Performance for a database located on Drive I remains completely normal. OS Impact: RDP sessions for users on this server periodically become unresponsive due to the resource drain. Troubleshooting Steps Taken: Prior to April 20, the Gateway ran on default settings with the Spooler and Mashup Cache located on Drive C. I have since applied the following tuning: Settings from 20.04 to 24.04 Container Tuning - from 20.04 to 24.04: Enabled overrides and adjusted Mashup pool containers. Currently set to MashupDefaultPoolContainerMaxCount = 4 and MashupDefaultPoolContainerMaxWorkingSetInMB = 8192. I/O Relocation: C drive Streaming: Toggled StreamBeforeRequestCompletes to TRUE. Memory Management: Reduced SQL Server max server memory to 140 GB Settings from 24.04: Container Tuning : Enabled overrides and adjusted Mashup pool containers. Currently set to MashupDefaultPoolContainerMaxCount = 12 and MashupDefaultPoolContainerMaxWorkingSetInMB = 4096. I/O Relocation: Moved the SpoolerDirectory and Mashup Persistent Cache to Drive I to alleviate potential disk contention. Streaming: Toggled StreamBeforeRequestCompletes to FALSE. Memory Management: Reduced SQL Server max server memory to 135 GB Current Status: These changes successfully reduced Gateway CPU usage and processing duration compared to the post-migration peak. However, performance is still significantly worse than it was before the migration. Has anyone experienced similar ASYNC_NETWORK_IO bottlenecks between local SQL Server instances and the Gateway Mashup engine after hardware/server migrations? Thank you in advance for your insights. EDIT: 30.07.2026 Created new gateway (testGateway) on different VM. Moved couple of reports to new testGateway. The issue is still there. Performance seems bit better, but still there is ASYNC_NETWORK_IO bottleneck.
API equivalent of "Configure Connection > Connect" for Dataflow Gen2?
We're automating Dataflow Gen2 onboarding for unattended refresh using the Fabric REST API. Our service account owns an on-premises gateway connection (OAuth / Organizational account) that reports Online via testConnection. We create or update dataflows with this connection in queryMetadata.json — service account is the item owner and connection owner. Refreshes fail with "Credentials are required" until we manually open the dataflow in the portal and click Configure Connection > Connect. After that single click, refreshes work indefinitely. Is there any API or programmatic method that replicates what "Connect" does? We cannot use manual interaction per dataflow, and cannot change to Basic/Windows credentials and must use OAUTH2
Can Scorecard(Goals) be used for custom Power BI visuals?
Hi everyone, I'm evaluating Power BI Scorecards (Metrics) for KPI/KRI tracking. During testing, I noticed that a Scorecard creates an associated semantic model that is visible in Fabric/OneLake. However, the semantic model appears to be DirectQuery-based, and I haven't been able to use it the same way I would a normal semantic model for reporting. My goal is to: Maintain KPI/KRI values in a Scorecard using manual data entry check-ins Build custom Power BI reports using that data Create visuals such as bar charts, pie charts, stacked columns, trend charts, and executive dashboards My questions are: Is the automatically created Scorecard semantic model intended to be used as a source for custom Power BI reports? Can regular check-in be used as a data entry point? Are there DirectQuery or modeling limitations that prevent custom visualization? Has anyone successfully used Scorecard metric data to build custom report visuals outside the Scorecard experience (other than the trend view)? I can see the associated semantic model in Fabric, so I'm trying to understand whether I'm missing a configuration step or if the model is only intended to support the Scorecard itself. Thanks in advance!
