Forum Discussion
Sending data outside Fabric
Hi Team,
Few questions around GrapghQL API:
1 )Can we create a 'writeAPI' using GRAPHQL in Fabric?
2) Do we have these security policies/validations while creating GRAPHQL APIs:
| Security Header / Policy |
| Content-Type Header |
| Content-Type-Options: nosniff |
| HTTP OPTION Method |
| WWW-Authenticate HTTP Header |
| Content Type Setting |
| Cross-Site Scripting Protection |
| Cache-Control Policy Header |
| Content Security Policy: |
| X-Frame-Options Header: |
| Access-Control-Allow-Origin Access-Control-Allow-Headers Access-Control-Allow-Methods |
| COOKIE POLICY |
| Misconfiguration in CORS Implementation |
| GraphQL Introspection Enabled |
| data validations a. Data Type b. Range, Length, Size c. Format d. Values" |
3) Is there a branching feature in GraphQL API also?
4) Is JSONB format supported?
Thanks
Hello ati_puri
1) GraphQL does indeed support mutations (write operations). However, data sources accessed via SQL Analytics Endpoints are read-only and therefore only allow queries (read operations). For Data Warehouses, a primary key must be defined in order for mutations to be generated automatically.
For further details, please see the GraphQL FAQ:
Microsoft Fabric API for GraphQL FAQ - Microsoft Fabric | Microsoft Learn
2) It is advisable to place your GraphQL API behind Azure API Management and implement security policies there. Through APIM, you can configure or validate settings such as Content-Type, HTTP OPTIONS, WWW-Authenticate, Cache-Control, and CORS, among others.
3) For source control, it is best practice to branch the API for your GraphQL item and promote it through different environments, rather than creating multiple versioned GraphQL endpoints.
4) Currently, the JSONB format is not supported.
2 Replies
Hello ati_puri
1) GraphQL does indeed support mutations (write operations). However, data sources accessed via SQL Analytics Endpoints are read-only and therefore only allow queries (read operations). For Data Warehouses, a primary key must be defined in order for mutations to be generated automatically.
For further details, please see the GraphQL FAQ:
Microsoft Fabric API for GraphQL FAQ - Microsoft Fabric | Microsoft Learn
2) It is advisable to place your GraphQL API behind Azure API Management and implement security policies there. Through APIM, you can configure or validate settings such as Content-Type, HTTP OPTIONS, WWW-Authenticate, Cache-Control, and CORS, among others.
3) For source control, it is best practice to branch the API for your GraphQL item and promote it through different environments, rather than creating multiple versioned GraphQL endpoints.
4) Currently, the JSONB format is not supported.
Thanks for the detailed response deborshi_nag
