Hi @SalmanKhan, thank you for your feedback. We will consider improving this in future enhancements of configuration analyzer. Confirming that this is current behavior in configuration analyzer today. This happens if the user uses the UX/portal to make policy changes. One way around this today, it to make policy changes via PowerShell.