|
1 | 1 | ---
|
2 | 2 | title: 'Generate and export certificates for P2S: PowerShell'
|
3 | 3 | titleSuffix: Azure VPN Gateway
|
4 |
| -description: Learn how to create a self-signed root certificate, export a public key, and generate client certificates for VPN Gateway Point-to-Site connections. |
5 |
| -services: vpn-gateway |
| 4 | +description: Learn how to create a self-signed root certificate, export a public key, and generate client certificates for VPN Gateway point-to-site connections. |
6 | 5 | author: cherylmc
|
7 |
| - |
8 | 6 | ms.service: vpn-gateway
|
9 | 7 | ms.topic: how-to
|
10 |
| -ms.date: 06/03/2021 |
| 8 | +ms.date: 07/06/2022 |
11 | 9 | ms.author: cherylmc
|
12 | 10 |
|
13 | 11 | ---
|
14 |
| -# Generate and export certificates for Point-to-Site using PowerShell |
| 12 | +# Generate and export certificates for point-to-site using PowerShell |
15 | 13 |
|
16 |
| -Point-to-Site connections use certificates to authenticate. This article shows you how to create a self-signed root certificate and generate client certificates using PowerShell on Windows 10 or later, or Windows Server 2016. If you are looking for different certificate instructions, see [Certificates - Linux](vpn-gateway-certificates-point-to-site-linux.md) or [Certificates - MakeCert](vpn-gateway-certificates-point-to-site-makecert.md). |
| 14 | +Point-to-site connections use certificates to authenticate. This article shows you how to create a self-signed root certificate and generate client certificates using PowerShell on Windows 10 or later, or Windows Server 2016 or later. |
17 | 15 |
|
18 |
| -The steps in this article apply to Windows 10 or later, or Windows Server 2016. The PowerShell cmdlets that you use to generate certificates are part of the operating system and do not work on other versions of Windows. The Windows 10 or later, or Windows Server 2016 computer is only needed to generate the certificates. Once the certificates are generated, you can upload them, or install them on any supported client operating system. |
| 16 | +The PowerShell cmdlets that you use to generate certificates are part of the operating system and don't work on other versions of Windows. The host operating system is only used to generate the certificates. Once the certificates are generated, you can upload them or install them on any supported client operating system. |
19 | 17 |
|
20 |
| -If you do not have access to a Windows 10 or later, or Windows Server 2016 computer, you can use [MakeCert](vpn-gateway-certificates-point-to-site-makecert.md) to generate certificates. The certificates that you generate using either method can be installed on any [supported](vpn-gateway-howto-point-to-site-resource-manager-portal.md#faq) client operating system. |
| 18 | +If you don't have a computer that meets the operating system requirement, you can use [MakeCert](vpn-gateway-certificates-point-to-site-makecert.md) to generate certificates. The certificates that you generate using either method can be installed on any [supported](vpn-gateway-howto-point-to-site-resource-manager-portal.md#faq) client operating system. |
21 | 19 |
|
22 |
| -[!INCLUDE [generate and export certificates](../../includes/vpn-gateway-generate-export-certificates-include.md)] |
| 20 | +[!INCLUDE [Generate and export - this include is for both vpn-gateway and virtual-wan](../../includes/vpn-gateway-generate-export-certificates-include.md)] |
23 | 21 |
|
24 | 22 | ## <a name="install"></a>Install an exported client certificate
|
25 | 23 |
|
26 |
| -Each client that connects to the VNet over a P2S connection requires a client certificate to be installed locally. |
27 |
| - |
28 |
| -To install a client certificate, see [Install a client certificate for Point-to-Site connections](point-to-site-how-to-vpn-client-install-azure-cert.md). |
| 24 | +Each client that connects over a P2S connection requires a client certificate to be installed locally. To install a client certificate, see [Install a client certificate for point-to-site connections](point-to-site-how-to-vpn-client-install-azure-cert.md). |
29 | 25 |
|
30 | 26 | ## Next steps
|
31 | 27 |
|
32 |
| -Continue with your Point-to-Site configuration. |
| 28 | +Continue with your point-to-site configuration. |
33 | 29 |
|
34 | 30 | * For **Resource Manager** deployment model steps, see [Configure P2S using native Azure certificate authentication](vpn-gateway-howto-point-to-site-resource-manager-portal.md).
|
35 |
| -* For **classic** deployment model steps, see [Configure a Point-to-Site VPN connection to a VNet (classic)](vpn-gateway-howto-point-to-site-classic-azure-portal.md). |
| 31 | +* For **classic** deployment model steps, see [Configure a point-to-site VPN connection to a VNet (classic)](vpn-gateway-howto-point-to-site-classic-azure-portal.md). |
0 commit comments