Azure: Accessing Private Resources
This page provides a step-by-step guide to setting up Twingate to access private Resources in Azure.
Let's take a simple example Azure tenant, with one virtual network, a VM running an SSH server, and a VM running an HTTP server. None of the servers have public IP addresses, so they aren't accessible over the Internet.


Preparing the Network
First, we need to deploy a Connector. To do this, we need to create a new subnet inside of Azure, because our Connector runs as a Container instance, and in Azure, Containers cannot be in the same subnet as VMs or anything else besides other Containers.
- Go to the Virtual Networks page.


- Next, add some address space to the virtual network.


- Now, go to the Subnets page.


- Using the new address space we've added, add a new Subnet and give it a name.


Updated about 1 year ago
Did this page help you?