An App Attach package was created for a Regional host pool in West Europe. It cannot be assigned to a second West Europe pool whose deployment scope is Geographical. The second pool must remain Geographical. Which change fits the documented scope rules?

✓ Correct answer

• Create a separate package for a host pool with the required deployment scope and assign that compatible package.

An App Attach package inherits its host pool’s deployment scope at creation, and that scope cannot be changed. Regional packages cannot be assigned to Geographical pools, even when both pools are in the same Azure region. Option explanations: A. Move the already regional SMB share within West Europe to override the package’s scope.: Share placement does not change the scope stored on an existing package. B. Assign more users to the package to override its deployment scope.: User assignments do not override deployment-scope compatibility. C. Edit the existing package’s deployment scope from Regional to Geographical.: The package’s inherited deployment scope is immutable after creation. D. Create a separate package for a host pool with the required deployment scope and assign that compatible package.: A separately created package with the appropriate inherited scope supplies a compatible assignment resource. Sources: Add and manage App Attach applications — https://learn.microsoft.com/azure/virtual-desktop/app-attach-setup

Read the source reference