As Visual Studio 2013 become RTM and Azure SDK 2.2 supports it, you should support it also in Windows Azure BizTalk Services SDK since it currently only support VS2012
It is really necessary ASAP.170 votes
Thanks for the feedback. We are looking to address this soon.
Since February it is also possible to do EDI integrations in Windows Azure BizTalk Services, awesome!
I'd love to have some extended functionality on the Transport part. Notice that I'm sending to a Service Bus but unfortunately there is no support for property promotion in my Brokered message.
Would be very cool to see functionality added in the future.16 votes
We are working on enabling this functionality. Thanks for your feedback.
Basically reusable integration artifacts, aimed at speeding time to deployment of the most common SaaS integration scenarios, they are like the BizTalk accelerators for SWIFT & healthcare.
I have seen support for these in Dell Boomi & IBM Castiron for a while, reviewing the recent magic quadrant for IPAAS several competing platforms like SAP Hana Cloud Integration (HCI) & Skyvva are making significant improvements in this space.
If Microsoft were not to deliver cloudstreams then perhaps creating a marketplace/framework for partners to develop these and make them easily consumable by integration customers from Azure maybe an option.13 votes
Thanks for the feedback. We will review this ask and get back to you.
To connect MABS with a Azure SQL you need to host BAS on a additional (on-premise) server, which makes no sense for me. Please consider the possibility to host BAS e.g. on the MABS unit in such cloud-to-cloud cases.
For more information see this thread:
Thanks for the feedback. We will review and get back on this.
The Test Map function is already quite usable, but real debugging capacities would be nice. Additionally, what I miss at the moment is the possibility to set the Test Map Output File to native/flatfile. At runtime the mapping and conversion from XML to Flatfile works fine, but I can't test my mapping at development, because the Output File is already XML.10 votes
The result of an EDI send pipeline has a content-type of "application/xml; charset=utf-8" while this is not the case.8 votes
We will double check on this. Thanks for your feedback.
similar to the prepackaged integration workflows suggestion, at minimum it would be good to have the SWIFT schema's available in the service.2 votes
Thanks for your response. We are looking into this ask and will get back to you.
- Don't see your idea?