Best 5 Resources for DevOps
1. DevOps Courses - https://bit.ly/3eEV8Au
2. DevOps Tutorials - https://bit.ly/3TZTPwg
3. DevOps Books - https://bit.ly/3eEscIR
4. DevOps Problem - https://bit.ly/3Pgnn5b
5. DevOps RoadMap by @VrashTwt
Discuss on Cloud, Best Practices on Cloud Deployments, Cloud implementations and options, administration understandings. How to approach Cloud, scale-up and on-premises deployments.Migrating workloads to major Cloud Services, Changes in architecture, security and policy settings, HA/DR option, monitoring options, support options, costing, and so on. Analyze all these in the blogs and discuss the pros and cons of Cloud,
Best 5 Resources for DevOps
1. DevOps Courses - https://bit.ly/3eEV8Au
2. DevOps Tutorials - https://bit.ly/3TZTPwg
3. DevOps Books - https://bit.ly/3eEscIR
4. DevOps Problem - https://bit.ly/3Pgnn5b
5. DevOps RoadMap by @VrashTwt
What is Cloud Network Segmentation? Network Segmentation is a proven network security technique that divides a network into smaller, manageable sub-networks that enable network security teams to compartmentalize the sub-networks.
Gain central visibility & control of security policies across heterogeneous environments. See how to get started & manage network segmentation for on-prem & cloud networks. Avoid misconfig errors. Network cloud solutions. Minimize audit prep. Automate network security.
Network segmentation
Maintain proper segmentation so that your workload's reliability isn't compromised by unauthorized access.
This architecture uses Network Security Groups (NSGs) to restrict traffic across subnets and the Connectivity subscription.
NSGs use ServiceTags for the supported services.
Cloud/Platform team
1- Enforce the use of NSGs through Azure Network Manager Policies.
2- Be aware of the workload design. There isn't any direct traffic between the stamps.
Also there aren't inter-region flows.
If those paths are needed, traffic must flow through the Connectivity subscription.
3- Prevent unnecessary hub traffic originating from other workloads into the mission-critical workload.
Egress traffic from regional stamps
All outgoing traffic from each regional spoke network is routed through the centralized Azure Firewall in the regional hub network. It acts as the next hop that inspects and then allows or denies traffic.
Cloud/Platform team
1- Create UDRs for that custom route.
2- Assign Azure policies that will block the application team from creating subnets that don't have the new route table.
3- Give adequate role-based access control (RBAC) permissions to the application team so that they can extend the routes based on the requirements of the workload.
Let's go through some important points
The Azure Virtual Network service is used to define an isolated network in Azure. The virtual network can then be used to host your resources such as Azure virtual machines.
The Azure virtual network gets assigned an address space which you specify when you create an Azure virtual network

You can then add subnets to your Azure virtual network. This helps divide your network into more logical segments.
An example is shown below of having multiple subnets. You could have one subnet named SubnetA in the virtual network to host your Web servers and another subnet to host the Database servers.

When you create a virtual machine in a virtual network, the virtual machine gets a Private IP address from the address space of the subnet is it launched in.

These are used to filter network traffic to and from Azure resources in an Azure virtual network.
A network security group is attached to the network interface attached to the virtual machine.

A network security group consists of Inbound rules that are used to control the traffic inbound into a virtual machine
By default all traffic into a virtual machine is DENIED.
You have explicitly add rules to allow traffic into a virtual machine
There are also outbound rules to control the traffic flowing out of the virtual machine. By default all traffic outbound onto the Internet is allowed.
Virtual Network Peering is used to connect two Azure virtual networks together via the backbone network.
Azure supports connecting two virtual networks located in the same region or networks located across regions.
Once you enable virtual network peering between two virtual networks, the virtual machines can then communicate via their private IP addresses across the peering connection.
You can also peer virtual networks that are located across different subscriptions.
The virtual networks can't have overlapping CIDR blocks.
A Point-to-Site VPN connection is used to establish a secure connection between multiple client machines an an Azure virtual network via the Internet.
Below is a diagram from the Microsoft documentation on a sample scenario

Image reference -https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal
To implement a Point to Site VPN connection, you need to create a VPN Gateway in Azure.
A Site-to-Site VPN connection is used to establish a secure connection between an on-premise network and an Azure network via the Internet.
Below is a diagram from the Microsoft documentation on a sample scenario

Image reference - https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal
On the on-premise side, you need to have a VPN device that can route traffic via the Internet onto the VPN gateway in Azure. The VPN device can be a hardware device like a Cisco router or a software device ( e.g Windows Server 2016 running Routing and Remote services). The VPN device needs to have a publically routable IP address.
The subnets in your on-premise network must not overlap with the subnets in your Azure virtual network
The Site-to-Site VPN connection uses an IPSec tunnel to encrypt the traffic.
The VPN gateway resource you create in Azure is used to route encrypted traffic between your on-premise data center and your Azure virtual network.