jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-08 21:02:10 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #34188 from github/repo-sync

Browse Source 
Repo sync
This commit is contained in:
docs-bot
2024-08-02 14:30:15 -07:00
committed by GitHub
parent 3045c2e781 31da5afcf4
commit 9877db901b
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
data/reusables/actions/azure-vnet-networking-policies.md
View File

@@ -3,3 +3,5 @@ Because the {% data variables.product.company_short %}-hosted runner's NIC is de
For example, if your VNET is configured with an Azure ExpressRoute to provide access to on-premises resources (e.g. Artifactory) or connected to a VPN tunnel to provide access to other cloud-based resources, those access policies also apply to your runners. Additionally, any outbound rules applied to your VNET's network security group (NSG) also apply, giving you the ability to control outbound access for your runners.
If you have enabled any network logs monitoring for your VNET, you can also monitor network traffic for your runners.
{% data variables.product.company_short %}-hosted runners use whatever outbound control your network is using. If your network relies on Azure's default outbound access, the IPs are not predictable and cannot be added to the {% data variables.product.company_short %} IP allow list. For recommendations on using a stable outbound IP, see [Default outbound access](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access) in the Azure documentation.