Adding EndPoints on Windows Azure VM’s

Adding EndPoints on Windows Azure VM’s

After you have created a Virtual Machine in Windows Azure, an EndPoint is created for accessing the Virtual Machine with Remote Desktop (RDP) from your local computer. An EndPoint is basically a mapping between a Public IP Port and a Private IP Port. Each time you use the Windows Azure Management Portal to connect to your Virtual Machine in Windows Azure, by hitting the Connect button, the RDP connection connects to the Public IP Port. The network traffic that arrives at that Public port, becomes routed to the Private port, making sure the network traffic accesses the application or service it was intended for.

So for RDP everything is setup nicely by Windows Azure, but say you have a SQL Server database on that VM, which you want to access from a (Azure) website or your local SQL Server Management Studio. In that case you need an extra EndPoint to be able to access that database from the outer world.

Although not advisable, you can map Public IP Port 1433 (SQL Server’s standard port) to Private Port 1433. But by doing so, you make it easier for hackers to access your database (although they don’t have security credentials), so it’s better to take a random number between 1024 and 65535 and configure that as the Public IP Port.

Follow these steps to create an EndPoint for accessing a SQL Server database.

Login to the Management Portal with your Microsoft account which is mapped to your Windows Azure subscription and click on ‘Virtual Machines’ in the menu on the left. Next select a Virtual Machine  by clicking on it (that is: if you’ve created one beforehand) and then click on ‘EndPoints’. In the screen that follows you’ll see that an EndPoint is already created for Remote Desktop connections.


Now click the ‘Add EndPoint’ button, afterwhich you get the first screen of a 2 pages wizard.

Leave the bullet on the first radio button and proceed to the next screen of the wizard, by clicking on the small arrow button in the lower right corner.

In this screen you have to make a couple decisions. First, select %ufeffan identifiable name for the EndPoint. Since we are creating an EndPoint for SQL Server, you could choose a name in that direction. Keep in mind that spaces are not allowed!
The second choice you have to make is the number of the Public Port. Choose a random number between 1024 and 65535, preferable NOT 1433.
The last choice is actually a value you should already know, namely the (Private) Port which is used for SQL Server. By default SQL Server communicates on port 1433. So unless you did configure another port, enter 1433 for the Private Port.

So far the configuration of the EndPoint. Now click the button with the check mark, to have Windows Azure create the EndPoint. This can take 1 or 2 minutes.

What’s next
Having an EndPoint configured to be able to access a database in a Windows Azure VM is only one step. The next steps will be creating a SQL Server authentication login and grant it the needed authorizations. Read more about it in this article on BizTalk Events.

Microsoft BizTalk Server 2013 available on MSDN

It took a while, but here it is… BizTalk Server 2013 is now in RTM (Manufacturing)! as of now you can download BizTalk 2013 from MSDN, and it will be available for purchase in April.

Besides all kinds of new features, the new version of BizTalk also brings us a whole new licensing model. At least it is new in terms of BizTalk pricings… it will be a per-core licensing model, just like the SQL Server licensing.

A more detailed info can be found on my companies blog post.
the official announcement of the BizTalk team, can be found in this post on their blog.

BizTalk Server 2013: It is RTM now!

I will be not the first nor last one that will blog, tweet or share through other social media that BizTalk Server 2013 is RTM. The 8th release in little over twelve years. That is amazing as I do not believe any Server Product has such a release cadence. Impressive as the Microsoft BizTalk Server Product keeps pushing out new features in the product.

There was talk, rumors or loud statements

BizTalk Server 2013 has RTM’d

The much anticipated new version of BizTalk Server has been Released to Manufacturing and is now available for download from MSDN.

To see the details about this release please see:

There has also been changes in the Licensing model for BizTalk Server 2013, it has now moved from Processor to Core Licensing: BizTalk Server 2013 Licensing Datasheet and FAQ

More …

BizTalk Server 2013 is Released to Manufacturing (RTM) – Now on MSDN

Today Microsoft announced BizTalk Server 2013 is now Released to Manufacturing (RTM).

The software is now available for download through MSDN in English only.  Just do a search for “BizTalk 2013” to find it.

This release brings new adapters, better Azure integration, enhanced SharePoint integration, support for SQL and Visual Studios 2012, and more.


BizTalk Server 2013 reached to RTM

BizTalk Server 2013 reached to RTM

Great news!!! Microsoft just announced publicly, about an hour ago, that BizTalk Server 2013 is now "Released to Manufacturing" (RTM)! BizTalk Server 2013 will be available for download on MSDN starting today (March 21). The English locale SKUs will be available for purchase starting April 2013. Other language SKUs will be available for purchase starting […]
Blog Post by: Sandro Pereira

BizTalk Server 2013 RTM

BizTalk Server 2013 RTM

QuickLearn is very excited to share the news that BizTalk Server 2013 is now available for download on MSDN. The eighth release of BizTalk Server has been much anticipated and promises to be the next step in the on-going investments in BizTalk. In the near future, we can look forward to announcements that include Infrastructure […]
Blog Post by: Monique Bulette

Understand BizTalk Server 2013 Licensing

Please note this is not official licensing document, this is based on our understanding, we added lot of examples and diagrams to make life easy for people to understand the new licensing model. You should always refer to official Microsoft sources before making purchase decisions. Original Article Link: With BizTalk Server 2013, Microsoft is […]

The post Understand BizTalk Server 2013 Licensing appeared first on BizTalk360 Blog.

Blog Post by: Saravana Kumar