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/azure.md
+28-1Lines changed: 28 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,34 @@ Sources:
36
36
37
37
## Cookbook
38
38
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
40
67
41
68
#### Working with App Registrations and Service Principals
0 commit comments