In this series of blog posts we will talk about Microsoft azure Virtual Networks. so let’s get started
Why Microsoft Azure? Microsoft azure is service everywhere anywhere and it can be anything you do.
Cloud consist of 3 main Services :
Platform as a Service PaaS supplies resources to build applications which enable you to develop on Microsoft cloud
Infrastructure as a service IaaS offers Hardware which enable you to create you infrastructure and run it on Microsoft cloud like Virtual Machines
What about Virtual Networks?
VNets is a services in IaaS which provide a layer of security and isolation to you VMs that are in the same network can access each other by default But what about the outside VMs? by default you can not access but You can configure the network to allow access to the external service. let’s imagine the next scenario
You are using an application like SharePoint which use SQL server database as a back-end, SharePoint play as the Front-end, SQL Server play as a back-end all of servers running in the cloud what about our DBs we need a layer of security and isolated from public so we can put the DBs server in the same Virtual network.
Let’s configure VNets to do it you need to have azure account to access Azure portal, get a free azure account from http://azure.microsoft.com/en-us/pricing/free-trial/ Once you have your account…
- + New in the bottom bar >> Virtual Network >> Quick Create
- Enter the VNet Name
- Choose the IP Adress Space you have 3 Spaces
- Allocate the Location
- About MAXIMUM VM COUNT and DNS SERVER we will talk about it Next
- Now you can Click on the √ mark to finish and Create a Virtual Network
In this blog we just talk about the Quick Create with default settings wait for the Next part we will deep dive in VNets 🙂