Introduction

This post is part of a series about implementing serverless approval workflows on Azure:

1. Approval Workflow on Logic Apps with Twilio
2. Approval Workflow on Azure Durable Functions and SendGrid (this)
3. Approval Workflow on Azure Durable Functions and Slack

Durable Functions is a new (in preview at the time...

Introduction

Azure API Management is a great product that we often use on customer solutions. It is an extremely effective way to provide a layer of abstraction between your callers and back-end APIs, and provides centralised governance across your API surface.

However, one of the most common questions from our...

Dependency Injections on Azure Functions are not very intuitive. I’ve written many blog posts about dependency management on Azure Functions to improve testability and this was my latest one. However, they are mostly about V1, which supports .NET Framework. Azure Functions V2 is now on public preview and I’m going to...

Introduction

No two systems integration projects are the same, given the large number of applications, platforms and component subsystems that can be brought together to function as an integrated system, and the wide range of business requirements and business outcomes that are typically pursued.

This article...

As one of serverless families in Azure, Cosms DB is becoming very popular. In many development scenarios, Cosmos DB actually replaces existing RDBMS because it requires relatively lower cost for maintenance, and is easy to use. Another serverless family, Azure Functions, also provides triggers and bindings for Cosmos...

In many information system development scenarios, including integration scenarios, handling date/time value is always problematic. If your information systems reside in your office or data centre located in your area, that won’t bring about too much trouble. However, if your organisation runs applications in several...

Introduction

A year ago, I wrote a post about this very same topic, the Microsoft Azure Integration Platform as a Service (iPaaS). At that time, the core iPaaS product offering, Azure Logic Apps, was roughly 6 months old, since it’s generally available launch. Since the launch date, we’ve seen an impressive release...

ARM template is a great tool for Azure resources deployment. However, it’s very tricky to use because:

• It’s a JSON object with massive number of lines,
• Its JSON structure is quite complex so that it’s not that easy to read at a glance,
• It’s hard to validate if there is a typo or not, and
• We only know if the resource...

Introduction

In Azure Logic Apps workflows, you can implement conditions and switch cases to control the flow based on runtime inputs and outputs. This functionality is quite useful, and in many cases, can be used to implement the business rules required. However, those business rules are inherent to the workflow, and...

There are many cases that we need to retrieve access keys and/or endpoints of Azure resources, as soon as they are deployed through ARM templates. Typical uses cases are:

1. To display those values in the outputs section of ARM templates,
2. To get a reference to the outputs section of nested ARM templates from their...