@@ -5,6 +5,8 @@ date: 2020-01-25 14:40-0500
55comments : true
66---
77
8+ ## UPDATE: 2020-01-30 export with https://resources.azure.com/
9+
810If you found your way to this post and your first reaction is
911"[ well duh] ( https://www.urbandictionary.com/define.php?term=Thank%20you%20Captain%20Obvious ) ",
1012please leave a comment, because I'd love to know how you came upon your
@@ -66,6 +68,33 @@ want to do this for each big chunk of functionality in your system, then
6668stitch them together. Iterate at the command line using the technique
6769in the next tip.
6870
71+ ### Use the resources.azure.com
72+
73+ I have observed that the "export template" feature does not always give
74+ you the full JSON. For example, in the case of Application Gateway, the
75+ ` backendAddresses ` was empty, even though it had a pool and targets. A
76+ colleague pointed out this enormously useful resource
77+ [ https://resources.azure.com/ ] ( https://resources.azure.com/ ) .
78+
79+ Here is a quick sketch of how I used it to get the full JSON of a
80+ deployed Application Gateway. Note, this is not an ARM template, but it
81+ can help a lot.
82+
83+ 1 . Visit https://resources.azure.com/
84+
85+ 2 . Type in the resource group in which the resource is deployed: ejb012803c
86+
87+ 3 . Maybe make a choice.
88+
89+ a. If offered with an autosuggest, pick the resource and you are done.
90+
91+ b. If not offered with an autosuggest. In the left pane, expand nodes like this
92+
93+ ```
94+ subscriptions > Your subscription > resourceGroups > ejb012803c > Providers >
95+ Microsoft.Network > applicationGateways > ejb012803c
96+ ```
97+
6998### Start with one of the templates from ` azure-quickstart-templates `
7099
71100My extremely helpful colleague [ Brian
0 commit comments