Script Execution Timeout GUI
Unable to change the timeout setting for configuration items. 60 isn't long enough for some configuration items to properly run their powershell scripts.
Simon Bond commented
This needs sorting. I work for a large org and this particular issue hits maybe 4-5% of machines which is a lot in our case. Frustrating to have to go through remediation at every upgrade cycle.
Ben Whitmore commented
Agree. Either a site setting that would change the policy for all clients or better still a client setting so we could extend the timeout on only the required clients.
MS marked this as a complete in one of the suggestions, but it's still missing in CI settings.