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/dev-box/how-to-manage-network-connection.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,16 +61,16 @@ To create a network connection, you need an existing VNet and subnet. If you don
61
61
62
62
63
63
## 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.
65
65
66
66
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).
67
67
68
68
## Plan a network connection
69
69
The following steps show you how to create and configure a network connection in Microsoft Dev Box.
70
70
### 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.
72
72
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.
74
74
75
75
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.
76
76
@@ -123,7 +123,7 @@ You can learn more about each type of join and how to plan for them here:
123
123
124
124
---
125
125
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:
127
127
1. Select **Review + Create**.
128
128
129
129
1. On the **Review** tab, select **Create**.
@@ -152,7 +152,7 @@ To resolve any errors, refer to the [Troubleshoot Azure network connections](/wi
152
152
153
153
154
154
## 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.
156
156
157
157
1. In the [Azure portal](https://portal.azure.com), in the search box, type *Dev centers* and then select **Dev centers** from the list.
0 commit comments