This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Hi,
Can someone explain to me why the timestamp in the Power BI Service is not according to the selected Arizona time zone when it comes to refreshing?
The Refresh timestamp in Power BI after refresh whereas it is really 2:28 PM here in Arizona....
How do I fix this??
Thank you,
Holly
Solved! Go to Solution.
thats is M. Applied step name is automatically generated so DAX AZ time is not needed.
Hi @Anonymous ,
As @lbendlin has mentioned, Power BI Services operates in UTC time zone, so have to be adjusted using DAX or Power Query by adding offset to UTCNOW().
Thanks,
Pallavi
Yes, I know it is running on UTC time zone. However, I am NOT getting anywhere with the DAX...I am not sure where I am doing this wrong? I tried in Excel and Power BI Power Query....
DAX AZ TIME = DateTimeZone.SwitchZone(DateTimeZone.LocalNow(),-8,0)
Is this expected??
thats is M. Applied step name is automatically generated so DAX AZ time is not needed.
Working now 🙂 Thank you!
Volatile functions like TODAY(), NOW() and the M equivalents are based on UTC. Consider using
UTCNOW() + TIME(8,0,0)
or
UTCNOW() + DIVIDE ( 8,24 )
Replace 8 with your UTC offset
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 10 | |
| 8 | |
| 7 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 49 | |
| 27 | |
| 21 | |
| 20 | |
| 20 |