Azure Site to Site VPN Connection

Youtube : https://www.youtube.com/watch?v=MorG47BTttU 


 

 

 

 

 

1. Step : Create a Resource Group :

The resource group : Site2Site-VPN , you need to make sure to which region you want to connect the on-Premise via the VPN connection. 

2. Step 2 : Creation of VNet: 

We still have one subnet to add which is the Gateway subnet that we are going to use apart from the "Default" subnect that we created while creating the VNet.

-- Question to ask : While creating the subnet how may IP Addresses are you expecting to have for this subnet.

3. Step 3: Create Local Network Gateway











Local IP address that you have in your internet router. if you do not remember . "www.whatsmyip.org"

Step 4: Creation of the Public IP Address:

Step : 5 Virtual Network Gateway

Step 6 : Create Connection

Step 7 : Create a Virtual Machine

Step 8 : Configure RRAS on local windows Serv  -- Routing Remote Access Service 

Lets move on to the on-premises environment 













Select Option : Secure Connection between two private networks







































RRAS : Routing and Remote Access 

No, you typically don't need to download RRAS separately because it's a built-in feature of Windows Server operating systems. RRAS functionality is included as a feature that you can enable or configure within Windows Server.

Here's how you can typically enable RRAS on a Windows Server:

  1. Server Manager: You can use the Server Manager tool in Windows Server to add roles and features. From there, you can select the Routing and Remote Access Services role to install it.

  2. PowerShell: You can also use PowerShell cmdlets to install RRAS. The cmdlet Install-WindowsFeature RemoteAccess can be used for this purpose.

Once installed, you would configure RRAS through the Routing and Remote Access console, which provides a graphical interface for setting up routing, VPN, NAT, and other related functionalities.









































We now need the Public IPSec - which we generated using Public IP .






















Comments

Post a Comment

Popular posts from this blog

APIM -- High Availability skipping DR and Geo-Redundancy

  Regional Redundancy : Deploy your APIM service in an Azure region that offers redundancy and fault tolerance. Azure regions consist of multiple data centers, ensuring resilience against data center failures within the region. Scale Units : Configure your APIM service with multiple scale units within the same region. Scale units are isolated instances of APIM infrastructure that handle incoming traffic independently. Distributing your API traffic across multiple scale units ensures redundancy and fault tolerance at the application layer. Define Terraform Configuration : Write Terraform configuration files (usually with a .tf extension) that describe the resources needed for your APIM deployment, including multiple instances representing scale units. Create Scale Units : Use Terraform to define multiple instances of the APIM service using the azurerm_api_management resource. Each instance represents a scale unit, capable of handling incoming traffic independently.   Availabi...
Read more

Working on Azure -- Terraform - connectivity

If you're using a service principal account to authenticate with Azure, you'll still need to install the Azure CLI on your VDI, but you'll also need to configure the CLI to use the service principal for authentication. Here's how you can do it: Install Azure CLI : Download and install the Azure CLI on your VDI by following the installation instructions provided by Microsoft. You can find the installation instructions for various operating systems here . Authenticate with Service Principal : Once the Azure CLI is installed, you'll need to authenticate with Azure using the service principal credentials. Run the following command and provide the necessary details:  
Read more