BizTalk360 V9.1 – New Features and Enhancements

BizTalk360 V9.1 – New Features and Enhancements

As you know BizTalk360 keeps up its standard by introducing new features or by improving existing features, that ease the user experience to the next level in every single release. We are delighted to inform you that the next version of BizTalk360 V9.1 will be released for production use within a couple of days!

New Features Introduced in BizTalk360 V9.1

Clustered NT Service Monitoring

BizTalk360 is already capable of monitoring clustered BizTalk and SQL Server resources such as Disks, System Resources, Event Logs, and NT Services. In the case of the failover scenario, the BizTalk360 monitoring service will automatically take the active server for monitoring.    

From this version on, the user can monitor clustered NT Services by setting up the expected state of the clustered service as ‘At least One Active’.

Consider a scenario where you have a clustered BizTalk environment, in which your Enterprise Single sign-on service is configured as Generic Type, i.e the SSO service is clustered, and you want to ensure that the SSO service should up and running in at least one of the clustered nodes.  This can be easily achieved through BizTalk360 NT service monitoring.

With this feature, you can monitor the state of your NT services in your BizTalk or SQL servers by configuring the Expected state as Started or Stopped. The clustered NT service can be monitored by configuring the expected state as “Atleast One Active”. The BizTalk360 monitoring service will ensure that the configured service is always up and running in any of the respective clustered nodes.  An alert will get triggered to the configured email-Id when the service goes down in all the nodes.

NOTE: For better understanding, the clustered nodes are grouped with similar colour code.


The user can also set up AutoCorrect for this. In this case, when the SSO service goes down in both the clustered nodes, then the BizTalk360 monitoring service will automatically try to start the service in any of the nodes. With this, you can ensure that there is no downtime in the service. 

Recurrence Scheduled Maintenance

The latest version of BizTalk360 will hold the enriched form of Stop alerts for maintenance, which is renamed as “Scheduled Maintenance”. Schedules can be configured to stop monitoring immediately or at a later point in time, based on your maintenance plan.

Immediate Maintenance

You can set up the maintenance immediately from the current time by enabling the ‘Immediate’ option and providing the maintenance End Date and Time in the schedule configuration.

Future Maintenance

Configure the schedule with Start and End Date/Time to stop monitoring during the future maintenance period. A future maintenance schedule can be configured for both once or recurrence execution.

  1. One Time Execution – You can create a One Time Schedule, if you want to stop the monitoring during, for example, the deployment of BizTalk applications, which has been planned only once in the future date, i.e on June 1st from 9 AM to 11 AM.


  2. Recurrence Execution – The schedule will be created once and can be executed multiple times based on the recurrence pattern daily, weekly, monthly, i.e daily 10-11 PM, alternate weekends, 4th Wednesday of every month, etc.


The user can now also edit the schedule and manually stop the maintenance in between, i.e. before the maintenance period gets over. So, it is not required to wait until the end of the configured maintenance cycle.

Schedule actions such as create, delete, modify, stop maintenance are audited for further reference.

Monitoring Improvements

Web Endpoint Monitoring

Monitoring Status Enabled/Disabled is introduced in Web Endpoint monitoring. This enables the user to define when BizTalk360 should start/stop monitoring the configured Web Endpoint.

For instance, you may configure multiple Web Endpoints, but you temporarily don’t want to monitor all the endpoints. In this case, you can set the monitor status as Disabled for those endpoints.

BizTalk360 will start to monitor the configured Web Endpoints only if the status is set as Enabled.


Clone Alarm

Users can now easily copy all the artifacts mapped for monitoring and the data monitoring configurations from one alarm to another. With the Clone alarm feature, users can copy both the alarm configurations and all the artifacts mapping configurations.


MSMQ Age Monitoring

With this enhancement, the user can monitor the oldest message in an MSMQ queue by using the threshold parameter ‘Message Age’. This threshold parameter is added to monitor and alert the oldest message in MSMQ, based on the configured message age units’ Days/hours/minutes.

Mapped Artifacts  

All the artifacts that have been configured for monitoring under a particular alarm are listed in the Manage Mapping section in Monitoring Dashboard.

SMTP Notification Channel  

The user can define for which error type(s) notifications should be sent through SMTP notification channels, i.e. only in case of Error & Warning or Error/Warning/Healthy state of the artifacts.

Rename Data Monitoring Schedule

The created Data Monitoring schedule can be edited and renamed at a later point in time. Also, users are restricted to create a duplicate schedule for the same alarm under the same monitor type.

Analytics Improvements

SQL Server Performance Widget

Widget to show the SQL server performance (CPU & Memory Usage) is added in the Analytics dashboard.

Reassociate the SQL Query

In the Reporting section, the Secure SQL Query widget can be edited and re-associated to any configured Secure SQL Query.

Event Log Data Collection Optimization

In earlier versions, the Advanced Event Viewer feature collected all the Event log entries for the configured Event Logs and Event Log Sources, but irrespective of error levels. From this version on, to avoid data growth, the user can (de)select the error levels (Information, Warning, Error, etc ) which should be collected. This way, BizTalk360 will start collecting event logs based on the selected error levels.

View MDN Message in EDI AS2

EDI AS2/MDN message content can be viewed as an encoded and wired format.

BizTalk Server 2020 Compatibility

We are proud to share that BizTalk360 is now compatible with BizTalk Server 2020!

Group Properties

Under BizTalk Group properties, users can view newly added properties in BizTalk Server 2020. 

  • Receive Location (Fault Tolerance)
  • Audit Log Operation

Receive Location Advanced Schedule Configuration

The recurrence schedule configured in BizTalk Server 2020 receive locations can now be viewed in BizTalk360.


Considering the feedback from our customers, BizTalk360 will continue to provide more useful features. Why not give BizTalk360 a try! It takes only 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments. 

The post BizTalk360 V9.1 – New Features and Enhancements appeared first on BizTalk360.

BizTalk Server 2020 – Features that Developers/Administrators can leverage

BizTalk Server 2020 – Features that Developers/Administrators can leverage


On January 15, 2020, Microsoft has announced the much-awaited release of BizTalk Server 2020 for public usage. Ever since Microsoft Product Team announced BizTalk Server 2020 in Integrate 2019 event, there has been a lot of expectations about the new release.  BizTalk Server 2020 is an important update with key features and addresses some of the existing challenges. This version has support for newer platforms like Visual Studio 2019, Windows Server 2019, Windows SQL Server 2019. BizTalk Server 2020 requires the following  Hardware and Software requirements.

New features that are shipped in this version are Analytical capabilities (Publish tracking data to Azure), Application Life Cycle Management with VSTS, Management APIs, Advanced Scheduling, TLS 1.2 Support, API Management, gMSA Account, Adapters (Event Hubs, Office 365, Blob) and more additional updates, like SSO Affiliate application support in SFTP Adapter. Partially disabled receive locations etc., Some of the features that are in the release have been updated with BizTalk Server 2016 feature packs (Automatic Deployment with VSTS in BizTalk Server and Manage API are part of Feature Pack 1 update)

