How to solve the "app.powerbi.com refused to connect." error when adding Power BI Reports in Jira Align

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

When attempting to add an external report from PowerBI into Jira Align, users encounter the following error message:

1 "app.powerbi.com refused to connect."

Environment

Jira Align Cloud

Diagnosis

Upon attempting to integrate PowerBI reports into Jira Align, users receive an error indicating that the connection to the PowerBI site is refused. This occurs despite having added the necessary PowerBI URLs to the approved URL pattern list within Jira Align settings.

Cause

The error is primarily caused by the PowerBI report not being publicly accessible. Jira Align requires reports to be accessible via public URLs in order to embed them successfully. If the report remains private or is restricted to specific users within PowerBI, Jira Align will be unable to establish a connection, leading to the refusal error.

Solution

To resolve this issue, follow the steps outlined below:

  1. Add PowerBI URLs to the Approved URL List: Ensure that PowerBI URLs are added to the approved URL pattern list within Jira Align. It is recommended to add the base URL with wildcards to cover all potential sub-paths as described in Reports settings. For example, add the following pattern to the list: https://app.powerbi.com/**.

  2. Make the PowerBI Report Public: Follow the instructions provided in the Microsoft documentation to publish the PowerBI report to the web. This involves configuring the report to be accessible via a public URL. The detailed steps are in the Microsoft article titled "Publish to web from Power BI."

By ensuring that the PowerBI report is public and that the URL patterns are correctly configured in Jira Align, the integration should function without encountering the "refused to connect" error. If the issue persists, verify that the URL patterns are accurately entered and that the report's public access settings are correctly applied.

Updated on February 14, 2025

Still need help?

The Atlassian Community is here for you.