Source article: https://learn.microsoft.com/en-us/powershell/module/networkatc/update-networkatc?view=windowsserver2025-ps
I have worked with a customer that was upgraded from Azure Local 22H2 to 23H2.
After upgrade and after configuring Network ATC Intents, we could not continue to solution upgrade because Network ATC Intents was switching between configured/success and validating, for both compute_management and storage intents.
After customer worked with Microsoft support, they was told to use the following PowerShell command to cool down the validation interval:
Update-NetworkATC -DriftTimerInMinutes 15 -ConfigurationChangeInSeconds 300
Comments