Forum Discussion

david_restrepo's avatar
david_restrepo
New Member
9 months ago
Solved

Fabric Alerts Activation time

Hi everyone,

I’m using Microsoft Fabric alerts, and when the alert is triggered, the Teams notification card displays an activation time in UTC. This is causing some confusion for users who expect to see local time or no timestamp at all.

I’m trying to find out:

  1. Is there a way to change the activation time shown in the Teams alert card to use local time instead of UTC?

  2. If not, is it possible to remove the activation time from the Teams card altogether?

I haven’t been able to find a configuration option for this in Fabric or in the Teams connector settings. Any guidance, workarounds, or confirmation on whether this is customizable would be greatly appreciated.

Thanks!

  • there’s currently no supported way to change or remove the “activation time” shown in UTC on the Fabric Activator -> Teams card.

     

    Here’s what I found:

    • Fabric currently operates in a single timezone (UTC) for capacity and system generated timestamps.

    • On the Fabric Community, this limitation has been acknowledged: there’s no config option to switch the alert timestamps to a different timezone. (https://community.fabric.microsoft.com/t5/Fabric-platform/Time-zone-for-Fabric-capacity/m-p/3588388)

    • There’s no documented setting in the activator rule or Teams connector to suppress or hide the activation timestamp. The standard “Set alert” flow only lets you pick where to send the notification, not how the timestamp is formatted or displayed.

    Workarounds/suggestions:

    1. Raise this on the Microsoft Fabric Ideas forum  as this is a common ask.

    2. Instead of using the built-in Teams message, you could build a small Azure Function or Logic App that receives the alert webhook, reformats the timestamp to local time (or strips it out), and then posts to Teams.

    3. If your data source supports it, include a date/time column in local time (or convert it before generating the alert). But note that the “activation time” in the Teams card appears to be system driven, not derived from your data directly.

     

3 Replies

  • there’s currently no supported way to change or remove the “activation time” shown in UTC on the Fabric Activator -> Teams card.

     

    Here’s what I found:

    • Fabric currently operates in a single timezone (UTC) for capacity and system generated timestamps.

    • On the Fabric Community, this limitation has been acknowledged: there’s no config option to switch the alert timestamps to a different timezone. (https://community.fabric.microsoft.com/t5/Fabric-platform/Time-zone-for-Fabric-capacity/m-p/3588388)

    • There’s no documented setting in the activator rule or Teams connector to suppress or hide the activation timestamp. The standard “Set alert” flow only lets you pick where to send the notification, not how the timestamp is formatted or displayed.

    Workarounds/suggestions:

    1. Raise this on the Microsoft Fabric Ideas forum  as this is a common ask.

    2. Instead of using the built-in Teams message, you could build a small Azure Function or Logic App that receives the alert webhook, reformats the timestamp to local time (or strips it out), and then posts to Teams.

    3. If your data source supports it, include a date/time column in local time (or convert it before generating the alert). But note that the “activation time” in the Teams card appears to be system driven, not derived from your data directly.

     

  • What's wrong with showing that in UTC?  Teams may not be able to figure out which timezone the user is currently in.   Providing the timestamp in UTC removes the ambiguity.

  • v-ssriganesh's avatar
    v-ssriganesh
    Icon for Community Support rankCommunity Support

    Hi david_restrepo,

    Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to Vinodh247 for sharing valuable insights.

     

    Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

     

    Thank you for being part of the Microsoft Fabric Community.