• The Reporting Challenge in Complex BizTalk Environments
• What’s New: A Quick Look at the Enhanced Capabilities
• Administration Dashboard: Total Operational Clarity
• ESB Exception Dashboard: Turning Exceptions into Opportunities
• Smarter Reports, Faster Decisions: What’s Changed in Analytics

The Reporting Challenge in Complex BizTalk Environments

BizTalk Server environments are inherently complex managing multiple host instances, orchestrations, send/receive ports, and message pipelines simultaneously. BizTalk Administrators needs clear, real-time visibility across landscape to keep operations running smoothly. Spotting the performance degradation, identifying suspended messages, and detecting infrastructure bottlenecks before they escalate requires consolidated insight rather than scattered, manual checks. As environments grow, so does the need for a centralised reporting layer that turns raw operational data into actionable intelligence helping administrators anticipate issues, prioritise effectively, and spend less time in troubleshooting and more time in resolving the issues.

What BizTalk environments need is a unified, intelligent reporting layer that speaks the language of BizTalk/SQL Administrators and Business Users: operational precision for administrators, transactional clarity for EDI teams, business-level visibility for BAM users, and rapid fault resolution for ESB teams. That is exactly where enhanced BizTalk360 reporting steps in.

What’s New: A Quick Look at the Enhanced Capabilities

BizTalk360 has steadily evolved its dashboard and reporting experience to give every stakeholder a tailored, data-rich view of their integration environment. The most recent releases bring a powerful set of dashboards with custom widgets, which are designed to represent the metrics that Administrators/Business users are interested.

Here’s a quick look at what’s now available:

Administration and ESB DASHBOARDS (INTRODUCED in v11.8)

The latest release rolls out two significant additions. The Administration Dashboard gives BizTalk and SQL administrators a consolidated, real-time view of infrastructure and operational health, while the ESB Dashboard brings clarity to fault handling and itinerary processing. Both are built to reduce the time it takes to move from detection to resolution.

EDI and BAM Dashboards (Introduced in v11.6)

Earlier, version 11.6 delivered the EDI Dashboard and the BAM Dashboard, extending rich visibility to EDI trading partner activity and Business Activity Monitoring data. These dashboards put transactional and business-level insights directly in front of the people who need them without requiring deep technical intervention each time.

Custom Widgets Across the Board

A defining theme across all these dashboards is flexibility. The ESB, BAM, and EDI dashboards all support custom widgets, allowing users to configure exactly the metrics they want to track and display. Whether it’s transaction counts, partner-level interchanges, or business milestones, each user can shape their dashboard around their own priorities.

This widget-driven approach extends to the newest dashboards as well. The Administration Dashboard offers configurable widgets covering key operational metrics, and the ESB Dashboard provides custom widgets for faults and itinerary metrics, letting integration teams keep the most critical fault and routing data front and centre.

To summarise where each feature is included in BizTalk360 reporting to share the trend analysis and failure insights, to respective stakeholders with periodic schedules (Daily, Weekly and Monthly)

