Skip to content

Commit 3d819a9

Browse files
committed
Final fixes from Acrolinx
1 parent 431a869 commit 3d819a9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/dev-box/how-to-manage-network-connection.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -61,16 +61,16 @@ To create a network connection, you need an existing VNet and subnet. If you don
6161

6262

6363
## Allow access to Dev Box endpoints from your network
64-
Network ingress and egress can be controlled using a firewall, network security groups, and even microsoft defender.
64+
Network ingress and egress can be controlled using a firewall, network security groups, and even Microsoft Defender.
6565

6666
If your organization routes egress traffic through a firewall, you need to open certain ports to allow the Dev Box service to function. For more information, see [Network requirements](/windows-365/enterprise/requirements-network).
6767

6868
## Plan a network connection
6969
The following steps show you how to create and configure a network connection in Microsoft Dev Box.
7070
### Types of Azure Active Directory Join
71-
The Dev Box service requires a configured and working Azure AD join or Hybrid AD join which defines how dev boxes join your domain and access resources.
71+
The Dev Box service requires a configured and working Azure AD join or Hybrid AD join, which defines how dev boxes join your domain and access resources.
7272

73-
If your organization uses Azure AD, you can use an Azure AD join, sometimes called a native Azure AD join. Dev box users sign into Azure AD joined dev boxes using their Azure AD account and access resources based on the permissions assigned to that account and policies assigned to the dev box account. Azure AD join enables access to cloud-based and on-premises apps and resources.
73+
If your organization uses Azure AD, you can use an Azure AD join, sometimes called a native Azure AD join. Dev box users sign into Azure AD joined dev boxes using their Azure AD account and access resources based on the permissions assigned to that account. Azure AD join enables access to cloud-based and on-premises apps and resources.
7474

7575
If your organization has an on-premises Active Directory implementation, you can still benefit from some of the functionality provided by Azure AD by using hybrid Azure AD joined dev boxes. These dev boxes are joined to your on-premises Active Directory and registered with Azure Active Directory. Hybrid Azure AD joined dev boxes require network line of sight to your on-premises domain controllers periodically. Without this connection, devices become unusable.
7676

@@ -123,7 +123,7 @@ You can learn more about each type of join and how to plan for them here:
123123

124124
---
125125

126-
Use the following steps to finish creating your network connection, for For Azure AD join and Hybrid Azure AD join:
126+
Use the following steps to finish creating your network connection, for both Azure AD join and Hybrid Azure AD join:
127127
1. Select **Review + Create**.
128128

129129
1. On the **Review** tab, select **Create**.
@@ -152,7 +152,7 @@ To resolve any errors, refer to the [Troubleshoot Azure network connections](/wi
152152

153153

154154
## Remove a network connection from a dev center
155-
You can remove a network connection from a dev center if you no longer want it to be used to connect to network resources. Network connections cannot be removed if they are in use by one or more dev box pools.
155+
You can remove a network connection from a dev center if you no longer want it to be used to connect to network resources. Network connections can't be removed if they are in use by one or more dev box pools.
156156

157157
1. In the [Azure portal](https://portal.azure.com), in the search box, type *Dev centers* and then select **Dev centers** from the list.
158158

0 commit comments

Comments
 (0)