When you use Copilot in Outlook to draft a meeting invitation or suggest a time for attendees in different time zones, the proposed time may display incorrectly. The meeting might show the wrong hour, or the time zone label might not match the recipient’s local region. This happens because Copilot reads the time zone setting from your Windows system clock but does not always convert it correctly for each attendee. This article explains why the time zone mismatch occurs and provides a step-by-step fix to ensure Copilot schedules meetings with the correct time zone for all participants.
Key Takeaways: Fixing Copilot Time Zone Errors in Outlook
- Windows Settings > Time & Language > Date & time > Time zone: Set to your current region and enable automatic time zone detection to prevent Copilot from using an incorrect base time.
- Outlook Calendar > Meeting invite > Time zone selector: Manually set the meeting time zone before using Copilot to generate the invitation; this overrides the default system time zone.
- Copilot pane > Time zone confirmation prompt: Read the time zone label in the Copilot-generated suggestion before sending; if incorrect, regenerate the proposal with the correct zone selected.
Why Copilot in Outlook Misreads Time Zones During Cross-Region Scheduling
Copilot relies on the Windows time zone setting as its primary reference point when it generates a meeting time. The feature does not automatically detect the time zone of each attendee from their Exchange Online mailbox. Instead, it applies the organizer’s local time zone to the entire proposal. If the organizer’s system clock is set to a time zone that does not match their actual location, or if the meeting includes participants from multiple regions, the displayed time can shift by several hours.
A second cause is the way Copilot handles time zone abbreviations. Outlook stores time zone information using Windows display names such as “Eastern Standard Time” or “Pacific Standard Time.” Copilot may use a different abbreviation in its natural language response, creating confusion. For example, Copilot might say “2:00 PM EST” when the actual meeting time is 2:00 PM EDT, which is a one-hour difference during daylight saving time.
The bug also appears when Copilot suggests a meeting time that spans a daylight saving transition. The feature does not always account for the shift, resulting in a proposed time that is off by one hour for attendees in regions that observe daylight saving.
Steps to Correct the Time Zone in Copilot Meeting Suggestions
Follow these steps in order to ensure Copilot uses the correct time zone for every cross-region meeting.
- Verify your Windows time zone setting
Open Windows Settings. Go to Time & Language > Date & time. Confirm that the Time zone dropdown shows your current region. Turn on the toggle for Set time zone automatically if you travel frequently. A correct system clock is the foundation for all Copilot time calculations. - Open Outlook and start a new meeting
In Outlook Calendar, click New Event or New Meeting. Do not use Copilot yet. First, click the Time zone button in the ribbon or the event details area. A second time zone row will appear below the start and end time fields. - Set the primary meeting time zone
In the start time field, click the time zone label next to the hour. Select the correct time zone for the meeting location. For example, if the meeting is for a team in London, choose GMT Standard Time. This step overrides the Windows default. - Add a second time zone if needed
If you need to see the meeting time in another region, click the second time zone row and select the additional zone. Outlook will display both times. This helps Copilot interpret the intended schedule correctly. - Use Copilot to draft the invitation
Click the Copilot icon in the toolbar or press Alt+I to open the Copilot pane. Type a prompt such as “Draft a meeting invitation for a 60-minute status update at the time shown.” Copilot will read the time zone you set in step 3 and generate the text accordingly. - Inspect the time zone in the Copilot output
Before sending, read the time zone abbreviation in the Copilot-generated body. If it says EST but you intended EDT, or if the time appears to be in a different zone, click the Regenerate button in the Copilot pane. Then manually specify the time zone in your prompt, for example: “Draft a meeting invitation for 2:00 PM Eastern Daylight Time.” - Send a test invitation to yourself
After you generate the invitation, send it to your own email address. Open the received meeting in your calendar. Verify that the start time matches the intended time in your local zone. If it does not, repeat step 6 with a more explicit prompt.
If Copilot Still Shows the Wrong Time Zone After the Main Fix
Copilot Uses a Different Time Zone Than the One I Set in Outlook
This happens when the Windows time zone and the Outlook meeting time zone are different. Copilot may give priority to the Windows system setting. To resolve this, close Outlook. Change your Windows time zone to match the meeting time zone you want. Reopen Outlook and create the meeting again. After you send the invitation, you can change your Windows time zone back to your local one.
Copilot Proposes a Meeting Time That Is One Hour Off During Daylight Saving Transitions
Daylight saving time boundaries cause this bug. Copilot does not always check whether the proposed date falls within the daylight saving period for the selected time zone. Fix this by manually setting the meeting time zone to a location that does not observe daylight saving, such as UTC. Alternatively, write your prompt to include the UTC offset explicitly. Example prompt: “Draft a meeting invitation for 3:00 PM UTC.”
Copilot Suggests a Meeting Time That Shows the Wrong Hour for Attendees in Other Regions
This occurs when Copilot applies the organizer’s time zone to the entire attendee list. The feature does not convert the time for each recipient. To work around this, add a note in the meeting body that states the time zone you used. Ask attendees to check their local time using the Outlook time zone converter. You can also use the Scheduling Assistant in Outlook to see each attendee’s local time before sending the invitation.
| Item | Windows System Time Zone | Outlook Meeting Time Zone |
|---|---|---|
| Description | Global setting used by all apps on the device | Per-meeting setting that overrides the system zone |
| Where to change | Settings > Time & Language > Date & time | Outlook Calendar event > Time zone button |
| Effect on Copilot | Copilot uses this as the default if no meeting zone is set | Copilot reads this zone when generating the invitation text |
| Best practice for cross-region meetings | Set to your current location | Set to the meeting host’s time zone or UTC |
After you apply the fixes above, Copilot will generate meeting invitations that display the correct time for all attendees. Always double-check the time zone abbreviation in the Copilot output before clicking Send. For complex schedules involving three or more time zones, set the meeting time zone to UTC to avoid confusion. This approach removes daylight saving ambiguity and gives each attendee a fixed reference point.