Integrate 2022

INTEGRATE 2022 – Day 1 Recap

Published on : Jun 13, 2022

Category : Events



Table of contents

  1. INTEGRATE 2022 – Welcome Speech
  2. Keynote – State of Integration
  3. Application and SaaS integration
  4. Low code – pro code unite
  5. Event Driven Architectures
  6. Logic Apps Deep Dive
  7. Service Bus Deep Dive
  8. Streaming with Event Hubs and Stream Analytics
  9. Modernize your API Stack with GraphQL and Azure API Management
  10. Getting started with SAP OData APIs using API Management

It is again the time of the year for the most-awaited conference to stay up to date with Microsoft Integration tech.

First things first, with this blog we’ll take you through all the highlights and important announcements that we had on day 1 of INTEGRATE 2022. Buckle Up!

#1: INTEGRATE 2022 – Welcome Speech – (Saravana Kumar)

After two years of remote INTEGRATE event, Saravana welcomes everyone to the 10th edition of INTEGRATE 2022. Overall 750+ audience with 250 live attendees and 500+ remote attendees.

After the quick introduction of and INTEGRATE, Saravana shared a quick rewind about the Key announcements made in the 10 years’ INTEGRATE journey. 

  • Native support for Java messaging services 2.0 in Service Bus
  • Introduced Private Hosting of Logic Apps via Integration Service Environments (ISE)
  • BizTalk server 2020 announcement
  • Unveiled BizTalk Migrator tool
  • Logic Apps Standard announcement
  • Debut of an API portal 

Key initiatives this year – Migrating to BizTalk Server 2020 book announcement.

A special mention to Microsoft and Microsoft MVP community and our sponsors for making the INTEGRATE a great success.

Saravana introduced the keynote speaker – Balan Subramaniyan

#2: Keynote – State of Integration – (Balan Subramanian)

Keynote at #INTEGRATE is always a very much-awaited session that sets the context for the next 3 days of a highly technology immersive conference.

Balan Subramanian, who leads APIM, Logic apps, DAPR, and other platform services in Microsoft. starts his first session at INTEGRATE conference highlighting the importance of Integration like when increase in integration takes place etc.

Integrating services, systems, and people

This empowers all individuals to be a part of the integration journey, from pro-IT developers exposing backend systems with APIs to citizen developers consuming those APIs in low code frontends.

Integrating services

Balan narrated with an example, streamlining community people like Coca-Cola (B2C scenario)as seen in the below screenshot describing the working flow of business.

Coca-Cola case study

Real-time applications

An increase in online business has led to building real-time applications, analytics, and experience around events. He highlighted the following topics

  • Event hubs
  • Azure Stream Analytics
  • Event Grid
  • Service Bus

DHL supply chain accelerated warehouse robotics integration

Balan explained the DHL supply chain where the team wanted to build a robotic integration warehouse consuming 1000’s processes within other components and analytics capabilities.

DHL case study

What Azure Integration services offer?

  • Peerless innovation
  • Unmatched experience
  • Strong security and compliance
  • Unbeatable offers
  • AIS offers

Balan invited Vikas Aggarwal, Enterprise Architect Integration & Engineering to give some insights about key benefits when implementing Azure Integration services which include

  • Cloud Native

Enable us to deliver cloud native & serverless solutions

  • Consumption based model

He mentioned that is the power of the cloud, we focussed on building rather than trying to identify volumetrics upfront. It is quite simple:

We pay for what we consumed on the platform

  • Developer enablement

Created a comprehensive library of patterns to enable faster delivery.

  • Agility

Microsoft is your Integration you can build whatever you want, and that provides the flexibility to change. This enables us to quickly respond to everchanging customer needs.

Next, Vikas took a deep dive into integration patterns. Attached is the screenshot for the integration patterns.

Integration pattern

With respect to AIS, the user can get:

  1. Boost Productivity
  2. Increase revenue opportunities
  3. Optimize costs

