Jesper Fajers

Hi @mikewo-dc thanks for voicing your need. The behaviour you describe in regard to the resource-type `Microsoft.Authorization/locks` not being pulled back by AzOps is correct and expected at this time,...

Moving forward our long-term plans are in the following direction: To expand AzOps capabilities by enabling Bicep file generation confidently with existing Pull operation (dependent on Bicep CLI) we have...

Hi @reckitt-maciejglowacki, thanks for updating this issue and sharing. I agree with your experience in regards to a bunch of different errors ultimately causing pipeline executions to fail. We started...

Hi @SebastianClaesson, thanks for reaching out. This scenario/situation and the given outcome is expected. AzOps requires the management group resource provider registered in the Azure subscription designated during initialization. To...

Great idea @SebastianClaesson, lets adopt both of your suggestions by clarifying this requirement in the wiki and in addition to the custom message we could output the generated error code...

Hi @DennisSchouwenaars, thanks for reporting this behavior. I will have a look at reproducing this and evaluate possible mitigations.

@DennisSchouwenaars, I have tried multiple combinations of Windows/Linux and I am not able to reproduce the issue as described. However I can simulate conditions by creating a file lock during...

Thank you for reporting this! I confirm that we see the same behavior. Ideally it should contain the additional [properties](https://learn.microsoft.com/en-us/azure/templates/microsoft.sql/servers/firewallrules?pivots=deployment-language-arm-template#resource-format-1)  Example from Azure Portal Export (missing additional properties): ...

@Xitric, lets sync up after your meetup with Bicep maintainers 👍 and take it from there as we aim to incorporate usage of Bicep features together with AzOps.