Solving an Enterprise Integration problem with Azure Serverless

This blog is a follow up to my webinar that aired 17th Sept on Pune User Group’s #PUGLive. Recording of the webinar is available and can be viewed at the end of this blog. I have used the follow up weeks to cover a few more interesting aspects of Azure’s Serverless offerings in this blog.

There are proven benefits of abstracting out servers for certain solutions where the focus lies more on the business logic and lesser on the logistics of it.[1][2][3] Serverless offerings are modelled for simplicity, but this can quickly lead to limitations especially while building enterprise focused solutions surrounded by niche requirements or compliances. Azure seems to have clearly inherited Microsoft’s proficiency in catering to Enterprise needs. Azure’s serverless offerings have managed to extend an array of features that help build compliant solutions with fair degree of ease. To evaluate just that, here we look at an Enterprise Integration problem and design a solution using Azure’s serverless offerings and highlight some of their capabilities.

Problem statement

North Wind Corp. runs an ERP solution where Request for Proposals (RFP) are uploaded for Vendors to access. North Wind wants to send out notifications to suppliers when they intend to raise RFPs. Vendors like Proseware Inc. would like to stay up to date on RFP events and trigger their internal business processes.

For the sake of simplicity, let’s break this problem statement down to three phases and address each of them with one of Azure’s serverless offerings.

Separation of Concerns

This is a cross-enterprise integration scenario. It is therefore important to understand that the solution needs to have clear separation of concerns between the two parties, North Wind and Proseware.

  • North Wind’s sole responsibility should be to issue the RFP notifications to all vendors along with relevant metadata.
  • Proseware and other vendors should be able to manage and route their own subscriptions.


North Wind is required to set up a notification infrastructure that its vendors can subscribe to. It is crucial for this infrastructure to support access for vendors to manage their own subscriptions.

RFP Notification being an event, Azure’s Event Grid starts to seem like a good candidate. Event Grid is designed to be used in event-based architectures where applications can emit events. Other applications and services can then subscribe to events of their interest. The general Event Hub offering supports deep integration with Azure allowing your Azure resources to readily start emitting event on the grid. The support for filters is also a huge plus especially for applications that would like to focus on a very specific range of events. If you are interested in a detailed overview, I would encourage you to read up if their Azure documentation.

If you want to improve your understanding of the key differences between Event Hubs, Event Grid and in some cases Service Bus head here[4]

We can approach a design where we create a topic dedicated for RFP notifications, but RBAC on the topic would not control vendors from accessing each other’s topic subscriptions. We can create a custom topic for each vendor allowing them to control all subscriptions on that topic. As each topic will have its own event publishing endpoint, North Wind’s internal ERP system will have to emit notifications on each topic endpoint. There should be a better approach.

All of the above constrains can be gracefully bypassed with Event Domains. Extending the same Event Grid infrastructure, domains allow applications to emit events across multiple topics over the same endpoint and at the same time allow RBAC to be applied on each topic created under the domain[5]. We can therefore have a dedicated topic for each vendor under the Event Domain and assign the EventGrid EventSubscription Contributor role to Integration teams at vendors like Proseware. Note that this role is not visible in the Azure Portal at the time of writing. This role can be assigned via PowerShell.

Source: Example of topic based access from Azure Documentation - Event Domains

There is still one last caveat here. The event size on Event Grid is limited to 1 MB (messages are metered at 64 KB)[6]. There can be RFPs larger than 1 MB and contain multimedia which is not suitable for the JSON schema supported by Event Grid. Even from a design stand point, the Event object should contain only enough metadata for the vendor to be able to locate the actual RFP and consume it into their processes. The location for the actual RFP is trivial to the problem statement as it could very well be in the ERP itself with authorized vendors allowed to pull information. For the sake of brevity, we opt for a Blob storage. We utilize the data property in the Event Grid schema to populate RFP metadata.

    "topic": "proseware",
    "subject": "rfp/new",
    "id": "11568938",
    "eventType": "new",
    "eventTime": "2020-10-02T13:41:00.9584103Z",
        "id": "IN934NZ12",
        "xml": ""
    "dataVersion": "",
    "metadataVersion": "1"