The Road ahead 2022 – Going to the cloud from BizTalk

As mentioned, this will take a slow step to move from BizTalk to Cloud, and he recently re-visited BizTalk Migration. His investigations included:

  • Customer Survey & Interviews
  • Partner and MVP Interviews

Customers have challenges with

  • Architecture guidance
  • Custom code
  • Industry capabilities

Capability parity between BizTalk and AIS

BizTalk and AIS

He mentioned that Microsoft is investing in Logic App designers, and he mentioned Intelligent integrations as well.

Full API lifecycle

Full API lifecycle

Balan mentioned upcoming investments: IPaaS and evolving Azure PaaS.

IPaaS Azure PaaS

Finally, he summarized the session with a clear note on the state of integration and he threw light on the new improvements made.

#3: Application and SaaS Integration – (Kent Weare)

Kent Weare presented the session on Application and SaaS Integration, which significantly focused on Application Modernisation and Azure Integration services and their advantages. Kent drove the session from a pro developer perspective, with demos being a significant part of the presentation.

The session began with the current application modernization trends. Kent listed down a few approaches that organizations prefer and are on-trend.

  • Lifting and Shifting – Continues to be the most popular method for Application modernization with operational benefits
  • Cloud Computing – Next option that the organization chooses to take advantage of consumption-based services
  • Re-architecture of Applications – Organisations choose this option during migration to leverage the benefit of cloud-native
  • Containers – In recent times, containers are becoming the way to build new applications

Followed by his talk in other generic terms, Kent shared the demo landscape,

demo landscape

He focused on the backend of this architecture, predominantly covering the stages having Azure Integration services. Meanwhile, the other half will be covered by Wagner in the upcoming session.

Scenario 1 – Order entry & Discount calculation

Order entry & Discount calculation

In this scenario, the Power app is going to access an API, and this API is going to expose a Logic App, which will further connect to a backend SQL Server. The features covered are Stateless Execution, VNET Connectivity, and SaaS Connectivity.

Scenario 2 – Shipping: Pickup Request


This scenario was primarily focused on Logic Apps covering the features of Stateful Execution, Azure messaging, and Microsoft Dataverse (SaaS) Integration.

Scenario 3 – Chatbot: Check on Shipping


Tracking is the focus in this scenario, where Kent explained how he achieved it by implementing an API. The features covered are Stateless Execution, Conversation AI (Chatbot), Bot Framework composer, and API Management Governance.

Scenario 4 – Delivery Status Updates

Delivery Status Updates

Regarding receiving delivery status updates, Kent used Twillio to achieve WhatsApp Integration.

In conclusion, Kent gave a takeaway on how Azure Integration services are scalable, agile, and extensible. Kent finally gave a call to action where he provided us with many resources regarding the usage of Logic App Standards. 

#4: Low code – pro code unite – (Wagner Silveira)

Wagner Silveira – Former Azure MVP, Senior Program Manager (Logic Apps) @ Microsoft presented the session on Low code – pro code unite which did focus on how Power platform and AIS works well together and the scenarios to explain the same.


  1. Basics:
  • Azure Integration Services
  • MS Power Platform
  1. Personas
  2. Power Platform + AIS better together
  3. Scenarios


Azure Integration Services

AIS is a combination of the following capabilities:

  • Messaging and event capabilities
  • Orchestration or workflow business process capabilities
  • We tend to extend that, the capabilities in the platform usually don’t suffice.
  • There is a need to expose business process as APIs, Extend the compute when the out-of-the-box capabilities don’t come with functions.
  • We usually work with either real-time events or messaging with the Service bus event grid and expose that through API management.
  • There are cases where message base or real-time doesn’t cut, and there are large sets of data that need to be exported, that’s where the data factory comes into place for all the ETL processes and do big data movements.

Microsoft Power Platform

Microsoft Power Platform


Empower all individuals to be a part of the integration journey, from pro-IT developers exposing backend systems with APIs to citizen developers consuming those APIs in low code front ends.

