Skip to main content

Azure Traffic Manager - How to use on-premises endpoints

By
Some weeks ago I wrote a short blog post about Traffic Manager. It is a great service that can be used to redirect traffic to the closest datacenter, redirect traffic in a balanced way (Round Robin) or to be able to redirect traffic to another location when an endpoint goes down.
For more information related to it please visit the following blog post: http://vunvulearadu.blogspot.com/2013/07/traffic-manager-overview.html
But let’s see what else we can do with Traffic Manager. Of course we can register very easily endpoints from Azure, this is normally. But you should know that it is possible to register public endpoint that are hosted on on-premises system or why not on other clouds providers.
This features is the kind of feature that can make your life easier. Why? Why not have endpoints on-premises and use Traffic Manager only for redirecting purposes, in case of failover and so on – almost like a load balancer, but without the ability to read the load of each endpoint (this cannot be done using Traffic Manager, but is full supported out of the box by the Load balancer from Azure – and is free!).
If you create a new Traffic Manager instance, you will see that you can register endpoints only from the same subscription and ONLY the one that are hosted on Azure – from the Azure portal. If you need to register an endpoint that is hosted on on-premises servers, than you need to do this by hand using PowerShell or the REST API.
REST API: http://msdn.microsoft.com/en-us/library/azure/hh758257.aspx
PowerShell: http://msdn.microsoft.com/library/dn690257.aspx
Why we cannot do this from portal? I don’t know, but it would be nice.
In both cases it is important to set the ‘Type’ of the endpoint to ‘Any’. Otherwise, you will add the endpoint as other endpoint.
PowerShell Sample:
Add-AzureTrafficManagerEndpoint 
  -TrafficManagerProfile $TrafficManagerProfile 
  -DomainName "foo.onpremises.com" 
  -Status "Enabled" 
  -Type "Any" | Set-AzureTrafficManagerProfile

Enjoy!
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more