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/concept-dev-box-deployment-guide.md
+18-3Lines changed: 18 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,9 +135,24 @@ You might consider creating multiple dev centers in the following cases:
135
135
136
136
Learn more about how to [create a dev center for Microsoft Dev Box](./quickstart-configure-dev-box-service.md).
137
137
138
-
### Step x: Configure network connections
139
-
- Azure networking connections
140
-
- Hosted networking connections
138
+
### Step 5: Configure network connections
139
+
140
+
Network connections control where dev boxes are created and hosted, and enable you to connect to other Azure or corporate resources. Depending on your level of control, you can use Microsoft-hosted network connections or bring your own Azure network connections.
141
+
142
+
Microsoft-hosted network connections provide network connectivity in a SaaS manner. Microsoft manages the network infrastructure and related services for your dev boxes. Microsoft-hosted networks are a cloud-only deployment with support for Microsoft Entra join. This option isn't compatible with the Microsoft Entra hybrid join model.
143
+
144
+
A Microsoft-hosted network connection is created and assigned to a specific dev center project. You can create multiple network connections per project. The network connection created in a project are not shared with other projects.
145
+
146
+
You can also use Azure network connections (bring your own network) to connect to Azure virtual networks and optionally connect to corporate resources. With Azure network connections, you manage and control the entire network setup and configuration. You can use either Microsoft Entra join or Microsoft Entra hybrid join options with Azure network connections, enabling you to connect to on-premises Azure Active Directory Domain Services.
147
+
148
+
You create Azure network connections and assign them to a dev center. All projects in a dev center share the network connections in the dev center.
149
+
150
+
Consider creating a separate network connection in the following scenarios:
151
+
152
+
- A developer or team is located in a different geographic region. The network connection region determines where the dev boxes are hosted.
153
+
- A developer or team needs access to Azure resources. Consider creating a separate Azure network connection per usage scenario (for example, access to a source control server, or access to a web app and database server).
154
+
- A developer or team needs access to corporate, on-premises resources. Create an Azure network connection and configure it for hybrid connectivity.
155
+
- Dev box users need to authenticate with their Active Directory account. Create an Azure network connection and configure it for hybrid connectivity.
0 commit comments