Microsoft Technology Licensing, LLC

Ashish Bhargava

Rishabh Tewari

Xinyan Zan

Nisheeth Srivastava

Naveen Prabhat

Abhishek Shukla

Sushant Pramod Rewaskar

Md Daud Hossain Howlader

Jayesh Kumaran

Parag Sharma

Abhishek Ellore Sreenath

Neha Aggarwal

Brian D Swander

Jie Li

Vikrant Arora

Chandramouleswaran Ravichandran

Neeraj Motwani

Vishal Taneja

Randy Joseph Miller

Sumeet Mittal

Poornananda Gaddehosur Ramachandra

Sarvesh Sakalanaga

Sumit Gupta

Anavi Arun Nahar

Raman Deep Singh

Vinaya Natarajan

Mohamed N Hassan

Raghav Mohan

Sourav Das

Daud Hossain Howlader

Policy-based network transmission routing is provided by accessing routing metadata in a wrapper of the transmission packet, the routing metadata representing a feature of the source or the destination, comparing the routing metadata to routing policy data associated with each of multiple routing policies defined within a routing policy structure, identifying, based on the comparing, one or more routing policies applicable to the transmission packet, identifying, based on the routing policy data, a highest priority routing policy from the one or more routing policies, the highest priority routing policy defining a route constraint usable to limit a selection of available routes to the destination, and selecting the route from the available routes based on the route constraint.

Policy-based network transmission routing

The disclosed technology is generally directed to virtual machines. In one example of the technology, a network change from a first virtual network to a second virtual network is reconfigured for a first virtual machine that is executing on a first virtual machine host. The reconfiguring includes the following. In the first virtual machine host, a mapping change from the first virtual network to the second virtual network is configured by reprogramming drivers in the first virtual machine host for route mapping for the second virtual network. A Dynamic Host Configuration Protocol (DHCP) retrigger is caused without rebooting the first virtual machine. A configuration file is provided to the first virtual machine. The configuration file includes user-specific networking settings. The first virtual machine is reconfigured in accordance with the user-specific networking settings.

Virtual machine client-side virtual network change

A virtual network manager and associated user interface/portal provide customers with simplified centralized management of virtual networks to implement logical groupings of network resources at scale. The virtual network manager enables network segmentation using names or tags, connectivity configuration to create different virtual network topologies, security configuration to provide enforcement of organizational rules without being overwritten and Network Security Group (NSG) management in a simple and scalable manner, safe deployment of network configurations to designated regions on a fix and roll forward basis, and virtual network (VNet) level monitoring.

Logical grouping of network resources and control at scale

A network interface controller (NIC) associated with a virtual machine (VM) in a cloud computing network is configured to be flexibly attached and detached from a parent NIC to thereby enable the virtual machine to simultaneously be attached to multiple different virtual networks (VNets) and/or subnets that are associated with the same or different subscriptions. The inventive NIC, referred to herein as a flexibly extensible NIC (eNIC), enables a service provider to inject compute instances into an existing VNet using a multi-homing configuration in which the data plane uses a dedicated network interface to connect the customer's VNet, while another dedicated network interface provides management plane connectivity to the service provider. Such multi-VNet homing advantageously provides data plane isolation for the customer's VNet to comply with applicable security policies without disrupting management traffic between the injected resources and the service provider.

Cross-subscription multi-VNet homing

A virtual network interface controller (NIC) associated with a virtual machine in a cloud computing network is configured to support one or more network containers that encapsulate networking configuration data and policies that are applicable to a specific discrete computing workload to thereby enable the virtual machine to simultaneously belong to multiple virtual networks using the single NIC. The network containers supported by the NIC can be associated with a single tenant to enable additional flexibility such quickly switching between virtual networks and support pre-provisioning of additional computing resources with associated networking policies for rapid deployment. The network containers can also be respectively associated with different tenants so that the single NIC can support multi-tenant services on the same virtual machine.

Multi-tenant support on virtual machines in cloud computing networks

A system includes a processor executing instructions from a computer-readable storage medium. The instructions include, in response to receiving a job request that identifies a first tenant, obtaining a first virtual network key (VNK) corresponding to the first tenant. The instructions include identifying a first computing system that has resources available to satisfy the job request. The instructions include transmitting a first command to the first computing system. The first command includes the first VNK, instructs the first computing system to assign a virtual machine to the job request, and associates the first VNK with the assigned virtual machine. The instructions include, in response to completion of the job request, transmitting a second command to the first computing system. The second command instructs the first computing system to associate a default VNK with the assigned virtual machine. The default VNK does not correspond to the first tenant.

Fast join and leave virtual network

The disclosed technology is generally directed to virtual machines. In one example of the technology, generic virtual machine artifacts are created. The generic virtual machine artifacts include at least one generic compute artifact and at least one generic network artifact. A first virtual machine is composed and booted with the generic virtual machine artifacts. The first virtual machine is caused to enter a state in which the first virtual machine is polling for a configuration with user-specific compute settings, user-specific networking settings, and user-specific storage settings.

Deployment of partially provisioned virtual machines

The disclosed technology is generally directed to virtual machines. In one example of the technology, a network change from a first virtual network having a first customer Internet Protocol (IP) address to a second virtual network having a second customer IP address is configured for a first virtual machine. The configuring includes controlling the following actions. The second virtual network is provided. At least one networking artifact is associated with a first user that is associated with the first virtual machine. The at least one networking artifact includes the second virtual network. A directory service is updated to map the second customer IP address to a first physical IP address. The first physical IP address is a physical IP address of the first virtual network.

Virtual machine server-side network adaptation

Growing community of inventors

Sammamish, WA, United States of America

Ashish Bhargava