Messages are in Active status over days. Which is wasting resources. BizTalk 360 should be able to monitor and alert, if a message has been in Active in Running Service Instance for over 3 hours

Within Biztalk Administration Console, when viewing a suspended instance you can right click and "Find Failed Message" This is key to us as often we need to remove the failed message and resume the rest in the queue. (Terminate kills all messages and resume just resends the same failed one, resulting in them being suspended again)

For analysis I regularly query the Subscriptions for Orchestrations and/or Send Ports. Unfortunately this is not possible with BizTalk360, so I would like to have that capability in BizTalk360.

Currently Via BizTalk 360 its not possible to drill down, to get example the XML message or look at the details. It only gives an Overview.

From time to time I need to save Tracked messages. When the messages are small, it is easy to select and copy the XML of those messages in the Graphical Flow module. But in case messages are larger than a couple KB's, it is tough to impossible (msgs over 50000 chars got truncated) to select and copy that XML.

For that reason I would like to have a button to be able to save Tracked messages.

For analysis purposes I often use the Orchestration Debugger from the Administration Console. Unfortunately this is not available in BizTalk360, so I would like to have that functionality, so I'm not forced to connect to the Admin Console.

When pinning a Flow in the Analytics DashBoard, it could be very good to have a graph with the performances of the flow (average response time, number of messages, ...) like the graphs displayed in front of the flow in the Analytics web pages.

Adding ability to configure folders where important log files (like IIS, Log4Net, Custom etc) are present in the server and ability to view them directly in the BizTalk360 web interface. This will avoid people logging into the server or setting up user rights for each individual users in the server.

When you have a suspended message and go into:
"Service Properties -> Error Information"
in order to see the error message.
It would be handy if the path to a server /folder could be a clickable link in the "Error Description"