Ability to export a Resource Group as a template
When doing work which needs to be repeating, i.e. deploying a large set of servers, configuring a complex set of dependencies, it would be very helpful to have the ability to save the resource group as a template, which could then potentially be used in the Azure Resource Manager within Visual Studio to be further refined for argument usage. The use case for this would be dev/test environments, where we need the ability to fully tare down and re-create the environment. This feature would build on top of the current ability to execute Save-AzureResourceGroupGalleryTemplate.
You can now export a template from your existing resource groups. We’re still evolving this experience, but try it out and let us know what you think!
Rich Chapler commented
Is export sufficient? A copy or clone function (real-time, without tons of steps) would be ideal.
Too bad that you can't export an ASA stream job - this is the error that I get:
The schema of resource type 'Microsoft.StreamAnalytics/streamingjobs' is not available. Resources of this type will not be exported to the template. (Code: ResourceTypeSchemaNotFound)
Cristian Satnic commented
The 'export template' functionality worked well for a few months until about 2 weeks ago or so when the option in 'Settings' switched from 'Export template' to 'Automation script'. After that change was made exporting the current state ARM template for a resource group or other ARM resource does not appear to work properly anymore.
For a more detailed discussion of the problem see this thread:
Can we add an option to download the ARM template from Azure portal.
1. The user creates all the resources through the portal.
2. Downloads the filled ARM template.
3. Uses that template for further deployments.
Michael Teper commented
Bunch of common object schemas (e.g. "classic" storage) are unavailable.
Brandon Marcus commented
I've been testing the new feature out. Looks interesting. Like exporting complex infrastructures and I get the export of Powershell and CLI. https://azure.microsoft.com/en-us/blog/export-template/
Anti Ohne commented
The export template only works for resources which have a published Json schema. I've tested the export function for example for a resource group with an Azure Automation account in it and it will give you an error stating that the schema of resource type 'Microsoft.Automation/automationAccount is not available'. Resources of this type will not be exported to the template.
Michael Jonsson commented
Is this request completed now? :)
Michael Jonsson commented
When did the Export feature pop up in the Portal?? Have not tried it out yet but seems to be something this thread has been asking for?
This would be a great feature!!, We have a fairly standard App service architecture comprising Web (admin portal) & Mobile APP's, both connecting to an API app providing logic and access to data services, backed of either to A documentdB or Azure SQL database, one thing to mention is we tend to keep the Database's in a separate resource group (as the elastic database pool is covers a number of different (APP's),
For us, some key aspects of this this feature would be 1) Topology (we are using VSTS to actually deploy to the APP's database etc), 2) the ability to use some formalised naming conventions to speed up / ease deployment &,
Andy B. commented
How's this coming along? Is there an expected release date for this feature?
We found this last week that seems similar to the request.
Eduardo Zabat Lorenzo commented
and maybe allow LiveIDs? :)
I tried it, had some problems with the generated template in the area of nested resources.
Has anyone experience with the tool Lyon Till posted ( https://capturegroup.azurewebsites.net/ ) ? Can I trust it? Does it work well (except the known issues) ?
Gerald Bauer commented
I would need the topology and the files of of a webdeploy package.
Paulo Ramos commented
Great job guys!! Looks really nice!
Can we call this using a REST request?
Doesn't Azure CLI provide this functionality currently:
"You can save the JSON data to file by using the > character to pipe the output to file. For example:
azure resource show "testRG" "MyUbuntuVM" Microsoft.Compute/virtualMachines -o "2015-06-15" --json > myfile.json"
Lyon Till commented
Awesome tool, thank you for developing this, please can you add the ability to export:
Also topology in our case. Great that work has started on this!
tec goblin commented
The topology mostly in my case :)