Power Platform + AIS better together

  • Build robust and scalable APIs using Azure Integration Services
  • Publish your pro code APIS to API management to be consumed by citizen developers in the power platform
  • Rapidly develop low code front ends using the power platform while leveraging pro code backends on Azure


Let’s see 3 scenarios here 

  • Hybrid Integration Via Custom Connector
  • Hybrid Integration
  • 3rd Party APIs via custom connector
  • Party APIs via custom connector
  • Reacting to Dataverse Changes
  • Reacting to Dataverse Changes

Choosing your service orchestrator

Here is how to choose your service orchestrator based on the need and desired solution 

service orchestrator

#5: Event Driven Architectures – (Kevin / Clemens Vasters)

Clemens Vasters who is well known as the top integration mind of Microsoft presented on the topic Event Driven Architectures which explained maximizing the use of Azure messaging services in building event driven architecture.

Event is something that captures the fact of the past, which we either don’t care about or take an action he added. When action is taken as a choice it is played in two effective ways or models, namely:

  • Event driven architecture
  • Imperative architecture
Event Driven Architectures

He continued with a story related to football, that emphasized solving customer’s problems upon integration with Eventim ticket portal.


Relationship between Observation, Signal, and Jobs

Clemens defined Signal, Event, Event stream, and Jobs as follows:

Signal: The capture of an occurrence (statement of fact) during the operation of a software system

Event: A data record expressing a signal and its context. The context is expressed in metadata annotating the signal.

Event Stream: A chronological sequence of events belonging to the same context.

Job: Not an event. A description of a task that needs to be performed by some party. Preferably just once.

He then followed up with one of the best examples ‘Fire Alarm’ to mark the relationship between Observation, Signal, and Jobs:

Observation, Signal, and Jobs

What do Modern Apps use?

Additionally, he provided an example stating that eventing and queue-based messaging are the functions used by modern apps, where he denoted “Event streaming is not ‘Modern’ and Queues are not ‘traditional’. Both are patterns of the state-of-the-art messaging infrastructure.”

Modern Apps

Finally, Clemens talked about CNCF (Cloud Native Computing Foundation) CloudEvents, it’s current work, and eventing on Azure Cloud that marked the end of the session.

#6: Logic Apps Deep Dive – (Slava / Wagner / Kent)

Kent and Wagner presented the logic apps deep dive session with the roadmap, patterns, and other significant updates. They initially started with feedback on the thoughts with Logic apps and its significance on the investment areas.


  • Announcements and road map
  • Recent Investments: Building Enterprise trust
    • Latency
    • Availability Zones
    • Integration Account
  • Feature Feedback
    • EDI/Integration Account
    • Automation Tasks

Product Updates

From the product updates point of view, it brought in a lot of things when compared to the previous year. The Inbuilt connectors which include Azure blog, Azure Table Storage, SFTP, and FTP is in the public preview stage. The SQL Storage provider  runs your logic apps state in SQL rather than storage for more control of costs, hosting options and throughput. Apart from these, exports are also included in public preview. AuthN and managed identity are generally available and Swift encoder/decoder are in the Private preview which enables the validation of SWIFT based financial transactions.

Product Updates


Working on an improved designer is to make it faster and to improve the performance of the designer.


Data Mapper

  • For Data, event, and application integration
  • Any format: start with XML, JSON, flat File, extensible and more to come.
  • Available in VS code and portal.
  • Integrated with Logic apps.
  • Data Mapper

Anatomy of Logic Apps Standard

Anatomy of Logic Apps Standard

Availability Zones for Consumption and standard

  • Increase availability across an Azure Region
  • Operated in an Active-Active-Active manner
  • No endpoint configuration to manage
  • Currently opt-in for consumption and standard
  • Will be automatically enabled for consumption in future
  • Available in select azure regions.

