You manage two pooled host pools: Pool-US in East US and Pool-EU in West Europe. You need autoscale to start session hosts at 08:00 local time for each region using native Azure Virtual Desktop scaling plans. You want to minimize objects while ensuring each region follows its own local time. What should you do?

Creating two separate scaling plans, each configured with the appropriate regional time zone (East US for Pool-US and West Europe for Pool-EU), directly addresses the requirement for session hosts to start at 08:00 local time in each respective region. This approach ensures that the scaling actions are synchronized with the local business hours of each host pool. A single scaling plan set to UTC would not account for the time difference between East US and West Europe, causing one region to scale incorrectly relative to its local 08:00. A single scaling plan cannot have different time zones assigned per host pool association; time zone is a plan-level setting. Enabling "Start VM on connect" is a user-driven scaling mechanism, not a scheduled autoscale solution, and would not guarantee hosts are ready at 08:00.