Public mode

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

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 16:45 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Fabric: Create support tickets from within Fabric

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

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, with source markup removed
What and Why Eligible Microsoft Fabric and Power BI users can now create support tickets directly within Microsoft Fabric from the Help pane. This update brings ticket creation into the product experience, allowing Microsoft to automatically capture relevant context (such as tenant and artifact metadata) to improve troubleshooting efficiency and reduce time to resolution. This change also aligns support workflows more closely with where users encounter issues. Rollout Schedule General Availability (Worldwide): Rollout begins in late June 2026 and is expected to complete in late June 2026. Impact on Your Organization Who is affected Microsoft Fabric users, based on tenant admin configuration Fabric admins managing tenant settings Platforms/Services Microsoft Fabric (web) Power BI (web) Power Platform Admin Center (PPAC) What will happen Users can create support tickets directly from the Help pane from anywhere in Fabric. (They don't need to navigate to the admin portal.) Users attempting to create support tickets for Power BI or Fabric from the Power Platform admin center (PPAC) will be redirected to the Fabric experience. When a ticket is created, Fabric includes contextual metadata (such as tenant and artifact identifiers) in the support request to assist troubleshooting. This experience provides more contextual information and centralizes support workflows within Fabric, improving troubleshooting and shifting where users initiate support requests. This experience is enabled by default; admins can control which users are able to create support tickets using existing tenant settings. Action Required / Recommendations Action may be required depending on your current configuration. Review tenant settings to ensure:Users are routed to the appropriate support experience (Microsoft support or internal help desk), and The correct users are permitted to create support tickets. If users are redirected to an internal help desk instead of creating tickets, verify the setting is configured correctly. Communicate this change to your helpdesk and support teams, especially if they currently rely on PPAC for ticket creation. Remind users to select the appropriate support plan and severity when submitting requests. Update internal documentation or support procedures, if applicable. Learn more: Publish "Get Help" information - Help and support tenant settings | Microsoft Fabric | Microsoft Learn Compliance considerations Question Answer Does the change include an admin control? Yes. Admins can control availability via the Publish "Get Help" information tenant setting. Does the change allow a user to enable/disable the feature themselves? Yes. User access depends on tenant configuration; users can create tickets if enabled by admin settings.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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 26 Oct 16:45 UTC · 272 of 272 readable · 271 fully read · documentation 469/469 current