GitHub’s Unique feature: Azure VNET Integration !

Private Networking Without Self-Hosted Runners

It’s been a while since I last posted… Writing articles was one of my 2025 resolutions, and somehow this year, i forgot to renew this resolution’s subscription xD. Life got pretty busy after I moved from DevOps into Cloud Architecture, and things have been moving fast. That said, I realized recently how much I actually missed GitHub and all the cool things around it. I’ve got quite a lot I want to share with you again; from technical articles to life experience stories andto some of the newer things happening in the GitHub ecosystem.

For today, let’s zoom in on one configuration I really like in GitHub, especially since I work a lot with Azure. When teams want GitHub Actions workflows to access internal resources (databases, private APIs, internal package feeds), the usual solution is self-hosted runners.

Well i’d be lying if i said it does’nt work. But it also introduces an operational burden. Once you deploy self-hosted runners, you become responsible for:

• provisioning the machines
• patching and updating them
• scaling them
• securing them
• maintaining the runner software