Networks › Virtual network peering: Connect virtual networks within the same Azure region › Global virtual network peering: Connecting virtual networks across Azure regions › Traffic remains on the Microsoft network
private endpoint › Choose to remove public IP on PaaS service › Traffic remains on the Microsoft network › Integration with on-premises and peered networks
Data Lake Storage Gen2 All public regions GA Azure SQL Database All public regions GA Azure Synapse Analytics All public regions GA Azure Cosmos DB All public regions GA Azure Database for PostgreSQL - Single server All public regions GA Azure Database for MySQL All public regions GA Azure Database for MariaDB All public regions GA Azure Key Vault All public regions GA Azure Kubernetes Service - Kubernetes API All public regions GA Azure Search All public regions GA Azure Container Registry All public regions GA Azure App Configuration All public regions GA Azure Event Hub All public regions GA Azure Service Bus All public regions GA Azure Relay All public regions GA Azure Event Grid All public regions GA Azure Web Apps All public regions GA
join a vnet(subnet) for egress › Two flavours: › Regional virtual network integration › Allows you to access resources in your vnet in the same region › Gateway-required virtual network integration › Allows you to access resources in other regions › You can block outbound traffic with an NSG
› Azure SQL Data Warehouse › Azure Database for PostgreSQL server › Azure Database for MySQL server › Azure Database for MariaDB › Azure Cosmos DB › Azure Key Vault › Azure Service Bus › Azure Event Hubs › Azure Data Lake Store Gen 1 › Azure App Service › Azure Cognitive Services › Public Preview: Azure Container Registry
Access through private IP Address Access through public IP Address Access form within Azure and on-premises to PaaS Access to PaaS in Azure More difficult to setup Easier to setup You need to own both sides* You do not need to own both sides Traffic remains on the Microsoft backbone 19 * Strictly speaking not true, but…
to VMs › Uses an HTML5 based web client that streams to your local device › No public IP is required on the Azure VM › No open RDP / SSH ports to the internet › Use the Azure Portal or Native Client 22
zones from an on-premises environment › Conditionally forward DNS requests to on-premises DNS servers › Fully managed: Built-in high availability, zone redundancy. › Cost reduction: Reduce operating costs and run at a fraction of the price of traditional IaaS solutions. › DevOps Friendly: Build your pipelines with Terraform, ARM, or Bicep. 28