Windows Azure – Manage VMs Endpoints

In past posts, i was blogging about how to

Now let’s see how to manage endpoints configured for your VM. This will be treated in 4 points:

  • Change an existing Endpoint
  • Assign ACL to an existing Endpoint
  • Create a new Endpoint
  • Remove an Endpoint

Change an existing Endpoint configuration

First of all, let’s determine what are the Endpoints knowed on our VM.

Here are the two endpoints created by default by Microsoft on our VM. Let’s bypass our work firewall 🙂

Here is how to do this, i’ll set the Public listening port on 443 forwarded 3389 RDP classic port… Beware this command can’t be used if your Endpoint load balanced..

Let’s check if everything is ok.

As you see our endpoint for RDP is listening on 443 and we can easily connect it on secure envs! But we have open our server through 443 port for every scanners or botnet all over the world, Microsoft thinks about it, and you can assign ACL to an endpoint 🙂

 Assign ACL to an existing Endpoint

As i said previously, let’s filter and protect our endpoint.

First, create an ACL object.

And, add rules on it… If you want to add multiple rules, don’t forget that the order must be unique and it’s important  (like ACL in your firewall).

Then we’ll just have to apply the ACLs and update the VM

And now, you can access your endpoint, only for a machine on the 192.168.10.0/24 network 🙂

Create a new Endpoint

Ok, if you install an IIS Apache Server on your VM and wanna make it accessible, you’ll have to create manually the Endpoint. Nothing diffcult here..

Let’s check the result..

Here we go, all is setted as we want, and our web server is visible for everyone on the internet.

Remove an Endpoint

Nothing difficult here, once again, you’ll have to pipe your VM object to the remove cmdlet and update your VM.

Your web Endpoint is now removed 🙁

 

Ok, you should know how to manage your endpoints !

Regards,