Integration Account Make-Over!!

  • Higher limits for artifacts
  • Improved experience for artifact management
  • Flexible data store
  • Better DevOps
  • DR support
  • Integration Account

#7: Service Bus Deep Dive – (Eldert Grootenboer)

Eldert Grootenboer, presented the session on Service Bus. He is a program manager for Services Bus. He started with a quick introduction about, what is Service Bus, followed by the below agenda.


  • Recent releases
  • Coming soon
  • Roadmap

Recent releases

  • Disable Local authentication
  • JMS and large messages
  • Minimum TLS picker
  • Service Bus Explorer in the portal

Disable Local authentication

Service Bus has two authorization models – SAS (local) & Integrated Azure Identity model. It’s now possible to completely disable local SAS authentication

Disable Local authentication

JMS and large messages

JMS 2.0 – for premium users. Support up to 100 Megabytes.

  • Java & Spring using JMS 2.0 API
  • Seamless migration
  • Works with enterprise connectors
  • Up to 100MB message size
  • JMS and large messages

Eldert showed a live demonstration for Service Bus Premium Java & Spring JMS 2.0 API.

Minimum TLS picker

Minimum TLS 1.2 has been released recently with the below features.

  • Set minimum TLS version
  • Connections with lower TLS versions are dropped
  • TLS 1.2 by default
  • Released for Service Bus and Event Hubs

Service Bus Explorer in the portal

  • Integrated into portal
  • Azure AD integrated
  • Implements most used features from stand-alone Service Bus Explorer
  • Incrementally introduce new features

Coming Soon

These features will be released in a couple of weeks/ months or sooner.

  • Scale sets
  • Consistent low lately queues

Scale Sets

  • Introduce partitions on Service Bus Premium
  • Allows for much higher scalability
  • Focus on high throughput scenarios where absolute order and message distribution are less important.

Consistent low lately queues

  • Consistent low latency on your entities
  • Higher reliability, as we move to local storage
  • Uses the same storage abstraction as Event Hubs


The below features are in the early phase and still in the designing stage. So there is no timeline for when it will be released.

  • Queue Purge
  • Durable terminus

Queue Purge

  • Purge all messages from a specific point in time
  • First focus is on the Dead letter Queue
  • Integrated with Service Bus Explorer

Durable terminus

  • We see more connections issue with containers & distributed system
  • Allow recovery of broken links
  • Keep track of full message state

Eldert closed the session by asking for feedback about the new feature releases from the audience.

#8: Streaming with Event Hubs & Stream Analytics – (Ajeta Singhal / Kevin Lam)

This blog is a transcript of the session “Streaming with Event Hubs & Stream Analytics” by Kevin Lam and Ajeta Singhal at INTEGRATE 2022.

Azure Event Hubs

Event Hubs is a simple, reliable, scalable, fully managed real-time data ingestion service that helps build dynamic data pipelines and respond quickly to business challenges by streaming millions of events per second from any source.

Streaming with Event Hubs

What’s coming in Event Hubs

  • Kafka portal experience – Enable Kafka admin operations and operational views
  • Data generator – Publish events into your Event Hub using sample data.
  • Managed Identity for Capture – Use managed identity for interaction with storage accounts. Capture into storage accounts in a different subscription.
  • Schema Registry schema types – Add support for JSON.
  • Rounding Out Kafka – Kafka compaction log retention policy. Enable use of Kafka connectors
  • Auto-Scale for Premium – Set up scaling rules to scale up and down clusters-based metrics
  • More Premium regions – Goal: All regions

Features of Azure Stream Analytics

  • Productive
    • Simple SQL language extensible with Javascript or c#.
    • Zero code integration with 15+ Azure services.
    • Best in class authorizing, debugging and diagnostics tooling.
  • Hybrid
    • Run your logic in the cloud (Multi-tenant or dedicated).
    • Deploy logic to the IoT Edge.
    • Or, run on-premises using Azure Stack.
  • Intelligent
    • Build-in ML functions integration with Azure ML
    • Built-in geospatial functions
    • Parallelize jobs automatically
  • Trusted
    • Highly certified and compliant with financially backed 3*9s SLA
    • No data loss, repeatability, and once-only processing guarantees.
    • Secure connection between your resources through private endpoints
    • Real time Event Streaming

