Forum Discussion
Failed to update data source credentials: The credentials provided for the Fhir source are invalid.
Hello harikrishna_m,
Thank you for providing an update on the issue.
The fact that you only see Dataflow Gen1 and not Dataflow Gen2 when creating a new item indicates that Dataflow Gen2 is likely disabled at the tenant or capacity level. Here’s how to enable it:- A Fabric tenant admin should go to the Microsoft Fabric Admin Portal >>navigate to Tenant Settings and look for a setting like "Enable Dataflow Gen2 " or "Allow Preview Features." Ensure it’s enabled for your organization or security group.
- Also, check the Capacity Settings for your F64 capacity in the Admin Portal. Under workload or feature settings, ensure Dataflow Gen2 is enabled.
You’ve correctly identified that the cross-tenant setup is causing the connectivity issue. The Azure API for FHIR in Tenant A uses a private endpoint, so Fabric in Tenant B cannot access it directly. Please consider the below option:
- Deploy an Azure Function or API Management (APIM) instance in Tenant A with a public endpoint. The Function/APIM authenticates with the FHIR API (using OAuth 2.0) within Tenant A and accesses it over the private endpoint. Fabric in Tenant B then connects to this public endpoint.
I trust this information proves useful. If it does, kindly “Accept as solution” and give it a 'Kudos' to help others locate it easily.
Thank you.
Power BI Dataflow Gen1 cannot authenticate to Azure API for FHIR because it doesn’t support OAuth2/Azure AD token-based auth hence the 400 error even with FHIR Data Reader access.
You can work on either of these options.
- Use Dataflow Gen2 (Fabric):
- Supports Azure AD / OAuth2
- Use Organizational Account or Service Principal
- Assign correct FHIR roles (Data Reader or Contributor)
- No on-prem gateway needed
- Use an Azure Function or API App as a proxy:
- Function handles AAD token and calls FHIR API
- Power BI Dataflow Gen1 connects to the function using Basic or Anonymous auth
- Returns JSON to Power Query
Hi Bhavin,
Thank you for sharing your valuable information,
I dint know that dataflow gen1 does not support OAuth2/AzureAD is there any MS documentation that i could refer to? i did try to save the dataflow gen1 file to gen2 and was seeing the below error,
i am guessing there is some changes need to be done in fabric capacity? we do have a fabric capacity with sku:F64.
Use https://app.fabric.microsoft.com, open a Fabric workspace (like with SKU F64), and create the Dataflow Gen2 from there. don’t use “Save As Gen2” from Gen1 and check once.
my current workspace where i am facing issues does have a fabric capacity with sku:F64 and when i am trying to create any new item, i can only see dataflow gen1,
is there enabling to be done on the tenant side to allow dataflow gen2?
Please refer this link for prerequisites,
Create your first Microsoft Fabric dataflow - Microsoft Fabric | Microsoft Learn