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
+60-26Lines changed: 60 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,32 +73,66 @@ The following table lists requirements that could influence your Microsoft Dev B
73
73
74
74
## Microsoft Dev Box deployment plan
75
75
76
-
77
-
78
-
Describe for each design area what the considerations are and, optionally, the recommendations. For complex areas, we might refer to a separate conceptual article, such as Intune configuration or networking.
79
-
80
-
1. Azure subscription
81
-
1. Dev center
82
-
- Considerations
83
-
- Recommendations
84
-
1. Networking
85
-
- Considerations
86
-
- Recommendations
87
-
1. Compute galleries
88
-
- Considerations
89
-
- Recommendations
90
-
1. Dev box definitions
91
-
- Considerations
92
-
- Recommendations
93
-
1. Projects
94
-
- Considerations
95
-
- Recommendations
96
-
1. Dev box access (browser vs RDP client)
97
-
- Considerations
98
-
- Recommendations
99
-
1. Intune configuration
100
-
- Considerations
101
-
- Recommendations
76
+
After you've defined your requirements for Microsoft Dev Box within your organization, you can start the deployment. To set up Microsoft Dev Box to give developers self-service access to dev boxes, follow these steps.
0 commit comments