Validate required AD DS DNS resolution and domain-join service ports across the session-host network. This would be appropriate for the different task-specific situation "New session hosts fail domain join even though TCP connectivity to a domain controller appears possible", because AD DS domain join depends on correctly resolved domain services and more than a single open TCP port. It does not directly resolve the stated condition, which calls for Use AVD's brokered reverse-connect architecture and remove unnecessary public inbound RDP access.

Upgrade supported Windows App clients and confirm version prerequisites and multipath status. This would be appropriate for the different task-specific situation "Windows App clients running obsolete builds do not display the expected RDP Multipath transport options", because RDP Multipath feature availability depends on supported client platforms and minimum Windows App versions. It does not directly resolve the stated condition, which calls for Use AVD's brokered reverse-connect architecture and remove unnecessary public inbound RDP access.

Provide an approved noninteractive outbound proxy path for Azure Virtual Desktop service endpoints. This would be appropriate for the different task-specific situation "A web filtering proxy requires interactive authentication and prevents unattended AVD agent HTTPS communication", because Session-host agents require reliable machine-level service connectivity even when no user is signed in. It does not directly resolve the stated condition, which calls for Use AVD's brokered reverse-connect architecture and remove unnecessary public inbound RDP access.

Pooled host placement respects configured session limits and load-balancing behavior. This describes the separate situation "A pooled host receives far more simultaneous users than planned because its session cap is too high" but does not justify the selected fix for the current issue. The decisive behavior is: AVD session host provisioning relies on Azure Compute quotas, not only AVD host pool creation permissions.

Explicit target identifiers reduce the risk of management scripts changing the wrong desktop environment. This describes the separate situation "Administrators accidentally apply development host pool settings to the production resource group through an unscoped script" but does not justify the selected fix for the current issue. The decisive behavior is: AVD session host provisioning relies on Azure Compute quotas, not only AVD host pool creation permissions.

A repeatable host lifecycle reduces dependence on manual changes to individual desktops. This describes the separate situation "An operations team needs to replace unhealthy hosts using a clean image rather than repair each VM in place" but does not justify the selected fix for the current issue. The decisive behavior is: AVD session host provisioning relies on Azure Compute quotas, not only AVD host pool creation permissions.

Configure Start VM on Connect and the required platform permissions for the personal host pool. This would be appropriate for the different task-specific situation "The IT team wants to turn on a powered-off personal VM only when its assigned user connects", because Start VM on Connect permits a supported AVD connection attempt to initiate a deallocated session host VM. It does not directly resolve the stated condition, which calls for Generate a replacement registration token and rerun the authorized registration step.

Disable drain mode after verifying the host is healthy and ready for user traffic. This would be appropriate for the different task-specific situation "A host in drain mode remains excluded from fresh connections after patch maintenance finishes", because A session host stays unavailable for new placements until its drain state is removed. It does not directly resolve the stated condition, which calls for Generate a replacement registration token and rerun the authorized registration step.

Test required outbound service connectivity and correct proxy or firewall restrictions. This would be appropriate for the different task-specific situation "A private host pool is created but none of its session hosts can reach required Microsoft AVD control endpoints", because Session-host registration and ongoing broker signaling require reliable agent outbound communication. It does not directly resolve the stated condition, which calls for Generate a replacement registration token and rerun the authorized registration step.

Repair the profile share's identity-based authentication, share roles and NTFS ACLs. This would be appropriate for the different task-specific situation "A user's FSLogix VHD exists but sign-in falls back to a local temporary profile due to SMB access denial", because FSLogix cannot attach a profile disk when the user or host cannot access the backing container. It does not directly resolve the stated condition, which calls for Configure and test valid multiple Cloud Cache provider entries and monitor replication state.

Use supported FSLogix storage plus an independently tested snapshot and backup strategy. This would be appropriate for the different task-specific situation "A tenant wants both profile portability and recoverable historical profile data", because FSLogix provides profile roaming, while separate storage protection covers deletion and corruption recovery. It does not directly resolve the stated condition, which calls for Configure and test valid multiple Cloud Cache provider entries and monitor replication state.

