Planning an Exchange hybrid deployment.  This page has the support statement around what cross-premises permissions are supported (The below is from August 2016).

You should consider the following before you implement an Exchange Hybrid Deployment:

• Hybrid deployment requirements Before you configure a hybrid deployment, you need to make sure your on-premises organization meets all of the prerequisites required for a successful deployment. For more information, see Hybrid deployment prerequisites.
  Continue reading

During many Exchange projects (On-Premises or in the Cloud) we see a lot of situations when organisations create an additional mailbox (secondary mailbox) for some users. Everybody, who works with Exchange environments, knows that a mailbox could have multiple email addresses associated with it. The question is always, why not just define an additional email as an alias to the mailbox? Of course, this scenario could work in some use cases. You probably think, it’s OK…

However, when someone sends an email to the address that defined as an alias, the recipient is not going to easily see to what email address the email was sent (in more details down in this blog post). Also, when we only use aliases, all emails that we send are always seen as if they were sent from the primary email address associated with the mailbox.

We all know that  pictures explain better than 1000 words, so let’s take a look. Because of this, let’s see how to do this On-Premises and in the Cloud (Office 365).

VNet Peering for Azure Virtual Network lets us directly link two virtual networks in the same region. Virtual machine resources in both virtual networks can connect directly through private IP addresses as if they were part of the same network.

VNet Peering routes packets between virtual networks through the internal Azure backbone network, so there’s no gateway in the path. This allows for a low-latency, high-bandwidth connection between virtual machines in the virtual networks.

VNet Peering also allows transit through the peered virtual networks, so a Network Virtual Appliance or a VPN gateway in one virtual network can be used by a virtual machine in another peered virtual network. Peering works across virtual networks in different subscriptions and between an Azure Resource Manager and an Azure Service Management virtual network.

Presenting “Cloud-Enabled Architecture”, at HPE Discover Recap Roadshow 2016 in 5 cities across Canada! Looking forward meeting with all of you!

Time to time, during our Microsoft Cloud projects, we get pretty much the same question: “Do Azure VPN or ExpressRoute provide traffic encryption?” So, here is an explanation :)…