Skip to content

Commit

Permalink
Update virtual-wan-faq-include.md
Browse files Browse the repository at this point in the history
Capitalize Azure (proper noun)
  • Loading branch information
ciphertxt authored Apr 16, 2019
1 parent 6e2aed2 commit 6007d14
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions includes/virtual-wan-faq-include.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ Yes. See the [Pricing](https://azure.microsoft.com/pricing/details/virtual-wan/)

### How do I calculate price of a hub?

You would pay for the service in the hub. For example, 10 branches or on-premises devices requiring to connect to Azure Virtual WAN would imply connecting to VPN end points in the hub. Lets say this is VPN of 1 scale unit = 500 Mbps, this is charged at $0.361/hr. Each connection is charged at $0.08/hr. For 10 connections, the total charge of service/hr would be $0.361 + $.8/hr. Data charges for traffic leaving azure apply.
You would pay for the service in the hub. For example, 10 branches or on-premises devices requiring to connect to Azure Virtual WAN would imply connecting to VPN end points in the hub. Lets say this is VPN of 1 scale unit = 500 Mbps, this is charged at $0.361/hr. Each connection is charged at $0.08/hr. For 10 connections, the total charge of service/hr would be $0.361 + $.8/hr. Data charges for traffic leaving Azure apply.

### How do new partners that are not listed in your launch partner list get onboarded?

Expand Down Expand Up @@ -124,4 +124,4 @@ The traffic follows the pattern: branch device ->ISP->Microsoft edge->Microsoft

### In this model, what do you need at each site? Just an internet connection?

Yes. An Internet connection and physical device that supports IPsec, preferably from our integrated [partners](https://go.microsoft.com/fwlink/p/?linkid=2019615). You can optionally, manually manage the configuration and connectivity to Azure from your preferred device.
Yes. An Internet connection and physical device that supports IPsec, preferably from our integrated [partners](https://go.microsoft.com/fwlink/p/?linkid=2019615). You can optionally, manually manage the configuration and connectivity to Azure from your preferred device.

0 comments on commit 6007d14

Please sign in to comment.