• Administration Dashboard (v11.8) – operational and infrastructure health, with configurable widgets. Dashboard widgets
• ESB Dashboard (v11.8 – faults and itinerary metrics, with custom widgets. ESB Exception Dashboard
• BAM Dashboard (v11.6) – BAM Dashboard (v11.6) BAM Dashboard
• EDI Dashboard (v11.6) – trading partner and EDI transaction metrics, with custom widgets EDI Dashboard and widgets | EDI custom widgets
• Analytics Dashboard (Earlier versions) – BizTalk Messaging and Server Performance metrics
• Application Dashboard (Earlier versions) – Deep insights about the application artifacts
• Secure SQL Queries (Earlier versions) – Consolidate query results

Together, these dashboards form a cohesive, customisable reporting experience – one that scales across the various metrics.

Administration Dashboard: Total Operational Clarity

The Administration Dashboard gives BizTalk and SQL administrators a single, consolidated view of their entire environment’s operational health. Instead of jumping between multiple consoles and queries, administrators get real-time visibility into the metrics that keep integrations running smoothly – all in one place.

What makes it truly powerful is its flexibility. The dashboard supports a range of configurable widgets, letting administrators build a view tailored to their priorities. Whether tracking host instance status, message processing activity, suspended service instances, or overall system performance, you decide what appears front and centre.

This widget-driven approach transforms the dashboard from a static report into an actionable operational insight.

ESB Exception Dashboard: Turning Exceptions into Opportunities

The ESB Exception Dashboard is designed to handle the complexity, transforming scattered fault data into clear, contextual insight that teams can act on immediately.

Rather than discovering failures only after downstream systems are affected, integration teams get a centralised, real-time view of ESB faults and itinerary processing. The dashboard surfaces what’s failing, where, and how often — giving teams the context they need to identify root causes faster and prioritise resolution based on actual business impact.

Configurable Widgets for Faults and Itineraries

The real strength of the ESB Exception Dashboard lies in its custom widgets. Teams can configure widgets to track critical metrics like

• Fault counts by application
• Exception trends over time
• Itinerary processing volumes
• Service-level routing activity

Use Case: Proactive ESB Monitoring in Order Processing — Purchase Orders & Invoices with ESB Reporting

The Scenario

Consider a manufacturing company that processes thousands of Purchase Orders (POs) and Invoices daily through its BizTalk ESB infrastructure. Purchase Orders arrive from customers via multiple channels, are validated and enriched through ESB itineraries, and are routed to the ERP system. Once orders are fulfilled, Invoices flow back through the ESB transformed, validated, and delivered to customers and the finance system. Every step is governed by dynamic itinerary-based routing across multiple services.

The Challenge

In this flow, a single failure can have a direct business cost. A Purchase Order that fails during validation or routing means a delayed or lost sale. An Invoice stuck in an itinerary step means delayed revenue recognition and frustrated customers. Worse, these failures often surface in different services at different stages making it hard to see whether an issue is an isolated glitch or a growing systemic problem.

How the ESB Exception Dashboard Changes the Game

With ESB fault and itinerary metrics consolidated into one configurable view, the order processing team gains continuous, contextual oversight:

• Fault widgets configured by application and service instantly reveal where Purchase Order failures are clustering – for example, a spike in validation faults pointing to a malformed message format from one specific customer channel.
• Itinerary metrics widgets track processing volumes across each stage of the PO and Invoice journeys, making it immediately obvious if Invoices are entering an itinerary but not completing it signalling a stalled routing step or an unavailable downstream service.
• Trend visibility highlights patterns over time: if invoice transformation faults rise every month-end during peak billing cycles, the team can address capacity or design issues before the next cycle hits.

Dive deeper into the capabilities in the ESB Exception Dashboard documentation.

Smarter Reports, Faster Decisions: What’s Changed in Analytics

The latest enhancements to the reporting including ESB, EDI, BAM Dashboards with custom widgets and Administration Dashboard they’re about enabling faster, more confident decisions across the organisation. By combining real-time dashboards with the ability to deliver insights periodically, BizTalk360 ensures the insightful information reaches the right people at the right time, even when they aren’t actively following the analytics data.

Empowering BizTalk Administrators

For administrators, the Administration Dashboard turns continuous operational data into a decision-ready summary. Instead of manually compiling status updates, administrators can rely on periodic reports that capture infrastructure health, message processing activity, and system performance immediately. This means trends are spotted earlier, capacity issues are anticipated rather than discovered, and routine reporting no longer eats into time better spent on resolution. Decisions about scaling, maintenance windows, or troubleshooting priorities can be made quickly, backed by clear and current data.

Supporting Business Users

For business users, the value lies in clarity and timeliness. The ESB Dashboard surface’s fault and itinerary metrics that, when delivered as periodic reports, translate technical events into business-relevant insight. Business stakeholders can understand the health of critical processes, see where exceptions are impacting operations, and gauge whether service levels are being met all without needing to interpret raw technical logs. This shared visibility bridges the gap between IT and the business, ensuring everyone is working from the same picture.

The Power of Periodic Reporting

What ties it all together is the shift from on-demand checking to proactive, scheduled insight. Periodic reports drawn from these dashboards keep both technical teams and business leaders continuously informed, reducing the lag between an event occurring and a decision being made. The outcome is a more responsive where issues are addressed sooner, priorities are clearer, and decisions are grounded in up-to-date, role-relevant data.

Conclusion

In short, smarter dashboards combined with timely reporting mean less time gathering information and more time acting on it.

To know more about the BizTalk360 features, try out the free trial or book a demo.

The post Unlock More Value from Enhanced BizTalk360 Reporting with Smarter Dashboards & Custom Widgets appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

But while BizTalk is robust and reliable solution for the typical integration scenarios in BizTalk Environment, the way it is traditionally managed often creates an unintended challenge.

Operations become too technical.

A simple question like “Why did this order fail?” can quickly turn into a dependency on developers or senior administrators. Accessing the BizTalk Administration Console, understanding artifacts like receive locations or orchestrations, or even identifying failed messages is not straightforward for someone outside the technical team.

Over time, this creates a familiar pattern: business teams lack visibility, support teams feel blocked, and developers end up handling routine operational issues that really shouldn’t need their attention.

Making BizTalk Understandable — Not Just Manageable

What makes BizTalk360 different is not just that it adds features on top of BizTalk. It changes how people interact with it.

Instead of exposing users to the complexity of the underlying system, it presents a clean, web-based interface that focuses on what matters in day-to-day operations.

A non-technical user doesn’t need to understand what a “send port” is. They just need to know: did the message go through or not?

BizTalk360 answers that question instantly. Dashboards give a clear view of system health, ongoing processes, and failures in a way that feels intuitive. Without digging into multiple tools or servers, users can quickly spot if something needs attention.

Managing Multiple Integration Tools from a Single Platform

For non-technical and support teams, managing multiple integration technologies like ESB, EDI, BAM, BHM, and BRE through separate tools can quickly become overwhelming. Different consoles, disconnected monitoring experiences, and scattered operational data often make day-to-day support more complex than it needs to be.

BizTalk360 simplifies this by bringing these integration technologies together into a single web-based platform, giving teams one centralized place to manage and monitor the entire environment.

With BizTalk360, teams can:

• Monitor and manage ESB exceptions, including message tracking and resubmission, from a dedicated ESB Portal
• Access BAM dashboards and business activity data to gain better visibility into transaction flows and business processes
• Monitor Business Hosts and Host Instances through BHM, helping teams quickly identify performance bottlenecks and availability issues
• Track EDI transactions, acknowledgements, parties, and agreements without switching between multiple tools
• Manage Business Rules through the web-based BRE Composer without requiring direct access to BizTalk servers

Instead of navigating multiple consoles and servers, operations and support teams get a unified operational experience inside BizTalk360. This reduces complexity, improves visibility, and helps both technical and non-technical users work more efficiently across the entire integration ecosystem.

From “Escalate Everything” to “Handle It Confidently”

In traditional setups, even minor issues get escalated. A failed message? Escalate. A stopped service? Escalate. When retry needed? Escalate. Not because the issue is complex, but because the tools are.

BizTalk360 changes this dynamic by simplifying how issues are presented and handled. Failed messages are no longer buried inside technical consoles. They’re surfaced clearly, along with meaningful error information.

More importantly, actions like resubmitting a message or retrying a process are made accessible in a controlled, user-friendly way. First-level support teams can resolve a large percentage of issues on their own, without waiting on developers.

Empowerment Without Risk

One of the biggest concerns when opening operational access to non-technical users is safety. What if someone accidentally stops a critical process? What if too much access is given?

BizTalk360 addresses this with granular role-based access control. Rather than an all-or-nothing approach, organizations can define exactly what each user can see and do. A business user might only track transactions, while a support engineer can handle resubmissions without touching configurations.

It’s a balance where teams are empowered to act, but within safe boundaries.

Removing the Need for Server Access

Traditionally, managing BizTalk means logging into servers, using remote desktop connections, and navigating complex admin tools. BizTalk360 removes that dependency entirely. Everything is accessible through a browser.

This might sound like a small change, but the impact is real. Operations teams can work faster, security overhead is reduced, and the friction of accessing production environments goes away. For non-technical users, it also removes the intimidation factor that comes with handling backend systems directly.

Proactive Instead of Reactive Operations

One of the bigger shifts BizTalk360 brings is in how issues are detected and handled. In many environments, problems only surface after they’ve already impacted the business when a partner raises a concern or a transaction fails downstream. That reactive cycle puts unnecessary pressure on support teams and delays resolution.

BizTalk360 introduces proactive monitoring and intelligent alerting, so teams are notified the moment something deviates from expected behaviour. But it doesn’t stop at alerts. With automated corrective actions, the system can step in on its own like restarting a stopped service, triggering a predefined action, or stabilizing a known issue without waiting for manual intervention.

Operations become less about watching and responding, and more about the system quietly taking care of itself. Non-technical users can trust that BizTalk360 will both flag and, in many cases, fix issues automatically so they can focus only on what genuinely needs their attention.

Learn More about the monitoring dashboard

Staying on Top of Azure Services Too

Modern BizTalk environments don’t live in isolation. Many organizations run Azure Logic Apps, Service Bus, and other Azure services alongside their BizTalk infrastructure, and monitoring them through separate tools only creates extra overhead.

BizTalk360 brings Azure services into the same monitoring experience. Logic Apps can be viewed, managed, and monitored directly within BizTalk360, allowing teams to check run history, enable or disable workflows, and resubmit failed runs without switching platforms. It extends the same simplicity and visibility from BizTalk into the cloud layer.

Learn More about Azure Services in BizTalk360

Getting Notified the Right Way

Knowing something went wrong is only valuable if the right person is informed quickly.

BizTalk360 supports multiple notification channels, allowing teams to receive alerts through the platforms they already use, including email, Microsoft Teams, Slack, and other integrations. This ensures organizations are not dependent on a single communication method for critical issues.

The notifications themselves are designed to be actionable. Instead of sending a vague alert, BizTalk360 provides meaningful context about the issue, helping recipients understand what happened and respond faster without having to start the investigation from scratch.

Learn More about Notification Channels

Analytics That Tell the Story Behind the Data

Day-to-day operations become far more manageable when teams can identify patterns instead of only reacting to isolated incidents.

BizTalk360’s Analytics section provides a historical view of environment performance, helping teams understand trends over time rather than focusing only on immediate issues. Customizable dashboards allow organizations to track the metrics that matter most to them, while shared dashboards ensure teams are aligned with the same operational insights.

Scheduled reports also make it easy for managers and stakeholders to stay informed through regular summaries, without needing to log into the platform themselves.

This shifts the conversation from simply asking “What is broken right now?” to understanding “How has the environment been performing over time?” — a far more proactive and informed way to manage operations.

Learn More about Analytics Dashboard

Understanding Performance Without Being a BizTalk Expert

Throttling is one of those issues that often goes unnoticed until business processes start getting delayed. When BizTalk comes under stress, it slows down message processing, but identifying the exact cause traditionally requires deep technical expertise and manual analysis of performance counters and logs.

BizTalk360’s Throttling Analyser simplifies this completely. It presents throttling data in a clear, visual way, helping teams quickly understand when the system is under pressure, what is causing it, and how long it has been happening.

This allows operations teams to detect performance issues early, escalate them with proper context, and respond proactively instead of reacting after failures occur.

Learn More about Throttling Analyser

Self-Service Help Through the Knowledge Base

In many BizTalk environments, the same issues keep repeating, but teams still spend time searching through emails, documents, or waiting for developer support to find the resolution.

BizTalk360 addresses this with its integrated Knowledge Base feature. Teams can create articles and directly map them to specific error codes, event IDs, exception messages, service instances, or throttling conditions. When the issue occurs again, BizTalk360 automatically displays the relevant Knowledge Base article alongside the error, helping users quickly understand the cause and resolution without additional investigation.

Because the guidance is available directly within the monitoring experience, support teams can resolve issues faster, reduce dependency on developers, and build a more efficient operational process over time.

Explore the BizTalk360 Knowledge Base

Speaking the Language of the Business

Perhaps the most underrated advantage is how BizTalk360 brings visibility closer to the people who need it.

Technical logs and message IDs don’t mean much to someone in operations or finance. They care about outcomes. Did the order go through? Was the invoice processed? Is the partner integration working?

BizTalk360 makes it possible to track at a level that aligns with business context, so non-technical stakeholders can get the answers they need without having to go through IT every single time.

A Shift That Impacts the Entire Organization

When non-technical teams can handle day-to-day operations confidently, the impact goes beyond convenience. Support teams become more efficient. Developers stop getting pulled into routine issues. Resolution times improve. And the relationship between business and IT becomes a lot smoother.

What was once a tightly controlled, technically heavy environment starts to feel more accessible and responsive to everyone involved.

Final Thoughts

BizTalk Server remains a powerful integration platform but managing it does not have to be complex. BizTalk360 takes a more practical approach by simplifying operational tasks, improving visibility, and helping non-technical teams manage environments without constant dependence on deep BizTalk expertise.

It is not just about making BizTalk easier to manage. It is about making it easier for people to work with.

To know more about the BizTalk360 features, try out the free trial or book a demo.

The post How BizTalk360 Helps Non-Technical Teams Confidently Manage BizTalk Operations appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

By integrating BizTalk360 with Jira, monitoring alerts can automatically be converted into trackable Jira tickets. This enables centralized incident management, improves accountability, reduces manual effort, and enhances collaboration between operations and support teams.

Use case

In BizTalk environments, SQL Servers are essential because BizTalk Server databases handle message processing, tracking, configurations, and operational data. Any issue with the SQL Server can directly impact BizTalk performance and message flow. With BizTalk360, administrators can continuously monitor the health, availability, and performance of SQL Servers from a centralized monitoring platform.

For example, if the SQL Server hosting the BizTalk databases becomes unavailable or experiences high CPU or memory usage, BizTalk360 immediately detects the issue and triggers an alert. Through the Jira notification channel, the alert is automatically converted into a Jira ticket with the violation details. This enables support teams to quickly assign ownership, track the incident, and resolve it faster. Reducing downtime and improves operational efficiency.

JIRA integration in BizTalk360

The JIRA notification channel in BizTalk360 enables teams to link monitoring alerts to Jira, a widely used platform for tracking and managing issues. This integration helps teams organize incidents, assign ownership, set priorities, and monitor progress in a centralized, structured way.

With this capability, BizTalk360 automatically converts alerts into tickets whenever a threshold is violated or an issue is detected. Instead of relying on traditional methods like email, notifications are sent via REST APIs, ensuring that every incident is captured as an actionable task. This approach ensures that critical problems are not only notified but also effectively tracked and resolved on time.

Configuring Authentication types in JIRA

To start using the JIRA notification channel, configure the JIRA channel in BizTalk360 and associate it with an alarm. Whenever a monitoring violation occurs, a corresponding ticket is automatically created in Jira with relevant details.

API Token Authentication

An API Token is a simple and commonly used method for authentication. It is easy to configure and can be set quickly without complex permissions configurations.

After generating the token, users need to select API Token as the authentication type in BizTalk360. Then, enter the Jira Base URL, provide the generated Jira API Token, and specify the Atlassian account email address to complete the configuration.

OAuth Authentication

OAuth provides a more secure and controlled way of authentication. Ideal for enterprise environments that require higher security and strict access control. More secure and scalable, as credentials are not directly exposed.

For OAuth 2.0 authentication, select OAuth 2.0 as the Authentication Type and provide the Jira Base URL, Callback URL, Client ID, and Client Secret obtained from the Atlassian developer console. Once the required details are entered, click Authorize to authenticate the Jira account and then save the configuration successfully.

Mapping JIRA Notification Channel to Alarm in BizTalk360

Once authentication is configured in the JIRA channel, the next step is to map the JIRA notification channel to an alarm in BizTalk360. This configuration ensures that whenever a monitoring rule violation occurs, BizTalk360 automatically creates a Jira ticket for the issue.

To send alerts to Jira, a few important properties need to be configured in the Alarm settings. These properties help define how the alert will appear in Jira and ensure that the ticket is assigned and categorized correctly for faster issue resolution.

• Title and Preview – Used to configure the Jira ticket title by adding dynamic tags such as Alarm Name, Environment Name, Alert Type, and Overall Status. The Title Preview section shows how the final alert title will appear in Jira after the configured tags are applied.
• Project Name – Specifies the Jira project where the alert ticket should be created. This ensures alerts are routed to the correct support or operations team.
• Work Type – Determines the type of Jira issue to be created, such as Bug, Task, Incident, or Story, based on the organization’s workflow.
• Assign To – Allows the alert ticket to be automatically assigned to a specific user or team member responsible for handling the issue.
• Priority – Sets the severity level of the alert, such as High, Medium, or Low, helping teams prioritize critical issues effectively.
• Labels – Add keywords to the Jira ticket for easier filtering, tracking, and categorization of alerts across projects.

By configuring these properties in the Alarm section, BizTalk360 can automatically generate well-structured Jira tickets whenever an issue is detected to improve visibility and collaboration. Whenever a monitored artifact, such as a SQL Server, application, or queue, violates a configured rule, an alarm is triggered, and BizTalk360 automatically creates a Jira ticket for the issue.

Conclusion

The JIRA notification channel in BizTalk360 bridges the gap between alerting and incident management by converting monitoring alerts into actionable tickets in Jira. This ensures that critical issues are not only detected promptly but also consistently tracked, assigned and resolved on time.

This integration helps organizations move towards a more proactive and structured approach to operations, improving both system reliability and team productivity.

To know more about the BizTalk360 features, try out the free trial or book a demo.

The post Transform Monitoring Alerts into Actionable Jira Tickets with BizTalk360 appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

Highlights from BizTalk360 v11.8

64-bit Support for BizTalk360 Services – Monitoring and Analytics services now run as 64-bit processes ,enabling improved scalability, better performance, and enhanced memory utilization for handling large-scale monitoring and analytics operations.

JIRA Notification Channel – Automatically create JIRA tickets when the monitoring detects violations. JIRA supports OAuth and API Token authentication for faster and secured incident tracking.

Azure Service Bus Automated Tasks – Schedule enable or disable actions for Service Bus queues and topics to automate message flow management during deployments and maintenance window.

File Monitoring Bulk Configuration – Define Folder, FTP, and SFTP monitoring configurations in a single place and reuse them across multiple locations for faster and consistent setup.

Enhanced Reporting Experience – Generate and share the ESB and Administration dashboards reports to the Administrators/Business users.

Acknowledge BizTalk360 Logs – “Acknowledge” the known issues in BizTalk360 Logs which helps to improve Advisor Score and focus only on active and relevant operational problems.

Let’s look at what’s new in BizTalk360 v11.8.

New Features

JIRA Notification Channel

Managing the incidents becomes much easier with the new JIRA Notification Channel.

BizTalk360 can now automatically create JIRA ticket whenever an alarm violation occurs. The integration supports secure authentication methods including OAuth and API Token, enabling seamless integration with existing support and DevOps workflows.

In many organizations, support teams manually create tickets after receiving alert notifications. This process can delay response time and increase the risk of missed incidents.

With JIRA integration:

• Alarm violations are automatically converted into actionable tickets.
• Teams can immediately begin troubleshooting.

Example Scenario

If a BizTalk Receive Location disabled unexpectedly or a Service Instance gets suspended, BizTalk360 detects the violation and instantly creates a JIRA ticket with the relevant details allowing teams to take immediate action.

Azure Service Bus Automated Tasks

BizTalk360 now supports Azure Service Bus Queues and Topics operations through the Automated Tasks, enabling users to manage queue and topic states through scheduled execution.

Users can automate actions such as:

• Active
• Disable

During deployments or maintenance windows, organizations often need to temporarily stop message inflow to avoid processing interruptions.

Using automated tasks, BizTalk360 disables selected Service Bus queues before deployment and enables them again after completion, ensuring controlled message flow and smoother operations.

With automated tasks schedule:

• Queues/Topics can be disabled before deployment
• Automatically re-enabled after maintenance
• Automatically re-enabled after maintenance

User will also get notified about the action taken to the configured email.

Monitoring Enhancements

File Monitoring Bulk Configuration

Configuring monitoring settings individually for hundreds of Folder, FTP, or SFTP locations can be repetitive and time-consuming.

Organizations with large integration landscapes often maintain consistent monitoring policies across environments. Repeating the same configuration for every endpoint increases operational overhead.

Now user can specify the File/FTP/SFTP configuration such as Authentication, Firewall configuration, Security details once and that can be reused for monitoring all the file locations.

User can also specify the centralised monitoring rule say, if all FTP locations are expected to receive at least one file every hour, teams can configure the rule once and reuse it across all locations instead of configuring each individually.

With Default Monitoring Configuration, users can now:

• Define monitoring rules once
• Reuse them across multiple locations
• Apply monitoring configurations in bulk

SHA-2 Authentication Support for SFTP

BizTalk360 now supports SHA-2–based authentication for nSoftware SFTP monitoring. Which supports enhanced security and compatibility with modern encryption standards.

Monitor Time

To provide better operational insights, BizTalk360 now includes:

• Violation Time in Errors & Warnings notifications
• Last Monitored Time visibility in dashboards and monitoring sections

These enhancements help teams to identify when an issue occurred and Verify whether monitoring is running correctly.

Direct Navigation from Monitoring to Administration

Users can now directly navigate from the Monitoring section to the corresponding artifacts in the Administration section for quicker action on artifacts and reduce the operational delay.

Enhanced Reporting Experience

Reporting has been significantly improved in v11.8.

1)Users can now include both ESB and Administration dashboards in scheduled reports and receive them automatically via email.

