How to create a new Azure Tenant

Reading Time: < 1 minute
  1. Login to
  2. Locate or search Azure Active Directory
  3. Click + Create Tenant
  4. Select a tenant type, ‘Azure Active Directory’
  5. Click Next
  6. Complete details (See example below)

    Organization name:
    Initial Domain Name: This needs to be a unique name and will form your domain ending

7. Click Review and Create, and ensure the validation process passes

8. Click create and wait for the action to complete

Creating a virtual network in the Azure portal

Reading Time: 3 minutes

What is an Azure Virtual Network (VNet)?

An Azure Virtual Network also known as a VNet is a representation of your network in the cloud. It is a logical isolation of the Azure cloud dedicated to your subscription. You can use VNets to provision and manage virtual private networks (VPNs) in Azure and, optionally, link the VNets with other VNets in Azure known as VNET peering. You can also connect a VNET in Azure to your on premises IT infrastructure to create hybrid or cross premises solutions. Each VNet you create has its own CIDR block and can be linked to other VNets and on premises networks as long as the CIDR blocks do not overlap. You also have control of DNS server settings for VNets, and segmentation of the VNet into subnets.

You can use VNets to:

  • Create a dedicated private cloud only VNet. Sometimes you don’t require a cross premises configuration for your solution. When you create a VNet, your services and VMs within your VNet can communicate directly and securely with each other in the cloud. You can still configure endpoint connections for the VMs and services that require Internet communication, as part of your solution.
  • Securely extend your data center. With VNets, you can build traditional site to site (S2S) VPNs to securely scale your data centre capacity. S2S VPNs use IPSEC to provide a secure connection between your corporate VPN gateway and Azure.
  • Enable hybrid cloud scenarios. VNets give you the flexibility to support a range of hybrid cloud scenarios. You can securely connect cloud based applications to any type of on premises system.

    How to create an Azure Virtual Network step by step
  1. Login to the Azure portal via
  2. Search for Virtual Network within the search bar, or click Create a resource and locate and click Virtual Network

3. Click Add

4. Complete details (Screenshot below for demo purposes), and click next

5. Complete the IP Addresses tab. For the purpose of this demo, I have completed the details as shown below, click next when done

6. Moving onto the Security tab, you will be provided with a few options. For the purpose of this demo, I will leave the defaults but I have provided links to each feature below.

DDos Standard Protection

7. For the purpose of this demo no tags will be used. You can click the following link to find out more about Azure tags

8. Click Review and create and then create. You’re done with your first basic VNET creation. Give it a try in your test Azure portal. Microsoft also offer a free 30 day trial you can take benefit of. Click Azure Free Trial

How to install Terraform

Reading Time: 2 minutes

What is Terraform?
Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions.

Configuration files describe to Terraform the components needed to run a single application or your entire datacenter. Terraform generates an execution plan describing what it will do to reach the desired state, and then executes it to build the described infrastructure. As the configuration changes, Terraform is able to determine what changed and create incremental execution plans which can be applied.

How to install Terraform?

1) Visit
2) Click download

3) Select your operating system. I’ll be selecting Windows for this demo

4) Download Terraform 32 or 64 bit depending on your requirements

5) Extract the file

6) Next add the .exe to the path within Windows – click the start menu, search and click view advanced system settings

7) Click Environmental Variable

8) Click path and click edit

9) Click new

10) Type the path to the Terraform folder you created

11) Click OK, OK and OK and that’s it

How to install AZ Module within PowerShell

Reading Time: < 1 minute

1) Firstly download and install the latest stable version of PowerShell to your device. You can download the latest version from:

To check the version of PowerShell you currently have installed, launch PowerShell, run the command below:

Get-Host | Select-Object Version

2) Now that you have the latest version of PowerShell installed, you will need to install the AZ module if not already installed. The command below will allow you to check if you already have the AZ Module installed including the version number.

Get-Module -Name Az -ListAvailable

3) If you already have the AZ module installed, the version will appear. If no version is installed, no results will appear after running the above command. You may find that you have more the one version installed.

To install the latest version, type the command below:

Install-Module -Name Az -AllowClobber

Please note, if you already have older versions of the Az Module installed, you may wish to add -force to the end of the command so that the module installs side by side with your existing versions. Such as:

Install-Module -Name Az -AllowClobber -force

Installing the module will take about a minute. Run the command below again to confirm the module has installed

Get-Module -Name Az -ListAvailable

If you have multiple versions of the AZ Module installed, the latest version will be used by default, unless you specify for an older version to be used.

Virtual machines show two datastores in the summary tab

Reading Time: < 1 minute

You have migrated your virtual machines to new storage but find that the summary tab of the virtual machines shows two datastores within the vSphere Web Client and vSphere Client. You have checked the datastore and no data resides on the LUN.

Here are a couple of things you want to check,

1) The most obvious is to check whether there are ISO’s mounted to your servers

2) vSwap file. Does a vSwap file exist on the data store? browse the datastore and check if any vSwap files exist. If yes, a VMotion of the Virtual Machine migrates the vswap to the new location. If you’re moving VM’s to new storage, don’t forget to check your vSwap configuration, especially if you originally configured the vSwap location to reside on a different LUN. Ensure the vSwap file location has been reconfigured to point to new storage.

3) Check if any VMWare snapshots exist. If a VMWare snapshot was taken whilst an ISO was attached to the VM, this could be the issue. Remove the snapshot