Azure ARM template

What is the best way of controlling dependencies or referencing dependencies that are not deployed in your template?

Are linked templates the way to go?

Is there a good way to reference a dependency that is not in your arm template? DependsOn only keeps track of what is in the current arm template deployment.

For example, the networking team will deploy subnets.

When I create resources that use those subnets, I want to ensure that they are there.

Is reference the way to go? Or arm template output calls the way to go in this manner?

submitted by /u/jona187bx
[link] [comments]

Read more here:

Content Attribution

This content was originally published by /u/jona187bx at Microsoft Azure, and is syndicated here via their RSS feed. You can read the original post over there.

%d bloggers like this: