Skip to content

VNet Peering Form

Azure VNET Peering Quest…

1. Requirements from the Customer

To initiate the peering process, the customer must complete two main tasks: providing network information and configuring a Service Principal for automation.

Technical and Network Details

The customer needs to provide the following specifics regarding their Azure environment:

  • Contact Information: A technical network administrator's name, phone number, and email.

  • VNet Specifics: The Remote VNet Resource ID, the Azure region (e.g., eastus), and the VNet Address Space (CIDRs).

  • Deployment Scope: Confirmation of whether both Non-Production and Production workloads should be peered.

  • CIDR Verification: Confirmation that there are no overlapping IP address ranges with Rhapsody’s Azure environment, as Azure blocks peering if CIDRs overlap.

Service Principal & Permissions

Rhapsody uses automated peering, which requires the customer to create a Service Principal (an identity for the application) with specific permissions. The customer must:

  • Create a Custom Role: Define a role named "VNet Peering Manager - Rhapsody" with permissions to read VNets and manage peering actions .

  • Assign Scopes: Limit this role's access specifically to the VNets being peered .

  • Share Credentials: Securely forward the Service Principal ID and Secret to the Rhapsody team.

2. What This Process Does

The goal of this questionnaire and the subsequent configuration is to establish a functional, secure connection between two separate Azure environments.

  • Enables Private Connectivity: Once peering is in a "Connected" state, traffic flows across the Azure backbone without traversing the public internet.

  • Automates Management: By using the Service Principal, Rhapsody’s Cloud Operations team can programmatically create and maintain the peering connection.

  • Supports Complex Routing: The configuration allows for advanced features like Gateway Transit (using a VPN gateway in one VNet for the other) and Global VNet Peering (connecting VNets across different Azure regions) .

  • Provides a Troubleshooting Framework: The document outlines a protocol for verifying Network Security Groups (NSGs), User Defined Routes (UDRs), and connectivity tests (like ping or