These features are helpful to Administrators and BizTalk Developers/Deployment Team with common updates like Adapters support. In this blog, we are focusing on the features that Developers, Administrators /Deployment team can take advantage of.

  1. XSLT 3.0 Support and Custom XSLT Transform
  2. Automatic Deployment with VSTS in BizTalk Server
  3. Manage API
  4. Publish API Services to Azure API Management

Custom XSLT Transform

From this version of BizTalk Server on, the BizTalk Mapper has the ability to select the Custom XSLT Transform (Saxon 9 HE) or .Net Framework. BizTalk’s default XSLT engine implementation is based on .Net Framework, however, this support is limited to XSLT 1.0.  By using this new property “XSLT transform engine”, other XSL transform engines can be configured at the map level.


XSLT 3.0

Support of XSLT 3.0 in BizTalk Server 2020 will help the developer to use any XSLT version in schema transformation in BizTalk Mapper. Developers can customize the XSLT based on their business requirements. XSL Functions can be defined, and it provides the option to choose the dynamic transform functionality.

What is Saxon-HE?

Saxon-HE is an open-source tool for processing XML documents using XSD schema and XSL Transform. Users can start using Saxon-HE 9 engines if they needed XSLT3.0 support during data transformation.

Let us take a business scenario in which EDI X12 850 data needs to be transformed into a purchase order. Saxon HE 9 XSLT will be used to transform the 850 by XSL Path and Custom extension XML to Purchase Order XML (XSLT3.0 will support the JSON Format in XPath Transform).



Note: Saxon 9 doesn’t support embedded scripting. As a result, functoids shipped as part of BizTalk may not function well with Saxon-HE  9.

Extend to other Custom XSLT Engines

Starting with BizTalk Server 2020, users can extend the custom XSLT transform engine in the BizTalk Mapper. Users can implement a custom XSLT transform engine by defining the XSLT transform implementation which is derived from abstract class Microsoft.XLANGs.BaseTypes.ITransform2 in assembly Microsoft.XLANGs.BaseTypes.dll.

Follow this article to know how to extend Custom XSLT with different Transform engines.

Automatic Deployment with VSTS in BizTalk Server

The deployment of BizTalk Applications can be a cumbersome process, as it can be hard to manage the artefacts binding information of different environments. Automatic Deployment of BizTalk Server with Visual Studio Team Services is released as part of the BizTalk Server 2016 Feature Pack1 update. Now, all the feature pack updates of BizTalk Server 2016 are clubbed into the BizTalk Server 2020 release. With Azure DevOps Service, users will be able to automate the deployment process through configuring a VSTS agent.

The VSTS Admin creates the build and releases definitions in Azure CI/CD pipelines. Developers will take advantage of the CI pipeline to build the BizTalk Applications and check-in the source code into Git or VSTS repositories. The CD pipeline will be used to deploy the BizTalk Applications into different environments (DEV, QA & Production).

You can follow the steps to create a deployment pipeline as mentioned in this article.

Manage API

BizTalk Server Developers can take advantage of REST APIs to customize their Business requirements through the exposed APIs covering the following areas in BizTalk Management Service. Management data APIs are endpoints that let you remotely update, add, and query the status of different Artifacts in your BizTalk Server environment.

  1. Parties & Agreements
  2. Applications
  3. Batches
  4. Business Profiles, Role Links
  5. Fallback Settings
  6. Hosts
  7. Operational Data
  8. Orchestrations, Receive Locations, Receive Ports, Send Ports and Send Port Groups
  9. Policies
  10. Protocol Types
  11. Resources
  12. Schemas and Transforms


REST APIs are installed as part of the BizTalk Server 2020 Setup. It has been configured in IIS.

  1. BizTalkManagementService
  2. BizTalkOperationalDataService


Swagger Definitions

The endpoints are added using REST and come with a swagger definition. Users can access the Swagger definitions of the installed Management Service APIs. With the swagger definitions, developers can benefit from knowing the input and output parameters of each API method. Users can try out/test API methods through Swagger definitions.



Publish WCF-Basic HTTP methods to Azure API Management

Starting from BizTalk Server 2020, WCF-Basic HTTP API endpoints can be published to Azure API Management. It will provide the option to monitor and manage the API methods from the Azure Portal.


The option to publish to API Management is only available for the Receive Locations of WCF-Basic Http Adapter type. Prior to publishing API methods, create the API Management Service in the Azure Portal.


Users can publish the API methods to the Azure API Management Service:

  1. Right-click the WCF-Basic HTTP Adapters and select the “Publish to API Management “option
  2. In the Publishing Dialogue, sign in to the Azure Portal
  3. Select the Azure Subscriptions, Resource Group, and API Management Service
  4. WSDL Specifications can be published by choosing either WSDL file or Http URL with single WSDL
  5. Mention the API Name
  6. Then click on the Publish button

Once the WCF HTTP APIs are published successfully, you can view the published APIs under the selected API Management Service. Now the user has the facility to test or push the API methods to higher environments.



As integration solution has started to focus on Azure Serverless technologies, Microsoft has started to provide Hybrid integration capabilities.  It will provide the options for the users to choose the solution that suits their business case. With the release of BizTalk Server 2020, more Azure Service offerings like Backup the BizTalk databases, API Management Service are introduced. Along with Logic Apps Adapter, these new features will help you build flexible integration solutions. Happy Integration!

The post BizTalk Server 2020 – Features that Developers/Administrators can leverage appeared first on BizTalk360.

What’s new in BizTalk Server 2020!

What’s new in BizTalk Server 2020!

At our annual event Integrate, Microsoft announced last year that BizTalk Server 2020 should have released in the first quarter of 2019. Only two weeks in the new year, Microsoft has released BizTalk Server 2020 (v3.13.717.0)! In this blog, we want to update you on what’s new in this version of the product.

No Changes in Available Editions

Similar to earlier versions of the product, BizTalk Server 2020 comes in 4 flavors:

  • Microsoft BizTalk Server 2020 Developer
  • Microsoft BizTalk Server 2020 Branch
  • Microsoft BizTalk Server 2020 Standard [to do: changed limitations]
  • Microsoft BizTalk Server 2020 Enterprise

You can download these products when you have an Enterprise MSDN account.


New Features in BizTalk Server 2020

During Integrate 2019, Paul Larsen, the Program Manager who is responsible for BizTalk Server, already highlighted which new features are coming in BizTalk Server 2020. You can read a recap about Paul’s session here.


As you can understand from Paul’s session, we were already expecting platform alignment. More importantly, BizTalk Server 2020 contains all features from BizTalk Server 2016, including the 3 Feature Packs, which have been released.

You can find the complete set of new features here

But, let’s have a look at some of the new features and capabilities.

Support for newer platforms

BizTalk Server 2020 adds support for the following Microsoft platforms:

