Azure Subnets: Disable Default Outbound Access
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
See: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access
In Azure, VMs that are created in a virtual network without a defined explicit outbound method are assigned a default public IP address that enables internet connectivity. On 30 September 2025, default outbound access connectivity for VMs in Azure will be retired.
Existing VMs will continue to work but we should ensure the Bastion Jump box vms have default outbound access disabled and instead use a NAT Gateway.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the infrastructure definitions for the Bastion jump box VMs and their Azure virtual network subnets, then review how outbound access is currently configured. Confirm the intended Azure NAT Gateway approach and validate that the deployed jump boxes have default outbound access disabled while retaining required connectivity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100