Setting up an Azure VM. You’re almost there!

Hi everyone. It’s time to start looking at the component level of Azure IaaS. So, Where do we start?

If you do not have an Azure subscription, you can sign up for a one at https://azure.microsoft.com/en-us/free/. You get a generous $260  to play with.

The next step is the installation of Azure modules for PowerShell. During the environment build, I will point out the differences  between creating objects using the portal and using PowerShell.

Click on: https://www.microsoft.com/web/handlers/webpi.ashx/getinstaller/WindowsAzurePowershellGet.3f.3f.3fnew.appids and install PowerShell.

 

Login to Azure (portal): https://portal.azure.com, enter your username and password.(the one that was used for the creation of the subscription).

Login to Azure (PowerShell): Run PowerShell ISE and type at the prompt:

 

PS> Login-AzureRmAccount

 

Enter your username and password at the login screen.

The first object that we need to create is a Resource Group. This is a container that contain resources with similar life cycle. For example, all the networking related objects will share a single Resource Group.

 

Creating  a resource Group (Portal):

1.       Click on Resource Group on the left side menu

resource1

2.       Click on the +Add

3.       Enter Resource Group Name, pick a subscription and choose a location. To complete, click the create button.

resource2

Creating Resource Group (PowerShell):

PS> New-AzureRmResourceGroup -Name RG-Blog-Mel -Location AustraliaSouthEast

 

Before creating any VM’s, we need to create a Virtual Network. Virtual Network require some planning and I highly recommend to engage a consultant to assist with creating the network design.

Here are some points for consideration when designing an Azure Vnet:

1.       Separate IP addressing scheme from your current LAN and WAN addresses

2.       VPN / ExpressRoute connection in the future

3.       Separate subnets for each deployment tier (Web, Application, Data, Etc.)

4.       Plan for future growth

5.       Placement of Network Security Groups and Load Balancers

6.       Azure reserves the first 4 addresses of each subnet for internal traffic

 

Copy and paste the following PowerShell script into your ISE session:

$ResourseGroupName = “RG-Blog-Mel”

$Location = “Australia SouthEast”

$vnet = New-AzureRmVirtualNetwork -ResourceGroupName $ResourseGroupName -Name BlogVnet -AddressPrefix 10.0.0.0/16 -Location $Location

Add-AzureRmVirtualNetworkSubnetConfig -Name BackEnd -VirtualNetwork $vnet -AddressPrefix 10.0.0.0/24

Set-AzureRmVirtualNetwork -VirtualNetwork $vnet

 

You should have a new Vnet called BlogVnet with 10.0.0.0/16 Address Space and a single subnet called BackEndSubnet with Address Range of 10.0.0.0/24

 

That’s it for today. Next week we will deploy our first VM!

 

Have a great weekend.