– Visual Studio 2019
– Windows Server 2019, Windows Server 2016, Windows 10
– SQL Server 2019, SQL Server 2017, SQL Server 2016 SP2
– Office 2019, Office 2016

Hardware and Software Requirements for BizTalk Server 2020


Operational Data Monitoring and Analytics.
Leverage the power of Azure (Application Insight and Event Hub) for deep data storage and Power BI for reporting and viewing of data.

Send tracking data to Azure
Configure data feed for Power BI

Application Lifecycle Management with VSTS

Using Visual Studio Team Services, you can define multi-server deployments of BizTalk Server 2020, and then maintain those systems throughout the application lifecycle.

Configure automatic deployment using VSTS

Management APIs

Manage your environment remotely using the new REST APIs with full Swagger support.

REST API reference

Advanced Scheduling

New and improved scheduling capabilities in Adapters.

Configure time zone and recurrence

Backup to Azure Blob Storage

When deploying BizTalk Server to Azure VMs, you can backup BizTalk Server databases to Azure blob storage.

Configure the Backup Job

Event Hubs Adapter

Using the new Event Hub Adapter, BizTalk Server can send and receive messages with Azure Event Hubs, where BizTalk Server can function as both an event publisher and subscriber, as part of a new Azure cloud-based event-driven application.

Event Hubs adapter

Office 365 Adapters

Leverage the power of BizTalk in newer office automation workflows by integrating with Adapters that allow you to send or receive Office 365 emails, receive or transmit Office 365 calendar events, and create Office 365 contacts.

Office 365 Outlook Email adapter
Office 365 Outlook Calendar adapter
Office 365 Outlook Contact adapter

Group Managed Service Accounts

Extend windows GMSA support to BizTalk operations and services.

Using Group Managed Service Account

Audit Log

Making BizTalk further secure by maintaining audit trails of all management operations.

New Read-Only Operator role

Brand new read-only operator role in facilitating the dev-ops model, where access to production stamp is provided without the ability to update anything.

Additional updates

·         Move to new long term supported Microsoft OLEDB Driver for SQL Server

·         Support for SSO Affiliate applications in the SFTP adapter

·         SQL Availability Group support for BAM DTS Package via SSIS Catalog

·         Partially disabled receive locations

·         Throughput improvements for Dynamic Send Ports with Ordered Delivery

Deprecated and Removed Features

Some features of the product are deprecated or removed from the product. Here’s the list:






Removed from BizTalk Server installation

POP3 and SMTP adapters


Office 365 adapters

Support for ACS authentication in adapters


SAS authentication

SOAP adapter


WCF-BasicHttp Adapter

Old SQL adapter


WCF-SQL Adapter

BPEL support



JDE OneWorld adapter



OWC redist



BAM Portal



WCF-NetTcpRelay adapter



Changes that Catch the Eye

Based on the above lists, and besides the already expected features and improvements, a few features catch the eye.

Audit Log

Until now, no auditing was available for any operations performed against the BizTalk environment. Luckily, from BizTalk Server 2020 on, the Administration console provides auditing of operations. To be able to use this feature, you will have to turn it on in the Group Settings screen.


The auditing data is stored in the Management database, and you can access it via the Operational Services. At the moment, the supported operations are:

  • Creating, updating and deleting ports
  • Suspending, resuming and terminating service instances
  • Adding, updating and removing BizTalk applications
  • Importing binding files


Although this is a good start, multiple important operations are still missing; think of starting/stopping of ports, orchestrations, and host instances. We hope that Microsoft adds such operations in the future.

Read more about this feature here.

Support of .NET Framework v4.7

Earlier, Microsoft has announced that .NET 4.8 will be supported.

New Read-Only Operator role

The BizTalk Operator role has changed. Where before, it was possible to perform actions like stopping/starting ports and changing the port configuration, this role is now completely read-only. This can certainly be useful for facilitating DevOps scenarios.


When accessing the BizTalk Server 2020 Admin console as a BizTalk Operator, all the operations are still accessible. However, when an operator tries, for example, to stop a port, an error message shows up, and the operation becomes blocked. Unfortunately, the error message is not always clear that the operation is blocked due to insufficient permissions.


BAM Portal is Deprecated

Microsoft has decided to deprecate the BAM portal. Probably due to the new capabilities to push data to Azure, they decided to deprecate the old-fashioned BAM portal. In case you are using BAM, and you are considering upgrading to BizTalk Server 2020, you can still install and configure the BAM portal from the BizTalk installer and configuration wizard; you won’t be left in the dark.

Deprecated and Removed Adapters

Multiple updates in this area as well. For example, Microsoft deprecates the POP3 and the SMTP adapters in favor of the Office 365 adapters, which appeared in the BizTalk Server 2016 Feature Packs. Next, the old SQL adapter has been removed and replaced by the WCF-SQL adapter, and the JDE OneWorld and the WCF-NetTcpRelay adapter have both been deprecated.

BizTalk360 Support of BizTalk Server 2020

The BizTalk360 product team has eagerly followed the developments around BizTalk Server 2020, and we are glad that BizTalk Server 2020 has been released. For BizTalk360, it is evident that the product must support all recent versions of BizTalk Server.

That’s why we made the latest released versions of BizTalk360 and Atomic Scope compatible with BizTalk Server 2020!


BizTalk Server 2020 has been released. This is the 11th version of the product since its inception in 2000. Although we have already seen most of the features of this release (in the BizTalk Server 2016 Feature Packs), this is still a useful release. Especially when you are still on versions older than BizTalk Server 2016, it will certainly be worth upgrading or migrating to this release.

The post What’s new in BizTalk Server 2020! appeared first on BizTalk360.

BizTalk360 V9.0.3 New Features and Enhancements Summary

BizTalk360 V9.0.3 New Features and Enhancements Summary

It’s time to upgrade your BizTalk360 installation! We are here with our next release of BizTalk360 V.9.0.3. 

A brief summary of new features we introduced in V9.0.3

Database Size Monitoring

Database Size monitoring helps to monitor the Data and log file size of the BizTalk and BizTalk360 databases, by simply configuring the error and warning threshold values for the database and log file sizes.

Below are the BizTalk databases that can be monitor using BizTalk360:

  • BizTalkDTADb
  • BizTalkMgmtDb
  • BizTalkMsgBoxDb
  • BizTalkRuleEngineDb
  • BAM databases (BAMPrimaryImport, BAMAlertsApplication, BAMArchive, BAMStarSchema)


Analytics Custom Widget Reporting

By using the BizTalk360 Reporting Custom widget, you can retrieve performance metrics of the BizTalk environment such as Messaging Performance, Message Transmission failure rate, Server performance, etc., as a report. Based on the configured schedule you can receive that report in your email box.


Configurable Polling interval for monitoring

By default, the BizTalk360 monitoring service checks the status of all configured artifacts every 1 min. However, BizTalk360 provides an option for the user to configure the polling interval. Based on the configured polling interval, the monitoring service will determine the monitor status of the endpoints.

