Sometimes I need to extract several thousand messages from tracking database (DTA). In BizTalk360 there is currently a limitation of 500 messages and 10mb file size (zip)

Would like the option to select several host instances and have the option to only have one active.
For instance in a non clustered BizTalk group to be able to have polling instances only active on of the machines in the bt group

I have 5 feature enhancements which are requirements from a lot of customers:
1. Ability to send an alert(email) per error. 1 alert for 1 error.
2. Ability to add message context or content to the alert email, for example “order number”.
3. Trigger the alert directly when the error occurs, (near)real-time alerting
4. Ability to choose any color in the custom email template.
5. Ability to add a company logo in the custom email template.

When UP alert is triggered and I have multiple down alerts I have to wonder what UP is related to DOWN one
It would be easier to see what was wrong in UP alert not the current healthy status of everything

The certificate used for https or AS2 has a validity date, after this date they are no more valid and the process stops. Would be nice if you could implemant a new feature the send an alarm when this date is getting closer.

We have a single monitor on a wall near our BizTalk DevOps team. This is used to display dashboards for Azure, VSTS and BizTalk360.

We use the “Tab Carousel” add-in for Chrome to rotate the pages.

We have the following problems rotating BizTalk360 Monitoring dashboards:
- We cannot display the "full screen" version.
- Zoom settings are lost.
- Dashboard 2 will refresh back to Dashboard 1 (first in drop down list).

The ability to add all SQL servers from Always On cluster for monitoring and use in the Advanced Event Viewer.

Supporting nsoftware sftp
Supporting Blogical Shared Adapters Sftp

It would be good if BizTalk360 was integrated with the BizTalk Best Practices Analyser:
https://www.microsoft.com/en-us/download/details.aspx?id=43382&751be11f-ede8-5a0c-058c-2ee190a24fa6=True
- Schedule the running of scans.
- Store the history of scan reports (within specified purge settings).
- Store which "best practices" you want to ignore (with a justification specified).
- Alert if any "best practices" fail following a scheduled scan (that you don't want to ignore).

How do we import\export application bindings with Biztalk360?

This is a core BizTalk functionality often used by BizTalk developers, thus is expected by your customers be integrated in your product as a default.

Hi,
The FILE and FTP notification features are great :) But it should also be great to have the ability to monitor locations that are not used by BizTalk.
I have a use case where my customer use an other product than BizTalk for several flows and we want to use BizTalk360 to monitor these locations too. Today it is not possible.

Export to Excel only exports a maximum of 1000 rows.
We need many more than 1000 rows.
Had this worked, we could have used Excel filters and widths instead.
Suggestion : Add 10,000 rows to drop down box.

Allow for Queue names to be updated on IBM MQ monitors. This is due to the fact that the current monitoring can't monitor AQ's which our organization uses. with this change, I won't have to make changes to queues on BizTalk to look at the LQ's.

The V 8.5 has FTP monitoring but it does not work with FTPs configured with SSO affiliates.

Hi,
It could be great to display a tooltip under the "KB" icon in the MessageBox queries, just to display the title of the KB and also to do a quick access to the KB tab.

Our analyst and support team want to view the actual AS2 message contents sent and the MDN message contents received from Trading Partners.

Allow for monitoring of 3 or more SQL instances, or include disk monitoring of BT instance by default.

By Default you can't Monitor the BT Instance Disks (Monitoring> SQLServer Instances > BT Instance Name)

So you have to add it to Settings > Monitoring and Notification > SQL Servers for Monitoring

This only gives you a maximum of two

We have 3 SQL Instances relating to the BizTalk Environment including the BT one, so we have to choose to not monitor one of them.