Dataflow refresh fails with status code 403 storageAccess when run from power automate.
Hi All, I have a Gen1 Dataflow in a Premium PPU Workspace that fails with status code 403 after about 50 to 70 minutes of execution when run from Power Automate with 'Refresh a dataflow'. The dataflow runs OK when refreshed manually. Error: PipelineException: Downstream service call to url 'https://wabi-canada-central-b-primary-redirect.analysis.windows.net/metadata/v201606/cdsa/dataflows/b2e8f2dd-658a-45de-b52a-96d352062012/storageAccess' failed with status code 403.: MashupValueException. RootActivityId = b6ad9bed-01c0-4070-8e34-c3720da61775.Param1 = PipelineException: Downstream service call to url 'https://wabi-canada-central-b-primary-redirect.analysis.windows.net/metadata/v201606/cdsa/dataflows/b2e8f2dd-658a-45de-b52a-96d352062012/storageAccess' failed with status code 403.: MashupValueException Request ID: 24a9300c-bbd9-45ba-9cb2-3bbfaaa3770f. I am running the dataflow as the owner of the workspace. The dataflow accesses previously run dataflows data only. I have refreshed the credentials in the dataflow also. The power automate action 'Refresh a dataflow' connection reference is mapped to the account that is the owner account. Any ideas or where I can get more detailed logs? Thanks
Best Practices for Automating Power BI Dataset Refresh and Monitoring Failures
Hi everyone, I'm exploring different approaches to managing automated semantic model refreshes and monitoring failures across multiple Power BI workspaces. For organizations managing several reports and data sources, maintaining reliable refresh schedules and identifying failures can become challenging as the environment grows. I'm particularly interested in how teams are approaching the following: Are you primarily using Power BI's native scheduled refresh capabilities, Power Automate, or REST APIs for refresh orchestration? How are you implementing centralized monitoring and automated notifications when refreshes fail? What strategies work best for handling refresh dependencies and retries without triggering duplicate executions? Are there recommended approaches for integrating Power BI refresh monitoring with existing enterprise automation workflows? I'm interested in understanding which approaches are most practical for environments with multiple workspaces, particularly when reliability, maintainability, and operational visibility are priorities. Would appreciate any recommendations, architecture patterns, or real-world implementation experiences. Thanks in advance!
Power BI Dataflows failing with "You've reached the refresh limit for your account"
Since yesterday, several of our Power BI Dataflows have started failing with the following error: You've reached the refresh limit for your account. Please try again later. The failures occur almost immediately, sometimes in less than one second, so the refresh does not seem to actually start processing the data. Initially, I suspected this might be related to Dynamics 365 Business Central, as we upgraded from BC v28 to v29 yesterday and the Dataflow failures started around the same time. Some of the affected Dataflows use OData web services based on Business Central pages. We are aware of the upcoming changes/deprecation affecting this type of integration, but as far as I understand, this is expected with Business Central v30 rather than v29, so it should not be affecting us yet. More importantly, I have now tested a Dataflow using SharePoint as the data source and it fails with exactly the same error. This seems to indicate that the issue is not specific to Business Central, OData, or the recent BC v29 upgrade. We are using Power BI Pro/shared capacity, and multiple Dataflows are being affected. Has anyone experienced the same issue recently? Could this be related to a Power BI Service account-level refresh/concurrent evaluation limit or a current service-side issue?Business Central v30: Power BI Dataflows using OData web services based on Microsoft pages
We currently have several Power BI Dataflows consuming Business Central data through OData V4 web services. Some of these web services are based on standard Microsoft Business Central pages. According to the Microsoft documentation, starting with Business Central v30 it will no longer be possible to expose a Microsoft page as an OData endpoint. We are currently on BC v29, so everything is still working, but this looks like potential technical debt that we should address before upgrading to v30. Many of these Dataflows are already in production and some retrieve accounting and operational data across multiple Business Central companies, so I would like to understand the recommended migration path rather than simply waiting for v30 to break the existing integrations. For those in a similar situation: Are you migrating these integrations to standard Business Central API pages/queries where available? For data that is not exposed through a standard API, are you creating custom API pages or API queries? Is replicating the existing Microsoft page in a custom extension and continuing to expose it through OData considered a reasonable transitional solution? Are there any relevant differences or limitations when consuming these alternatives from Power BI/Dataflows compared with the current OData page web services? I would be interested to hear how others are approaching this migration, particularly for existing Power BI solutions with multiple Dataflows and companies. Thanks in advance for any experiences or recommendations.
Combined dataflow - most rows missing
Hello, I am combining 9 dataflows into one dataflow. When doing so I lose most of the source rows. So for example, a source table as verified in PBI works and gives multiple millions rows of data. But the same table returns just a few tens of thousand rows in the combined dataflow. I use the gen 1 dataflow. What could cause this? I think the total is around 40 million rows, and the combined dataflow refresh time is 1h 30 min which is less I think than the cap of 2 hours. I have tried to look into datatypes, and the main field existing in all tables, like part number and location seem to be the same, (but I haven't verified the data type of all included fields from all source tables.) So not sure what is going on. I have thought I could try to create a new dataflow and add one dataflow at a time and verify the result in PBI after each pass, but it is a lot of work. The filtering being made in the combined dataflow is simple, it is removing columns and filtering on part number which shouldn't have this effect on the number of rows at all. Thanks for any help in order to track down the cause of this discrepancy. I have Googled and used AI to try to solve it but so far I haven't solved it. // Daniel
Dataflow Gen2 parameter works with current value but fails when passed from Fabric Pipeline
I have a Dataflow Gen2 that calls a SOAP API using Web.Contents(). The Dataflow has an APIKey Text parameter, which I use in Power Query: v_apikey = Text.From(APIKey) The value is inserted into the SOAP request header/body before making the Web.Contents() call. The issue: API key entered as the Dataflow parameter's current value → Works Exact same API key passed from a Fabric Pipeline parameter → Fails The failure eventually results in: Expression.Error: There weren't enough elements in the enumeration to complete the operation. The SOAP XML navigation also shows an empty table: #table({"Name", "Table"}, {}) I'm trying to understand the runtime execution path: Pipeline parameter → Dataflow activity → Dataflow parameter → Power Query → Web.Contents() Does Dataflow Gen2 apply Pipeline parameter overrides before Power Query/Web.Contents is evaluated, including any metadata evaluation? Are there known limitations when a runtime Dataflow parameter is used inside the POST body of Web.Contents()? Also, is there a safe way to verify that the Pipeline-supplied API key reached Power Query correctly without exposing the key itself?Power BI Dataflow Refresh Fails Despite Queries Loading Successfully in Power Query
Hi everyone, I'm facing an issue with a Power BI Dataflow and would appreciate some guidance. I have three queries pulling data from different sources, which I've appended into one final query using Table.Combine. All three queries load correctly in Power Query, and the appended query also previews the combined data without any errors. I've disabled Enable Load for the three source queries and kept it enabled only for the final appended query. However, whenever I refresh the dataflow, the refresh fails, and the error only shows a Request ID and Activity ID without any specific details. I've also tried simplifying the final query to just the basic append operation, but the refresh still fails. Has anyone experienced something similar? Could this be related to query dependencies, combining different data sources, or dataflow settings? Any suggestions on how to troubleshoot or resolve this would be greatly appreciated. Thank you!
Unable to Submit a Microsoft Fabric Technical Support Ticket: Only 'Add New Contract' Available
Hello Microsoft Fabric Community, I am seeking assistance with accessing Microsoft Fabric technical support for an unresolved Dataflow Gen2 authentication issue. I have an existing discussion covering the complete technical investigation, troubleshooting history and diagnostic results: Dataflow Gen2 Lakehouse connection fails with AADSTS70008 | Original Discussion Rather than repeating the entire troubleshooting history, I am opening this focused discussion to seek help with the remaining support-access issue. 1. Brief technical background My original Dataflow Gen2 connection to LakeHouse_Training in the Nikolai_Schuler_Udemy workspace fails with: AADSTS70008: The provided authorization code or refresh token has expired due to inactivity. Attempts to update credentials or create a new connection to the original Lakehouse also result in an Invalid credentials message. I completed a clean-room diagnostic test using the same Microsoft Entra tenant, organizational account and Fabric trial capacity. The results were: Created a new workspace: Fabric_OAuth_Diagnostic. Created a new Lakehouse: LH_OAuth_Diagnostic. Created a new Dataflow Gen2: DF_OAuth_Diagnostic. Successfully established a fresh Organizational account connection. Successfully imported CSV data and loaded it into a new Lakehouse table. The Dataflow execution completed in approximately 22 seconds. However, connecting to the original LakeHouse_Training from the same diagnostic environment continues to fail. This indicates that the issue appears to be specific to the original Lakehouse or its connection/authentication path. The underlying root cause remains unconfirmed. 2. Microsoft Fabric technical support access issue I attempted to obtain technical assistance through the official Microsoft Fabric Support portal and the Contact Support option in Power BI/Fabric. However, the Support plan dropdown only displays: Add new contract The Microsoft Fabric Subscription option is missing, and I cannot proceed with submitting a technical support request. My environment: Microsoft Fabric trial capacity. Fabric Free per-user license. Organizational member account in a Microsoft Entra tenant. Global Administrator permissions in the Entra tenant. I do not have a Unified or Premier support contract. I also previously submitted an Azure Basic Support request for this issue, but it was closed because technical break-fix support is not covered by that plan. 3. Microsoft documentation According to Microsoft's current documentation, users with a Fabric Free license can create support tickets for Fabric products. The documentation also states that the support-plan selection can be made using Microsoft Fabric Subscription or a Unified/Premier support plan. The Add new contract option is intended for users who already have a Unified or Premier contract that is not listed. Documentation: https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket Unfortunately, my support form does not display the documented Microsoft Fabric Subscription option. 4. Assistance requested Could someone from Microsoft Fabric Support or the Community Support team please clarify: Why is the Microsoft Fabric Subscription option missing from the support-plan dropdown? Is there any additional prerequisite or account configuration required for a Fabric Free user with an active trial capacity to submit a technical support ticket? Is there an alternative route to obtain a technical escalation for this Dataflow Gen2/Lakehouse connection issue? I would particularly appreciate assistance from a Microsoft Fabric employee or someone who can route this to the appropriate Data Factory or Lakehouse connector support team. I can provide the detailed Entra sign-in logs, trace IDs, correlation IDs, timestamps and other diagnostic information privately if required. Thank you for your time and assistance.Dataflow Gen2 Lakehouse connection fails with AADSTS70008
I am learning Microsoft Fabric and preparing for the DP-600 certification. I have spent several days trying to resolve a Dataflow Gen2 Lakehouse authentication failure, and I need help identifying the root cause. Environment Microsoft Fabric trial capacity, with a Fabric Free per-user license. Personal Azure Free account and a newly created Microsoft Entra tenant. Workspace: Nikolai_Schuler_Udemy. Lakehouse: LakeHouse_Training. Dataflow: Dataflow 1. Authentication: Organizational account, OAuth 2.0. Privacy level: Organizational. Gateway: None. The Entra tenant was originally created through an Azure signup using a personal Gmail account. I created an onmicrosoft.com member account with Global Administrator permissions and use that account for Fabric. The original Gmail identity exists in the tenant as a guest. Problem Dataflow Gen2 cannot connect to the Lakehouse. The query editor displays “Credentials are required to connect to the Lakehouse source.” When creating or updating the connection, Fabric reports: AADSTS70008: The provided authorization code or refresh token has expired due to inactivity. Send a new interactive authorization request for this user and resource. HTTP status: 400 Cluster: https://api.powerbi.com The same failure occurs when editing credentials for an existing connection. The account picker can open, but reauthentication has not restored access. A newly created connection appears in Manage Connections, yet the Dataflow editor still cannot connect. Troubleshooting completed Tested Chrome, Edge, and Edge InPrivate. Retried interactive sign-in using the onmicrosoft.com member account. Confirmed Microsoft Authenticator MFA is registered. Tested existing and newly created Lakehouse connections. Used Edit credentials in Manage Connections and Gateways. Confirmed the Lakehouse and SQL analytics endpoint are accessible in Fabric. Enabled GitHub integration and successfully synchronized the workspace to a public GitHub repository. This did not resolve the authentication error. Checked Entra sign-in logs. A previous Power BI Data Refresh sign-in failed with error 70008, and the credential update continues to fail with the same error. Support-access problem Microsoft's current support documentation says Fabric Free users can submit support tickets for Fabric products. However, the Fabric Help and Support form only offers “Add new contract”; “Microsoft Fabric Subscription” is missing. I submitted an Azure subscription-management request, but it was closed because Basic Support does not cover technical issues. I still have no technical support case. Questions Why does a fresh OAuth authorization continue to fail with AADSTS70008 in this new tenant? Is there a known issue with Dataflow Gen2, Power Query Online, or the Lakehouse connector's OAuth token handling? Could the tenant identity setup or Fabric trial capacity affect OAuth authorization or Fabric support eligibility? How can I obtain a proper Fabric technical support escalation as a Fabric Free user? Could a Microsoft Fabric employee or Data Factory specialist investigate this and advise on the next diagnostic step? I can provide the full trace ID, correlation ID, request ID, tenant details, and screenshots privately if needed.
