TrueStack Direct Connect is a VPN management server made to connect Windows and Mac computers to Windows domain controllers and files servers in the AWS and Azure clouds.  This tutorial will help you set up your own TrueStack Direct Connect instance in your Microsoft Azure account.

  1. If you don’t have an Azure account, create a free account.
  2. Log in to the Azure portal.
  3. Click on Create a resource.  In the search field type TrueStack and click enter. Click on TrueStack Direct Connect
  4. Choose between TrueStack Direct Connect 10 (Free), 25, 50 or Unlimited device connections.
  5. For testing purposes, we recommend choose Start with a pre-set configuration.  Leave it as D-series default and click Continue to create a VM.
  6. If you don’t already have a subscription, set one up and choose Pay-as-you-go.
  7. Under the Basics tab, Resource Group, click Create New and choose a name for your resource group.
  8. Create a name for your virtual machine.  Remember this because this is also the initial logon password (see below).
  9. Choose an availability zone, any is fine.
  10. Create a username and password or use an SSH public key.  This username/password will only be used if you need to ssh into the Virtual Machine to reset the default password for the console.
  11. Leave everything else as defaults and Click Next : Disks >
  12. Leave as defaults and click Next: Networking >
  13. Leave as defaults and click Next : Management >
  14. Leave as defaults and click Next : Advanced >
  15. Leave as defaults and click Next : Tags >
  16. Leave as defaults then click Next : Review + Create >
  17. Choose Create
  18. If you choose to use an SSH public key in step 10 you’ll be prompted to Choose Download Private Key and Create Resource.  Save the Private Key to a secure location.
  19. Next you will be taken to a deployment page.
  20. It may take 3 – 4 minutes for your TrueStack Direct Connect virtual machine to deploy.

Next create a Route Table:

A route table will allow you to access connected devices from a Windows or other server in your Azure account.  This is required for Windows group policies and DNS to work correctly.
  1. First, you’ll need the local IP of your virtual machine. Click on Home, then Resource Groups and open your Resource Group that you just created above.
  2. Click on your Virtual Machine.Find and notate the private IP of your TrueStack Direct Connect Virtual Machine.  It may be something like this.  Also notate the Public IP.  It might be similar to this  You’ll need it later.

  3. Click Home in the upper left-hand corner.
  4. Click on Create a Resource
  5. Search for Route Table
  6. Choose the first one on the list, Route Table Microsoft.
  7. Click on Create.
  8. Create a name for the Route Table, Choose your Resource Group. Click Review+Create then Create
  9. Open your Resource Group
  10. Click on the Route Table you just created.
  11. Click on Routes on the left panel
  12. Click Add at the top, to add a route.
  13. Type in a route name.
  14. In the Address Prefix type  This is the subnet that TrueStack Direct Connect will use for the VPN connections.
  15. In the Next hop type choose Virtual Appliance from the drop down.
  16. For the next hop address type the IP of the TrueStack Direct Connect virtual machine that you notated earlier.  Something like  Click Ok.
  17. On the left panel of the route table click on Subnets.
  18. Click Associate at the top.
  19. Click on the drop-down for Virtual Network and choose your Resource Group Virtual Network, Something like this TSCDResourceG-vnet.
  20. Click on the drop-down for Subnet and choose the default subnet for that virtual network. Click Ok
  21. Click on Overview on the upper left side to see how it appears.  Here’s how you’re route table should look:

Accessing the Console

  1. To access the console open a browser.  We recommend using Google Chrome.
  2. Type in the public (static) IP address in the address bar.  It will redirect to a TrueStack https address.  Something like  Save this DNS address.  You can use it to access the console at anytime in the future.
  3. On the console logon page, accept the Eula and type in your TrueStack Direct Connect Virtual Machine name for the passwordThe password is the name you created at the beginning on the basics tab.  It isn’t the password you created if you used password instead of an SSH key.  That password will only be used to SSH into the server if needed.  If you do not know it, go back to your Resource Group and look at the name of your virtual machine.
  4. We recommend changing this default password on the settings tab after you logon.
Azure – TrueStack Direct Connect Initial Configuration