Azure Blueprints loose blueprint level dependencies when edited in UI
This is a bug... when you set up dependencies in blueprint.json they are removed if you subsequently edit the blueprint in the UI.
- Create blueprint in UI
- Export with AzBlueprint, set up dependencies and import
- Export again, dependecies are still there
- Edit in UI
- Export, dependencies are gone
The dependency management is not a great experience at the moment, it needs to be visible in the UI, also, I the documentation should be updated to clearly state if you can make one resource group dependent on another rather than making them dependent on artifacts in another resource group.