Hi Chandra ,

When I created this post, only the AzureRm was available. The Az module didn’t exist.
You need to translate all the commands to Az. The Set-AZVMOSDISK is described here: https://docs.microsoft.com/en-us/powershell/module/az.compute/set-azvmosdisk?view=azps-6.0.0

When I will find some time I will update the guide.

Is this script is correct. I am getting the below error

Set-AzVMOSDisk: Parameter set cannot be resolved using the specified named parameters. One or more parameters issued cannot be used together or an insufficient number of parameters were provided

Can you help me out to fix this

it would be kind of assymetric routing

Please help on Lan to Wan routing on Pfsense and Azure portal both
and Wan to Lan routing on Pfsense and azure portal both
Is IP forwarding still required on Lan Ip configuration required to be done

Your insights will be really helpful and i have a lab ready also if you want to work together on this scenario on Azure.
Looking forward to hear from you.
Regards,
Jeegar

The VM is at the subnet 10.1.2.0/24
The pfSense LAN NIC at the subnet 10.1.0.0/24
The pfSense WAN NIC at the subnet 10.1.3.0/24

Configuration on pfSense:

LAN interface
static IP 10.1.0.5/24
IPv4 Upstream gateway: None
Azure NIC: Static IP 10.1.0.5 on subnet 10.1.0.0/24

WAN interface
static IP: 10.1.3.4/24
IPv4 Upstream gateway: (new gateway with the first IP of the Azure subnet) 10.1.3.1
Azure NIC: Static IP 10.1.3.4 on subnet 10.1.3.0/24

Rules
WAN: None
Lan: Default

System / Routing / Gateways
new gateway: subnet LAN 10.1.0.1 10.1.0.1

System / Routing / Static Routes
new static route:
10.1.2.0/24 subnet – 10.1.0.1 LAN

VM on subnset 10.1.2.0/24
At the pfSense I added a NAT rule port 38745 to 10.1.2.4 port 3389 for RDP to my VM

At the Azure Portal, the custom Route 0.0.0.0/0 to 10.1.0.5, that is applied at the VM’s subnet 10.1.2.0/24, will forward all traffic of the VM to the pfSense

So to access the VM i RDP to the public ip of pfSense @ port 38745

Hi, thanks for the revision. I corrected the link and also removed the NSG part, at the test I added the NSG form the Portal and I forgot to change the Script.

This one is redundant too:
$backendSubnet = Get-AzureRMVirtualNetworkSubnetConfig -Name default -VirtualNetwork $vnet

in the Azure agent install you left off the last t (gi.. t) on this line:
git clone https://github.com/Azure/WALinuxAgent.gi

This line of the create VM script isn’t used anywhere either.
$NSGname = “******”

Otherwise great to get this all in one spot- thank you. I had to do quite a bit of searching last time I loaded an image to Azure and even now, Azure thinks the start up fails every time because the agent isn’t running correctly (it runs fine so I haven’t bothered to change it)