---
title: "Power BI Connector for Jira Data Center FAQ"
canonical: "https://support.appfire.com/space/SUPPORT/3550674959/Power%20BI%20Connector%20for%20Jira%20Data%20Center%20FAQ"
format: markdown
---
This FAQ answers common security, network, and deployment questions about Power BI Connector for Jira Data Center if you're evaluating the app for use in restricted, private, or air-gapped environments.

> ℹ️ If you're reviewing the app as part of a security or infrastructure assessment, this article focuses on network behavior, data flow, data residency, and deployment considerations.

## Frequently asked questions

<details>
<summary>Does Power BI Connector for Jira Data Center require outbound internet access?</summary>

No. The app itself doesn't require outbound internet access from the Jira Data Center server to perform its core functionality.

Its primary operation happens within your local Jira environment, where it reads Jira data and makes it available for reporting and analytics use cases.
</details>

<details>
<summary>Does the app make any outbound calls to external services?</summary>

No. The app doesn't make outbound internet calls as part of its normal product behavior.

There's no app-level telemetry, analytics, or crash-reporting component required for the connector to operate.
</details>

<details>
<summary>Can the app be used in an air-gapped environment?</summary>

Yes. You can use Power BI Connector for Jira Data Center in air-gapped or otherwise network-restricted environments, provided that the underlying Jira Data Center environment supports the installation and operation model your organization requires.

The connector’s native behavior doesn't depend on live external connectivity.
</details>

<details>
<summary>Does the app send Jira data to Appfire or to a cloud service?</summary>

No. The app doesn't send Jira data to Appfire-managed cloud services as part of its core functionality.

Data stays within the Jira Data Center environment that you manage unless you intentionally export, connect, or route that data elsewhere through your own reporting architecture and processes.
</details>

<details>
<summary>Where is the app’s data stored?</summary>

The app operates within the Jira Data Center environment and uses the local Jira-side infrastructure available to it.

Any app-relevant data remains within the environment you control rather than being stored in an Appfire-hosted cloud backend for this product flow.
</details>

<details>
<summary>Does the app require inbound network access from external systems?</summary>

No. The app itself doesn't require any special inbound internet connectivity to the Jira server.

Any access to Jira or to app-provided endpoints should follow your own network design, reverse proxy configuration, and access-control policies.
</details>

<details>
<summary>How does licensing work if the app doesn't make outbound calls?</summary>

Jira’s standard app management and licensing mechanisms handle licensing. In Data Center environments, licensing-related behavior is part of the Atlassian platform and its administration model rather than a separate outbound communication channel built into the connector’s functional runtime.
</details>

<details>
<summary>Does the app include telemetry, analytics, or crash reporting?</summary>

The connector doesn't require any app-specific telemetry, analytics, or crash-reporting behavior to function.

If you need highly restricted deployments, you can evaluate the app based on its operational behavior within Jira Data Center rather than on dependency on external observability services.
</details>

<details>
<summary>How does the app work with other Jira apps or integrations such as Tempo or Assets?</summary>

When the app uses information exposed within the Jira environment by other installed apps, that interaction is local to the Jira instance.

The connector works with data available inside your Jira deployment rather than reaching out to external vendor cloud services as part of that integration path.
</details>

<details>
<summary>Is the app read-only?</summary>

For reporting and analytics scenarios, the connector is intended to expose Jira data for consumption rather than to modify Jira issue content as part of the reporting workflow.

You should still validate permissions and access scopes in your own environment to ensure they align with your internal governance requirements.
</details>

<details>
<summary>Is your data encrypted in transit?</summary>

Traffic should be protected in transit according to your Jira Data Center deployment architecture, including HTTPS where you've configured it.

Transport-layer protection is therefore governed primarily by your organization’s own Jira and network setup.
</details>

<details>
<summary>Does the app require any special firewall allowlisting?</summary>

In general, you don't need app-specific outbound allowlisting for core product functionality, because the app doesn't depend on outbound internet calls to operate.

You should still review standard Jira platform requirements and any internal routing rules that apply to your own environment.
</details>

<details>
<summary>What should security reviewers know when assessing this app?</summary>

For most reviews, the key points are listed in the [Summary](#Summary) section.
</details>

## Summary

If you're assessing this app as part of a security review, keep these key points in mind:

- The app operates within Jira Data Center.
- Core functionality doesn't require outbound internet access.
- The app doesn't rely on an Appfire-hosted cloud backend for normal operation.
- Data remains in the environment you manage unless you choose to export or connect it elsewhere.
- Integration behavior is local to the Jira ecosystem you deploy.