Migration Scenario – After migration, the default polling interval 1 min will be set to all the Endpoints. This can be modified as per your requirements.


SQL Server Cluster Monitoring

we extend our support to monitor the SQL Server cluster. Cluster SQL Server can be monitored by configuring the SQL Server Network name. BizTalk360 will start monitoring the currently active node. In case of a failover, BizTalk360 will automatically take the active server for monitoring.

The following resources can be monitored by configuring the SQL Server:

  • CPU & Memory
  • NT Services
  • Disks (available disk space)
  • Event Logs


Subscriptions (Message Box)

In addition, to retrieve the service instance and message details, BizTalk360 allows users to execute queries to retrieve the details of the subscription from the message box database. The subscription details such as Name, Service Name, state, subscription type, service instance id will be retrieved on message box query execution.


Look at this blog article to see the benefits of the above features in detail.

Let’s jump into the feature improvements in detail

SQL Authentication Support

BizTalk360 allows users to view and monitor the SQL Query results by using Secure SQL Query and database query monitoring functionality. In Which BizTalk360 executes the Query by connecting to the server against windows system users (using windows authentication mode).

But shared server can have multiple users having access to different instances and Databases. So, to support this, we have improved these functionalities by supporting SQL Authentication mode, With this user can connect to the database with the relevant user credentials.  From this version on, you can also query your Azure databases.


Dashboard Improvements

The dashboard is one of the key functionalities where customers would be using more often on a day-day basis. So, we have considered improving the dashboard frequently based on customer feedback.

BizTalk360 Monitoring Dashboard improvements

  1. Indication of alarm status (Enabled/Disabled)
  2. Number of Alerts Notified (2/3)
  3. The artifacts from the collapsed view are now clickable to route to the respective mapping section


BizTalk Group Dashboard improvements

BizTalk group dashboard in BizTalk360 gives the consolidated view of all the artifacts mapped to all the alarms in an environment.

From this version on, we allow the user to configure the BizTalk group dashboard based on their needs. Users can choose the artifacts types (Application, Servers, Queues, Folder Monitoring, etc . ) that they want to look into the dashboard. So that BizTalk360 monitoring service will fetch the status of only the chosen artifacts type on every cycle, rather looking for all the artifacts. In this way, we have improved the performance of the monitoring service. Also, you can Enable or Disable the BizTalk Group dashboard at any point in time.

Migration Scenario – After migration, the BizTalk Group Dashboard will be in enable mode, with all the artifacts type chosen. After which you can reconfigure this as per your requirement.


Tracking (DTA) Performance Data Collection Optimisation

In the earlier version, Users can enable tracking data collection for various metrics type, say  Failure/Success rate for Port, Schema, Messaging Performance for the port , schema, orchestration, etc, where BizTalk360 will start collecting data for all the metrics of the selected type. From this version on, to improve the performance, we allow users to choose the relevant DTA metrics, which will reduce the number of calls to the DTA database.

Users can choose the DTA metrics at the environment level in a well-ordered tree view diagram.

Migration Scenario –If you enabled Tracking (DTA) Performance Data Collection then after migration all DTA metrics under the selected type will be enabled. This can be modified as per your requirements.


Logic App

With the rise of Hybrid integration solutions, the job of BizTalk administrators has extended to the (Azure) cloud. BizTalk360 helps these administrators by providing operational and monitoring support for Logic Apps and  API Apps, thereby admin need not check the Azure portal to know the health of these services,  where they can easily operate and monitor from BizTalk360.

However, in the earlier version of BizTalk360, we allow all the users to manage all the LogicApps there is no access restriction. We have improved this in this release where admin can define which user can manage (enable, disable, delete, trigger) the Logic Apps based on the role.

In addition to this, we have introduced the filter option to filter the logic apps under different subscriptions.

Quick Alarm

With the quick alarm, you can select the application artifacts that you want to monitor, BizTalk360 will automatically map that artifacts for monitoring.


Notification Channel

Now you can define the error type i.e. only error & warning or error/warning/healthy of the artifacts to get notified in the notification channels(slack, Service Now, Webhook).


Place Holder Encryption

Place holders can be used in the custom widgets. To tighten the security now all the placeholder values configured in custom widgets will get encrypted. For the existing placeholder, values will get encrypted automatically once you upgraded to the latest version.

Service Instance operations 

From this version on, we allow the user to enter the reason in the comment section (optional) for all the service instance operations (Resume/Suspend/Terminate). The same will get audited for reference.


All the file mask patterns supported in BizTalk server will now support in BizTalk360


Considering the feedback from our customers, BizTalk360 will continue to provide more useful features.

Why not give BizTalk360 a try! It takes only 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments. 


The post BizTalk360 V9.0.3 New Features and Enhancements Summary appeared first on BizTalk360.

What is coming in BizTalk360 Version 9.0 Phase 3?

What is coming in BizTalk360 Version 9.0 Phase 3?

We are super excited to share the list of features that are planned for our upcoming BizTalk360 release 9.0 Phase 3. We always aim to constantly improve our product in every release, based on customer feedback and their business needs. Generally, we release a new version each quarter. In August 2019, we released Version 9.0 Phase 2. Now Version 9.0 Phase 3 is planned for late November and our team is energetically working towards it.

Reporting for Analytics custom widget

The BizTalk360 Reporting feature offers out of the box capabilities that allow users to create schedules and generate PDF documents of critical performance metrics at specific time periods.

From v9.0 phase 3 on,  you can configure analytics custom widgets with the performance metrics of your BizTalk environment such as Messaging Performance, Message Transmission failure rate, Server performance, etc . and get that as a report, based on the schedule configuration.

For example, you can get a report by the end of the day with the number of messages processed for a particular schema or a particular send port.


Database Size Monitoring

This feature will be helpful for BizTalk administrators who frequently check the database growth to ensure the health of the BizTalk databases.

Some of the BizTalk databases can grow extremely big; it’s not uncommon to have over 1 million records in certain tables (ex: MessageInOutEvents table in Tracking Database). As the database size grows, the SQL server will need more memory and CPU to read data from the tables, and when the size of each table increases, it slows down the DB operations and affects the BizTalk operation.

With Database Size Monitoring, you can monitor the database and log file size of below BizTalk and BizTalk360 databases, by simply configuring the error and warning threshold values for the database and log file sizes.

  • BizTalkDTADb
  • BizTalkMgmtDb
  • BizTalkMsgBoxDb
  • BizTalkRuleEngineDb
  • BAM Db’s
  • BizTalk360

For example, If the size of the BizTalkDTADb is greater than a threshold value configured, then you will get notified.


Configurable polling interval for monitoring

