Microsoft will retire the Virtual Network Injection in Azure, a feature that lets users manage network traffic
The retirement timeline starts on February 1st, 2025.
2 min. read
Published on
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more
Microsoft plans to retire the Virtual Network Injection feature for its customers using Azure Data Explorer. This functionality enabled users to incorporate their Azure Data Explorer cluster into a virtual network, managing how network traffic moved towards and away from the cluster.
However, Microsoft has recognized some problems with this feature, such as the need for a specific subnet for every cluster and the heavy upkeep it demands.
Because of these issues, the Virtual Network Injection feature will not be available for any new Azure Data Explorer customer, and those who already use it must switch by February 1st, 2025.
In a blog post, Microsoft says maintenance tasks like refreshing firewall lists or utilizing public IP addresses have burdened end-users. These difficulties have led Microsoft to suggest a change towards a private endpoint method, providing better security and less complex handling of network connections.
A private endpoint is like a network interface that lets users connect with Azure services in a private and protected way. It uses an IP address from the user’s virtual network, ensuring they can only access this endpoint via their virtual network.
This method enhances security by not needing a public IP or outbound internet connection for communication between the client and service. At the same time, it simplifies network layout because many clusters/services can share one subnet.
Microsoft says it will help people who are worried about migration at every step. The company has created a process for moving that aims to reduce time when systems are not working. There are also office hours where customers can ask questions or get advice. Now, Customers should begin planning their migration to avoid any difficulties before the February 2025 deadline.
This action aligns with Microsoft’s general move to simplify its Azure services. Only a week ago, they declared that the functions of Azure Lab Services would be retired, which would direct users toward other virtual network services.
