About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Multi-site Australian businesses may need hosted application servers reachable from a branch without advertising RDP or database listeners on the public internet. That goal is met with private connectivity: encrypted site-to-site links between branch firewalls and the hosting environment, or user VPN that lands on the same private network as the hosted workload. The pattern is generic; carrier and hyperscaler products vary by contract.
Why it matters
Publishing application ports broadly increases attack surface and complicates compliance conversations. Branches still need predictable paths for printing integrations, file drops, or thick clients that cannot use a public gateway. Private reachability also keeps internal hostnames meaningful when you use split-horizon DNS — see Internal DNS names as a production dependency between hosted applications for production naming dependencies.
For managed hosting buyers, the benefit is continuity: warehouse, clinic or regional office staff work the same hosted LOB as head office, with traffic that never needs to be "on the internet" except inside encrypted tunnels.
How it works
At a high level, three building blocks recur (author synthesis, not a single vendor checklist):
- Private network at the hoster. A logically isolated network (often described as VPC, VNet or private VLAN design) holds application servers and management interfaces. What is included is contract-defined.
- Encryption endpoint at each branch. A firewall or router terminates IPsec or vendor-equivalent VPN toward the hosting side.
- Routing and DNS. Branch subnets receive routes to hosted private prefixes; names resolve to private addresses when staff are on branch networks.
Branch LAN ----[site-to-site VPN]---- Hosting private network ---- app servers
^
|
(optional user VPN for travellers)
Microsoft's Azure networking documentation hub lists hybrid offerings (VPN Gateway, ExpressRoute, Private Link) as a table of contents, not branch-by-branch design rules. For concrete site-to-site mechanics, Microsoft's site-to-site VPN (VPN Gateway) tutorial illustrates gateway configuration at editorial level; your hoster's attachment may use different appliances. RFC 4301 defines the IPsec security architecture in vendor-neutral terms.
Contrast with published internet entry: RD Gateway or TLS-terminated application gateways place a controlled entry on the internet. Branches may use that path when private link is uneconomic; this article focuses on the private alternative.
Material difference from published articles: RD Gateway or site-to-site VPN for staff reaching hosted applications compares access paths for staff. Customer integrations into a hosted ISV product: VPN, API and file drop covers integration attachment. This piece focuses on branch LAN reachability without publishing application ports, plus address overlap planning before cutover.
What to choose and why (editorial recommendations)
Choose site-to-site when the branch has stable internet, qualified firewall admin, and many users sharing the same subnets. Operating cost is mostly fixed; per-user VPN load is lower.
Choose user VPN when the branch is small, temporary, or lacks decent CPE — travellers reuse the same profile.
Choose a gateway hybrid when only some functions need private reachability (for example, a nightly file feed) while interactive users use a gateway. Document which flows use which path to avoid duplicate routes.
Work with your hoster early on addressing overlap. Branch 10.x and hosted 10.y must not collide; renumbering a stubborn legacy subnet is cheaper before cutover than during it (standard practice; confirm in your addressing plan).
Read next
Related articles you may want next.
- HostingRD Gateway or site-to-site VPN for staff reaching hosted applicationsChoose a per-user RDP gateway or routed site connection by the resources staff need, with separate identity, segmentation and MFA decisions.Read article
- HostingCustomer integrations into a hosted ISV product: VPN, API and file dropChoose an integration route while preserving tenant identity, authorised access, bounded resource use and reliable handling of retries and duplicates.Read article
- HostingInternal DNS names as a production dependency between hosted applicationsWhy hard-coded hostnames, short TTLs and split zones couple routine DNS changes to hosted application outages.Read article
Risks and limits
Assuming "private" means "secure without auth." Network privacy does not replace application authentication, patching or least privilege.
Single circuit branches. One NBN or 4G link without failover still breaks the branch; hosting uptime does not fix local outages.
Enterprise carrier products. ExpressRoute, Direct Connect and similar designs are valid for some enterprises. Ask your provider what private attachment they actually operate — see VPC networking.
Diagnostics elsewhere. This is reachability design, not step-by-step repair of established tunnels that fail health checks.
Related education: VPC networking. Delivery context: How it works.
Sources
- Microsoft Learn — Azure networking documentation — hybrid connectivity service list.
- Microsoft Learn — Site-to-site VPN (VPN Gateway) — illustrative site-to-site pattern (Azure-specific).
- RFC 4301 — Security Architecture for IP — IPsec framework at editorial level.
Learning notes
- Private branch reachability uses encrypted links, not public port exposure.
- Address planning and DNS belong in the same workshop as the VPN.
- Site-to-site suits stable branches; user VPN suits small or mobile sites.
- Private network path does not remove application auth requirements.
- Provider contract defines what private attachment is actually offered.
This article was originally published on .