A governance team assigns an 'Allowed locations' policy at a management group. Some legacy resource groups must be temporarily exempted until a migration completes in six months. You must: 1) Mark those resources as exempt with an expiration date, 2) Continue evaluating other resources for compliance, and 3) Track remediation task progress for non-compliant resources where a deployIfNotExists policy fixes configuration drift. What should you do?

This option directly addresses all requirements. Azure Policy exemptions with an 'Expires On' date allow temporary exceptions for specific resource groups while ensuring the policy continues to evaluate other resources. The Azure Policy compliance dashboard is the central place to monitor overall compliance. For deployIfNotExists policies, remediation tasks are initiated and tracked within the Remediation tasks blade, providing clear progress visibility. Incorrect options: Disabling the policy assignment would stop evaluating all resources, not just the legacy ones, and Activity Log isn't designed for tracking remediation progress. Initiative-level exclusions are static and don't support expiration dates, and Azure Monitor Workbooks are not the primary tool for tracking Policy remediation task status. Tagging resources and modifying the policy rule is a workaround that requires policy modification and doesn't offer an expiration date, and Azure Resource Graph is not for tracking remediation status. Moving resources to a separate subscription is an unnecessary and disruptive organizational change, and manual checks are inefficient and error-prone.