Upcoming Breaking Changes in Azure API Management

There are some upcoming changes in Azure API Management. Full list is given below.  Main one is stv1 Platform retirement. And the retirement date is August 31st 2024. So make sure you move to the upgraded version before the retirement date. 

How to check? - On the Azure portal, if you open the Azure API Management, you could see the platform version on the Overview blade. 

Full List:

https://learn.microsoft.com/en-us/azure/api-management/breaking-changes/overview

Azure Function - HTTP Trigger Use Case

 As you all know, there are different triggers available in the Azure Functions. And sometimes it becomes handy to define Cloud solutions. Here is an Azure Function HTTP Trigger scenario.

Customer receive Marketing emails and but choose to unsubscribe / opt out. Then Third Party Marketing Solution sends a webhook in order to update the consents. In this diagram, I have shown Dynamics 365 CRM as the system which stores the consent. But it could be any system which stores the consents. 

Azure function with HTTP Trigger will consume the webhook and updates the consent. In short words, it is used as a light weight API here. So next time that customer will not be included in the Marketing emails. Azure API Management is used here as an API Gateway to secure the Azure Function End point. Diagram is given below. 

Cloud Migration and Modernisation Approaches

Here are the key High-Level Approaches for the Migration from On-Premise to Cloud - Rehost, Refactor, Rearchitect, Rebuild and Replace. Microsoft provided a nice table where it is clearly described more details. Highly recommended if you are considering Cloud migration or modernisation. It will help you with planning and achieve the good Cloud migration results.

Ref: https://azure.microsoft.com/en-gb/resources/research/making-the-business-case-for-moving-to-the-cloud

Difference between Automation, Machine Learning and AI

We hear a lot about Automation, Machine Learning and Artificial Intelligence. And sometimes it gets confused between them as well. Recently came across a good and clear explanation about it. It is easy to remember too. Thought to share it.

Credit: Steven Killick

Defender for APIs / Defender for Azure API Management APIs is in Public Preview

Defender for APIs went to public preview in April 2023. In simple words, "Defender for Cloud continuously monitors the configuration of your API management to identity potential security vulnerabilities and recommends actions to mitigate them"

I had a look at my Azure instance. It can be found under the security section.

 If your organisation has many APIs and especially if it is exposed as public APIs or partner APIs or even internal APIs then this would be very useful. Because it continuously monitors.

 Remember security is always important. This adds one more layer of security feature to the Azure API Management service.

Ref:

https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-apis-introduction

Azure Data Factory Connectors Overview/ Supported Connectors for Azure Data Factory

Recently I was searching, whether it's possible to write to SharePoint using Azure Data Factory. But couldn't find many options. And found this useful info on the Microsoft Site.

• Source - Where data starts

• Sink - Where data ends

And for SharePoint, it had this row

Always check whether connectors are available as per your requirements. Here is the link to the documentation

https://learn.microsoft.com/en-us/azure/data-factory/connector-overview

How to Choose managed Azure Data store?

Have you struggled to choose the right managed azure data store for your application? Did you know that Microsoft had released a cool decision tree for it? I found it quite useful when I had choose the correct Azure managed data store. 

(Ref: https://learn.microsoft.com/en-us/azure/architecture/guide/technology-choices/data-store-decision-tree)