The BizTalk360 Monitoring Service usually runs every 60 seconds and checks for the status of the artifacts which are mapped for monitoring, which include Application artifacts, File/FTP/SFTP, Queues, web endpoints, etc. We got requests from a few of our customers that they have configured multiple endpoints for monitoring and the BizTalk360 monitoring service calls the endpoint for every 60 secs to check the status, but they don’t want to call the endpoints frequently i.e. every 60 secs. So, to improve this, we are providing an option to configure the polling interval for monitoring; depending on the configurated time, only then the monitoring service calls the endpoint.

SQL Server Cluster Monitoring

In BizTalk360, we have a BizTalk and SQL Server Monitoring which allows you to monitor the Disks, System Resources, Event Log, and NT Services. From this version on, we extend our support to monitor the SQL Server cluster. By configuring the SQL Server network name for monitoring, BizTalk360 will start monitoring the current active node and in case of failover scenario, BizTalk360 will automatically take the active server for monitoring.



Support SQL Authentication SQL Query

The standard BizTalk Admin Console does not come with any capabilities related to accessing SQL Server data. This leaves the support people to rely on external SQL tools like SQL Server Management Studio (SSMS). Tools like SSMS are designed for DBA’s and Developers, and it’s not particularly friendly when it comes to pure support and management; a level of technical expertise is required to be able to use SSMS. We understood the practical challenges of not having an integrated SQL data access tool along with the BizTalk Administration and the challenges it exposes.

That’s why we have already built the “Secure SQL Queries” feature in BizTalk360.

Using Database Query monitoring, you can set up thresholds that are limited to database scalar values. For every BizTalk360 Monitoring cycle, the monitoring service will validate the results of the SQL query against the configured threshold values. If any violation happens, it will trigger a notification to the configured emails in the alarms.

However, since BizTalk360 does not support SQL authentication, currently you cannot access Azure databases from Secure SQL query and in Database Query monitoring. From this version on, the product supports SQL authentication for database access. You can query your Azure databases from the BizTalk360 Database query monitoring and Secure SQL Query sections.

Logic Apps Improvements

From this version on, you can provide access restrictions for logic apps. Based on the role, you can define which user can manage (enable, disable, delete, trigger) the Logic Apps.

Additional details such as Version, Last Run Time and Last Run Status of the logic app will get listed in the grid.

Copy Alarm along with artifact mapping

The first step in monitoring by using BizTalk360 is to create Alarms. Alarms in BizTalk360 act like a package to associate things together. We already have an option to copy the alarm which will copy only the alarm configuration. Now we are extending this to copy the alarm along with the artifact mapping configuration.

Alarm and Monitoring Dashboard Improvements

Below are some of the improvements, we have planned for this release in the Monitoring section:

  • Indication of alarm status (Enabled/Disabled)
  • Last Execution Time of the alarm
  • Number of Alerts Notified (2/3)
  • Indication whether Auto Correct is enabled or not
  • The artifacts from the collapsed view will be made clickable to route to the respective configuration

Performance data collection improvement for DTA

We already optimized performance data collection in the last release. in this release, we are improving on DTA performance data collection. With this, we allow users to choose the relevant DTA metrics, which will reduce the number of calls to the DTA database.


Considering the feedback from our customers, BizTalk360 will continue to provide more useful features on every release.

Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments.

The post What is coming in BizTalk360 Version 9.0 Phase 3? appeared first on BizTalk360.

Consolidated monitoring with the new BizTalk Group Dashboard

Consolidated monitoring with the new BizTalk Group Dashboard


BizTalk users who use BizTalk360 can manage their BizTalk environment in a more efficient way. Monitoring and Notification is amongst the most important features in BizTalk360, The first and foremost step for monitoring is mapping the artifacts to an alarm. In which user can use this on a daily  basis to monitor their BizTalk environment and get notified if any violation occurs.

The Monitoring Dashboard is the one stop point for users to view the status of the artifacts which are mapped to an alarm. Typically a customer displays the monitoring dashboard in big screens and looks for the health of their BizTalk environment visually.  The monitoring dashboard is structured at alarm level, which lists the status of all the artifacts mapped to the respective alarm. However, you cannot see all the alarms and their mapped artifacts status in a single view, which was a usability problem persist from our side. To overcome these we are implementing the “BizTalk Group Dashboard” for the v9.0 (phase 2). With this dashboard you can view the status of all the artifacts mapped to any number of alarm in a single view and you can easily customize it using the rich filter option provided  

Let’s deep dive into BizTalk Group Dashboard and see how it solves the problem.

BizTalk Group Dashboard

The BizTalk Group Dashboard is designed to monitor all the artifacts (and view all errors) which are mapped to all the configured alarms in BizTalk360, in a single view. The BizTalk Group Dashboard can be found under the Home of Monitoring section. The “BizTalk Group Dashboard” will automatically pick up all the artifacts (which are mapped to any of the BizTalk360 alarms) and displays the status of the artifacts in a graphical manner . Also the error details of the displayed artifacts  are shown in a grid view . The BizTalk Group dashboard checks the status of the artifacts in every 60 seconds .

For better usability, BizTalk Group Dashboard splits the windows in two sections:

  1. Displays the mapped artifacts in a graph
  2. Show the Error/Warning details in an artifact level segregation

The dashboard has a draggable separator so that the user can adjust the width of the graphical window and the error/warning pane, based on their resolution. They can even minimize or maximize the error/warning pane to the leftmost section.

There is a chance of mapping the same artifact to multiple alarms. In such cases, the BizTalk Group Dashboard picks only the positive state of artifacts for monitoring. For instance, a Receive Location is mapped to an alarm1 with the expected state as Enabled and the same receive location is mapped to another alarm, say alarm2, with the expected state as Disabled; in this scenario, the BizTalk Group dashboard will only consider the positive state mapping such as expecting state as Enabled for monitoring.

Note: BizTalk group Dashboard is only designed for visual monitoring of the BizTalk environment and artifacts. It will not trigger any alert notifications.

Advantages of BizTalk Group Dashboard

Comparing to the already existing Monitoring Dashboard, the BizTalk Group dashboard has quite some advantages. Some of the main advantages of the BizTalk Group Dashboard are:

  • It consolidates the status of all the artifacts which are mapped to any alarm and there is no need to switch alarms for viewing the status of any other artifact
  • The BizTalk Group Dashboard can be split into two windows; one for the artifact graph and the other for viewing the Error/Warning pane. For usability, the split windows can be adjusted based on the monitor resolution
  • For better monitoring, the user can apply filters (at the top of the graph) based on the artifact and/or based on the event type filter option
  • The user can view the Error/Warning details along with the graph



Many organizations use different alarm configurations and patterns for their processes. Some of the commonly used alarm configuration patterns are:

  1. Integration-based alarm configuration
  2. Role-based alarm configuration
  3. Entity-based alarm configuration