The RFP XML document hosted on the North Wind blob storage is structured as follows.

    <title>Intent to create the largest Lego Death Star</title>
            <name>Darth Vader</name>
            <name>Storm troopers</name>
            <name>Emperor's Royal Guards</name>
            <name>Square blocks</name>
    <note>Vendor to take care of shipping and other logistics.</note>

The solution at this point looks something like this. We have everything in place to:

  1. Emit events to a single endpoint.
  2. Provide isolated control for each vendor’s Active Directory backed guest users to setup event subscriptions on their own topics.

Separation of Concerns between North Wind and Proseware.

Integration Point

Proseware, like most businesses operates its own enterprise solutions protected within a private network. The RFP notification should be received by a gateway service that can securely transfer and host the corresponding RFP document within the Proseware network to be picked up by one or more internal business processes. We assume that Proseware’s private network is extended into Azure using either a Site-to-site VPN or ExpressRoute.


Here we play the role of the Integration team at Proseware. We would like to future-proof the solution by creating a single internal integration point where one or more business applications running within the corporate network can pick the RFP for further processing. Simplifying it by storing the RFP in a Blob storage that can be accessed through the Proseware VNET.

We can setup a subscription on the Event Grid Topic. For event destinations, Event Grid supports Webhooks or Azure resources like Functions, Storage Queues, Event Hubs, Hybrid Connections or Service Bus. As this is a cross-enterprise integration scenario (Proseware and North Wind have separate Azure Subscriptions) we won’t be able to use the deep integrated Azure event destinations supported by Event Grid. That narrows down our choice to Webhooks.

The webhook subscription needs to point to a web service capable of doing the following.

  1. Receive the webhook notification on a HTTP endpoint.
  2. Parse the JSON based Event Grid schema to extract the RFP location on North Wind’s storage account.
  3. Download the RFP from the North Wind storage account and place it on a Proseware storage account that can be accessed only via a VNET.

It is important to understand that Event Grid requires a notification confirmation within 30 seconds. In our case, the HTTP endpoint should be able to respond quickly. The design needs to ensure that RFP downloads in step 3 should not block the HTTP response as the downloads especially in case of batch events might take longer. Also note that this case does not require step 3 to make an authenticated call to fetch the RFP document from North Wind, we would like to use an approach that could be extended to support a custom authentication mechanism.

Azure Functions app with a HTTP trigger works well for us here. The ability to implement just the business logic in languages like C#, Python, PowerShell and JavaScript allows us to extend the functionality if needed. We are going to require access to the Proseware VNET, for which the Function app can be hosted on a Premium plan or a dedicated App Service Plan or App Service Environment which allow VNET integration. Here we opt for the App Service Plan as any spare compute can be shared by other functions apps or app services. If you prefer to benefit from serverless scaling, Premium Plan would be the way to go.[7]

With Functions are now able to implement the service with minimal code (complete solution).We can leverage the Durable Functions extension to implement asynchronous activities in the functions app. The webhook can be pointed a HTTP trigger that initializes an orchestrator instance. The orchestrator can then use the fan-out/fan-in pattern to download each RFP in the list of events individually without blocking the webhook response.

public static async Task<dynamic> RunOrchestrator(
    [OrchestrationTrigger] IDurableOrchestrationContext context)
    List<EventGridEvent> events = context.GetInput<List<EventGridEvent>>();
    var tasks = new List<Task<bool>>();

    foreach (EventGridEvent e in events) 
        tasks.Add(context.CallActivityAsync<bool>("DownloadRFP", e));
    await Task.WhenAll(tasks);
    return from t in tasks select new { TaskId = t.Id, Status = t.Result };

