Skip to content

Commit cabd2a5

Browse files
authored
Merge pull request #184746 from cherylmc/patch-2
Update quickstart-any-to-any-template.md
2 parents ab65e26 + 5aaffc1 commit cabd2a5

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

articles/virtual-wan/quickstart-any-to-any-template.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: virtual-wan
66
author: cherylmc
77
ms.service: virtual-wan
88
ms.topic: quickstart
9-
ms.date: 02/02/2021
9+
ms.date: 01/11/2022
1010
ms.author: cherylmc
1111
ms.custom: subject-armqs, mode-arm
1212
---
@@ -24,7 +24,7 @@ If your environment meets the prerequisites and you're familiar with using ARM t
2424
## Prerequisites
2525

2626
* If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
27-
* Public key certificate data is required for this configuration. Sample data is provided in the article. However, the sample data is provided only to satisfy the template requirements in order to create a P2S gateway. After the template completes and the resources are deployed, you must update this field with your own certificate data in order for the configuration to work. See [User VPN certificates](certificates-point-to-site.md#cer).
27+
* Public key certificate data is required for this configuration. Sample data is provided in the article. However, the sample data is provided only to satisfy the template requirements in order to create a P2S gateway. After the template completes and the resources are deployed, you must update this field with your own certificate data in order for the configuration to work. See [Generate and export certificates](certificates-point-to-site.md#cer) for information and steps.
2828

2929
## <a name="review"></a>Review the template
3030

@@ -54,7 +54,7 @@ Multiple Azure resources are defined in the template:
5454
* [**Microsoft.Network/expressroutegateways**](/azure/templates/microsoft.network/expressroutegateways)
5555
* [**Microsoft.Network/vpnserverconfigurations**](/azure/templates/microsoft.network/vpnserverconfigurations)
5656

57-
>[!NOTE]
57+
>[NOTE!]
5858
> This ARM template doesn't create the customer-side resources required for hybrid connectivity. After you deploy the template, you still need to create and configure the P2S VPN clients, the VPN branches (Local Sites), and connect the ExpressRoute circuits.
5959
>
6060
@@ -72,7 +72,11 @@ To deploy this template properly, you must use **Deploy to Azure** button in the
7272

7373
[![Deploy to Azure](../media/template-deployments/deploy-to-azure.svg)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3a%2f%2fraw.githubusercontent.com%2fAzure%2fazure-quickstart-templates%2fmaster%2fquickstarts%2fmicrosoft.network%2fvirtual-wan-with-all-gateways%2fazuredeploy.json)
7474
1. To view the template, click **Edit template**. On this page, you can adjust some of the values such as address space or the name of certain resources. **Save** to save your changes, or **Discard**.
75-
1. On the template page, enter the values. For this template, the P2S public certificate data is required. If you are using this article as an exercise, you can use the following data from this .cer file as sample data for both hubs. Once the template runs and deployment is complete, in order to use the P2S configuration, you must replace this information with the public key [certificate data](certificates-point-to-site.md#cer) for your own deployment.
75+
1. On the template page, enter the values. For this template, the P2S public certificate data is required. If you are using this article as an exercise, you can use the following example data from this .cer file as sample data for both hubs. Once the template runs and deployment is complete, in order to use the P2S configuration, you must replace this information with the public key certificate data for your own deployment. For more information, see [Generate and export certificates](certificates-point-to-site.md#cer).
76+
77+
> [!NOTE]
78+
> The certificate data in example below is supplied for demonstration purposes only. You must replace this information with the public key [certificate data](certificates-point-to-site.md#cer) for your own deployment if you want this configuration to work properly.
79+
>
7680
7781
```certificate-data
7882
MIIC5zCCAc+gAwIBAgIQGxd3Av1q6LJDZ71e3TzqcTANBgkqhkiG9w0BAQsFADAW

0 commit comments

Comments
 (0)