Scribd
Upload
2 views

Virtual Network1233211412001

A Virtual Network (VNet) with address space 10.0.0.0/16 is created to host a Virtual Machine (VM) within a subnet of 10.0.0.0/24. The VM is configured with a Standard_DS1_v2 size and Windows Server 2019 Datacenter OS, connected to the subnet via a Network Interface (NIC) that assigns it a private IP address. Public IP addresses can be assigned for external access, while Network Security Groups (NSGs) control traffic to and from Azure resources.

Uploaded by

Ritesh K
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views

Virtual Network1233211412001

A Virtual Network (VNet) with address space 10.0.0.0/16 is created to host a Virtual Machine (VM) within a subnet of 10.0.0.0/24. The VM is configured with a Standard_DS1_v2 size and Windows Server 2019 Datacenter OS, connected to the subnet via a Network Interface (NIC) that assigns it a private IP address. Public IP addresses can be assigned for external access, while Network Security Groups (NSGs) control traffic to and from Azure resources.

Uploaded by

Ritesh K
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Virtual Network (VNet):

A VNet is created with an address space 10.0.0.0/16. This is the private


network where

the VM will reside.

A subnet is created within the VNet with the address range 10.0.0.0/24.
This subnet will

contain the VM.

Network Interface (NIC):

A Network Interface (NIC) is created for the VM. The NIC connects the VM
to the subnet we

just created in the VNet.

The VM will be assigned a private IP address from the VNet’s subnet.

Virtual Machine (VM):

A VM is created with the following specifications:

1. Size: Standard_DS1_v2 (a common VM size).

2. OS: A Windows Server 2019 Datacenter image.

3. Network Profile: The NIC created earlier is associated with the VM,
which means the

VM will be placed inside the subnet of the VNet.

Key Points:

1. Private Network (VNet): The VM is created inside a private network, and


it will not
have any public IP. It can only communicate with other resources inside
the same VNet.

2. Private IP: The VM will get a private IP address assigned automatically


(via Dynamic

allocation) from the subnet 10.0.0.0/24.

*/

/* Public IP Address (PIP):

// A Public IP Address in Azure is an IP address that is accessible from the


internet and

is used to connect to resources like Virtual

// Machines (VMs), Load Balancers, or Azure services that need to be


accessed externally.

Public IP addresses are essential for

// applications or services that need to be accessed from outside the


private network or

from the internet.

// It provides external access to Azure resources like VMs over the internet.

// Assigned to resources (e.g., VMs) to make them reachable via SSH, RDP,
or HTTP.

// Can be Static (fixed) or Dynamic (changes when the resource is stopped


and started).

// Network Security Group (NSG):

// Controls inbound and outbound network traffic to/from Azure resources.

// Allows you to define rules (e.g., open port 22 for SSH or 3389 for RDP) to
control

access.

// Enforces security by restricting or allowing traffic based on source IP,


destination,
ports, etc.

// Private Link Service (PLS) with Backend Resources: If you are exposing a
service (e.g.,

an internal

// application or backend service) through a Private Link Service (PLS) and


the service

behind it requires

// high availability, you would typically use a Load Balancer to distribute


traffic to

multiple backend instances.

// If your goal is to simply create a Virtual Machine with either a public IP


or private

IP (depending on the endpointType parameter),

// and not to create a Private Endpoint (which is used for connecting


privately to Azure

services), then you don't need to use the Private Endpoint resource at all.

// The VM itself can be configured with either a public IP or private IP, and
the endpointType

parameter will control whether the VM gets a public IP or a private IP.

*/

You might also like