Integration-based alarm configuration means configuring BizTalk artifacts, File location, Queues, Web endpoints, etc. in an alarm, which all belong to the same integration.
Role-based alarm configuration is configuring alarms for people in different roles. For example, a platform administrator will be interested in infrastructure settings like Disk, system resources, host instances in an alarm.A Database Administrator (DBA), on the other hand, will be more interested in the SQL Server instances and the jobs which have been deployed in it.
Entity-based alarm configuration is configuring similar components in the same alarm. For instance, putting all the queues like IBM Queue, Azure service bus queue, MSMQ in one alarm.

Irrespective of the alarm configuration/pattern, now the user can customise the BizTalk group dashboard using the filter capablity .Say Administrator can monitor the infrastructure components which are mapped to all the alarm .) and queues in a single dashboard window by filtering only the Infrastructure components.


With this feature, users are able to visually monitor all the artifacts and view error/warning details in a single dashboard with a much more comprehensive view. If you have any feedback or suggestions, please write to us at You can get started with monitoring your BizTalk environment via the BizTalk Group Dashboard by downloading the 30-day free trial of BizTalk360.

The post Consolidated monitoring with the new BizTalk Group Dashboard appeared first on BizTalk360.

BizTalk360 v9.0 Released

BizTalk360 v9.0 Released

It’s time to upgrade your BizTalk360 installation! We are here with our next release of BizTalk360, v9.0. We always aim to constantly improve our product based on customer’s feedback and their business needs. The features added in this release are typically chosen from our feedback portal and based on the impact and the number of requests.

Benefits out of this release

BizTalk360 Auditing – When you are a group of support people, diagnosing and solving problems in your production environment, it’s important to keep track of who is doing what in the environment. With BizTalk360 activities auditing, you can easily identify who did what.

SMTP Notification Channel – Managing the email recipients which are mapped to an alarm is very simple now. With the SMTP notification channel, you can configure email distribution lists which can be mapped to multiple alarms. In addition to this, you can also configure specific team member emails to receive Up and Auto Correct alerts.

Switch User Role – The User roles can be changed in a single step. You can easily convert a super user to a normal user and vice versa.

Unmapped Application Artifacts – We don’t want you to miss artifacts for monitoring. With this new Unmapped application artifacts feature, you can determine the artifacts which are not (yet) mapped for monitoring.

System Alerts – The BizTalk360 administrator can get to know about the health of BizTalk360 environment through System Alerts. The administrator can now get alerts about BizTalk360 License expiration, Unmapped application artifacts list and Monitor error details.

Copy to Clipboard – With this,user can copy the field values in a single click from the BizTalk360 UI.

Let’s jump into the features in detail

BizTalk360 Auditing

BizTalk360 has a powerful operational governance and auditing capability to maintain the logs of the user activities in the system. This feature helps the BizTalk administrators to find out “Who did what” in the environment over a period of time. BizTalk360 already has the capability to audit BizTalk level activities. You can think of actions on BizTalk Applications, Service Instances, Host Instances, BizTalk and SQL Servers, ESB Messages and Business Rules.

For this release we have implemented BizTalk360 activities auditing. This will give a clear insight about the various activities performed by the user in the Manage Alarm, Artifacts Mapping, and Secure SQL query sections. 

Alarm operations such as new alarm creation, changing the alarm status (Enable/Disable), deleting an alarm, updating alarm details will be logged with the existing and new values, along with the user details. Administrator can also view the artefact mapping details. For instance, if any artifacts have been added or removed from an alarm mapping for monitoring, that will be logged.

Secure SQL query auditing includes Creating new query, Editing/Deleting the query and Query import.


SMTP Notification Channel

The SMTP Notification Channel provides an ability to create email distribution lists by grouping email ids based on the business needs.

Using the same email recipients for multiple alarms was not easy in earlier versions; the recipient’s details needed to be entered for each alarm.  To overcome this, we have introduced the SMTP Notification channel, through which the user can configure email distribution lists under one channel and can be mapped to multiple alarms. In addition to this, we have added email grouping for Up Alert and Auto Correct Alert. With this, the user can configure different email ids to receive Up and Auto Correct alerts.

Switch User Roles

In earlier versions, there was no option to convert a Super user to a Normal user or vice versa. To change the user roles, the profile needed to be deleted and recreated again, which is a time-consuming process. This has been solved in this version; the user roles can quickly be converted in a single step, by editing the user and toggling the user roles.

Unmapped Application Artifacts List

BizTalk360 can monitor amongst others BizTalk application artifacts. With this new Unmapped application artifacts feature, you are able to determine the artifacts which are not (yet) mapped for monitoring.

You will get a summarized list of unmapped application artifacts in the Monitoring Dashboard. This list contains the artifacts which are not mapped to any of the alarms for monitoring. For instance, if any new artifacts have been added in your BizTalk environment, we will bring that to your notice and you can easily map the artifacts for monitoring.

System Alerts

BizTalk360 is the single tool to manage operational activities, monitoring and analytics of the mission-critical BizTalk environment. Systems Alerts are sent to the BizTalk360 administrator about the health of BizTalk360 environment. The administrator can now easily get the alerts about BizTalk360 License expiration and Unmapped application artifacts list in the BizTalk environment.

The list of Unmapped application artifacts can be notified based on the alert schedule in the system settings. License Expiration notification will be automatically be triggered on 30, 15, 7 and 2 days before the license expiry.

Copy To Clipboard

Our business data is highly valuable. The information uses contain decision-making and problem-solving. From v9.0 on, the Copy to Clipboard option is provided to copy information in a single click from the BizTalk360 UI to the Windows Clipboard.

Few Enhancements and Bug Fixes

Besides these new features, we have also brought several enhancements and bug fixes.

Default Auto Correct Reset Interval

Auto healing is an existing feature which tries to bring the artifacts back to the expected state after a violation has occurred. The system will retry the auto healing process for a configured number of times. Once the retry limit is reached, the auto healing process will be stopped. The user can set the number of retries and reset it when the maximum limit is reached. However, it can be time-consuming to set the reset interval time for every configured auto correct. To overcome this, an option to set the default auto-correct reset interval is introduced in the System settings section.

Monitoring Dashboard Improvements

The BizTalk360 ‘Monitoring Dashboard‘ becomes the one-stop point for support people to view the health status of the BizTalk environment. You can see the summarized dashboard can be seen in a much enriched view.

Now the monitoring graph can be resized based on the screen resolution.

Blade Improvements

When multiple blades are opened, there was a partial inconsistency with the blades. Already opened blades remained open until the user close it manually. Now, the blade will get closed when the user clicks on another blade and the user is able to view only the relevant blades.


Considering the feedback from our customers, BizTalk360 will continue to provide more useful features. Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments. 


The post BizTalk360 v9.0 Released appeared first on BizTalk360.

System Alerts and Unmapped Application Artifacts in BizTalk360

System Alerts and Unmapped Application Artifacts in BizTalk360


BizTalk360 has powerful monitoring features to manage the BizTalk Application Artifacts, Queues, Infrastructure, Health check tools, etc. Most of the customers are using BizTalk360 for its core monitoring capabilities. BizTalk360 is the single tool to manage operational activities, monitoring and analytics of the mission-critical BizTalk environment. In this transforming phase, it is a tedious process for a dedicated person to monitor all the configurations. To address this scenario, System Alert notification is implemented in BizTalk360 v9.0.

