If you have ever had to configure the ports or endpoints for a Windows Azure Virtual Machine, you probably already know how painful it is to have to add multiple ports one-at-a-time in the interface.
Even the most basic router has this support so why not Windows Azure?
Well, for the time being, Microsoft still has not offered this support, however there is a workaround available in PowerShell:
http://fabriccontroller.net/blog/posts/adding-multiple-endpoints-to-your-windows-azure-virtual-machines-by-using-a-csv-file/
The PowerShell script allows you to configure all of the ports you want opened in a CSV file and then the PowerShell script will open all of the necessary endpoints.
Of course, if you want to be able to open a range of ports directly through the Windows Azure Management Portal, you should vote for this UserVoice feedback item here: http://feedback.azure.com/forums/217313-networking-dns-traffic-manager-vpn-vnet/suggestions/4338247-endpoints-can-accept-a-port-range-instead-of-enter
Even the most basic router has this support so why not Windows Azure?
Well, for the time being, Microsoft still has not offered this support, however there is a workaround available in PowerShell:
http://fabriccontroller.net/blog/posts/adding-multiple-endpoints-to-your-windows-azure-virtual-machines-by-using-a-csv-file/
The PowerShell script allows you to configure all of the ports you want opened in a CSV file and then the PowerShell script will open all of the necessary endpoints.
Of course, if you want to be able to open a range of ports directly through the Windows Azure Management Portal, you should vote for this UserVoice feedback item here: http://feedback.azure.com/forums/217313-networking-dns-traffic-manager-vpn-vnet/suggestions/4338247-endpoints-can-accept-a-port-range-instead-of-enter
No comments:
Post a Comment