Operations and support teams often require regular visibility into:

• ESB exception activities
• Failed itineraries and processing trends
• Environment health and administrative status

Instead of manually logging into BizTalk360 to review dashboards, teams can now schedule reports and receive the required insights directly in their inbox.

2)Improved report generation using the new Playwright-based rendering engine.

The previously used “SelectPDF” rendering engine has been deprecated. We strongly recommend upgrading BizTalk360 to the latest version v11.8 to continue generating reports without issues.

64-bit Support for BizTalk360 Services

The BizTalk360 Monitoring and Analytics services now run as 64-bit processes. This enhancement allows BizTalk360 to handle larger workloads more efficiently in enterprise environments.

Acknowledge BizTalk360 Logs

Enterprise environments often contain recurring warnings or known operational events that do not require action.

Say, non-critical warning generated during scheduled maintenance no longer needs to repeatedly impact the environment health score.

With the new Acknowledge Logs capability ,known issues can be acknowledged and suppressed for defined duration. These acknowledged logs are excluded from Advisor Score calculations and Health status reflect only active and relevant issues.

Conclusion

Whether you are managing complex hybrid integrations or large-scale BizTalk environments, v11.8 helps your teams operate more efficiently and proactively.

Upgrade to BizTalk360 v11.8 today and experience smarter monitoring, seamless integrations, and greater operational control. BizTalk360 v11.8 Release Notes – https://docs.biztalk360.com/docs/v118

