Skip to content

Commit a460481

Browse files
committed
Added number of required IPs
1 parent 946daee commit a460481

File tree

3 files changed

+6
-4
lines changed

3 files changed

+6
-4
lines changed

articles/dev-box/concept-dev-box-deployment-guide.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,8 @@ When you have the following requirements, you need to use Azure network connecti
108108

109109
When connecting to resources on-premises through Microsoft Entra hybrid joins, work with your Azure network topology expert. Best practice is to implement a [hub-and-spoke network topology](/azure/cloud-adoption-framework/ready/azure-best-practices/hub-spoke-network-topology). The hub is the central point that connects to your on-premises network; you can use an Express Route, a site-to-site VPN, or a point-to-site VPN. The spoke is the virtual network that contains the dev boxes. You peer the dev box virtual network to the on-premises connected virtual network to provide access to on-premises resources. Hub and spoke topology can help you manage network traffic and security.
110110

111+
Network planning should include an estimate of the number of IP addresses you'll need, and their distribution across VNETs. Additional free IP addresses are necessary for the Azure Network connection health check. If the health check fails the dev box definition will not update. You need 1 additional IP address per dev box, and two IP addresses for the health check and Dev Box infrastructure.
112+
111113
Learn more about [Microsoft Dev Box networking requirements](./concept-dev-box-network-requirements.md?tabs=W365).
112114

113115
### Step 3: Configure security groups for role-based access control

articles/dev-box/concept-dev-box-network-requirements.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -229,6 +229,8 @@ These FQDNs and endpoints only correspond to client sites and resources. This li
229229

230230
## Troubleshooting
231231

232+
This section covers some common connect and network issues.
233+
232234
### Connection issues
233235

234236
- **Logon attempt failed**
@@ -243,7 +245,6 @@ These FQDNs and endpoints only correspond to client sites and resources. This li
243245

244246
For more information about troubleshooting group policy issues, see [Applying Group Policy troubleshooting guidance](/troubleshoot/windows-server/group-policy/applying-group-policy-troubleshooting-guidance).
245247

246-
247248
### IPv6 addressing issues
248249

249250
If you're experiencing IPv6 issues, check that the *Microsoft.AzureActiveDirectory* service endpoint is not enabled on the virtual network or subnet. This service endpoint converts the IPv4 to IPv6.
@@ -252,11 +253,10 @@ For more information, see [Virtual Network service endpoints](/azure/virtual-net
252253

253254
### Updating dev box definition image issues
254255

255-
When you update the image used in a dev box definition, you must ensure that you have sufficient IP addresses available in your virtual network.
256+
When you update the image used in a dev box definition, you must ensure that you have sufficient IP addresses available in your virtual network. Additional free IP addresses are necessary for the Azure Network connection health check. If the health check fails the dev box definition will not update. You need 1 additional IP address per dev box, and two IP addresses for the health check and Dev Box infrastructure.
256257

257258
For more information about updating dev box definition images, see [Update a dev box definition](how-to-manage-dev-box-definitions.md#update-a-dev-box-definition).
258259

259-
260260
## Related content
261261

262262
- [Check access to required FQDNs and endpoints for Azure Virtual Desktop](/azure/virtual-desktop/check-access-validate-required-fqdn-endpoint).

articles/dev-box/how-to-manage-dev-box-definitions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ The following steps show you how to create a dev box definition by using an exis
9696

9797
Over time, your needs for dev boxes can change. You might want to move from a Windows 10 base operating system to a Windows 11 base operating system, or increase the default compute specification for your dev boxes. Your initial dev box definitions might no longer be appropriate for your needs. You can update a dev box definition so new dev boxes use the new configuration.
9898

99-
When you update the image used in a dev box definition, you must ensure that you have sufficient IP addresses available in your virtual network.
99+
When you update the image used in a dev box definition, you must ensure that you have sufficient IP addresses available in your virtual network. Additional free IP addresses are necessary for the Azure Network connection health check. If the health check fails the dev box definition will not update. You need 1 additional IP address per dev box, and two IP addresses for the health check and Dev Box infrastructure.
100100

101101
You can update the image, image version, compute, and storage settings for a dev box definition:
102102

0 commit comments

Comments
 (0)