In the new ARM portal of azure you cannot assign dynamic ip’s to Virtual machines, You can however create a loadbalancer, assign a static ip and forward this traffic to you internal static IP of your VM!
I came across this blog that creates a loadbalancer in the new ARM portal via Powershell:
However, these commands are all depreciated as of 0.9.3 and you have to replace Azure with AzureRM:
#public ip for the load balancer
$lbpip = New-AzureRMPublicIpAddress -Name "RemoteDesktopServerlbpip" -ResourceGroupName "AvontuurGlobusRG" -Location "West Europe" -AllocationMethod Dynamic
#configure the public ip as the fronend ip for the load balancer (access endpoint from the internet)
$lbfe = New-AzureRMLoadBalancerFrontendIpConfig -Name "LB-Frontend" -PublicIpAddress $lbpip
#create an address pool for load balanced servers (later we add addresses to that pool)
$lbbepool= New-AzureLoadBalancerBackendAddressPoolConfig -Name "LB-backend"
#create a load balancing policy: balance all RDP traffic 3389
$lbrule = New-AzureLoadBalancerRuleConfig -Name "RDP" -FrontendIpConfiguration $lbfe -BackendAddressPool $lbbepool -Protocol Tcp -FrontendPort 3389 -BackendPort 3389
#Here we actually create the load balancer resource with all the settings previously defined
$lb = New-AzureLoadBalancer -ResourceGroupName "AvontuurGlobusRG" -Name "RemoteDesktopServerLB" -Location "West Europe" -FrontendIpConfiguration $lbfe -LoadBalancingRule $lbrule -BackendAddressPool $lbbepool
#Now to add to the pool of load balanced addresses. We add 2 pre-existing NICs to the pool.
#These nics was created beforehand and was associated to working servers.
$nic1 = Get-AzureNetworkInterface -ResourceGroupName iron -Name "rds2517"
$nic2 = Get-AzureNetworkInterface -ResourceGroupName iron -Name "rds3897"
$nic1 | Set-AzureNetworkInterface
$nic2 | Set-AzureNetworkInterface
One thing that nobody says: Do not forgot to apply NAT rules !
And yes, once your loadbalancer is created, you can config your properties in the GUI azure ARM portal.