Support using Azure Blueprints without requiring Managment Groups
For customers like us not using Management Groups it is hard to try/use Azure Blueprints.
You can now save a blueprint definition at a subscription scope
You can now export/import a BluePrint definition using this script: https://www.powershellgallery.com/packages/Manage-AzureRMBlueprint/2.0
I opened an issue on this on GitHub. I see BluePrints as "patterns" - much like ARM templates. They should be independent until assigned to a particular scope. The rules I have do NOT always follow a strict hierarchy. Forcing us to place all definitions in a management hierarchy from the start makes little sense.
I second this. A blueprint is a pattern (like an ARM template). I should be able to be able to define that pattern SEPARATELY from applying or publishing it to a Management Group