Using Outlook for Android in educational settings for communication and organization
The behavior is consistent with a one‑hour daylight saving time (DST) offset between what Outlook is using and what the device/calendar view is using.
In Outlook and Exchange, all calendar items are stored in UTC and then converted to local time based on:
- The time zone and DST rules of the device/Outlook client at creation time.
- The current Windows/device time zone and DST settings when the item is displayed.
If there is any mismatch in DST handling between the time zone rules and the current settings, the result is exactly a one‑hour shift between the time shown on the block and the position on the calendar grid. This is the same underlying issue described for Outlook on Windows when “Automatically adjust clock for Daylight Saving Time” is not aligned with the time zone rules: the UTC offset is off by one hour, so the calendar renders items one hour away from the intended slot.
Because all the usual fixes (reinstalling Outlook, clearing cache, toggling automatic time zone, checking Outlook on the web) are already done, the issue is almost certainly in how the device and Outlook mobile are interpreting DST for the selected time zone. The mismatch will be most visible around the days when DST starts or ends and can cause events to appear shifted by one hour in the visual grid while still showing the “correct” time text inside the item.
On affected days, Outlook’s calendar view can show incorrect offsets between time zones and misalign events, as documented for multiple time zones and DST transitions. The same normalization logic applies on mobile: Outlook converts from UTC to local using the device’s time zone and DST rules, so any discrepancy in those rules produces the one‑hour offset being observed.
If the problem persists across reinstalls and correct time zone settings, it is likely a client bug or a DST rules issue specific to the current Outlook for Android build on that device. In that case, the only durable resolution will be a client update from Microsoft that corrects the DST handling for that region/time zone.
References: