Reference
IT administrator configuring time zone settings in Microsoft Intune admin center
Cloud ComputingIntermediate

How to Configure Time Zone Settings for Windows Devices Using Microsoft Intune

Deploy consistent time zone configurations across Windows devices in your organization using Microsoft Intune's Settings Catalog. Create profiles, target device groups, and ensure synchronized time settings.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
March 12, 202615 min read8 Steps

What You Need

  • Microsoft Intune Plan 1 or Microsoft 365 E3/E5 license
  • Global Administrator or Intune Administrator role in Microsoft Entra ID
  • Windows 10 (version 1903+) or Windows 11 devices enrolled in Intune
  • Access to Microsoft Intune admin center at https://intune.microsoft.com
  • Target devices must be Microsoft Entra ID joined or hybrid joined

Why Should You Manage Time Zone Settings Through Microsoft Intune?

Managing time zone settings across an organization's Windows devices ensures consistency for scheduled tasks, meeting times, log timestamps, and compliance requirements. Without centralized management, devices might have incorrect time zones, leading to confusion in global organizations and potential security issues with time-sensitive authentication.

Microsoft Intune's Settings Catalog provides the most reliable method for deploying time zone configurations to Windows 10 and Windows 11 devices. This approach uses native Windows policies and ensures settings persist even after user modifications.

What Are the Prerequisites for Configuring Time Zones in Intune?

Before starting this configuration, ensure you have the proper licensing and permissions. You'll need Microsoft Intune Plan 1 or Microsoft 365 E3/E5 licensing, along with Global Administrator or Intune Administrator roles in Microsoft Entra ID.

Your target devices must be running Windows 10 version 1903 or later, or any version of Windows 11. These devices need to be enrolled in Microsoft Intune and either Microsoft Entra ID joined or hybrid joined. The Intune management extension will automatically deploy to devices when you use Settings Catalog policies.

How Do You Identify the Correct Windows Time Zone ID?

Windows uses specific internal identifiers for time zones that differ from display names. Getting this right is crucial for successful policy deployment.

Open PowerShell as Administrator on any Windows device and run this command to see all available time zones:

Get-TimeZone -ListAvailable | Format-Table Id, DisplayName -AutoSize

The Id column contains the exact values you'll use in Intune. Common time zone IDs include:

