Currently, when a Power BI report is created in Desktop and then published to Fabric, the timestamps (like “Last Refreshed”) or any time-based visuals are tied to the Power BI Service’s default time zone (typically UTC) or the Fabric workspace’s server region, rather than automatically adjusting to the viewer’s local time zone. This becomes a challenge when the same report is used by clients or team members across multiple time zones. Everyone sees time-related data based on a fixed zone, which may lead to confusion, misinterpretation, or errors in decision-making. I propose the introduction of a built-in feature that allows reports to be time zone-aware. Specifically, this feature should: Help global teams collaborate on the same report without time-based confusion Improve clarity for refresh status, timelines, and date-based KPIs Reduce the need for complex DAX workarounds or custom columns to simulate local times This would significantly improve the experience for global teams who rely on consistent and localized reporting. This capability is especially important in today's distributed and remote work environments, where teams and clients are often located in different regions and time zones.
... View more