Evaluate supported profile VHD compaction and cleanup procedures during maintenance. This would be appropriate for the different task-specific situation "FSLogix container VHDs remain very large after users delete files inside their Windows profiles", because Deleting content inside a virtual disk does not necessarily shrink its backing VHDX file immediately. It does not directly resolve the stated condition, which calls for Configure and test valid multiple Cloud Cache provider entries and monitor replication state.

Review host pool load balancing and session caps to distribute connections appropriately. This would be appropriate for the different task-specific situation "A pooled desktop host's maximum session limit causes users to wait although spare CPU exists on other hosts", because Placement settings can prevent optimal use of available pooled compute capacity. It does not directly resolve the stated condition, which calls for Use supported session management to disconnect or sign out the affected session after appropriate notification.

Choose a current supported AVD client for the device platform or use a compatible web client. This would be appropriate for the different task-specific situation "An administrator deploys a Remote Desktop client to an unsupported operating system and users cannot authenticate", because Client support is platform-specific, and not every remote access feature works on every device. It does not directly resolve the stated condition, which calls for Use supported session management to disconnect or sign out the affected session after appropriate notification.

Deploy and update the approved client through Microsoft Intune or another managed software channel. This would be appropriate for the different task-specific situation "A new Windows App release must reach all managed corporate laptops consistently", because Central client deployment reduces version drift and ensures supported feature availability. It does not directly resolve the stated condition, which calls for Use supported session management to disconnect or sign out the affected session after appropriate notification.

Create an authorized storage private endpoint and configure its associated private DNS resolution. This would be appropriate for the different task-specific situation "An Azure Files SMB profile share is reachable over a public endpoint that security policy forbids", because Private endpoints provide a private IP path to the Azure Storage file endpoint for eligible client networks. It does not directly resolve the stated condition, which calls for Configure the documented Active Directory connection and SMB volume permissions.

Increase the appropriate file-share quota and address per-profile growth under retention policy. This would be appropriate for the different task-specific situation "A file share has a low quota and reaches capacity during an organization-wide sign-in event", because Share capacity ceilings can block new profile writes even when underlying storage connectivity is healthy. It does not directly resolve the stated condition, which calls for Configure the documented Active Directory connection and SMB volume permissions.

Design a supported cross-region recovery solution with tested profile replication or backup and DNS cutover. This would be appropriate for the different task-specific situation "An organization wants its profile storage to tolerate a full Azure region outage", because Zone redundancy protects a zonal failure but does not alone provide recovery from a region-wide outage. It does not directly resolve the stated condition, which calls for Configure the documented Active Directory connection and SMB volume permissions.

Create a Log Analytics scheduled query alert over supported AVD diagnostic tables. This would be appropriate for the different task-specific situation "The team wants an alert if AVD connection failures exceed a threshold during business hours", because Log-based alerts can turn queryable connection error events into operational notifications. It does not directly resolve the stated condition, which calls for Use Azure Monitor Agent and an appropriate data collection rule for guest memory counters.

Choose one supported host power-management automation approach and disable conflicting schedules. This would be appropriate for the different task-specific situation "A team tries to run an Azure Automation shutdown script and AVD autoscale simultaneously on the same host pool", because Competing scalers can counteract one another and create unstable session-host availability. It does not directly resolve the stated condition, which calls for Use Azure Monitor Agent and an appropriate data collection rule for guest memory counters.

Add AVD-specific diagnostic settings and workbook queries to the monitoring design. This would be appropriate for the different task-specific situation "A team uses a generic Azure VM dashboard and assumes it covers all AVD application group connection failures", because General VM metrics cannot replace the service-specific events that explain remote resource access failures. It does not directly resolve the stated condition, which calls for Use Azure Monitor Agent and an appropriate data collection rule for guest memory counters.

