Deploy tenants in separate Azure resource groups #51
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ppiwowa-csco
force-pushed
the
multi-tenancy-azure
branch
from
be35e50 to
75da7b9
Compare
ppiwowa-csco
force-pushed
the
multi-tenancy-azure
branch
from
75da7b9 to
88af9f1
Compare
cicharka
approved these changes
Oct 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request summary:
Part of cisco-en-programmability/ansible-collection-catalystwan#59. Support for multi tenancy in Azure deployments. Tenant's edges will be deployed in isolated resource group.
Checklist: