Bringing Enterprise-Level Security and Even More Power to GitHub-hosted Runners

Full Document

Readwise/Full Document Contents/Bringing Enterprise-Level Security and Even More Power to GitHub-hosted Runners.md

Highlights

Today, we unveil the next chapter by generalizing Azure private networking, ensuring all runner tiers, starting from our 2-vCPU runners, now support auto-scaling, static IPs and private networking capabilities. ([View Highlight] (https://read.readwise.io/read/01htxzsrn04h826pew156tqqn9))

We are excited to announce that Azure private networking for GitHub-hosted runners is now generally available. This feature allows you to run your actions workflows on GitHub-hosted runners that are connected to your Azure virtual network, without compromising on security or performance. ([View Highlight] (https://read.readwise.io/read/01htxzt1rsaevpxfvzh0j6ectm))

With Azure private networking, you can easily create GitHub-hosted runners that are provisioned within your Azure virtual network and subnet of choice. Thereafter, your actions workflows can securely access Azure services like storage accounts, databases, and on-premises data sources, such as an artifactory through existing, pre-configured connections like VPN gateways and ExpressRoutes. ([View Highlight] (https://read.readwise.io/read/01htxzv3n1bmyqjp2xk6sa8h1p))

Any existing or new networking policies, such as Network Security Group (NSG) or firewall rules, will automatically apply to GitHub-hosted runners ([View Highlight] (https://read.readwise.io/read/01htxzvmm67ep0tfkxpcsj90e8))

Azure private networking is now supported with the GitHub Team plan, in addition to the GitHub Enterprise Cloud plan ([View Highlight] (https://read.readwise.io/read/01htxzw5majg2py6eknnrnv78t))