A single resource-intensive app does not by itself prove every user needs dedicated desktop infrastructure. This describes the separate situation "A planning team proposes replacing all pooled desktops with personal VMs after noticing one application's high CPU use" but does not justify the selected fix for the current issue. The decisive behavior is: Application compatibility is a prerequisite for session-host OS and pooling decisions.

AVD control-plane resource location and virtual machine compute location are distinct design choices. This describes the separate situation "Administrators confuse the host pool's Azure region with the physical region of each session host VM" but does not justify the selected fix for the current issue. The decisive behavior is: Application compatibility is a prerequisite for session-host OS and pooling decisions.

Azure VM SKU and GPU availability varies by region and subscription quota. This describes the separate situation "A customer requires GPU-intensive design apps but cannot find its selected GPU VM family in the planned region" but does not justify the selected fix for the current issue. The decisive behavior is: Application compatibility is a prerequisite for session-host OS and pooling decisions.

App Masking can control application visibility without reinstalling the app per user. This describes the separate situation "An application that is installed on all pooled session hosts must be hidden from nonlicensed users" but does not justify the selected fix for the current issue. The decisive behavior is: Overly broad exclusions undermine the purpose of a roaming profile container.

Cloud Cache behavior depends on correctly configured remote providers and consistent local disk cache operation. This describes the separate situation "A Cloud Cache deployment lists unreachable remote profile storage providers and logons become very slow" but does not justify the selected fix for the current issue. The decisive behavior is: Overly broad exclusions undermine the purpose of a roaming profile container.

Profile detach and cache synchronization can lengthen sign-out when remote storage is saturated. This describes the separate situation "Desktop sessions experience long logoff delays when very large profile disks upload changes" but does not justify the selected fix for the current issue. The decisive behavior is: Overly broad exclusions undermine the purpose of a roaming profile container.

Check Windows App client support, Teams versions and installed redirection components. This would be appropriate for the different task-specific situation "A help desk reports that the Teams optimization status shows not optimized for a portion of users", because Media optimization depends on compatibility across the endpoint client and session-host software. It does not directly resolve the stated condition, which calls for Install the required version consistently on every host eligible to receive that RemoteApp session.

Prepare a compatible MSIX App attach package and configure its host pool association. This would be appropriate for the different task-specific situation "A large pool requires a signed MSIX application without baking it into the base session host image", because App attach delivers packaged applications dynamically to eligible session hosts and user sessions. It does not directly resolve the stated condition, which calls for Install the required version consistently on every host eligible to receive that RemoteApp session.

Validate both Teams optimization status and allowed client camera redirection policies. This would be appropriate for the different task-specific situation "Microsoft Teams calls work, but user cameras do not appear in sessions after a client policy change", because Teams real-time media and remote device redirection have separate compatibility and policy requirements. It does not directly resolve the stated condition, which calls for Install the required version consistently on every host eligible to receive that RemoteApp session.

A single resource-intensive app does not by itself prove every user needs dedicated desktop infrastructure. This describes the separate situation "A planning team proposes replacing all pooled desktops with personal VMs after noticing one application's high CPU use" but does not justify the selected fix for the current issue. The decisive behavior is: Autoscale can power down surplus hosts, but sufficient capacity and start-up behavior must still support user sign-ins.

Redundancy at the VM placement layer reduces the impact of a single zonal failure domain. This describes the separate situation "A pooled desktop service must remain available during a single Availability Zone outage" but does not justify the selected fix for the current issue. The decisive behavior is: Autoscale can power down surplus hosts, but sufficient capacity and start-up behavior must still support user sign-ins.

Remote access rights depend on the chosen AVD operating system, user population and licensing model. This describes the separate situation "Contractors need AVD desktops but their identity and Microsoft license eligibility are unclear" but does not justify the selected fix for the current issue. The decisive behavior is: Autoscale can power down surplus hosts, but sufficient capacity and start-up behavior must still support user sign-ins.