Global VNet to VNet peering is when you connect different virtual networks (VNet) across Azure regions. Once the connectivity is established between the virtual networks, traffic is then privately routed through the Microsoft backbone infrastructure providing a low-latency, high-bandwidth connection between your resources meaning no public internet, gateways or encryption is required in the communication between the virtual networks.

This guide shows you how to peer a VNet in the UK South region with a VNet in East US.

Understanding exactly where your business resources and data sits within the cloud is an important part of your governance, control and your geo-compliance requirements. It can also assist with reducing latency if the regions are the closest to your end users.

This guide shows you how to implement Azure region policies to only allowing your resources to be deployed in UK locations.

A Point-to-Site (P2S) VPN gateway lets you create a secure connection to your Azure virtual network from an individual client computer, Point-to-Site VPN connections are useful when you want to connect to your Azure VNet from remote locations such as your home or hotel. This is very similar to a traditional VPN client but rather than connecting to your office which normally has some sort of single points of failure (such as a single internet connection or 1 firewall) you are utilising the highly available Azure configuration. This guide shows you how to set up a Client VPN connection with certificates to your Azure environment using the portal.

The virtual machine serial console in the Azure portal provides access to a text-based console for Windows virtual machines. This serial connection connects to the COM1 serial port of the VM providing access to it, independent of the virtual machine's network or operating system state. Access to the serial console for the VM can be done only by using the Azure portal.

When a user is deleted from Office 365 the account is moved into a recycle bin where it is held for 30 days before being purged, this is very useful should users be accidentally deleted and can be easily recovered however this can still cause issues with Azure Active Directory Connect (AADC - used for syncing users from on-premise to Office365) when you have duplicated users/errors when trying to link up accounts for the first time when the first sync may have been done incorrectly, this guide shows you how to permanently delete the problematic deleted item therefore allowing you to redo the AADC sync as if for the first time.

The following commands is designed for Microsoft Cloud Solutions Providers (CSP) to connect to a customer tenant using PowerShell.