You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-wan/openvpn-azure-ad-tenant-multi-app.md
+7-13Lines changed: 7 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,18 +6,18 @@ author: anzaman
6
6
7
7
ms.service: virtual-wan
8
8
ms.topic: conceptual
9
-
ms.date: 02/19/2020
9
+
ms.date: 03/19/2020
10
10
ms.author: alzam
11
11
12
12
---
13
13
# Create an Azure Active Directory tenant for P2S OpenVPN protocol connections
14
14
15
-
When connecting to your VNet, you can use certificate-based authentication or RADIUS authentication. However, when you use the Open VPN protocol, you can also use Azure Active Directory authentication. If you want different set of users to be able to connect to different VPN gateways, you can register multiple apps in AD and link them to different VPN gateways.
15
+
When connecting to your VNet, you can use certificate-based authentication or RADIUS authentication. However, when you use the Open VPN protocol, you can also use Azure Active Directory authentication. If you want different set of users to be able to connect to different gateways, you can register multiple apps in AD and link them to different gateways.
16
16
17
17
This article helps you set up an Azure AD tenant for P2S OpenVPN authentication, and create and register multiple apps in Azure AD to allow different access for different users and groups.
18
18
19
19
> [!NOTE]
20
-
> Azure AD authentication is supported only for OpenVPN® protocol connections.
20
+
> Azure AD authentication is supported only for OpenVPN® protocol connections.
@@ -41,7 +41,7 @@ A P2S configuration defines the parameters for connecting remote clients.
41
41
```
42
42
43
43
> [!NOTE]
44
-
> Do not use the Azure VPN client's application ID in the commands above: It will grant all users access to the VPN gateway. Use the ID of the application(s) you registered.
44
+
> Do not use the Azure VPN client's application ID in the commands above: It will grant all users access to the gateway. Use the ID of the application(s) you registered.
45
45
46
46
## <aname="hub"></a>7. Edit hub assignment
47
47
@@ -77,7 +77,7 @@ Use the VPN profile to configure your clients.
77
77
78
78
5. Extract the downloaded zip file.
79
79
80
-
6. Browse to the unzipped “AzureVPN” folder.
80
+
6. Browse to the unzipped "AzureVPN" folder.
81
81
82
82
7. Make a note of the location of the "azurevpnconfig.xml" file. The azurevpnconfig.xml contains the setting for the VPN connection and can be imported directly into the Azure VPN Client application. You can also distribute this file to all the users that need to connect via e-mail or other means. The user will need valid Azure AD credentials to connect successfully.
83
83
@@ -86,7 +86,7 @@ Use the VPN profile to configure your clients.
86
86
To connect, you need to download the Azure VPN Client and import the VPN client profile that was downloaded in the previous steps on every computer that wants to connect to the VNet.
87
87
88
88
> [!NOTE]
89
-
> Azure AD authentication is supported only for OpenVPN® protocol connections.
89
+
> Azure AD authentication is supported only for OpenVPN® protocol connections.
90
90
>
91
91
92
92
#### To download the Azure VPN client
@@ -147,16 +147,10 @@ Use this [link](https://go.microsoft.com/fwlink/?linkid=2117554) to download the
147
147
148
148
1. Navigate to the virtual WAN.
149
149
150
-
2. On the Overview page, each point on the map represents a hub. Hover over any point to view the hub health summary.
150
+
2. On the Overview page, each point on the map represents a hub.
151
151
152
152
3. In the Hubs and connections section, you can view hub status, site, region, VPN connection status, and bytes in and out.
153
153
154
-
## <aname="viewhealth"></a>11. View your resource health
155
-
156
-
1. Navigate to your WAN.
157
-
158
-
2. On your WAN page, in the **SUPPORT + Troubleshooting** section, click **Health** and view your resource.
159
-
160
154
## <aname="cleanup"></a>Clean up resources
161
155
162
156
When you no longer need these resources, you can use [Remove-AzureRmResourceGroup](/powershell/module/azurerm.resources/remove-azurermresourcegroup) to remove the resource group and all of the resources it contains. Replace "myResourceGroup" with the name of your resource group and run the following PowerShell command:
Copy file name to clipboardExpand all lines: articles/virtual-wan/vpn-over-expressroute.md
+2-7Lines changed: 2 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: cherylmc
6
6
7
7
ms.service: virtual-wan
8
8
ms.topic: article
9
-
ms.date: 02/18/2020
9
+
ms.date: 03/19/2020
10
10
ms.author: cherylmc
11
11
12
12
---
@@ -218,14 +218,9 @@ If you need instructions to configure your device, you can use the instructions
218
218
## <aname="viewwan"></a>5. View your virtual WAN
219
219
220
220
1. Go to the virtual WAN.
221
-
1. On the **Overview** page, each point on the map represents a hub. Hover over any point to view the hub's health summary.
221
+
1. On the **Overview** page, each point on the map represents a hub.
222
222
1. In the **Hubs and connections** section, you can view hub, site, region, and VPN connection status. You can also view bytes in and out.
223
223
224
-
## <aname="viewhealth"></a>6. View your resource health
225
-
226
-
1. Go to your WAN.
227
-
1. In the **SUPPORT + Troubleshooting** section, select **Health** and view your resource.
228
-
229
224
## <aname="connectmon"></a>7. Monitor a connection
230
225
231
226
Create a connection to monitor communication between an Azure virtual machine (VM) and a remote site. For information about how to set up a connection monitor, see [Monitor network communication](~/articles/network-watcher/connection-monitor.md). The source field is the VM IP in Azure, and the destination IP is the site IP.
0 commit comments