Real-time Event Streaming

Stream Analytics

What’s coming in Stream Analytics

  • 30% Performance boost
    • Continuous platform improvements automatically improve job performance by up to 30%.
  • PostgreSQL and Azure Data Explorer output
    • High Throughout egress to PostgreSQL for real-time applications and ADX for telemetry analytics
  • Physical job diagram
  • System and User Assigned Managed identities
    • Authenticate with managed identities and not deal with connection strings.
  • Faster recovery on restarts
    • Improved automatic checkpoint restoration dramatically increases catch up rate on failures
  • GA of autoscale and no code editor
    • Polishing the preview experience and graduating these features to GA.

#9: Modernize your API Stack with GraphQL and Azure API Management – (Elizabeth / Adrian Hall)

Elizabeth Barnitt from Microsoft Azure API management presented the session about the recent product update, deep dive, into the session on how you can use GraphQL to modernize API Stack with a quick demo.

She started the session with the API Management authorizations (public preview). API Management authorizations is a new capability that makes it easier to manage access tokens when sending requests to APIs based on OAuth 2.0 standard. It’s currently in public preview, this feature creates value for professional and citizen developers alike, supporting scenarios

API Stack with GraphQL

Followed by a bunch of generally available updates with regards to API management and stack,

API management and stack


Before getting into the GraphQL, she discussed where REST APIs fall short and covered up a couple of points,

  • Many calls are required to serve a single component.
  • Over-fetching and under-fetching
  • Inefficient for modern client-side development

She also touch based on how it has been implemented in Windows Apps to call the categories and icons, top and bottom section


Quick Introduction to GraphQL

Like an API endpoint, GraphQL is an HTTP endpoint that prioritizes giving clients exactly the data they request and much more.

 Introduction to GraphQL


The advantages of GraphQL in quick words,

  • Introspection
  • Auto backwards compatible
  • Client generation
  • Self-documenting
  • Real-time updates

Followed by the advantages, she showed how we implement the GraphQL with a quick demo.


GraphQL is investing in the security issues below,

Finally, Elizabeth concluded with the take ways, as you can use GraphQL without losing your backend investments. Production GQL is easier and more secure with Azure API management.

#10: Getting started with SAP OData APIs using API Management – (Martin Pankraz / Eastbury)

Following the previous API management session, this session also focused on the same but in a different context. Martin Pankraz and William Eastbury joined us for the first time at INTEGRATE to help us get started with SAP OData APIs and demonstrated live integration scenarios using API Management.

Martin and William started the session with some figures giving us awareness of why we should care about SAP.


They gave a pure demo-based session and made it more interactive by bringing in scenarios discussed in previous sessions of the day.


  • Meet the corporate ninja cat
  • A risky integration demo with SAP technical user
  • Understand SAP OData flow complexity for integration
  • Another risky live demo with user mapping – aka SAP Principal Propagation

Martin and William started the session by introducing the Ninja Cat stickers, followed by an interactive demo session. The first demo was a simple architecture where the Logic Apps is listening using twitter connectors.


Understanding the SAP OData flow complexity for integration was the central part of the demonstration. They also presented workflows based on SAP OData and interesting demos of how it is implemented in real-time. In specific, they also showed how this could be done with API Management.

SAP OData flow complexity

Martin and William concluded the presentation with an interactive Q&A session and some resources based on this session for reference.

That’s a wrap on our summary of Day 1 at INTEGRATE 2022. We already looking forward to Day 2 and Day 3 sessions. Thanks for reading! Good night from Day 1 at INTEGRATE 2022.

Stay tuned with #INTEGRATE2022

This blogpost was prepared by: