Power BI connector

Hi Kristen - I have the same issues.   We will be change MS Tennant soon so I was going to wait to see if it corrects the problem.    Scott

From what we see across other Microsoft integrations, this behavior is typically driven by your Azure AD (Entra ID) tenant's consent and security policies rather than anything inside Workfront Fusion. The "Workfront Fusion PowerBI Connector" app has to be allowed by your tenant and not blocked by conditional access or consent restrictions; if the tenant silently refuses or blocks the sign‑in, Fusion just receives a generic "Connection failed" from Microsoft.

Then suggest concrete checks for their Microsoft admin:

1. Verify the app in the correct tenant

   • In Azure portal → Enterprise applications, locate "Workfront Fusion PowerBI Connector".
   • Confirm it's present in the same tenant where the user's Power BI account lives.

2. Check sign‑in logs for the failing user

   • Azure AD → Sign‑in logs, filter on the user and the approximate time they try to create the connection.
   • There should be a failed sign‑in for the Fusion Power BI app with a more specific error (e.g. conditional access, consent, or tenant restriction).
   • This is exactly what we recommend for similar consent loops on other Microsoft connectors. Conversation from #support-questions channnel

3. Review consent / conditional access policies

   • Some customers have global settings that force per‑user admin approval, or block certain apps/scopes even after an approval. That mismatch is what causes "approved" + "Connection failed" combinations in other Fusion–Microsoft cases. Conversation from #ask-wf-adobe-integrations channnel

if your admin confirms the sign‑in is successful on Microsoft's side but Fusion still fails, then open a ticket so we can look at Fusion's logs with a precise timestamp and correlation ID.

also if its workfront data for power bi have you considered workfront data connect - 

 

• Workfront Data Connect overview
  Explains the Data Connect data lake, supported BI tools (Tableau, Power BI, Domo, Looker, etc.), and data types (current state, change events, daily history).
  👉 https://experienceleague.adobe.com/en/docs/workfront/using/reporting/data-lake/data-lake-overview
  – Workfront Data Connect overview

Hi ​@KristenS_WF 

Yes, the Power BI connector does work; what you're hitting is almost always an Azure AD admin‑consent/config issue, not a Fusion problem.

Do this with your M365/Azure admin:

• In Azure portal -> Azure Active Directory -> Enterprise applications, open "Workfront Fusion PowerBI Connector".
• On Permissions / Permissions and consent, verify that "Grant admin consent for <Org>" shows as granted for all required scopes. If not, click it and confirm.
• Under Users and groups / Properties / Conditional access, ensure:
  • The user creating the Fusion connection is allowed to sign in to that enterprise app.
  • No conditional access policy is blocking the app or requiring extra steps that never complete.
• Then, in a fresh incognito/private window, go to Fusion and create the Power BI connection again, making sure you're logged into the same tenant where the admin consent was granted.
• If consent is correctly granted and you still get the same "Connection failed" loop, the remaining fix is on Microsoft's side (AAD consent caching/tenant policies); at that point involve Microsoft support along with your tenant admin—there is nothing further to configure in Fusion for this flow.