Johan Dahlbom

We currently do not maintain a complete, updated list of supported resources providers. See following page for list of supported platform (proxyOnly) resources. As you can see, locks is the...

As discussed offline, this will be implemented with a separate push pipeline that can only be triggered manually accepting deploymentscope as input (managementGroup -> subscription -> resourceGroup -> resource/individual template)

As discussed offline yesterday, the implementation approach will be as follows: - [x] Remove `Sort-Object` from deployment logic in [Invoke-AzOpsPush](https://github.com/Azure/AzOps/blob/main/src/functions/Invoke-AzOpsPush.ps1) to honor deploymentlist ordering - [ ] Add additional step...

Hey @reckitt-maciejglowacki , We have customers with over 1000 subscription running this, so it should definitively work. Can you share how the below settings are configured in the settings.json file?...

Thank you. For troubleshooting purposes, could you please try and change the `Core.SkipResourceGroup` setting to `true` and report back the results?

You would only want RG discovery if you intend to do RG level deployments (like VMs or other resources) with AzOps, which I assume is not the intent here?

Are you going to manage that from a central platform perspective via AzOps or let the individual LZ teams do it?

Understood. Can you try to change back the setting to discover RGs and change the pipeline timeout in ADO to 6 hrs and see if it completes successfully?

Thank you for confirming this. We will take a look at this and see what we can do. The advise would be to disable resource group discovery for now.

Hey @reckitt-maciejglowacki - we are currently working on this, unfortunately no short term fix. I will make sure to keep the progress updated in this issue.