, ,

Timezone Control in AVD & Windows 365 via Intune

Timezone Control in AVD & Windows 365 via Intune

Managing timezones in cloud-based desktops might seem trivial, but it can make or break user experience — especially in distributed teams. Whether you’re running Azure Virtual Desktop (AVD) or Windows 365 Cloud PCs, Intune gives you full control over how time is handled.

Let’s explore how to redirect the client timezone, when it’s already enabled by default, and how to lock it to a specific timezone if needed.

🌍 Timezone Redirection: AVD vs. Windows 365

  • AVD: Timezone redirection is not enabled by default. You need to explicitly allow it via policy.
  • Windows 365: Timezone redirection is enabled by default. Users see their local time without any extra configuration.

This means for AVD, you’ll want to enable it manually. For Windows 365, you might want to override it — for example, to enforce a consistent timezone across all Cloud PCs.

🛠️ Enabling Timezone Redirection in AVD

Use Intune’s Settings Catalog to allow the session host to use the client’s timezone.

Steps:

  1. Go to Devices > Configuration profiles
  2. Create a new profile:
    • Platform: Windows 10 and later
    • Profile type: Settings catalog
  3. Search for Allow Time Zone Redirection
  4. Set it to Enabled
  5. Assign to your AVD session hosts

This ensures that users see their local time, no matter where they connect from.

🧭 Enforcing a Specific Timezone in Windows 365

In some scenarios — like centralized support teams, compliance requirements, or shared shift environments — you may want all Cloud PCs or AVD Sessions to operate in the same timezone, regardless of user location.

To do this, you’ll need to disable timezone redirection first, and then set a fixed timezone via policy.

🔧 Step-by-Step: Enforce Timezone via Intune

  1. Create a new Settings Catalog profile
    • Platform: Windows 10 and later
    • Profile type: Settings catalog
  2. Disable Timezone Redirection
    • Search for Allow Time Zone Redirection
    • Set to Disabled
      This ensures the Cloud PC ignores the client’s local timezone.
  3. Configure a Fixed Timezone
    • Search for Configure Time Zone
    • Set to Enabled
    • Choose your desired timezone from the dropdown (e.g., W. Europe Standard Time for CET)
  4. Assign the profile
    • Target your Windows 365 Cloud PC device group
    • Review and create

Once applied, all Cloud PCs will operate in the specified timezone — regardless of where the user connects from.

💡 If you want to enforce a specific timezone via Intune, you’ll need to know the exact TimeZone ID — and PowerShell makes it easy to list all supported options.

Get-TimeZone -ListAvailable

Use the Id value (e.g., W. Europe Standard Time) when configuring the Configure Time Zone setting in Intune.

✅ Final Thoughts

Whether you want to respect the user’s local time or enforce a standard across your environment, Intune gives you the flexibility to do both. AVD needs a little help to redirect timezones, while Windows 365 is ready out of the box — but both can be shaped to fit your needs.

Time is precious. Make sure your virtual desktops know what time it is.

Leave a Reply

Your email address will not be published. Required fields are marked *