Microsoft Azure: Implementing Internet Facing Load Balancer

 

Microsoft Azure: Implementing Internet Facing Load Balancers using Azure Resource Manager

 

In this Video, I will show you How to create an External Load balancer using Azure Resource Manager. We will create two load balanced web-servers publicly accessible through a common IP address.

Then we will test that load balancer through a common IP

 

Step 1: Create a VM in one region

Step 2: Create another VM in that region

Step 3: Create a Load Balancer

Step 4: Test Load Balancer

Create a new resource group

 

 

Create a new Virtual network

Create a Virtual Machine

 

Create a Availability Set

Select appropriate VM compute resources

 

 

 

Create another VM and add in same region and availability set

                               

 

Create a Load Balancer for both VM

 

Create a new Probe

Add rule to redirect load balancer port

 

Test Load Balancer:

Test the LB by turnoff one VM

Vnet-Vnet Between Different Region and Different Subscripiton

Overview:

 

This article helps you connect virtual networks (VNets) by using the VNet-to-VNet connection type. Virtual networks can be in different regions and from different subscriptions. When you connect VNets from different subscriptions, the subscriptions don't need to be associated with the same Active Directory tenant.

SetUp a xyz company network

 

Create a new Resource group :

 

 

Create a Virtual Network :

 

Create a Gateway Subnet :

 

 

 

Create a VM in your Virtual Network .

Create a Virtual Network Gateway

 

 

SetUp a ABC Company network

 

Create New resource group for abc company

 

 

Create a Virtual Network

Add SubNet

 

Create a new VM

Create a Virtual Network Gateway

Connect Abc and Xyz Virtual Network Gateway using Powershell CLI

 

Fetch the id for Vnet-Gateway using command :

 

az network vnet-gateway show -n xyz-vnet-gateway -g xyz-resgroup

 

Execute below command in Subscription 1:

 

az network vpn-connection create -n xyzvnet-abcvnet -g xyz-resgroup --vnet-gateway1 /subscriptions/subscription-id2/resourceGroups/xyz-resgroup/providers/Microsoft.Network/virtualNetworkGateways/xyz-vnet-gateway -l "West US 2" --shared-key "eeffgg" --vnet-gateway2 /subscriptions/subscription-id/resourceGroups/abc-resgroup/providers/Microsoft.Network/virtualNetworkGateways/abc-vnet-gateway

Execute below command in Subscription 2:

 

az network vpn-connection create -n abcvnet-xyzvnet -g abc-resgroup --vnet-gateway1 /subscriptions/subscription-id/resourceGroups/abc-resgroup/providers/Microsoft.Network/virtualNetworkGateways/abc-vnet-gateway -l "East US 2" --shared-key "eeffgg" --vnet-gateway2 /subscriptions/subscription-id2/resourceGroups/xyz-resgroup/providers/Microsoft.Network/virtualNetworkGateways/xyz-vnet-gateway

Test the connection :

Test the RDP using private IP from one machine to another machine.

 

Create a logic apps for receiving a json array (Employee records) using Rest end point and save each record in Azure SQL database

Create a logic apps for receiving a json array (Employee records) using Rest end point  and save each record in Azure SQL database .

Create Logic Apps

Create a Azure SQL database and database server.

3 resources created in your resource group now

Create Table in your database using Azure Query editor

Query:

CREATE TABLE [dbo].[Employee](

      [ID] [int] IDENTITY(1,1) NOT NULL,

      [UserId] [nvarchar](50) NULL,

      [JobTitleName] [nvarchar](50) NULL,

      [FirstName] [nvarchar](50) NULL,

      [LastName] [nvarchar](50) NULL,

      [PreferredFullName] [nvarchar](50) NULL,

      [EmployeeCode] [nvarchar](50) NULL,

      [PhoneNumber] [nvarchar](50) NULL,

      [EmailAddress] [nvarchar](50) NULL

     

 CONSTRAINT [PK_Employee] PRIMARY KEY CLUSTERED

(

      [ID] ASC

))

Design Logic App using a blank logic app

We are using HTTP end point as trigger so that you can trigger or call your logic apps through a URL.

Employess sample JSON Payload

{

"Employees" : [

{

"userId":"rirani",

"jobTitleName":"Developer",

"firstName":"Romin",

"lastName":"Irani",

"preferredFullName":"Romin Irani",

"employeeCode":"E1",

"region":"CA",

"phoneNumber":"408-1234567",

"emailAddress":"romin.k.irani@gmail.com"

}

]

}

Next choose foreach control

Now add action inside foreach loop (SQL Connection).

Map json with Table Column

Save the logic app .

It will generate the end point for your logic app .

Test Logic app using postman (must set content type as json ).

Create API gateway for logic apps using Azure API Management.

Create API in API management and point to logic apps

ASP.Net Web App CI CD using VSTS online and Azure Web Apps

Code

Create a Web Application in Visual Studio and create a Git repository at GitHub

Create a blank repository and Push the code from Visual studio at Git Repository .

Deploy

Create a Web App on Azure .

Configure CI/CD

Configure Continuous delivery for Web Application.

Click on configure and choose Source code repository 

    

Click on Build configuration for CD

Create a staging slot for testing

Once you have configured and click on OK it will create a build and a release definition in the VSTS account　A new slot created a for testing 

It will create a default build and Release definition for building web apps on VSTS

You can apply branch Filter at VSTS build definition

       

Default Deployment tasks created for Azure Web App deployment 

Configure CI/CD for Multi Stage environment

Create Multiple slots in your Azure Web Application (ex: Dev, QA, UAT)

                   

Go to VSTS default release process

Clone existing environment

Change Pre deployment condition to After release

Edit Task and change the slot to required slot.

Deploy to any slot on Cloud

　Create a new release and configure the environment where you want to deploy release

Select version for release