The post What’s New in BizTalk360 v11.8 appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

• The Challenge: BizTalk Service Instance Failures Disrupt Critical Business Transactions
• Enhanced Capabilities Service Instance Monitoring
• Simplified Automation with Automated Tasks
• Operational Benefits: Smarter Monitoring. Greater Control. Confident Operations

BizTalk360 is one stop tool to manage your BizTalk environments with powerful Monitoring, Administrative capabilities.

Let us see how BizTalk360 effectively manage the Services Instances.

The Challenge: BizTalk Service Instance Failures Disrupt Critical Business Transactions

In BizTalk environments, failed or suspended service instances can silently interrupt critical business transactions. Relying solely on reactive monitoring often means teams discover issues only after business impact has already occurred.

In a typical Microsoft BizTalk Server environment, service instances represent the live execution of your integrations like order processing, invoice submissions, EDI exchanges, API orchestration, and internal system synchronization. When these service instances fail or become suspended, the impact goes far beyond the middleware layer.

A suspended orchestration might mean:

• Orders are not reaching the ERP system
• EDI messages are not delivered to trading partners
• Invoices are stuck before billing
• Business acknowledgments are never sent

The real challenge is that many of these failures occur without immediate visibility.

Many teams still rely heavily on reactive monitoring manually checking the Admin Console, responding to user complaints, or waiting for downstream systems to report missing data. By the time issue is detected, the damage is already done:

• Escalations from business users
• Revenue delays
• Compliance risks

Service instances can fail for many reasons including,

• Mapping or transformation errors
• Schema validation issues
• Connectivity failures to SQL, FTP, SFTP, or APIs
• Throttling conditions
• Resource constraints (CPU, memory, disk)

Without proactive monitoring and automated handling, suspended instances accumulate rapidly in the Message Box database. Performance degrades. Troubleshooting becomes harder because engineers must sift through historical noise to find the real issue.

In high-volume environments, even a short monitoring gap can translate into hundreds or thousands of unprocessed transactions.

Modern BizTalk operations require:

• Real-time visibility into running and suspended instances
• Intelligent filtering and categorization
• Automated remediation where possible
• Alerting that prioritizes business impact, not just technical failure

How BizTalk360 effectively manage suspended service instances

Let us see how BizTalk360 Service Instances monitoring and automated tasks proactively act to avoid the transactions failures.

When it comes to managing your BizTalk environment, BizTalk360 offers a comprehensive set of capabilities designed to keep business transactions running smoothly.

With powerful Service Instance management, including bulk operations and archive options, teams can quickly resolve and maintain large volumes of transactions. Threshold and Data Monitoring enable proactive oversight, while Automated Tasks and Automated Actions help address potential issues before they impact operations. On top of that, built-in Analytics metrics provide clear visibility into performance trends and recurring challenges, empowering teams to make informed decisions and continuously optimize their environment.

Data Monitoring Automated Actions

When an incorrect schema is deployed, one that doesn’t align with the transform schema configured in the Send Pipeline. This situation can immediately disrupt message processing and push transactions into a suspended state.

With BizTalk360 Data Monitoring, you can proactively track such failures and configure automated actions on suspended service instances. Instead of relying on manual intervention, the system can automatically resume valid instances once the schema issue is corrected reducing downtime, preventing transaction backlogs, and keeping business operations moving without disruption.

This feature is widely used by many customers over a decade in-order to take control of business transactions without degrading the performance.

Enhanced Capabilities in Service Instance Monitoring

In earlier versions, Service Instance monitoring was limited to detecting issues based solely on instance status. In the latest version, monitoring has been enhanced with metric-based threshold rules and advanced filtering capabilities, enabling more precise detection and refined monitoring results.

• Threshold rules monitoring
  Configure thresholds to detect abnormal service instance volumes before they escalate into failures. Gain granular visibility to take timely and appropriate actions, such as resuming, suspending, or terminating affected instances.

  With the multiple filter search options, instances monitoring can cover the multiple failure scenarios in a single threshold rule configuration. It helps the operation teams to validate the business transaction from the single view.

• Improved filters with the multiple values and flexible operators
  In the service instance queries, multiple filter values selection for the parameters like Service Name, Application, Error Description are being in-corporate. This implementation provides the flexible control over the service instances with granular and targeted instances.

Simplified Automation with Automated Tasks

Monitoring the service instances is no longer just about visibility, it’s about decisive action.

With enhanced Service Instance Monitoring, automated tasks can now trigger corrective measures the moment predefined conditions are met. Instead of waiting for manual intervention, the system can automatically:

• Start or stop artifacts
• Restart NT Services
• Restart Host Instances
• Execute predefined PowerShell scripts

By combining automated actions with configured threshold rules, you can proactively respond to abnormal conditions before they escalate into business disruptions.

For example, when files are not being processed at a receive location, it often signals that the associated Host Instances are in a throttled state. Instead of waiting for manual intervention, automated tasks can immediately trigger corrective measures such as restarting the impacted Host Instances. This will help in restoring the normal processing and minimizing downtime.

This approach shifts operations from reactive firefighting to controlled, intelligent remediation ensuring business continuity without constant manual monitoring.

Service instances often face other real-world scenarios such as suspended messages, failed orchestrations, or unusually long processing times. Left unchecked, these can disrupt critical business transactions and escalate quickly.

The result of proactive monitoring and automation?

Faster resolution. Reduced operational overhead. Greater confidence in business continuity.

Automation isn’t just about convenience, it’s about ensuring your integration platform stays resilient, responsive, and business-ready always.

Operational Benefits: Proactive Monitoring, Stronger Control, Audit-Ready Security

The modern integration environments demand more than basic health checks. They require intelligent monitoring that not only detects issues but actively helps to prevent business disruption.

