Skip to content

Commit 02d8ec1

Browse files
authored
Add Windows dev machine setup instructions
Added instructions for spinning up a Windows dev machine with Visual Studio for .NET development in Azure.
1 parent 277bdec commit 02d8ec1

File tree

1 file changed

+28
-1
lines changed

1 file changed

+28
-1
lines changed

_articles/azure.md

Lines changed: 28 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,34 @@ Sources:
3636

3737
## Cookbook
3838

39-
### RBAC
39+
### Spin up a Windows dev machine with Visual Studio for .NET development
40+
41+
To have a Windows .NET environment for testing, especially for legacy frameworks like .NET Framework on Windows, you can spin up a virtual machine with the following settings (tested in Jan 2026):
42+
43+
**1. Create the VM**
44+
45+
- Virtual machine name: **yourname-dev-machine**
46+
- Zone options: (just pick 1 zone)
47+
- Image: **Visual Studio 2022 Community on Windows 11 Enterprise, version 25H2 (x64)**
48+
- Size: **Standard_D4s_v3** (4 vcpus, 16 GiB memory) - note that this costs $233/mo.
49+
- Public inbound ports: **None**
50+
- Disks: (accept the default, 127 GiB)
51+
- Networking tab:
52+
- NIC network security group: **Advanced** (we'll allowlist your IP address after VM creation)
53+
- Delete public IP and NIC when VM is deleted - **yes**
54+
- Accept the rest of the defaults and **Create**.
55+
56+
**2. Update the Security Group**
57+
58+
Azure always wants to open up RDP to the entire internet for some reason. So you'll need to lock it down. After creation:
59+
60+
1. Edit the new Network Security Group (NSG) that is associated with the VM.
61+
1. Delete the default "allow all" inbound rule to port 3389
62+
1. Add a new rule: Settings > Inbound security rules > Add:
63+
- Source: **My IP Address**
64+
- Service: **RDP**
65+
66+
### RBAC in Azure
4067

4168
#### Working with App Registrations and Service Principals
4269

0 commit comments

Comments
 (0)