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

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

By
In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more