Smarter Monitoring

Instead of relying solely on service instance status, monitoring now incorporates threshold-based detection and refined filtering. This enables you to identify abnormal service instance volumes, recurring failures, or performance bottlenecks before they escalate. It’s about spotting patterns early avoid the business disruption.

Smarter Monitoring

Instead of relying solely on service instance status, monitoring now incorporates threshold-based detection and refined filtering. This enables you to identify abnormal service instance volumes, recurring failures, or performance bottlenecks before they escalate. It’s about spotting patterns early avoid the business disruption.

Greater Control

With enhanced filtering capabilities and automated corrective actions, teams gain precise control over service instances. Whether it’s restarting host instances, stopping artifacts, or executing predefined scripts, actions can be triggered automatically when thresholds are breached. You define the rules. The system executes them consistently.

Confident Operations

Reduced manual intervention leads to fewer firefighting scenarios. Automated responses shorten resolution time and minimize business disruption. Teams can focus on optimization and innovation rather than repetitive operational tasks.

Security & Auditing

BizTalk360 enforces role-based access through user access policies, ensuring operational users can view and manage only the service instances relevant to them. It maintains a detailed audit trail of all service instance operations, tracks corrective actions taken during monitoring, and captures activities performed through the BizTalk Admin Console. This provides complete operational transparency, accountability, and governance across the environment.

Conclusion

The outcome is clear: improved stability, better visibility, and a monitoring strategy that actively supports business continuity not just reports on failures after they occur.

The latest version of BizTalk360 offers more features with more control on your BizTalk environments. Try out the BizTalk360 which provides reliable monitoring with lesser manual interaction and more control during the maintenance.

The post Enhanced Service Instance Monitoring with Intelligent Automation! appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

Let’s take a closer look at what’s new in BizTalk360 v11.7 and how it benefits your day-to-day operations.

New Features

Customized Data Monitoring Schedule

Process and Data Monitoring now support custom time-range scheduling, giving you complete control over when monitoring should run. You can schedule monitoring on specific days of the month, selected weeks, or define custom execution durations based on your operational needs. This enhanced scheduling experience is now fully aligned with the Receive Location scheduling options available in the BizTalk Admin Console.

Flexible Custom Scheduling Options

With the Custom scheduling option, you can fine-tune monitoring execution using flexible time ranges:

• All Months – Define recurring execution intervals in hours, days, or weeks—for example, run monitoring every 2 hours, every 2 days, or every 2 weeks.
• Specific Months – Choose a particular month and configure specific occurrences, such as the first and fourth weeks of January, or patterns like the last Friday of every month or a specific week.

Many businesses run critical batch jobs or validations only during specific periods, such as month-end or weekly business cycles. With Customized Data Monitoring Schedule, you can now run monitoring exactly during these windows—for example, on the 15th and 31st of the month or only during the first week—ensuring that checks are timely, relevant, and free from unnecessary monitoring overhead.

Ignore BHM Known Issue for Monitoring

In many BizTalk environments, certain health check errors/ warnings are known and accepted due to design decisions or business constraints. However, these known findings continue to appear in reports and trigger repeated alerts, creating alert fatigue for operations teams.

Recurring health check findings can now be marked as Known Issues. Once marked, these issues are automatically excluded from threshold monitoring and no longer trigger repeated alert notifications.

Role-Based Control for Monitoring

Role-based access control is enhanced for monitoring features. Access can be defined based on roles such as BizTalk Administrator, SQL Administrator, or Operator, ensuring users can view and manage only what’s relevant to their responsibilities.

In complex integration environments, different teams are responsible for different parts of the platform. Providing the unrestricted access to all monitoring features can lead to accidental changes, or security risks. Role-Based Control ensures the right level of visibility and control is granted to the right users.

Say, SQL administrators can focus exclusively on SQL Servers, instances, and jobs, while BizTalk administrators and operators access only BizTalk-specific monitoring.

Import & Export User Access Profiles

User Access Profiles can now be exported and imported, making it easy to back up access configurations and reuse them across environments.

When setting up Test or Production environments, teams can reuse the same role definitions from Development without manually recreating access policies—ensuring consistency and saving time.

Enhancements

Automated Tasks – PowerShell Script Path Support

Automated Tasks now support referencing external PowerShell script file paths, enabling centralized script management. Teams can reuse the same scripts across BizTalk360 and external automation tools such as Azure DevOps, reducing duplication and simplifying maintenance.

Say, Organizations using shared PowerShell scripts for maintenance or recovery can now manage scripts from a single location, ensuring consistency across automated tasks and CI/CD pipelines.

Auto correct Enhancements

Audit – AutoCorrect actions are now audited along with the associated alarm name, providing better traceability and audit clarity.

Notification – Users can also control when AutoCorrect notifications should trigger —only for successful actions, only when all retry attempts fail, or for both success and failed attempts.

BAM Related Activity Preview

Users can now preview the content of related BAM activities before downloading the associated documents.

This allows users to quickly validate BAM data and download only what’s relevant, saving time and reducing unnecessary downloads.

Enriched Filter capability

Filtering and search capabilities are enhanced to provide more fine-grained control for managing and analyzing data.

• Users can now use advanced operators such as Not Equals and Contains while searching for artifacts
• In the Advanced Event Viewer, multiple values can be specified within a single filter, such as multiple sources, categories, or computers
• Additionally, in ESB Data Monitoring, the Service Name can now be filtered using the Contains operator for more flexible and precise searching

Default Alarm in Monitoring Dashboard

Users can now set a default alarm view in the Monitoring Dashboard, ensuring the most critical alarms are displayed first based on individual preferences.

For example, Administrators responsible for system health can prioritize health-related alarms, while other users focus on process-specific alarms.

Azure Service Bus Topics Monitoring

Added new metrics such as Throttling Requests, Completed Messages, and throughput indicators for deeper visibility.

Clone Dashboard

Analytics dashboards can now be cloned along with their widget configurations, including the ability to copy custom widgets making dashboard reuse faster and easier.

Like this user can also clone ESB and EDI dashboard and the widgets

Schedule Maintenance for multiple BizTalk environments

BizTalk360 now supports a common maintenance schedule across all environments, with system maintenance status clearly visible on the landing page.

Conclusion

BizTalk360 v11.7 delivers smarter monitoring, and greater operational control, empowering integration teams to manage complex BizTalk environments with clarity and confidence.

Upgrade to BizTalk360 v11.7 now and experience a more focused, efficient, and reliable way to monitor and manage your BizTalk environment.

The post BizTalk360 v11.7 Release: Smarter Monitoring, Reduced Noise, Greater Control appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

• Challenges with manually executing BHM-recommended maintenance tasks
• How BizTalk360 automates BHM maintenance using Automated Tasks
• Using predefined templates to simplify BHM maintenance task configuration
• Scheduled execution for routine BizTalk maintenance activities
• Auto-triggering maintenance tasks based on BHM Health Check recommendations
• Improved visibility into recommended, triggered, and executed maintenance tasks

Overview

BizTalk Health Monitor (BHM) plays a key role in maintaining the health and stability of BizTalk Server environments. It continuously analyses the environment and identifies a wide range of potential issues such as Message box database growth, tracking data accumulation, orphaned instances, refcount inconsistencies, and performance-related configuration gaps.

Based on this analysis, BHM generates detailed health check reports and recommends appropriate maintenance tasks to resolve the identified problems. These maintenance tasks are built using predefined SQL and WMI scripts that help administrators inspect, repair, optimize, or clean different components of the BizTalk environment.

Limitations in Executing BHM Maintenance Tasks

While BHM is effective at detecting issues and recommending corrective actions, executing those maintenance tasks remains a manual process. This leads to several limitations:

• No automatic triggering when issues occur

When BHM detects problems such as abnormal Message box database growth or orphaned tracking data, it can recommend the relevant cleanup or repair tasks, but it cannot automatically trigger them when those conditions are detected.

• Manual execution of recommended actions

Once a BHM health check report is generated, administrators must review the report, identify the suggested maintenance tasks, validate the required parameters, and execute the actions manually.

• No scheduling support for routine maintenance

Many maintenance tasks, such as purging tracking data or repairing orphaned records, are safe and beneficial when executed on a weekly or monthly basis as part of routine maintenance. However, BHM does not offer a mechanism to schedule the execution of these maintenance tasks.

