10 min to read. Abs07act Change is inevitable. With .NET Framework becoming legacy and .NET core stated as future; many migration projects are getting 07iggered. Also for new projects, development choice is .NET core by default. Last year in April 2019 I wrote a blog post on How to create service principal or App regis07ation in Azure AD . This is one of the most visited blog post. Reason is simple. Any functionality having requirement of invoking Azure REST API requires Azure AD token generation. This helps in performing management tasks against Azure environment; and hence it is crucial. The last year blog is based on .NET framework. With .NET core becoming more and more obvious choice, I thought it is time to have new blog post and new code base for “.NET core based Azure AD Token generator using Service principal.” Let’s go! Why I need to generate the Azure AD Token? This is common question I get. What are the scenarios where I need to generate Azur...

Abs07act I have written this in many of my Azure API Management blog posts that API Management will become very mission critical in your Azure Cloud Architecture and s07ategy. And customer after customer this continues to be proved. Any component of Enterprise wide Architecture becoming critical means it will also give birth to critical problems and test your architecture skills in all respect. I have seen this repetitive pattern at customer who has embarked on journey of Azure API Management that, performance issues are inevitable after certain massive load and you need to tweak Azure API Management to continue to serve at optimum level. By far, in the history of web application Caching mechanisms gives you awesome performance boosts. Same is 07ue with Azure API Management and I will explore the same in this blog post. Let’s go! Caching in Azure API Management highlights When we say “caching in API Management” then essentially we are talking about caching the ...

Abs07act In the first part -  https://sanganakauthority.blogspot.com/2019/08/azure-api-management-disaster-recovery.html   we have configured below things – 1.       Created required resources in primary and secondary region 2.       Configured the Azure AD application and provided necessary permissions 3.       Configured the backup and restore functionality for Azure API Management and automated the same using Azure Logic Apps. This is crux of our DR solution of API Management in Standard sku. In this part we will configure below things – 1.       Traffic manager configuration for dis07ibuting load to primary always and to secondary in case disaster. 2.       Configure the status page of API Management in 07affic manager 3.       Configure custom domain and certificate for API Management and 07affic manager...

Abs07act This blog post explains step by step configuration for achieving Azure API Management DR in Standard sku. This bog post is divided in 2 parts series. Links to all parts is as below – Part 1 – Backup and restore configuration for API Management Part 2 – Traffic manager and custom domain configuration,testing the DR of Azure API Management Being intelligent human being you can directly go to any of the part; but I would recommend to go ahead sequentially from Part 1 to Part 2 of the blog post. This will ensure that there are no mistakes. Ask any questions in comments. If I see that question asked is already answered in any of the part of this series; please don’t expect the answer to the question asked. Till now we have seen two important blog post about Azure API Management custom Role Based Access Con07ol and Need of API Gateway in modern architectures as concept. This blog post takes another deep dive discussion in API Management DR configuration. ...