Why System Alerts?

Currently BizTalk360 use Alarms to send out the notifications of Application artifacts, queues, Infrastructure settings health of the BizTalk environment. In the same perspective there is need to know the health of BizTalk360, which will helpful to the administrator who takes care BizTalk360. The BizTalk360 Monitoring service will take care of sending system notifications to the configured admin user email boxes. These email boxes can be configured in the system settings. A new monitoring sub service called ‘System Alert’ has been introduced to send system related notifications. System Alerts can be enabled in the System Alert Settings under Monitoring and Notification tab of system settings. A user can configure multiple admin emails with semicolon separated values.

A System Alert notification can be pushed to the admin users in the two ways:

  • Scheduled
  • Automatically Triggered

The BizTalk360 Monitoring service has a polling interval of 60 seconds and it will check for system alerts to be pushed. Either these alerts will be pushed based on a trigger or on a schedule.

NOTE: Custom Notification channel alerts are not applicable for Systems Alerts in this version (9.0).

System Alert Schedules

System Alert Schedules will send periodic reports of unmapped application artifacts. This will be helpful to the BizTalk Operation Users/ Administrators who can take appropriate actions to configure the artifacts for monitoring.

System Alert configuration can be scheduled as follows:

  1. Daily – Daily schedule will push the notification at the specified time in a day for all the days of the week.
  2. Weekly – Weekly schedule can push the notification on the specified day and time in the week (for example, Wednesday, 12 PM)
  3. Monthly – Monthly schedule can push the notification on the specified day and time in the month (for example, the 15th day of the month, 10 AM)

System Alerts Schedule Configuration

Based on the configuration, the Monitoring Service will alert the Unmapped Application Artifacts in the BizTalk Environment. The Unmapped Application Artifacts list will be available as an attachment in the email notification.

Unmapped BizTalk Application Artifacts

The Unmapped Application Artifacts list feature can be used to manage the artifacts which are not mapped to any of the BizTalk360 Alarms for monitoring.


It will be helpful for the administrators who are taking care of the application artifact’s health. When BizTalk Developers or a deployment team deploy new artifacts into the BizTalk Group, the BizTalk administrators might not exactly know the newly deployed artifacts. In such cases, the Unmapped Application Artifacts status will provide a warning indication to the administrators/operators.

The status of Unmapped artifacts is shown in the monitoring dashboard. Unmapped application artifacts status will be healthy when all the application artifacts in an environment are mapped to the alarm. It will show the unhealthy status, when any of the artifacts left unmapped for monitoring. “Unmapped Application Artifacts Link” will be listed with the application artifacts which are still unmapped.

Unmapped Application Artifacts

Unmapped Monitor State

From BizTalk360 version 9.0 on, the new Unmapped monitoring status is introduced. This is the default state for application artifacts. Users can set the expected state and start monitoring the artifacts.

NOTE: Users can use the Do Not Monitor state, if they don’t want to monitor an artifact. In such cases, that artifact will not be listed under Unmapped application artifacts.

Automatic Triggered Alerts

When the events or conditions meet the triggering rules, then the alerts will be triggered automatically. System Alerts can be of triggered based

  • BizTalk360 License Expiration
  • Database Sizes (BizTalk Database & BizTalk360)

In this version of BizTalk360, BizTalk360 License Expiration is implemented. Database Sizes triggered notification will be implemented in a future version of BizTalk360.

License Expiration

When your BizTalk360 license is about to expiry, BizTalk360 System Alerts service will notify the license expiration to the admin users. Notification can be sent on the 30, 15, 7, 2 days before the license expiry date.

System Alert History

Click on the ‘System Alert History’ button to view the historical System Alerts. Alert History is maintained for both alert types(Schedule and Trigger). Users can view the system alerts email notification which has been sent to admin users in HTML Format.

System Alerts History

Data Purging

System Alerts historical records are maintained based on the data purging policy of “Alert & Maintenance History”. BizTalk360 will maintain the system alert notification history up to the configured number of days/months.

Based on your requirement you can set the purge duration.


System Alerts notifications will be helpful to BizTalk Administrators to manage the BizTalk Group health and BizTalk360 environments.

Get started with the free 30 days trial. For any queries/feedback please write to us

The post System Alerts and Unmapped Application Artifacts in BizTalk360 appeared first on BizTalk360.

Introducing BizTalk Server Availability Monitoring (BizTalk360 version 8.5)

Introducing BizTalk Server Availability Monitoring (BizTalk360 version 8.5)

A typical highly available BizTalk Server group contains one or more BizTalk Servers.  We have witnessed some of the complex BizTalk Server environment handling high volume traffic having an infrastructure similar to the one shown below with 6 BizTalk Server and 3-4 SQL Servers.


There are 2 main reason for having multiple BizTalk Server is the group

  • Scalability
  • Resilience/High Availability

Scalability: The more servers you have in the group means more processing power. You can create multiple BizTalk Server Host and Host Instances in each one of the available servers and increase the volume of messages you can process.

Resilience/High Availability:  If you wanted to make sure the environment is highly available, you need to have at least 2 BizTalk Servers in the group and also need to carefully plan how the host/host instances are configured to make sure if one server goes down it doesn’t bring the whole environment down.

Why do you need this?

As a BizTalk Administrator you need to make sure all of your BizTalk Servers are up and running and processing messages at expected level.  In the above 6 server configuration, there is a possibility one of the BizTalk Servers goes down and no one really notice it for a long period, until the environment itself becomes a bottle neck. In smaller environments (ex: 2 BizTalk Servers), it becomes super important to make sure your BizTalk Servers are up and running all the time to avoid down time or react to down time quickly.

To address these challenges we are introducing BizTalk Server Availability monitoring in BizTalk360 version 8.5.

As always, one of the core strength of BizTalk360 for monitoring BizTalk Server environments is we wanted to make it super simple and great user experience to configure things. It will literally take less than 2 minutes to setup BizTalk Server Availability Monitoring in-spite of the complexity of your environment.


The above screen show how you can configure the availability monitoring for a 2 BizTalk Servers group. The servers are already listed, you simply need to select them and click the “Enable Monitoring” button.  (PS: You need to understand the concept of Alarms in BizTalk360)

Protocol Type: In order for us to check the availability we need to reach the servers, we support “Ping” and “Telnet” to achieve this, one of these protocols need to be enabled.

Monitor Availability (either all or one of them)

This is very important and very specific to BizTalk Server availability monitoring. You can choose the option to alert either if one of the BizTalk Server is the group has gone down or alert only when all of the servers in the group has gone down. The first one is useful if you know there are intermittent issues and the server will come back online after some time and there is no need to alert the teams unnecessarily.


Give it a try on your own environment by downloading a 14-day free trial of BizTalk360.

