如何在Azure中管理夏令时及修复Web Jobs夏令时调度偏移问题

Hey there! Let's break down your two Azure daylight saving time (DST) questions step by step—this is a super common gotcha, so I've got you covered.

When dealing with DST in Azure, the key is to minimize manual timezone conversions and leverage built-in support wherever possible:

• Prioritize UTC for all core scheduling and storage: Most Azure services operate on UTC under the hood. Storing times in UTC and using it for base scheduling avoids confusion when DST kicks in. Only convert to local time when presenting data to end users.
• Use Azure service timezone support: Many Azure services (like Web Jobs, Logic Apps, and Azure Automation) let you specify a local timezone instead of defaulting to UTC. These services automatically handle DST transitions if you pick a timezone that observes it (e.g., "Mountain Standard Time").
• Handle timezone conversions in code intentionally: If your application needs to work with local times, use platform-native tools like .NET's TimeZoneInfo class. For example, TimeZoneInfo.FindSystemTimeZoneById("Mountain Standard Time") will automatically account for DST when converting between local time and UTC.
• Validate configurations before DST transitions: A quick check a week or so before DST starts/ends ensures your scheduled tasks, alerts, and time-based logic are set up to adjust correctly.

It sounds like your Web Job is scheduled using a hardcoded UTC time that mapped to MST 8:00 pre-DST, but now that DST is active, MST becomes MDT (Mountain Daylight Time)—so UTC 15:00 translates to MDT 9:00. Here's how to fix this:

• Configure the Web Job to use your local timezone directly:
  • If you're setting up the trigger via the Azure Portal, when defining the schedule, select Mountain Standard Time from the timezone dropdown instead of UTC. Then set the trigger time to 8:00 AM. Azure will automatically adjust the underlying UTC time when DST starts or ends.
  • If you're using a settings.job file for a triggered Web Job, add the timeZoneId property to specify your timezone, and set the cron schedule to your desired local time. Example:

    {
      "schedule": "0 0 8 * * *",
      "timeZoneId": "Mountain Standard Time"
    }
    

• Avoid hardcoding UTC-to-local mappings: Never write logic that assumes a fixed offset (like MST = UTC-7). Timezone offsets change with DST, so relying on built-in timezone handling is far more reliable.
• Test the schedule: You can simulate DST transitions using tools like TimeZoneInfo.ConvertTime in your code to verify that the trigger fires at the correct local time regardless of the season.

内容的提问来源于stack exchange，提问作者Uday