This manual approach is time-consuming and difficult to manage, especially in large or dynamic environments where health checks run frequently.

With the introduction of BHM Maintenance Tasks integration in Automated Tasks, BizTalk360 addresses these challenges by bridging the gap between health check recommendations and execution.

In this blog, we will explore how BizTalk360 simplifies BHM maintenance by automating recommended actions and walk through the configuration steps.

BHM Maintenance Integration with Automated Tasks

BizTalk360 Automated Tasks is designed to reduce manual effort by allowing users to automate routine and corrective actions across BizTalk environments. It allows you to define tasks, configure schedules, and execute actions automatically or on demand, while also providing execution history and notifications for better visibility.

To simplify task creation, BizTalk360 offers predefined templates. These templates act as ready-to-use building blocks, enabling administrators to quickly configure commonly used automation scenarios without starting from scratch

Starting with BizTalk360 v11.6, we are happy to introduce a new predefined template:
BHM Maintenance Integration. This template brings BHM maintenance actions directly into Automated Tasks. It includes a comprehensive set of predefined SQL-based maintenance tasks that align with the recommendations generated by BizTalk Health Monitor.

These tasks are grouped into four logical categories:

• Performance
• Manage
• Delete
• Purge

Each category contains relevant SQL scripts designed to perform specific BizTalk database maintenance and optimization operations, such as repairing inconsistencies, improving performance settings, cleaning up orphaned data, and purging obsolete records.

Creating a BHM Maintenance Automated Task

Let’s see how to create a BHM Maintenance task in BizTalk360:

• Navigate to Administration → Automated Tasks
• Click Create from Predefined Template
• Select BHM Maintenance Integration
• Choose the Task Type (Performance, Manage, Delete, or Purge)
• Select the required maintenance task from the list.

The parameter values are automatically populated based on the connected BizTalk environment. If needed, users can modify these values to suit their environment or operational requirements.

Next, configure the schedule, retry behaviour, and notification settings.

Note: Hovering over the info icons near the Script and Parameters sections explains what the script does and displays detailed information about each parameter. This ensures users understand the impact of the task before execution.

Automated Execution of BHM Maintenance Tasks

BizTalk360 provides two flexible execution models for BHM Maintenance Tasks, allowing users to choose what best suits their operational needs.

Scheduled Execution

The first option is scheduled execution, where maintenance tasks are executed at predefined intervals. While creating a BHM Maintenance Task in Automated Tasks, users can configure a schedule to run the task periodically, such as weekly or monthly.

Once scheduled, BizTalk360 automatically executes the task at the configured time and sends notifications with the execution status and SQL output. This ensures consistent maintenance without manual effort.

Scheduled execution is ideal for maintenance tasks that are safe to run periodically and do not depend on real-time conditions.

Example: Repair Orphaned DTA Service Instances

In many BizTalk environments, orphaned DTA service instances can accumulate over time due to unexpected failures or interruptions. These records are not cleaned up by the DTA Archive Purge job and can slowly increase the size of the tracking database.

Instead of waiting for the issue to be detected repeatedly in Health Check reports, administrators can schedule the Repair Orphaned DTA Service Instances task to run weekly or monthly using BizTalk360 Automated Tasks. This ensures orphaned records are consistently prepared for cleanup without manual intervention, keeping the tracking database healthy as part of regular maintenance.

Once the task is executed, the notification includes the SQL output returned by the task, giving clear visibility into what was executed and the outcome.

Auto-Trigger Based on Health Check Recommendations

The second and more dynamic option is auto-triggered execution, which is driven by BizTalk Health Monitor reports. During each run of health check profiles, BHM analyses the environment and recommends maintenance tasks based on detected issues.

BizTalk360 extends this capability by converting those recommendations into automated actions. When a recommended maintenance task is enabled for auto-trigger, BizTalk360 automatically executes the corresponding Automated Task as soon as it appears in the latest Health Check report.

To enable auto-trigger execution, ensure the following configuration is in place:

• Under Environment Settings > General > BizTalk Health Monitor, verify that the Health Check Profile is scheduled for execution.
• Open the health check profile under BHM Profiles.
• Enable Automated Action (Execute recommended tasks from latest report).
• Select the BHM maintenance tasks that are safe to auto-trigger when recommended.

For environments where all maintenance tasks are considered safe to execute automatically, users can enable Toggle to consider all available BHM maintenance tasks. This avoids the need to manually select individual tasks.

To understand this better, let’s look at a scenario involving failed tracking data

In high-throughput BizTalk environments, message processing failures can gradually lead to an accumulation of failed tracking records in the DTA or BAM databases. Over time, these records can impact tracking performance, slow down reporting, and increase database size without adding operational value.

During a Health Check run, BHM evaluates the state of tracking databases and identifies abnormal growth in failed tracking data. When such a condition is detected, BHM recommends purging outdated or excessive failed tracking records to restore optimal database health.

With BHM Maintenance Tasks integrated into BizTalk360 Automated Tasks, this recommendation no longer requires manual follow-up. If the corresponding maintenance task is enabled for automated action, BizTalk360 automatically executes the purge operation as soon as it appears in the latest Health Check report. This ensures tracking databases remain lean and responsive, while administrators stay informed through execution notifications and detailed results.

How BHM recommendations are mapped to Automated Tasks

BizTalk360 currently supports a predefined set of 20 BHM maintenance tasks. Each of these tasks has a unique identifier and name, and the same identifiers are used by BHM when it recommends maintenance actions in a Health Check report.

When a Health Check runs, BHM generates a list of proposed maintenance tasks based on the issues it detects. BizTalk360 compares these proposed tasks with the configured BHM Maintenance Automated Tasks. If a matching task is found and it is enabled for auto-trigger, BizTalk360 automatically executes the corresponding Automated Task.

Example mapping from BHM Report to BizTalk360 Automated Tasks

Visibility into Proposed and Triggered Tasks

After a Health Check report is generated, administrators can view proposed and executed maintenance tasks by navigating to:

Administration > BizTalk Health Monitor > Select Profile > Maintenance Tasks tab.

This view clearly shows:

• Which maintenance tasks were recommended by the BHM report
• Whether the task was triggered automatically by BizTalk360
• If auto-triggered, then the corresponding Automated Task name
• The reason if a task was not triggered

Users can also review historical recommendations and executions by selecting different report timestamps from the dropdown, providing complete visibility into past maintenance actions.

Conclusion

Maintaining a healthy BizTalk environment requires more than just identifying issues. The real challenge lies in acting on those insights at the right time, in the right way, and without unnecessary manual effort. By integrating BHM Maintenance Tasks with BizTalk360 Automated Tasks, this gap is effectively closed.

We hope these enhancements to BHM maintenance automation contribute significantly to your overall operational efficiency and business value.

To know more about the BizTalk360 features, try out the free trial or book a demo.

The post Turn BHM Recommendations into Automated Actions with BizTalk360 appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

Every release, every enhancement, and every optimization delivered throughout the year had a single purpose: to reduce operational noise and give integration teams greater control, clarity, and confidence. We want our BizTalk360 users to operate their BizTalk environment with minimal manual intervention.

2025 marked a meaningful step forward, not just in features, but in how BizTalk operations are automated, monitored, and optimized.

Let’s look back at what made this year impactful.

A Year of Consistent Delivery:

Throughout 2025, BizTalk360 delivered multiple quarterly releases, each focused on strengthening automation, refining monitoring depth, enhancing analytics, and improving platform stability without disrupting existing environments.

Quarterly Releases

• v11.3 – 3 New Features, 17 Improvements
• v11.4 – 2 New Features, 16 Improvements
• v11.5 – 19 Improvements
• v11.6 – 4 New Features, 13 Improvements

The Year of Automation: From Alerting to Self-Healing Systems

Automation was our primary focus in 2025. We moved BizTalk360 beyond alerting toward intelligent, self-healing operations.

BHM Maintenance Automation

Maintaining a healthy BizTalk environment is critical, especially as message volumes and integration complexity grow. Database growth, inactive service instances, and accumulated tracking data can quickly impact performance if not addressed proactively.

With the new BHM Automated Task capability, BizTalk360 now automates the execution of maintenance actions recommended by the latest BHM reports. Using predefined SQL templates, the platform can automatically perform:

