A few years ago, I wrote a blog post about Azure Maps Authentication to help developers get started with securing their applications. At the time, the goal was simple: show how to connect to Azure Maps and choose an authentication method that fit your project. Since then, Azure has evolved, authentication standards have matured, and some of the old approaches are now considered outdated.
One of the requirements when building a business application, which may give access to private business data, is that only authenticated employees or agents be able to see that data. So how can you use Azure Maps in combination with authentication and authorization to ensure only the people that should be allowed have access?
Our Azure Maps docs describe in detail many different authentication scenarios but the complexity can make it seem difficult to implement. This blog post will focus on our most requested authentication scenario for Azure Maps. Use the following step by step guidance to have a .NET web application embedded Azure Maps web control where only authenticated users can see the website and use the map.