Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - combination Deny vNet peering cross subscription & Deny-VNET-Peering-To-Non-Approved-VNETs #1674

Open
timmoh opened this issue Jun 13, 2024 · 2 comments
Labels
Area: Policy 📝 Issues / PR's related to Policy Type: Feature Request ➕ New feature or request

Comments

@timmoh
Copy link

timmoh commented Jun 13, 2024

szenario:

  • HubToSpoke Peering done by: Deny-VNET-Peering-To-Non-Approved-VNETs => fine
  • subscription intneral peering: Deny vNet peering cross subscription => fine

but if we've got an HubToSpoke Subscription with internal vnet peering. This won't work with these to Policy.

Suggestion:

  • Option A) Deny-VNET-Peering-To-Non-Approved-VNETs

    • add an option to allow inner subscription peering
  • Option B) Deny vNet peering cross subscription

    • add an excludelist of vnet ids which are ok to do cross subscriptions

or both ;-)

@jtracey93 jtracey93 added Area: Policy 📝 Issues / PR's related to Policy Type: Feature Request ➕ New feature or request labels Jun 14, 2024
@Springstone
Copy link
Member

Springstone commented Jun 27, 2024

Tracking in AB#35840

@Springstone Springstone added this to the policy-refresh-fy25-q1 milestone Jul 4, 2024
@Springstone
Copy link
Member

#1731

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Policy 📝 Issues / PR's related to Policy Type: Feature Request ➕ New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants