Microsoft Technology Licensing, LLC

Vishal Taneja

Xinyan Zan

Abhishek Shukla

Parag Sharma

Kaihua Xu

Deepak Bansal

Rishabh Tewari

Harish Kumar Chandrappa

Nisheeth Srivastava

Ashish Bhargava

Milan Dasgupta

Neeraj Motwani

Vaibhav Kumar

David Michael Brumley

Anavi Arun Nahar

Sarvesh Sakalanaga

Vladimir Serov

Narayan Annamalai

Raghav Mohan

A hybrid state for a virtual machine (VM) in a cloud computing system enables a VM to communicate with other VMs that belong to a virtual network (VNET VMs) while maintaining connectivity with other VMs that do not belong to the virtual network (non-VNET VMs). A non-VNET VM can be transitioned to a hybrid VM that operates in a hybrid state. The hybrid VM can be assigned a private virtual IP address (VNET address) for communication with other VNET VMs. The hybrid VM can continue to use a physical IP address to communicate with other non-VNET VMs. In this way, the hybrid VM is able to maintain connectivity with other non-VNET VMs during and after migration to the VNET. A network stack can be configured to process data packets that are destined for non-VNET VMs differently from data packets that are destined for VNET VMs.

Support of virtual network and non-virtual network connectivity on the same virtual machine

Virtual networks located in different regions of cloud provider are peered using unique regional identifiers for the virtual networks. The regional identifiers and other information are pushed down a network management stack to implement the peering.

Cross-regional virtual network peering

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

Growing community of inventors

Seattle, WA, United States of America

Vishal Taneja