Author: Saravana Kumar

Saravana Kumar is the Founder and CTO of BizTalk360, an enterprise software that acts as an all-in-one solution for better administration, operation, support and monitoring of Microsoft BizTalk Server environments. View all posts by Saravana Kumar

What is going to be the future of BizTalk360?

What is going to be the future of BizTalk360?

About 10-12 years ago (around 2004-2005), Service Oriented Architecture (SOA) was a big topic in the enterprise world. Massive projects were initiated to align enterprises to be more service oriented with a middleware/ESB platform like BizTalk Server in the middle.

When we talked about SOA implementation using Microsoft technologies during this period, only two technologies/platform stood out –

  • Windows Communication Foundation (WCF), and
  • Microsoft BizTalk Server

WCF was set of libraries built on top of the .NET Framework that helped to build SOAP based (later REST support was added) web services. WCF was more of a platform that shipped along with the .NET Framework and evolved gradually along with the .NET releases. BizTalk Server, on the other hand, was a full blown Enterprise Server Product that acted as a Middleware platform mainly addressing the challenge of not creating an integration spaghetti between those services (represented as APP in below pictures) created using WCF.

Without BizTalk Server With BizTalk Server

BizTalk360 journey between 2011 – 2016

When we started BizTalk360 back in 2010, the objectives were pretty straight forward. Nearly 10,000 medium to large organisations have invested in Microsoft BizTalk Server to address their integration requirements.

We spotted a lot of gaps in BizTalk Server when it comes to BizTalk Server day-to-day administration and monitoring. It looked like a straightforward bet to build a world-class product that can help these 10,000+ customers to improve their operational efficiency.

We started off initially with BizTalk360 as a monitoring solution for BizTalk Server and the product slowly evolved into addressing various operational and analytics needs of the BizTalk Server. There are over 100 features in the product now covering various aspects of day-to-day operational needs like Security, Governance/Auditing, Monitoring, Analytics, Productivity Tools, Knowledge Base, Rich Dashboards, etc. making it a must have add-on product for any Microsoft BizTalk Server customers.

BizTalk360 currently has over 500 enterprise customers, and we are proud to say that Microsoft itself is one of our biggest customers. Microsoft internally uses BizTalk Server for all of their IT and Supply Chain requirements and they rely on BizTalk360 for their day-to-day operations. You can read the case study “Why Microsoft chose BizTalk360 instead of SCOM

What is the state of Integration today in Microsoft Stack?

In the last 5-6 years, the innovation around technology exploded in all directions. Cloud and mobile became mainstream and companies like Microsoft, Amazon, Google and IBM pumped a lot of investment into the cloud. On the other hand, SaaS (Software as a Service) based products exploded in other direction. Today, no one really wants to buy off-the-shelf software products, run their own servers and manage upgrades and patches. They simply want to use software or services provided by the third party rather than owning them. About 10-15 years ago, SIEBEL was the leader in CRM space, however, today that segment is ruled by technologies like Salesforce and Microsoft Dynamics 365. Similar story exists in all software segments like Source Control (GIT and Visual Studio Team Service), Productivity Tools (Office365, Google Apps), Email (Office365, Google) etc.

With all these changes, it’s natural for Integration Platforms and Products to evolve as well. The role of integration has become so immense in the last 5 years due to the above mentioned reasons. Today, companies buy/use multiple software products which do one thing really well rather than living with a monolithic beast software which claims to do everything but not good at anything.

This change in attitude also means all these independent software product/services need to talk to each other, which created a new segment of integration products in the likes of IFTTT, Zapier, Azure Logic Apps, SnapLogic, Dell Boomi, etc

Microsoft responded well to this growing challenge in the integration space, addressing the requirements of: Hybrid Integration solutions (the combination of Cloud + On-Premise integrations), Quick & Easy integration solutions, Business Users (aka citizen integrators) integration solutions etc.

If you look at Microsoft Integration Stack today, it’s not just BizTalk Server and WCF anymore. There are at least a dozen products/services that are mainly geared towards Integration in Microsoft Stack.

  • Microsoft BizTalk Server
  • ASP.NET Web API’s
  • Azure Logic Apps
  • Azure App Services (Web Jobs)
  • Azure Functions (Serverless Compute)
  • Azure API Management
  • Azure Service Bus (Queues/Topics)
  • Azure Stream Analytics
  • Azure Event Hubs
  • Microsoft PowerApps
  • Microsoft Flow
  • Azure Gateway (Hybrid Connection)

BizTalk360 – 2017 and beyond

One of the key aspects of a product company like us is that we need to be on the forefront of technology all the time. We need to adapt quickly to the change and understand the fact “change is the only constant”. We cannot just sit back and relax saying BizTalk360 is doing well. We have been closely monitoring the trend what’s going on, what will happen to the existing BizTalk Server customers in the next 10-15 years.

We are fortunate enough to build up a close relationship with Microsoft and the Integration community and are fully aware of the changes that are happening around Integration.

BizTalk360 is now slowly evolving into a product that will cater for the big picture. We wanted to create a single unified tool that will help any customer who invested in Microsoft platform for their integration needs.

We can clearly see the challenges that are building up when you have so many technologies included in a solution. There is no single management tool that will cater for the day-to-day operations. Customers might end up using BizTalk Server Admin Console for some of the activities and Azure Portal for some of the other activities, which is not productive and you are never going to be confident you set up access rights correctly across multiple tools, educating support people how to operate and monitor your solutions.

There are various other challenges like, for example, for Monitoring, you will need an end-to-end monitoring solution that covers both on-prem and cloud, you will also need tracking and analytics solution that will stretch between on-prem and cloud etc. We predict customers might end up building management tools, exactly like what they did 10 years ago for BizTalk solutions. BizTalk360 was born to address the challenge faced by BizTalk Server customers.

Today we are at a juncture where we see the same challenge at a bigger level and BizTalk360 is well positioned to address that challenge since we are already halfway through covering the on-premise solution.

What available and what’s coming in BizTalk360

We realized this situation almost 2 years ago and started expanding BizTalk360 to cover both on-premise and cloud technologies that fall into the Integration bucket with a vision of creating a single unified management and monitoring tool for Microsoft Integration.

Today, BizTalk360, in addition to its full blown support for BizTalk Server, can also manage and monitor related Azure Integration Technologies like

In the upcoming 8.5 version (planned for July 2017), we are bringing in support for Azure Integration Accounts, App Services, and Azure Stream Analytics.

We are also working on a secret project with a bigger vision, which I cannot talk much at this stage (stay tuned).

We will continue our investment in this direction and make BizTalk360 a single must have tool for anyone using Microsoft Technologies for their Integration Requirements.

Author: Saravana Kumar

Saravana Kumar is the Founder and CTO of BizTalk360, an enterprise software that acts as an all-in-one solution for better administration, operation, support and monitoring of Microsoft BizTalk Server environments. View all posts by Saravana Kumar