Forum Discussion
SQl Database Preview CheckBox
In the admin settings, I have enabled creation of SQL database preview only for a specific security group. However, I am unable to uncheck the box for 'fabric admins can create' which is inherited tenant setting. Is this disabled for fabric admins outside of the security group that I specified, or are they still able to create this in their capacity? I would not like them to be able to create it unless they are a member of the security group that I listed in the settings.
Hello SeattlePowerBI - I do see that SQL Databases (and a few other features) have the 'capacity admins can enable/disable' checked without the ability to uncheck it. I tested and have confirmed that capacity admins can enable this for all users in the respective capacity, even those that are not included in the security groups specified at the tenant level. I have submitted a ticket to get feedback on how this can be controlled.
Support Request ID 2505120040010670
8 Replies
Hi SeattlePowerBI,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like you are facing challenges while unchecking the "fabric admins can create" setting box. As jennratten already responded to your query, please go through the response and check if it answers your query.
I would also take a moment to thank jennratten, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hello SeattlePowerBI - I do see that SQL Databases (and a few other features) have the 'capacity admins can enable/disable' checked without the ability to uncheck it. I tested and have confirmed that capacity admins can enable this for all users in the respective capacity, even those that are not included in the security groups specified at the tenant level. I have submitted a ticket to get feedback on how this can be controlled.
Support Request ID 2505120040010670
Hi SeattlePowerBI ,
You're correct in observing that the checkbox for "Fabric admins can create" is inherited from the tenant-level setting, which means it cannot be overridden at the workspace or capacity level unless that tenant setting is changed.
Even if you've restricted SQL Database Preview creation to a specific security group, Fabric admins may still retain the ability to create it if the tenant-level setting allows it. This is because tenant settings take precedence over scoped security group restrictions.
To ensure that only members of your specified security group can create SQL Database Previews, you would need to:
- Disable the tenant-level setting that allows Fabric admins to create SQL Database Previews.
- Then, enable it only for the specific security group you’ve defined.
If you don’t have access to tenant-level settings, you may need to coordinate with your global administrator.
Hope this clarifies things!
I will try disabling this setting in tenant, unchecking the box, then enabling again with security groups. Unfortuantely, this creates a service disruption for exisiting users in those security groups. MS should fix by allowing checking / unchecking regardless. We missed the notification about this being enabled by default and now would like to remove it but can't without causing an issue for our Fabric user base.
You're absolutely right—this limitation in the current tenant setting behavior creates a real challenge for managing access cleanly. The fact that disabling the tenant-level setting causes a disruption for users already relying on SQL Database Preview is definitely not ideal, especially when the feature was enabled by default without clear notification.
It would be much more effective if Microsoft allowed toggling the "Fabric admins can create" checkbox independently of the tenant-level setting, or at least provided a graceful transition mechanism for existing users. Until then, the workaround you mentioned—temporarily disabling and re-enabling with scoped security groups—is the only viable path, albeit disruptive.
Hopefully, Microsoft will consider improving this experience in a future update. In the meantime, documenting this behavior internally and coordinating closely with tenant/global admins seems essential to avoid unexpected service interruptions.
