Share analytical data from Fabric HorizonDB

Use the mirrored analytical copy to share Fabric HorizonDB results through supported Fabric analytical experiences. Operational PostgreSQL access remains restricted to the database creator.

Important

Fabric HorizonDB is in public preview. Only the Microsoft Entra identity that created the database can connect to PostgreSQL. Sharing the database item doesn't enable another user or principal to connect. For more information, see Microsoft Fabric preview features.

Prerequisites

  • Healthy mirroring and the analytical item you intend to share.
  • Permission to manage access to that SQL analytics endpoint, semantic model, or report.
  • A clear list of the data and operations the recipient needs.

Choose the analytical surface

  1. Confirm that the initial mirroring copy has completed for the required tables.
  2. Open the associated SQL analytics endpoint.
  3. Choose whether the recipient needs endpoint access or only a semantic model or report.
  4. Grant the minimum permissions supported by that analytical experience.
  5. Review the resulting access list.

For the distinction between item permissions and PostgreSQL access, see Item permissions and database access.

Validate analytical access

Have the recipient use their own identity to open the shared analytical item. For endpoint access, run a read-only query such as:

SELECT
    customer.customer_name,
    COUNT(order_row.order_id) AS order_count
FROM horizon_sample.customers AS customer
LEFT JOIN horizon_sample.orders AS order_row
  ON order_row.customer_id = customer.customer_id
GROUP BY customer.customer_id, customer.customer_name
ORDER BY customer.customer_name;

Use the schema name displayed by the SQL analytics endpoint if it differs from horizon_sample. For a report, validate the visible rows and totals against the intended audience. Mirroring is asynchronous, so communicate freshness.

Don't give the recipient the creator's credentials, and don't create PostgreSQL login roles to bypass the preview restriction.

Revoke shared access

  1. Remove access from the shared analytical item and any other permission path that grants the same access.
  2. Have the recipient reopen the analytical experience.
  3. Confirm that the intended analytical access is denied.

Review endpoint, semantic-model, report, and workspace permissions separately. Don't treat an analytical permission change as a PostgreSQL session-termination mechanism.