Ability to chain/link blueprints together
It would be handy to be able to group/chain together blueprints in order to be able to define a "product". For example:
Within a company, there are many distinct product offerings, some API's, some Service Fabric apps and some containerised apps.
Some of these may need to have the standard offering for a SQL Server, a Web App and a Storage account. Others may need access to a Service Fabric cluster and other such Azure services.
Within the ARM templates, these things can all be linked whereby the definition of a SQL Server is a linked artefact and the same with all the other bits.
Blueprints doesn't seem to be able to accomplish this - each blueprint needs to have all the associated ARM items bundled within it.
The reason having the ability to link them would be good is to be able to define a revised "SQL Server" blueprint centrally and when it is published, trigger updates to (whether in draft or final) all/any other blueprints that consume this one.
Thereby allowing for central governance of said services without needing to reflect the same changes in all blueprints - possibly missing some or making things inconsistent.
Again, this is all do-able with linked ARM templates but it then does miss out the more formal processes that are offered by Blueprints.
This is something that could be accomplished more easily now that we have the Az.Blueprint powershell module, but as of now there is no first class support for something like this you are right.
It's something that we would like to enable, but can't give an ETA atm.