Azure VNet Scenarios
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
# Scenario 1: Private access to backend resources
Public internet -> ACA -> VNet -> Azure Storage
Public internet -> AppService -> VNet -> Azure Storage
Public internet -> ACA -> VNet -> Cosmos
Public internet -> AppService -> VNet -> Cosmos
Public internet -> ACA -> VNet -> Sql Server
Public internet -> AppService -> VNet -> Sql Server
# Scenario 1.5: Public access with special frontends
Public internet -> AFD -> ACA (ServiceTags)
Public internet -> AFD -> ACA (Private Link etc)
# Scenario 2: Hybrid Cloud (using Azure an example)
Corporate PC -> Internal Network -> Express Route -> VNet(1) -> ACA -> VNet(1) -> Azure Storage
Corporate PC -> Internal Network -> Express Route -> VNet(1) -> ACA -> VNet(2) -> Azure Storage
Corporate PC -> Internal Network -> Express Route -> VNet(1) -> ACA -> VNet(1) -> On Prem Resource
# Scenario 3: Network overlays
PC -> Overlay Network -> ACA (via Overlay proxy) ... eg. tailscale/netbird
Contributor guide
Assessment
This issue has not been assessed yet.