public static async Task<bool> DownloadRFP([ActivityTrigger] EventGridEvent e,
[Blob("northwind-rfp-collection", Connection = "RFPStorageConnection")] CloudBlobContainer blobContainer,
ILogger log)
    log.LogInformation("Processing event {0}.",e.Id);
    // Check if event is for Webhook registration -
    if (e.EventType == "Microsoft.EventGrid.SubscriptionValidationEvent") {
        EventGridValidation validationObject = (e.Data as JObject).ToObject<EventGridValidation>();
        log.LogInformation("Validation URL: {0}", validationObject.validationUrl);
        return true;

    RFPDescriptor descriptor = (e.Data as JObject).ToObject<RFPDescriptor>();
    log.LogInformation("Downloading RFP document ID {0} from North Wind",;
    var response = await _httpClient.GetAsync(descriptor.xml);
    var responseString = await response.Content.ReadAsStringAsync();

    // Store RFP to Blob Storage
    string blobName = String.Format("{0}.xml",;
    log.LogInformation("Uploading RFP document ID {0} to internal storage",;
    CloudBlockBlob blob = blobContainer.GetBlockBlobReference(blobName);
    await blob.UploadTextAsync(responseString);

    return true;

After implementing the integration point, Proseware is able to grant internal business processes access to the Blob storage to pick up fresh RFPs coming in from North Wind.

Proseware’s Integration Point to North Wind’s RFPs

Evolving processes

Businesses units like Sales, within Proseware would like to own and control their processes to reduce operational overheads. The solution needs to provide enough flexibility for the business process to evolve quickly. To begin with, the sales team would like to receive an email notification when a RFP is uploaded to the Proseware RFP Store (Blob storage). The email should include the specifics mentioned in the XML document in human readable format.


Considering that businesses would like to own and control the process here, it is ideal to pursue a low-code or no-code solution that businesses can easily maintain. The flexibility offered by Power Platform for such cases is incredible. But we are dealing with a scenario where RFPs are stored in a Blob storage controlled by Proseware with a private network.

Logic Apps on Azure could help, but they do not normally offer VNET integration that would allow us to access the Proseware Blob storage. However, a Logic App can be hosted in an Integrated Service Environment (ISE) - an offering from Azure specifically tailored for Logic Apps which offer the same level of resource isolation that App Service Environments (ASE) offer for App Services. This comes along with the ability to run specific actions with the ISE and leverage the provided VNET integration[8].

Actions marked as CORE and ISE are executed in the ISE.

Further, we need to parse the XML file and extract the RFP specifications and place it in an email. This is where the Enterprise Integration Pack (EIP) comes in handy. It is important to note that EIP offers much more than just XML parsing. With EIP, an integration account can be used to store mapping instructions in form of Liquid templates, XSLT or HIDX. For XML to text, we will use the following Liquid template. You can learn more about Liquid here.

Hello team,
North Wind has issued a notification requesting proposals against the following order.
Title: {{content.title}}<br/>
ID: {{}}<br/>
Type: {{content.type}}<br/>
Order details:<br/>
{% for order in content.orders %}<br/>
{{}} x {{order.quantity}}<br/>
{% endfor %}<br/><br/><br/>

Please follow up at the earliest.<br/><br/><br/><br/>

Kind regards,<br/>
Proseware Integration Team<br/>

If we use this template against the sample North Wind RFP XML, the end result looks like this.

Hello team,

North Wind has issued a notification requesting proposals against the following order.

Title: Intent to create the largest Lego Death Star
ID: IN934NZ11
Type: M582

Order details:

Darth Vader x 1

Storm troopers x 60

Emperor's Royal Guards x 20

Square blocks x 80000000

Blasters x 176

Vendor to take care of shipping and other logistics.

Please follow up at the earliest.

Kind regards,
Proseware Integration Team

We implement the following steps in the Logic App, starting with a blob file trigger followed by mapping the XML into text using the above template. The text is then sent over email to the sales team.

Logic App

With the full solution in order, we achieve the following:

  1. North Wind’s ERP is able to publish events for vendors to consume.
  2. Vendors like Proseware are able to create and manage their own subscriptions.
  3. Proseware is able to pick RFP documents and make them accessible to internal processes.
  4. The Sales team at Proseware is able to control and setup their own process like receiving emails with RFP details from North Wind.

Evolving Process


The solution above is prepared with the intention to focus on the key serverless offerings from Azure. The reader is requested to revisit design decisions when building solutions to address their own requirements.


  1. Marketing software company gives customers greater flexibility using serverless functions
  2. E-discovery company uses serverless computing to speed internal development of its SaaS solution
  3. The Urlist — An application study in Serverless and Azure
  4. Choose between Azure messaging services - Event Grid, Event Hubs, and Service Bus
  5. Azure Documentation - Event Grid Domains
  6. Event Grid - Quotas and Limits
  7. Azure Functions - Scale
  8. Connect to Azure virtual networks from Azure Logic Apps by using an integration service environment (ISE)

Webinar Recording

PUG Live: Easing up Enterprise Integration with Azure Serverless

If you would like to stay up to date with new recording, subscribe to the Pune User Group youtube page