RegionTime Zone IDDisplay Name
US East CoastEastern Standard Time(UTC-05:00) Eastern Time
US West CoastPacific Standard Time(UTC-08:00) Pacific Time
UK/IrelandGMT Standard Time(UTC+00:00) Dublin, Edinburgh, Lisbon, London
Central EuropeW. Europe Standard Time(UTC+01:00) Amsterdam, Berlin, Bern, Rome
IndiaIndia Standard Time(UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi
JapanTokyo Standard Time(UTC+09:00) Osaka, Sapporo, Tokyo

Verify your current time zone format with:

Get-TimeZone | Format-List Id, DisplayName
Warning: Time zone IDs are case-sensitive and must match exactly. Using display names, abbreviations like "EST" or "PST", or incorrect capitalization will cause policy failures.

How Do You Create a Time Zone Configuration Profile in Intune?

Navigate to the Microsoft Intune admin center at https://intune.microsoft.com and sign in with your administrator credentials. The interface has been streamlined in 2026, making policy creation more intuitive.

From the left navigation menu, click Devices > Configuration to access your configuration profiles. Click Create > New policy to start the profile creation wizard.

Select these options:

  • Platform: Windows 10 and later
  • Profile type: Settings catalog

Click Create to proceed to the profile configuration.

On the Basics page, provide a clear, descriptive name that indicates the time zone and target audience. Examples:

  • Corporate Time Zone - Eastern US Offices
  • Time Zone Policy - London Operations
  • APAC Time Zone - Singapore Standard

Add a detailed description explaining the policy's purpose and scope. This helps other administrators understand the configuration later.

What Settings Should You Configure in the Time Zone Policy?

The Settings Catalog approach provides granular control over Windows time zone settings. On the Configuration settings page, click Add settings and search for "time zone" in the settings browser.

Expand Time language settings from the search results and select Configure Time Zone. This setting directly controls the system time zone and prevents users from changing it.

In the Configure Time Zone field, enter the exact time zone ID you identified earlier. For example:

Eastern Standard Time

The policy will enforce this time zone on all assigned devices, overriding any user-configured settings. Users will see "Some settings are managed by your organization" in the Windows Settings app, indicating the policy is active.

Pro tip: Consider creating separate profiles for different regions rather than one massive global policy. This approach makes troubleshooting easier and allows for more targeted deployments.

How Should You Assign Time Zone Policies to Device Groups?

Proper group assignment ensures the right devices receive the appropriate time zone settings. On the Assignments page, click Add groups under Included groups.

Choose assignment strategies based on your organizational structure:

  • All devices: For organizations with a single primary time zone
  • Regional device groups: For multi-location organizations with different time zones
  • Dynamic device groups: Based on device attributes like location or department
  • Static device groups: Manually managed groups for specific device sets

You can also exclude specific groups. For example, exclude devices used by traveling executives who need automatic time zone detection, or exclude conference room devices that might need different settings.

Consider these assignment scenarios:

ScenarioAssignment StrategyExample Groups
Single officeAll devicesAll Corporate Devices
Multi-regionalLocation-based groupsUS East Coast Devices, EMEA Devices
Department-specificRole-based groupsFinance Laptops, Sales Tablets
Mixed requirementsInclusion + ExclusionInclude: All Devices, Exclude: Executive Laptops

How Do You Monitor and Verify Time Zone Policy Deployment?

After creating the profile, monitor its deployment progress through the Intune admin center. Navigate to Devices > Configuration and click on your time zone profile.

The Device status tab shows deployment progress across assigned devices. Status indicators include:

  • Succeeded: Policy applied successfully
  • Pending: Device hasn't checked in yet
  • Error: Policy application failed
  • Not applicable: Device doesn't support the setting

Devices typically receive policies within 15-30 minutes of the next check-in cycle. You can force immediate sync for testing:

From Intune Admin Center:

  1. Go to Devices > All devices
  2. Select a target device
  3. Click Sync
  4. Wait 2-3 minutes for completion

From the Device:

  1. Open Settings > Accounts > Access work or school
  2. Click your Intune enrollment
  3. Click Sync

PowerShell Method:

Get-ScheduledTask | Where-Object {$_.TaskName -eq "PushLaunch"} | Start-ScheduledTask

How Do You Verify Time Zone Settings on Target Devices?

Once policies deploy, verify they're working correctly on target devices. Open PowerShell as Administrator and run:

Get-TimeZone | Format-List Id, DisplayName, StandardName, DaylightName

The output should match your configured time zone. You can also verify through the Windows Settings interface:

  1. Open Settings > Time & Language > Date & time
  2. The time zone dropdown should be grayed out
  3. Text should indicate "Some settings are managed by your organization"
  4. The displayed time zone should match your policy

To check policy application events and troubleshoot issues:

Get-EventLog -LogName System -Source "Microsoft-Windows-Kernel-General" -Newest 10 | Where-Object {$_.Message -like "*time zone*"}

For comprehensive verification, check these additional elements:

  • Registry verification: Check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
  • Group Policy results: Run gpresult /h report.html to see applied policies
  • Intune management extension logs: Check C:\ProgramData\Microsoft\IntuneManagementExtension\Logs
Pro tip: If settings appear grayed out with "managed by organization" text, that's the expected behavior. This indicates the policy is successfully enforced and users cannot override the time zone setting.

What Are Common Issues and How Do You Troubleshoot Them?

Several common issues can occur when deploying time zone policies through Intune. Here are the most frequent problems and their solutions:

Policy Not Applying (15-90 minute delays):

  • Force device sync through Intune admin center or device settings
  • Restart the target device to trigger immediate policy refresh
  • Check device enrollment status and Intune connectivity
  • Verify the device is in the assigned groups

Incorrect Time Zone ID Errors:

  • Verify the time zone ID matches exactly with Get-TimeZone -ListAvailable
  • Check for typos, extra spaces, or incorrect capitalization
  • Don't use display names or abbreviations like "EST" or "PST"

Settings Grayed Out on Devices:

This is normal behavior when policies are enforced. Users will see "Some settings are managed by your organization" in the Windows Settings app. This indicates successful policy application, not a problem.

Cloud PCs (Windows 365) Issues:

  • Local user device time zone may override Cloud PC settings
  • Create separate policies specifically targeting Cloud PC device groups
  • Consider enabling automatic time zone detection for Cloud PCs

Dynamic Time Zone Requirements:

Intune's native Settings Catalog only supports static time zone enforcement. For dynamic time zone detection based on location, you'll need additional configuration:

  • Enable location services through additional Intune policies
  • Deploy PowerShell remediation scripts for advanced scenarios
  • Use custom OMA-URI settings for location-based automatic detection
Warning: Avoid deploying conflicting time zone policies to the same devices. Multiple policies can cause unpredictable behavior and policy application failures.

For advanced troubleshooting, check these log locations:

  • Intune Management Extension: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
  • Windows Event Logs: Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider
  • Registry changes: Monitor HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation for policy application

This comprehensive approach to time zone management through Microsoft Intune ensures consistent time settings across your Windows device fleet, improving operational efficiency and reducing time-related confusion in global organizations.

Step-by-Step Guide

1
Step 1 / 8

Identify the Correct Time Zone ID

Before creating any Intune policies, you need to identify the exact time zone ID that Windows uses internally. These IDs are different from display names and must be precise.

Open PowerShell as Administrator on any Windows device and run:

Get-TimeZone -ListAvailable | Format-Table Id, DisplayName -AutoSize

This command lists all available time zones. Look for the Id column - this is what you'll use in Intune. Common examples:

  • India Standard Time for India
  • W. Europe Standard Time for Western Europe
  • Eastern Standard Time for US East Coast
  • Pacific Standard Time for US West Coast

Verification: Check your current time zone with Get-TimeZone | Format-List Id, DisplayName to confirm the format.

2
Step 2 / 8

Access Microsoft Intune Admin Center

Navigate to the Microsoft Intune admin center and prepare to create a new configuration profile.

Open your web browser and go to https://intune.microsoft.com. Sign in with your administrator credentials.

From the left navigation menu, click Devices > Configuration. You'll see your existing configuration profiles here.

Click Create > New policy to start creating a new configuration profile.

Pro tip: Bookmark the Intune admin center URL. The old endpoint.microsoft.com redirects here, but using the direct URL is faster.

Verification: You should see the "Create a profile" wizard with platform and profile type options.

3
Step 3 / 8

Create the Time Zone Configuration Profile

Set up the basic profile configuration using the Settings Catalog approach, which provides the most granular control over Windows settings.

In the profile creation wizard:

  1. Platform: Select Windows 10 and later
  2. Profile type: Select Settings catalog
  3. Click Create

On the Basics page:

  • Name: Enter a descriptive name like Corporate Time Zone - Eastern US or Time Zone Policy - London Office
  • Description: Add details like Enforces Eastern Standard Time for consistency across all corporate devices

Click Next to proceed to configuration settings.

Verification: The profile name should clearly indicate which time zone and which devices it targets.

4
Step 4 / 8

Configure the Time Zone Setting

Add the specific time zone configuration to your profile using Intune's Settings Catalog.

On the Configuration settings page:

  1. Click Add settings
  2. In the search box, type time zone
  3. Expand Time language settings from the results
  4. Check the box next to Configure Time Zone
  5. Click Add

In the Configure Time Zone field that appears, enter the exact time zone ID you identified in Step 1. For example:

Eastern Standard Time

or

India Standard Time
Warning: The time zone ID is case-sensitive and must match exactly. Using display names or abbreviations will cause the policy to fail.

Click Next to proceed to assignments.

Verification: The setting should show "Configure Time Zone" with your specified time zone ID in the value field.

5
Step 5 / 8

Assign the Profile to Device Groups

Target specific device groups or all devices in your organization with the time zone policy.

On the Assignments page:

  1. Under Included groups, click Add groups
  2. Select the appropriate device groups:
    • All devices for organization-wide deployment
    • Specific Azure AD device groups for regional offices
    • Dynamic device groups based on location or department
  3. Click Select

You can also exclude specific groups if needed. For example, exclude devices used by traveling executives who need automatic time zone detection.

Pro tip: Create separate profiles for different regions rather than one massive policy. This makes troubleshooting and management much easier.

Click Next to review your configuration.

Verification: The assignments section should show your selected groups with the correct inclusion/exclusion settings.

6
Step 6 / 8

Deploy and Monitor the Configuration

Complete the profile creation and monitor its deployment across your targeted devices.

On the Review + create page:

  1. Review all your settings carefully
  2. Verify the time zone ID is correct
  3. Confirm the assigned groups are appropriate
  4. Click Create

The profile will now deploy to targeted devices. Monitor the deployment:

  1. Go to Devices > Configuration
  2. Click on your newly created time zone profile
  3. Click Device status to see deployment progress

Devices typically receive the policy within 15-30 minutes, but you can force immediate sync on test devices.

Verification: The Device status page should show "Succeeded" for devices that have received and applied the policy.

7
Step 7 / 8

Force Policy Sync on Target Devices

Speed up policy deployment by manually triggering sync on test devices to verify the configuration works correctly.

For immediate testing, force sync on a target device:

Method 1 - From Intune Admin Center:

  1. Go to Devices > All devices
  2. Find and click on a target device
  3. Click Sync at the top of the device page
  4. Wait 2-3 minutes for the sync to complete

Method 2 - From the Device Itself:

  1. Open Settings > Accounts > Access work or school
  2. Click on your Intune enrollment account
  3. Click Sync

Method 3 - PowerShell Command:

Get-ScheduledTask | Where-Object {$_.TaskName -eq "PushLaunch"} | Start-ScheduledTask

Verification: Check the last sync time in the device properties to confirm the sync completed successfully.

8
Step 8 / 8

Verify Time Zone Configuration on Devices

Confirm that the time zone policy has been applied correctly on target devices and troubleshoot any issues.

On a target device, open PowerShell as Administrator and run:

Get-TimeZone | Format-List Id, DisplayName, StandardName, DaylightName

The output should show your configured time zone. You can also check the Windows Settings:

  1. Open Settings > Time & Language > Date & time
  2. The time zone dropdown should be grayed out with text "Some settings are managed by your organization"
  3. The correct time zone should be displayed

To check policy application events:

Get-EventLog -LogName System -Source "Microsoft-Windows-Kernel-General" -Newest 10 | Where-Object {$_.Message -like "*time zone*"}
Pro tip: If settings appear grayed out, that's normal behavior indicating the policy is enforced. Users cannot override managed time zone settings.

Verification: The time zone should match your policy, and users should see the "managed by organization" message in Settings.

Frequently Asked Questions

How long does it take for Intune time zone policies to apply to Windows devices?
Time zone policies typically apply within 15-30 minutes of device check-in with Microsoft Intune. You can force immediate application by manually syncing the device through Settings > Accounts > Access work or school > Sync, or by restarting the device. The Intune management extension processes Settings Catalog policies during regular check-in cycles.
Can users override time zone settings managed by Microsoft Intune policies?
No, users cannot override time zone settings when they're managed by Intune policies. The time zone dropdown in Windows Settings becomes grayed out with the message 'Some settings are managed by your organization.' This is the intended behavior to ensure consistent time zone enforcement across corporate devices.
What's the difference between using Settings Catalog and Custom OMA-URI for time zone configuration in Intune?
Settings Catalog provides a user-friendly interface with built-in validation for time zone configuration, making it the recommended approach. Custom OMA-URI requires manual XML configuration and deeper technical knowledge but offers more advanced options like automatic time zone detection. Settings Catalog is more reliable and easier to troubleshoot for standard time zone enforcement scenarios.
How do you configure automatic time zone detection for traveling users with Intune?
Microsoft Intune's Settings Catalog doesn't natively support dynamic automatic time zone detection. You need to enable location services through additional policies and potentially deploy PowerShell remediation scripts. Alternatively, create separate time zone policies for different user groups and exclude traveling users from static time zone enforcement, allowing them to use Windows' built-in automatic detection.
Why might Intune time zone policies fail to apply to some Windows devices?
Common causes include incorrect time zone IDs (must match exactly with Get-TimeZone -ListAvailable output), devices not being in assigned Azure AD groups, Intune connectivity issues, or conflicting Group Policy settings. Check device enrollment status, verify group membership, ensure the time zone ID is case-sensitive and spelled correctly, and review Intune Management Extension logs for detailed error information.

About the Author

Emanuel DE ALMEIDA

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Last updated March 12, 2026

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...