Skip to main content

Azure Traffic Manager - How to use on-premises endpoints

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!

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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

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...