-
Notifications
You must be signed in to change notification settings - Fork 121
Network-25535 : Outbound traffic from VNET integrated workloads is routed through Azure Firewall #746
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
base: main
Are you sure you want to change the base?
Conversation
|
@microsoft-github-policy-service agree |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds a new network security assessment test (Test-Assessment-25535) that verifies outbound traffic from VNET-integrated workloads is routed through Azure Firewall. The test validates that network interfaces have user-defined routes directing 0.0.0.0/0 traffic to Azure Firewall private IP addresses.
Key Changes
- Implements automated assessment to check if NICs have default routes (0.0.0.0/0) pointing to Azure Firewall
- Validates routing configuration across all subscriptions by comparing effective route tables against Azure Firewall private IPs
- Generates compliance reports showing which NICs are properly configured to route through Azure Firewall
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 8 comments.
| File | Description |
|---|---|
| src/powershell/tests/Test-Assessment.25535.ps1 | New PowerShell test script that enumerates Azure Firewalls, retrieves NIC effective routes, and validates routing compliance |
| src/powershell/tests/Test-Assessment.25535.md | Documentation describing the security control, its importance, and remediation steps |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.