Forum Discussion
Bug in Fabric API SDK - Creating Azure SQL Mirror Database
When creating a mirrored database using a test licence on the workspace, everything works as expected. However, when changing to a fabric licence I get the below error. I have tried scaling up to a F32 sku and have the same problem.
On any sku from F2 to F32 I am able to create the mirrored database in the UI, just not via this API SDK. We like to have the service principal own all the workspace objects so using the API is quite important to us.
We are using v1.0.0 of Microsoft.Fabric.Api Nuget package.
Content:
{"requestId":"deb6b398-dc4f-4205-9330-f9eb9a09d8e5","errorCode":"FeatureNotAvailable","message":"The feature is not available"}
Headers:
Cache-Control: no-store, must-revalidate, no-cache
Pragma: no-cache
Transfer-Encoding: chunked
x-ms-public-api-error-code: REDACTED
Strict-Transport-Security: REDACTED
X-Frame-Options: REDACTED
X-Content-Type-Options: REDACTED
RequestId: REDACTED
Access-Control-Expose-Headers: REDACTED
request-redirected: REDACTED
home-cluster-uri: REDACTED
Date: Mon, 03 Nov 2025 09:00:23 GMT
Content-Type: application/json; charset=utf-8
Azure.RequestFailedException: The feature is not available
Status: 403 (Forbidden)
Content:
{"requestId":"deb6b398-dc4f-4205-9330-f9eb9a09d8e5","errorCode":"FeatureNotAvailable","message":"The feature is not available"}
at Microsoft.Fabric.Api.MirroredDatabase.ItemsRestClient.CreateMirroredDatabaseAsync(Guid workspaceId, CreateMirroredDatabaseRequest createMirroredDatabaseRequest, CancellationToken cancellationToken) in /_/SDKs/csharp/Generated/MirroredDatabase/ItemsRestClient.cs:line 211
at Microsoft.Fabric.Api.MirroredDatabase.ItemsClient.CreateMirroredDatabaseAsync(Guid workspaceId, CreateMirroredDatabaseRequest createMirroredDatabaseRequest, CancellationToken cancellationToken) in /_/SDKs/csharp/Generated/MirroredDatabase/ItemsClient.cs:line 94
JAnder Assuming the Service Principal is part of the security groups which the admin switch is enabled for them I don't have any other ideas for configurations that might be missing.
I did see issues in the past where Fabric didn't resolve correctly security groups memberships for users, especially service principals.
I don't know if a trial license doesn't require the admin switch to be enabled for creating items.
I would suggest (if possible) to temporarily enable the "Users can create fabric items" setting for the entire organization and try to see if the issue is indeed related to that setting. Note that you might have to wait some time for the change to take affect.
4 Replies
JAnder I suggest you make sure that the admin switch for creating items is enabled in Fabric's admin portal.
The item type you are trying to create is a GA item, so there's an admin switch that controls whether Fabric GA items can be created by users in the tenant.
There's also a possibility for capacity admins to override the tenant level configuration for a specific capacity,so you can check there as well.
Reference: Enable Microsoft Fabric for your organization - Microsoft Fabric | Microsoft Learn
Thanks for the reply Amos. Under Tenant Settings and "Users can create fabric items" we have a security group which includes the service principal used when creating the mirror. In the fabric capacity settings, under "delegated tenant settings", we do not have any of the overrides in use.
Are there any specific settings that might impact this working. With it working on a trial licence that would indicate an issue with the setup I agree.
JAnder Assuming the Service Principal is part of the security groups which the admin switch is enabled for them I don't have any other ideas for configurations that might be missing.
I did see issues in the past where Fabric didn't resolve correctly security groups memberships for users, especially service principals.
I don't know if a trial license doesn't require the admin switch to be enabled for creating items.
I would suggest (if possible) to temporarily enable the "Users can create fabric items" setting for the entire organization and try to see if the issue is indeed related to that setting. Note that you might have to wait some time for the change to take affect.
