Extend Fabric REST API to Include Cloud Connection Status and Tenant-Wide Visibility for Admins

[SaiValipireddy]

Description:

Microsoft Fabric currently provides a REST API to retrieve metadata about cloud connections (GET /v1/connections/{connectionId}), but it lacks two critical capabilities for administrators:

• Live connection status (e.g., online/offline)
• Tenant-wide visibility of all cloud connections without requiring explicit access to each individual connection

These limitations hinder proactive monitoring, automation, and governance in enterprise environments.

Proposed Enhancements:

• Extend the Fabric REST API to include: Connection health status (online/offline)
• Introduce a new admin-level endpoint to:
  • List all cloud connections across the tenant
  • Include health status

Benefits:

• Enables automated monitoring of cloud connection health
• Supports CI/CD pipelines with pre-deployment checks
• Reduces manual effort in troubleshooting refresh failures
• Improves governance and observability for platform teams
• Empowers admins to audit and manage connections centrally

Use Case Example: As a Fabric Platform Lead, I want to periodically check the status of all gateway / cloud connections used in semantic models and dataflows across the tenant. If any are offline or misconfigured, I can proactively alert owners or reauthenticate the connections managed by myself— all without relying on manual UI checks or refresh failure logs.

This capability is essential for maintaining reliability and performance in large-scale deployments.

[tkakiuchi]

Strongly agree with this. A tenant-wide admin endpoint to list all cloud connections without per-connection access is exactly what we need — GET /v1/connections is caller-scoped today, so admins can't inventory the tenant. Please also include the SSO state in the output (credentialDetails.singleSignOnType / credentialType), so admins can periodically audit which connections have SSO enabled/disabled across the tenant.