Skip to content

Conversation

@cloudchristoph
Copy link

Addresses issue #2

Copy link
Owner

@aidanfinn aidanfinn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The suggested change assumes that the hub and spoke are in the same subscription. In an enterprise-scale deployment, they usually are not.

@cloudchristoph
Copy link
Author

I'm not sure what you mean Aidan.

The hub subscription is referenced separately via the "hubSubscriptionId" parameter in the spoke template and this parameter does not have to (and usually will not - as you correctly pointed out) match the spoke subscription.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants