Overview
Network connections enable secure communication between your on-premises or Azure-based systems and your Entegrata instance. These connections allow Entegrata collectors to access your systems while maintaining network isolation and security. Entegrata supports two primary connection types:- Site-to-Site (S2S) VPN - Encrypted tunnel between your network and Entegrata
- VNet Peering - Direct Azure Virtual Network connection for Azure-based infrastructure
Network connections are configured during instance provisioning. Contact your Entegrata representative if you need to modify your connection type.
Connection Status
The Network Connections card displays the current status of your connection with color-coded badges for quick identification.
Network Status Meanings
🟢 Connected - Network connection is active and functioning🟡 Transitioning - Connection is being established or modified🔴 Error - Connection failed or encountered an issue⚫ Not Connected - No active connection configured
Network Configuration
What Network Configuration Controls
Network configuration defines which IP addresses and CIDR ranges are allowed to communicate with your Entegrata instance. This ensures that only authorized systems can establish network connections.Viewing Network Configuration
To view your current configuration select **Network Information: View Details **on the Network Configuration card. The modal displays:- Internal/API Whitelisting: IPs Entegrata uses to call external APIs
- Firm Systems Access: CIDR ranges allowed to access firm systems To view your current network configuration:
IP Whitelisting
Why IP Whitelisting Matters
Security and Access Control
Security and Access Control
IP whitelisting ensures that only known and trusted systems can communicate with your Entegrata instance. This prevents unauthorized access attempts and provides an additional security layer beyond authentication.
Collector Connectivity
Collector Connectivity
Entegrata collectors running in your environment must have their IP addresses whitelisted to successfully transmit data to your instance. Missing IPs will result in collection failures.
Compliance Requirements
Compliance Requirements
Many regulatory frameworks require strict network access controls. IP whitelisting helps satisfy these requirements by providing traceable, auditable network access restrictions.
CIDR Ranges for System Access
Understanding CIDR Notation
CIDR (Classless Inter-Domain Routing) notation allows you to specify ranges of IP addresses efficiently:| CIDR Range | Description | Number of IPs |
|---|---|---|
x.x.x.x/32 | Single IP address | 1 |
x.x.x.x/24 | Class C subnet | 256 |
x.x.x.x/16 | Class B subnet | 65,536 |
x.x.x.x/8 | Class A subnet | 16,777,216 |
Managing Network Connections
How Connections Are Established
Network connections are typically configured during instance provisioning:Infrastructure Assessment
Entegrata’s team assesses your network architecture to determine the optimal connection type (S2S VPN or VNet Peering).
Connection Configuration
Based on your infrastructure, the appropriate connection parameters are configured, including:
- Gateway IPs
- Encryption settings (for S2S VPN)
- Peering settings (for VNet Peering)
Infrastructure Deployment
The connection is provisioned through Azure infrastructure, creating the secure network path between your systems and Entegrata.
Troubleshooting Connection Issues
Status stuck in Transitioning
Status stuck in Transitioning
If the status remains in Transitioning for more than 30 minutes:
- Refresh your browser to ensure you’re seeing the latest status
- Check if other infrastructure changes are in progress
- Contact Entegrata support if the issue persists
Connection shows Error status
Connection shows Error status
If the connection displays Error:
- Check the Network Connections card for error details
- Verify your VPN gateway is running (for S2S VPN connections)
- Confirm firewall rules aren’t blocking the connection
- Contact Entegrata support with error details
Collectors can't connect despite Connected status
Collectors can't connect despite Connected status
If collectors fail to connect even with Connected status:
- Verify collector IPs are in the network whitelist
- Check collector logs for specific connection errors
- Confirm collectors are using the correct endpoint URLs
- Review your local firewall rules for outbound blocks