• MessageBox cleanup
• DTA database purging
• Reindexing and performance optimization

Automated Server Recovery: Minimizing Downtime

Downtime directly affects business continuity, particularly when BizTalk or SQL servers become unavailable.

Previously, BizTalk360 alerted administrators when a server went offline, but recovery still required manual action.

Now with Server Availability Automated Tasks, BizTalk360 can now automatically perform recovery actions such as:

• Restarting critical services
• Executing PowerShell scripts
• Clearing temporary files

These actions are triggered the moment a server is detected as unavailable—helping teams reduce downtime and restore services faster without manual intervention.

Reporting

Data is only valuable when it’s accessible and actionable. BizTalk360 enhanced reporting to help teams move from raw metrics to meaningful insights.

EDI & BAM Dashboard Reporting

Users can now create custom EDI and BAM dashboards and include them directly in scheduled reports. With dynamic, interactive widgets, teams gain continuous visibility into:

• Transaction volumes and message flow
• Failed EDI batches and acknowledgment status
• Business process health and trends

Daily scheduled reports provide summarized insights that help operations teams proactively address issues—before they impact business operations.

EDI Dashboard: Complete B2B Visibility

The EDI Dashboard delivers a comprehensive view of B2B message exchanges between trading partners.

• Total interchanges processed
• Failed or delayed transactions
• Partner-wise message flow
• Batch status overview

These insights help teams identify bottlenecks, prioritize corrective actions, and ensure timely business document exchange.

BAM Dashboard: Real-Time Business Process Monitoring

The BAM Dashboard provides real-time visibility into key business processes tracked using BizTalk BAM activities.

With configurable widgets and advanced filtering, business users and analysts can monitor:

• Average order processing times
• Activity summaries by status (active, completed, failed)

This enables faster identification of workflow inefficiencies and data-driven process optimization.

Monitoring That Goes Deeper and Smarter

Monitoring enhancements in 2025 focused on precision, prevention, and faster recovery.

Enhanced Service Instance Monitoring

Administrators can now apply advanced filters such as:

• Service Name
• Host Name
• Error Code or Description

Thresholds can be defined to raise alerts when suspended instance counts exceed expected limits. These alerts can also trigger Automated Tasks, such as resuming instances or restarting services restoring message flow automatically.

Secure Office 365 Monitoring with OAuth

As Microsoft deprecated SMTP basic authentication, BizTalk360 introduced support for Office 365 SMTP OAuth (Modern Authentication).

Using the built-in SMTP Authenticator Tool, administrators can easily configure secure authentication, ensuring alerts and scheduled reports are delivered reliably and securely.

ActiveMQ Monitoring: Real-Time Queue Visibility

ActiveMQ plays a critical role in modern integration architectures. BizTalk360 now provides real-time monitoring of ActiveMQ queues, including metrics such as:

• Enqueued and dequeued message counts
• Message size
• Expired messages
• Consumer and producer counts

Alerts are triggered instantly when thresholds or expected states are violated, allowing teams to act before backlogs impact downstream systems.

IBM MQ – Channels and Queues Metrics monitoring

Monitoring capabilities were further expanded to include threshold-based monitoring of IBM MQ queues and channels,

• Queue metrics: Messages In, Messages Out, Uncommitted Messages, Open Input Handles, Open Output Handles .Which provide deep visibility into queue health and processing behaviour.
• Channel metrics: Messages Sent/Received, Buffers Sent, Buffers Received, Bytes Sent, Bytes Received.

Platform Stability & Performance Improvements

While features took the spotlight, 2025 also delivered important improvements behind the scenes:

• Optimized memory management to improve service efficiency
• Improved handling of unreachable or unavailable servers for faster data collection
• Continued artifact monitoring even after orphaned artifacts are detected

These enhancements ensure BizTalk360 remains stable, resilient, and reliable—even in complex and unpredictable environments.

BizTalk360 is now fully compatible with BizTalk Server 2020 CU7, ensuring customers remain aligned with the latest supported Microsoft platform updates.

Technology stack upgrade – To support long-term stability, BizTalk360 client technology stack was also upgraded. This includes Angular 19.2.x, the latest versions of Kendo UI and GoJS, an updated Chromium browser, and the introduction of Playwright to enable more reliable and efficient browser-based report generation.

API Security – Several API security enhancements were implemented to further strengthen platform stability and resilience. Input validation and access controls were tightened to prevent unauthorized access and unsafe operations. Sensitive actions are now restricted to authorized users only, reducing security risks. These improvements ensure a more secure and reliable experience across all environments.

Looking Ahead

2025 was a year of meaningful progress, With automation at the core, deeper monitoring, and actionable analytics, BizTalk360 continues to evolve to meet the real-world needs of integration teams.

Thank you to our customers, partners, and community for being part of this journey. Your feedback continues to shape our roadmap, and we look forward to bringing you even more powerful capabilities in the year ahead.

The post 2025 Year in Review: A Year of Automation, Stability, and Smarter BizTalk Operations appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

BizTalk360 provides a centralized platform with real-time visibility into EDI messages, interchanges, and transactions. Features like EDI Queries, help users to easily view interchange and acknowledgment statuses and drill down into transaction sets and batch reports from a single interface. With intuitive dashboards and role-based access, BizTalk360 helps business users to quickly identify issues and manage EDI operations efficiently.

Overview of EDI Custom Dashboards in BizTalk360

The EDI Custom Widget in BizTalk360 allows users to monitor EDI transactions in a personalized dashboard. It provides options to filter data based on partners, agreements, and transaction types. Users can track transaction statuses, view errors, and monitor in real time. The widget supports multiple visualization formats, like grids and charts, for easy analysis.

Use Case:

A logistics and supply chain company exchanges EDI documents such as shipment details, delivery confirmations, and invoices with multiple trading partners. During peak business hours, several shipment acknowledgments start failing, which could lead to delivery delays and SLA breaches. To gain better visibility, the operations team can create an EDI Custom Widget in BizTalk360 and configure it using the Interchange/ACK Status query type, select the relevant partners, and set a short plot frequency for near real-time monitoring. The widget clearly highlights a spike in failed acknowledgments for a specific partner. By drilling down from the widget, the team can identify a batching issue caused by an agreement misconfiguration. They can quickly fix the configuration, reprocess the failed messages, and restore the EDI flow. This real-time visibility through custom widgets helps the team respond faster, reduce operational impact, and maintain smooth partner communication.

Configuring predefined and custom widgets in the EDI Dashboard

BizTalk360 dashboards help you monitor EDI transactions effectively in one place. You can add a new dashboard and manage it by updating, deleting, or customizing it as needed. Predefined EDI widgets provide instant insights into common metrics like transaction status, errors, and volumes. Custom EDI widgets allow you to filter data by partners, agreements, or document types for more focused monitoring. Together, these widgets display real-time trends in grids or charts, helping teams quickly spot issues.

Integrate EDI Dashboard with Reporting

To receive updates at regular intervals, these dashboards can be mapped with reporting. Users can simply choose the EDI dashboard and include it in a report. During execution, the report retrieves all necessary EDI metrics and charts automatically, eliminating the need for manual action. The completed report is then emailed to the configured recipients for quick access. This helps teams stay updated without opening the dashboard manually.

For example, a retail team can schedule daily EDI reports to monitor purchase order and invoice transactions. These daily reports help the team quickly verify whether all expected documents were received, processed, and acknowledged successfully. If any transactions fail or get delayed, the team can identify the issue early in the day and take immediate action, such as reprocessing messages or coordinating with trading partners, before it impacts the orders. This proactive monitoring helps keep retail operations running smoothly.

Managing Role-Based Access for the EDI Dashboard

In BizTalk360, access to the EDI Dashboard is managed through the User Access Policy (UAP), which ensures only authorized users can view or modify it. Using UAP, admins can grant specific users permission to access the dashboard, customize widgets, or export EDI data when required. The admin user retains complete control, including the ability to add, remove, or update widgets and manage the entire dashboard configuration. This setup provides a secure environment while giving flexibility to team members based on their roles. It also ensures that sensitive EDI information is visible only to users who truly need it for their daily tasks.

