Traditionally, accessing private resources with GitHub Actions required the setup and management of self-hosted runners. Now, with new features available for GitHub's Teams and Enterprise plans, you have the capability to configure GitHub-hosted runners to connect directly to your Azure virtual networks. This enables direct network access from the hosted runner to private resources, whether they're hosted on Azure, or connected through hybrid networks from your Azure VNET to other cloud environments, or even on-premises environments!

Let's take a look at how to set this up and walk through the end-to-end configuration!


// SUBSCRIBE ✅
http://www.youtube.com/mattallford?su...


// RESOURCES & REFERENCES 📃
GitHub Repository:
🔗https://github.com/mattallford/github...
About Azure private networking for GitHub-hosted runners in your organization:
🔗https://docs.github.com/en/organizati...
Configuring private networking for GitHub-hosted runners in your organization:
🔗https://docs.github.com/en/organizati...
About Ubuntu and Windows Larger Runners:
🔗https://docs.github.com/en/enterprise...


// FOLLOW ME 👉
Blog - https://mattallford.com
LinkedIn -   / mattallford  
Twitter -   / mattallford  
GitHub - https://github.com/mattallford


// CHAPTERS 🕛
0:00 Introduction
0:56 What Problem is Being Solved?
2:51 Example GitHub Workflow
6:05 The Demo Environment
6:46 What Did We Do Before?
10:45 GitHub Runner VNET Integration
13:14 Reviewing the GitHub Documentation
18:23 GitHub Enterprise Configuration
20:00 High Level Configuration Workflow
22:00 IaC for My Demo Environment
24:43 Prerequisites
26:59 Be Aware of the Deny Outbound NSG Rule!
29:35 Obtaining the GitHub Database ID
33:10 Configure Azure Resources
40:18 GitHub Networking Configuration
42:08 GitHub Runner Groups
43:49 Create a New Hosted Runner
45:45 GitHub Runner Billing and Spending Limit
48:28 Update and Test The Workflow
51:46 Troubleshooting Time - I Made a Mistake!
54:55 Test The Workflow - Take 2
57:06 Summary
59:02: A Final Thought About Managing Cost