Azure Networking

This will give you the basics that you need to understand : Core Fundamentals in Azure Network


 

 

 

 

 

 

 

 

 

 

If you are someone who architects networks you will come across the concept 

--Hub and Spoke Model :

Here is where we keep a lot of management service , all services that we use to connect back to other networks . This could be your on-premises network or perhaps VPNS into another Azure network in other regions if needed. 

Yes, in the context of networking architectures, a "hub" virtual network typically refers to a central or primary virtual network within Azure that serves as a centralized point for connecting other virtual networks, often referred to as "spoke" networks. The hub virtual network acts as a central point of connectivity and can provide various services such as routing, network security, and connectivity to on-premises networks or other cloud environments.

There are things like Global peer and other services that are available but you can still connect through gateways to other networks as well

 


The subnets within the same Vnet can connect to each other since they are in the same VNet. And if you want to filter traffic we can use NSGs (Network Security Groups).  This is something like the firewall where you decide if the traffic from subnet A reaches subnet B or not you decide based on the rules you define.


IP Address :













Azure reserves 5 IP Address in each subnet :

 

Can't you can communicate outbound anyway : you absolutely can If you have VM in a Vnet . It can absolutely talk out to the internet and it uses network address translation allow that VM to communicate . But you put a Public IP to that you are for sure able to communicate outside the internet.

Azure services you can PIP (Public IP Addresses are): 


Azure Network Topology: 

18: Vnet peering and connectivity

  • Hub & Spoke
  • Daisy Chain
  • Mesh


VNet -- Connecting different Vnet 

Site-2-Site VPN : This is what most of the people get going before they commit to something larger. This involves connecting your datacenter over a VPN device to Azure. 







 

 

 

 

 

 

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