Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Communications on default checkbox changes on tenant settings and billing start for SQL database in Fabric

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Action date

7 Mar 2025 619d ago Act by , as Microsoft's metadata states

What the notice says

Microsoft’s text, safely structured

We want to announce an upcoming change in the behavior of an existing tenant setting in Fabric that lets Fabric admins enable SQL database in their Fabric tenant. We will be introducing a checkbox on February 8, 2025, for tenant admins to accept Microsoft’s default selection (off for entire organization) for this specific setting. The default value for this setting will be turned on or after March 8th if Fabric admins do not take any action.

This update helps enhance visibility and ease of access for our customers, ensuring you're aware of and can leverage this functionality effortlessly.

Note also, billing for compute usage and data storage for SQL databases in Fabric commenced after February 1st, with backup charges following after April 1st. For the latest updates on billing practices and to ensure you are fully informed on how charges are applied, please refer to the following detailed blog post: Monitor SQL database usage and consumption in Microsoft Fabric.

Why are we updating this setting?

The update to our tenant settings is designed to ensure Fabric admins can act based on their organizational policy before the setting is enabled by default. From February 8, 2025, when the checkbox is available to March 8, 2025, admins can assess impact and act on enablement. By setting SQL database in Fabric as a default option, we ensure that you don’t miss out on leveraging its full potential right from the start. This change reflects our commitment to enhancing user experience and operational efficiency.

When This Will Happen

  1. The default activation of the checkbox for SQL database in Fabric is scheduled to commence on March 8th, 2025
  2. Billing for compute and data storage for SQL databases in Fabric commenced after February 1, 2025. Backup charges will commence after April 1, 2025.

What You Need to Prepare

  1. Review and Decide on Settings:
    • Enable SQL database in Fabric by Default: As this setting is ON by default, please review its implications and decide if it should be enabled for your organization.
  2. Action for M365 and Fabric Admins:
    • If no actions are taken on the tenant setting, SQL database in Fabric will remain active for all users, enhancing accessibility to database functionalities. If your organization prefers not to have this setting enabled by default, tenant admins must manually turn OFF this setting within the next 30 days.
    • We encourage you to assess these new settings and make any necessary changes to align with your organization's compliance and data storage policies.
  3. Review and Prepare for Billing Start:
    • As billing for compute and data storage commenced after February 1, 2025, and backup charges will commence after April 1, 2025, it is essential to conduct a comprehensive review of your current and projected usage to anticipate charges.

If you have any questions or need further assistance, please do not hesitate to contact our support team.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

No related announcements were found in the saved public history. Check the source for newer announcements.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 03:41 UTC · 274 of 275 readable · 259 fully read · 11 waiting for GitHub's hourly limit · documentation 469/469 current