Skip to main content

Define multiple networks (NIC) on Azure VMs

By
NIC comes from Network Interface Controller. What is connection between NIC and Microsoft Azure?
Starting from now we have the possibility to define multiple virtual network interfaces for each VM that is hosted on Azure. In on-premises this features is used to connect to multiple networks and provide mechanism to isolate different tiers of our system.
This can be used with success, in combination with a VPN connection to connect to multiple on-premises networks or Azure Virtual Networks. In this way we can establish a Cross Premises Connectivity.
In this moment the configuration can be made using PowerShell scripts and commands. An important pre requirement for NIC is to have Azure Virtual Network already configured on that VM.
A NIC can be configured only on VM. You cannot make this configuration on a web role or web sites. In this moment this feature is available only for VM. There is also a limit of number of NICs that you can define on each VM. The number is direct connected to the size of the machine. For example for an A6 you can define 2 NICs, but for an A7 you can define 4 NICS.
Because NICs are a new feature on Azure, there are some limitation in this moment. I expect that in the near future this limitation will be relaxed or even disappear. Below you can find a part of this limitations:
You cannot have multiple NICs on the same subnet
IP and MAC of each NIC will remain the same after a restart. The same thing is also for the network orders even if the order or networks cannot be controlled.
You cannot add/remove NICs once the VM is connected. This is one of the limitations that I hope that will be removed in near future.

Labels:

Comments

Post a Comment

Popular posts from this blog

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

By
The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more