{"id":3022,"date":"2017-12-03T12:58:37","date_gmt":"2017-12-03T12:58:37","guid":{"rendered":"http:\/\/pariswells.com\/blog\/?p=3022"},"modified":"2017-12-03T12:58:37","modified_gmt":"2017-12-03T12:58:37","slug":"how-to-create-nat-rules-in-a-azure-resource-manager","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/azure\/how-to-create-nat-rules-in-a-azure-resource-manager","title":{"rendered":"How to create NAT rules in a Azure Resource Manager"},"content":{"rendered":"

If you are looking to\u00a0Migrate a classic VM in Azure to ARM , you will need to change your Endpoint port forwards via a Load Balancer<\/p>

Go to the Azure portal:\u00a0http:\/\/portal.azure.com<\/a><\/p>

Click \u201cNEW<\/em>\u201d\u00a0-><\/strong>\u00a0write \u201cLoad Balancer\u201d in search field<\/em>\u00a0-><\/strong>\u00a0Click \u201cLoad Balancer\u201d<\/em><\/p>

\"\"<\/a><\/p>

After you have clicked the \u201cLoad Balancer\u201d, click the \u201cCreate\u201d button.<\/p>

Then fill out the configuration\u00a0blade as shown below:<\/p>

\"\"<\/a><\/p>

Azure will take a few minutes to create the Load Balancer.<\/p>

 <\/p>

Once created, your resource group will look like this:
\"\"<\/a><\/p>

Step 2: Configure Load Balancer Backend Pool<\/strong><\/h3>

In order to connect our newly created load balancer to our virtual machines, we need to create a so-called \u201cBackend Pool\u201d.<\/p>

To do so click on your load balancer to open its configuration blade.<\/p>

Click on the item called \u201cBackend Pool\u201d in the menu to the left:
\"\"<\/a><\/p>

Then click the \u201cAdd\u201d button:
\"\"<\/a><\/p>

\u00a0<\/p>

 <\/p>

Fill out the \u201cAdd backend pool\u201d configuration blade as shown below:<\/p>

\"\"
<\/a><\/p>

Now click on \u201c+ Add a target network IP configuration\u201d:
\"\"<\/a><\/p>

\u00a0<\/a><\/p>

 <\/p>

\u2026and select the IP configuration for your virtual machine:
\"\"<\/a><\/p>

\u00a0<\/a><\/p>

 <\/p>

Finally, click the \u201cOK\u201d button to save the Backend Pool.<\/p>

Now repeat this step; \u00a0but this time choose\u00a0VM1<\/strong>\u00a0instead of VM0.<\/p>

All in all, this will give us two backend pools pointing to VM0 and VM1 respectively:<\/p>

\"\"<\/a><\/p>

It will take Azure 1-2 minutes to create the Backend Pools<\/p>

Step 3: Configure NAT rules<\/strong><\/h3>

Now our load balancer is connected to our virtual machine and we now need to configure rules for redirecting network traffic.<\/p>

Start by clicking \u201cInbound NAT Rules\u201d in the menu to the left:
\"\"<\/a><\/p>

Then click the \u201cAdd\u201d button:
\"\"<\/a><\/p>

Fill out the \u201cAdd inbound NAT rule\u201d configuration blade as shown below:
\"\"<\/a><\/p>

<\/p>

\"\"<\/p>

 <\/p>

Now repeat this step, but this time choose\u00a0VM1<\/strong>\u00a0instead of VM0 .<\/p>

We will now end up with two Inbound NAT Rules: one with port 8088 associated to VM0 and one with port 8089 associates to VM1 :<\/p>

\"\"<\/a><\/p>","protected":false},"excerpt":{"rendered":"

If you are looking to\u00a0Migrate a classic VM in Azure to ARM , you will need to change your Endpoint port forwards via a Load BalancerGo to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2092],"tags":[1464,2263,2261,2260,2258,929,1409,2262,2259],"class_list":["post-3022","post","type-post","status-publish","format-standard","hentry","category-azure","tag-azure","tag-change-rdp-port","tag-classic","tag-endpoint","tag-load-balancer","tag-migration","tag-nat","tag-network-address-translation","tag-port-forward"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t