Microsoft has launched Fabric API for GraphQL, moving the data access layer from public preview to general availability (GA). This release introduces several enhancements, including support for Azure SQL and Fabric SQL databases, saved credential authentication, detailed monitoring tools, and integration with CI/CD workflows.
The release supports Azure SQL and Fabric SQL databases (Preview). Developers can now query these databases directly using GraphQL, simplifying the integration of structured data into applications. Fabric SQL offers a streamlined experience, allowing developers to create GraphQL endpoints from databases with minimal configuration.
Looking ahead, Amir Netz, a CTO of Microsoft Fabric, confirmed plans to expand its database support further, including NoSQL databases.
Furthermore, the saved credentials feature provides an alternative to traditional client credentials. With this method, APIs access backend data sources through preconfigured connections rather than requiring user-specific credentials for each call. This approach not only reduces the risk of exposing sensitive information but also simplifies permissions management across environments with multiple users and data sources. Client credential-based authentication remains an option for scenarios where user-specific access is required. Single sign-on (SSO) functionality is also supported, providing flexibility in how APIs connect to backend resources.
(Source: Microsoft's Blog)
The release also includes a monitoring dashboard that provides a clear view of API activity, helping developers analyze usage patterns, troubleshoot issues, and optimize performance. Metrics can be aggregated by time ranges, and detailed logs allow for deeper investigation of individual API requests.
The Fabric API for GraphQL now supports integration with GitHub and Azure DevOps repositories, allowing developers to maintain version control for API definitions. Deployment Pipelines simplify the movement of APIs across development, testing, and production environments. Developers can also automate deployments based on changes in API configurations, ensuring consistency and reducing manual intervention during the release process.
The release has garnered enthusiastic responses from the developer community. Chris Nunn commented:
The Fabric ecosystem just got a new family member, and wow what an addition! This really rounds out Fabric's vision and gives customers a choice of engine to best tackle any workload.
Raghavendra Prabhu added:
Kudos to Microsoft and the Fabric team for this big announcement timed appropriately, around the first anniversary of Fabric GA. With this announcement of databases, Fabric completes the ART (Analytics, Real-Time, Transactions) of the Data Platform.
Questions about cost implications were also raised. Emmanuel O. Appiah asked if the new API would require separate billing beyond capacity units. Amir Netz answered that no additional costs would be incurred.
Further details can be found in the official documentation.
