Skip to content

Commit 018388b

Browse files
authored
Merge pull request #49894 from cherylmc/vwan2
update
2 parents 87a97a2 + 852042e commit 018388b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-wan/virtual-wan-configure-automation-providers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: cherylmc
66

77
ms.service: virtual-wan
88
ms.topic: conceptual
9-
ms.date: 07/10/2018
9+
ms.date: 08/23/2018
1010
ms.author: cherylmc
1111
Customer intent: As a Virtual WAN software-defined connectivity provider, I want to set up a provisioning environment.
1212
---
@@ -19,7 +19,7 @@ Software-defined connectivity solutions typically use a controller or a device p
1919

2020
## <a name="access"></a>Access control
2121

22-
Customers must be able to set up appropriate access control for Virtual WAN in the device UI. This is recommended using an Azure Service Principal. Service principal-based access provides the device controller appropriate authentication to upload branch information.
22+
Customers must be able to set up appropriate access control for Virtual WAN in the device UI. This is recommended using an Azure Service Principal. Service principal-based access provides the device controller appropriate authentication to upload branch information. For more information,see [Create service principal](../azure-resource-manager/resource-group-create-service-principal-portal.md#create-an-azure-active-directory-application).
2323

2424
## <a name="site"></a>Upload branch information
2525

0 commit comments

Comments
 (0)