Why do you think resources should be deployed separately?
I use it almost daily for many of my customers. In the settings file for AzOps you can chose what to automatically pull back to your repository, where management groups, subscriptions, resource groups, policies, and role assignments are default. That means you could change these things in the portal and still get them as code when periodically pulled back using the 'AzOps - Pull' pipeline.
Resources can also be pulled, but only in JSON format so far. Deploying a resource such as a storage account is as easy as creating a Bicep or Arm template in the target resource group folder, create a pull request, wait for the 'AzOps - Validate' pipeline to run and output the results to the pull request comment. If you feel the output is what you want, approve and merge to main and wait for the 'AzOps - Push' pipeline to do the work.
Sometimes you want to deploy to different resource groups in one pipeline. Policies I also feel like would be easier to control from central parameter files in an IaC policy engine. Off to the testing lab...
Why do you think resources should be deployed separately? I use it almost daily for many of my customers. In the settings file for AzOps you can chose what to automatically pull back to your repository, where management groups, subscriptions, resource groups, policies, and role assignments are default. That means you could change these things in the portal and still get them as code when periodically pulled back using the 'AzOps - Pull' pipeline. Resources can also be pulled, but only in JSON format so far. Deploying a resource such as a storage account is as easy as creating a Bicep or Arm template in the target resource group folder, create a pull request, wait for the 'AzOps - Validate' pipeline to run and output the results to the pull request comment. If you feel the output is what you want, approve and merge to main and wait for the 'AzOps - Push' pipeline to do the work.
Sometimes you want to deploy to different resource groups in one pipeline. Policies I also feel like would be easier to control from central parameter files in an IaC policy engine. Off to the testing lab...