Azure File Share Between Two Azure Windows VMs

A hands-on project that deploys two Windows VMs in a single Azure VNet, secures them with NSGs/Windows Firewall, and configures a Windows file share on the Server VM that is mapped and used from the Client VM. Includes end-to-end connectivity testing (ICMP) and read/write validation both directions.

Architecture

---

Installation & Demonstration (Step-by-Step)

How to read this section:
Each step has a short instruction and one screenshot with a precise title. Follow the steps in order; you’ll end with verified two-way file sharing.

1) Azure setup

1. Create a Resource Group

   • Azure Portal → Resource groups → Create.
   • Use Azure-IT-Lab, Region East US.
     

2. Create a Virtual Network (Basics)

   • Name IT-VNet, RG Azure-IT-Lab, Region East US.
     

3. Define Address Space and Subnet

   • Address space 10.0.0.0/16; default subnet 10.0.0.0/24.
     

4. Review + Create the VNet

   • Confirm validation passed and deploy.
     

5. Verify VNet shows in the Resource Group

   • RG overview lists IT-VNet.
     

6. Open the VNet Overview

   • Address space 10.0.0.0/16, Azure-provided DNS.
     

7. Deploy Two Windows VMs (ServerVM & ClientVM)

   • Both in IT-VNet / default subnet, Windows images, public IPs enabled.
   • After deployment, confirm both are Running.
     

8. Capture VM Details

   • ClientVM: private 10.0.0.5, public 20.115.41.100.
     
   • ServerVM: private 10.0.0.4, public 20.51.216.86.
     

9. Open NSG and Allow Required Inbound Traffic

   • Ensure RDP (TCP/3389) allowed for management.
   • Add/verify ICMP (AllowPing) for lab ping tests.
   • (Shown here on ServerVM NSG.)
     

(Optional reference of subnets blade used later)

---

2) Configure Windows file sharing on the ServerVM

10. RDP into ServerVM

    • From your PC: mstsc → connect to ServerVM public IP.
      
      

11. Create the shared folder

    • Create C:\SharedFiles.
      

12. Enable sharing + permissions

    • Advanced Sharing → Share this folder as SharedFiles.
    • Permissions → Everyone: Full Control (lab simplicity).
      
      

13. Create a test file on the Server

    • In C:\SharedFiles, create AzureLabTest.txt with sample text.
      

(Windows Firewall ICMP rule validation—used for ping tests)

---

3) Map the share on the ClientVM & verify

14. RDP into ClientVM

    • From your PC: connect to ClientVM public IP.
      

15. Map a network drive to the Server share

    • This PC → Map network drive
    • Drive letter Z:; Folder \\10.0.0.4\SharedFiles; Reconnect at sign-in checked.
      

16. Confirm the mapped drive shows the server’s file

    • Z:\ displays AzureLabTest.txt.
      

17. Open the file from the Client

    • Read AzureLabTest.txt via mapped drive.
      

---

4) Verify Client → Server write (two-way test)

18. Create a file from the Client in the share

    • In Z:\content (create folder if needed), create ClientCreated.txt.
      

19. Confirm the Server sees the new client file

    • On ServerVM: C:\SharedFiles\content shows ClientCreated.txt present.
      

---

5) Connectivity tests (ICMP across private IPs)

20. (Before enabling ICMP) Ping failure (expected)

    • From ServerVM → Test-Connection 10.0.0.5 fails until ICMP allowed.
      

21. (After enabling ICMP) Ping success

    • From ServerVM → Test-Connection 10.0.0.5 succeeds (~1ms).
      

22. Client → Server ping success

    • From ClientVM → Test-Connection 10.0.0.4 succeeds.
      

---

Results

• Both VMs deployed in IT-VNet (10.0.0.0/16, default /24).
• Windows share exposed from ServerVM at \\10.0.0.4\SharedFiles.
• ClientVM successfully mapped Z: and read Server’s file.
• ClientVM created a file in the share; it appeared on ServerVM (write verified).
• ICMP working both directions after enabling NSG + host firewall rules.

---

What you’ll need

• Azure subscription, Owner/Contributor rights for RG.
• RDP access to both public IPs (lab only).
• Windows user creds for each VM.

---

Clean-up

• Unmap the drive on ClientVM.
• Stop/Delete the two VMs, NICs, public IPs, and the RG to avoid charges.

---