For example, A compliance officer needs monthly EDI data for audit reviews, so the admin gives them permission to export the EDI Dashboard. The officer can download the required information but cannot edit widgets or change dashboard settings. The admin retains full control to manage and secure the dashboard. This ensures the compliance team gets the data they need while keeping the dashboard protected.

Exporting and importing the EDI Dashboard configuration

EDI Dashboard can be exported and imported to another environment or server, making it easy to replicate dashboard setups across multiple instances. Users can export the dashboard configuration, including widgets and filters, and then import it into another BizTalk360 environment without recreating it from scratch. This feature saves time and ensures consistency across development, testing, and production servers.

Conclusion

The EDI Dashboard in BizTalk360 makes monitoring and managing EDI transactions simple and efficient. Predefined and custom widgets provide real-time insights, while scheduled reports keep the team updated automatically. UAP-based access ensures security, and export/import features maintain consistency across environments. Overall, BizTalk360 helps organizations stay on top of EDI operations and resolve issues quickly from a single dashboard.

To know more about the BizTalk360 features, try out the free trial or book a demo.

The post Optimizing EDI Visibility with Customizable Dashboards in BizTalk360 appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.

• Benefits of BizTalk Server 2020 CU7
• BizTalk Server 2020 CU7 upgrade considerations
• Real-world validation checklist before upgrade
• BizTalk360 Compatibility to BizTalk Server CU7 Pack

Benefits of BizTalk Server 2020 CU7

Microsoft BizTalk Server 2020 CU7 is a major update especially for organizations looking to modernize their BizTalk infrastructure and development workflows. This cumulative update introduces support for Visual Studio 2022 and resolves issues identified after the original BizTalk Server 2020 release.

• Support for modern platforms: CU7 adds official support for newer Microsoft platforms.
• Visual Studio 2022
• Windows Server 2022
• SQL Server 2022

This means you can run BizTalk 2020 and develop BizTalk projects on up-to-date technology stack without risking unsupported-platform issues.


• All cumulative fixes up to date: As with any cumulative update, CU7 rolls up all previously released hotfixes (functional and security) since last CU. That consolidates fixes, reduces fragmentation, and ensures you’re on the latest stable baseline.
• Modernized development experience: By enabling VS 2022 support (via the required BizTalk VS 2022 extension), CU7 lets development teams move their development environment forward rather than being tied to older Visual Studio versions. This is an advantage if you want to standardize on modern IDEs, benefit from newer Visual Studio capabilities, and align with other .NET frameworks.
• Future-proofing for infrastructure: Since newer operating systems and SQL Server versions are supported, CU7 helps ensure your BizTalk deployments remain compatible with evolving infrastructure — OS upgrades, database upgrades, and broader environment refreshes. This reduces technical debt and avoids being stuck on older unsupported OS/DB versions.
• Unified update path: Because CUs are cumulative, installing CU7 gives you a clean, consolidated update path — fewer separate patches, fewer bit-versions to track, easier maintenance. This simplifies upgrade planning for admins
• CU7 is Optional but enabling: Microsoft explicitly positions CU7 as optional, you don’t have to apply it unless you need VS 2022 or the new platform support. This flexibility allows teams to choose their upgrade timeline instead of being forced into immediate deployment.

BizTalk Server 2020 CU7 – Upgrade Considerations Before You Touch Production

CU7 isn’t your typical “apply patch and carry on” update. It introduces structural changes that affect BizTalk groups, developer tooling, adapters, and compatibility across your ecosystem. Before moving forward, consider below key areas.

1. Re-creation of BizTalk Groups

• CU7 requires you to recreate BizTalk groups for existing BizTalk Server instances. You must:
1. Remove the existing BizTalk servers from the old group
2. Uninstall the existing BizTalk Server
3. Install BizTalk Server 2020 with CU7
4. Create (or join) a new BizTalk group
• Cannot have BizTalk servers in the same group at different CU levels. All instances in a group must be at the same CU.

Impact: This is a disruptive change. You’re effectively standing up a brand-new BizTalk group, with all the downtime, reconfiguration effort, and risk of misconfiguration that entails. Careful planning and a dedicated test environment aren’t optional, they’re mandatory.

2. BizTalk Developer Tools & Project Rebuild Requirements

CU7 pushes development to Visual Studio 2022, and everything must be rebuilt.

• After installing CU7, BizTalk solutions / projects must be reloaded and rebuilt in Visual Studio 2022.
• Deployment of these rebuilt solutions is only supported to BizTalk instances that have CU7 installed.
• If you have the BizTalk Developer Tools installed, you must also install the BizTalk Server Visual Studio 2022 extension (version 3.14.2.0 or later).

Impact: Development teams must move to VS2022, recompile all BizTalk projects, and align deployment pipelines with CU7 environments. This requires coordination across dev, QA, and deployment teams.

3. Deprecated / Incompatible Extensions

The older BizTalk Visual Studio extension for VS 2019 stops working after applying CU7. It must be uninstalled.

For ESB Itinerary Designer, you need the VS 2022 extension version (same as above) to continue working.

Impact: If teams are still using VS 2019 for development, they’ll lose tooling support. Also, ESB-based workflows will need the updated extension installed.

4. Adapter Reinstallation

Adapters for Enterprise Applications, Accelerators, and BizTalk ESB Toolkit need to be reinstalled to be compatible post-CU7.

MQSeries (MQ) adapter

Microsoft warns that MQSAgent.dll on the IBM MQ server must be the same CU level as BizTalk. Historically, mismatched MQSAgent versions produce intermittent failures and performance degradation.

Action: Coordinate with MQ admins to upgrade MQSAgent on MQ servers to the same CU and test end-to-end.

Impact: Any LOB (Line-of-Business) integration that uses these adapters will need adapter-level work and validation again.

5. SQL / Binding Redirects

If you’re using SQL Server 2022, you need to apply binding redirects.

For MQSeries adapter, you must update the MQSAgent.dll on the IBM WebSphere MQ server to match the BizTalk CU level; mismatched versions can lead to performance issues.

Impact: If your stack already has SQL 2022 or if you integrate with IBM MQ, these version and DLL compatibility considerations are critical.

Real-world validation checklist before upgrade

Before moving CU7 into production, validate the following to avoid any impacts:

1. Full backup: BizTalk DBs, SSO master secret, certificates, host / binding exports. (Non-negotiable.)
2. Replica test environment: Recreate your planned CU7 install in a full staging environment that mirrors production topology (hosts, adapters, MQ, SSO, SQL versions).
3. MQ parity: Ensure MQSAgent.dll on IBM MQ servers is upgraded to the same CU level before bringing production BizTalk-MQ integration live. Run known test scenarios and concurrency tests.
4. Adapter reinstallation& configuration compare: Reinstall enterprise/ESB/accelerator adapters, then compare config and bindings with pre-upgrade snapshots.
5. JSON regression tests: Run sample messages that use JSON maps/encoders and verify boolean types and other formatting unchanged. If you see regression, check Microsoft.BizTalk.JsonExtension.dll versions.
6. SFTP (WinSCP) validation: Confirm SFTP adapter functions with your WinSCP version; run file transfer tests and error conditions. WinSCP – Free SFTP and FTP client
7. Build pipeline update: Move builds to VS2022 + new BizTalk VS extension; validate CI agents, signed assemblies, and deployment tasks.
8. SQL 2022 binding redirects: If DB tier is SQL 2022, ensure required binding redirects are configured as documented.
9. Rollback plan test: Practice rollback steps and validate DLL versions are restored properly.

BizTalk360 Compatibility to BizTalk Server CU7 Pack

As BizTalk360 is one stop solution to monitor and administrate your BizTalk environments. It’s now aligned and made compatible to support BizTalk Server 2020 CU7!

Conclusion

Cautious: Defer CU7 until you have a clean plan for VS2022, adapter reinstallation, MQ parity, and a large test plan. CU7 is optional — don’t rush it unless you need VS2022.

Planning to adopt CU7 now: treat it like a platform migration. Test everything end-to-end, coordinate MQ/admin teams, and open a Microsoft Support case early. Expect a non-trivial amount of work (group recreation planning, rebuilds, adapter re-installs).

To know more about the BizTalk360 features, try out the free trial or book a demo.

The post BizTalk Server 2020 CU7: Strategic Overview of Platform Alignment and Impact Analysis appeared first on BizTalk Server Monitoring & Management Solution | BizTalk360.