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.127 votes
Thanks for the feedback. We are looking to address this soon.
We are working on enabling this. Thanks for your feedback.
For dev/test scenarios, we really need to be able to stop/suspend a BizTalk Service container.
Now we have two options:
- Pay a lot, to not lose our instance
- Delete and recreate our service everytime again, when we need to give a demo or do dev. And then we have to upload everything, add all our partners, etc. (or use scripted deployment for that)
I expect a premium cloud service to have this option by default. Especially when economics is used as a sales argument in cloud.62 votes
Thanks for the feedback. We will review this requirement.
Although BizTalk services is a new feature of Windows Azure I expected more managebility in the management portal.
Here are some small examples -
- No start/stop on a source
- No enable/disable of a destination
- You can't double click on a tracking log
I'm currently using a tool by Steef Jan that enables me to do more with a Visual Studio Add-in than I can do with the portal... (http://social.technet.microsoft.com/wiki/contents/articles/22075.windows-azure-biztalk-service-explorer.aspx)31 votes
Thanks for your feedback. We are working on improvements to the management portal. More updates on 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.15 votes
We are working on enabling this functionality. Thanks for your feedback.
Currently the UI in VS is perfect, untill you switch your VS theme to black and everything is unusable. Can this be supported as well please?9 votes
Thanks for the feedback. We will review your ask
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.8 votes
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 result of an EDI send pipeline has a content-type of "application/xml; charset=utf-8" while this is not the case.7 votes
We will double check on this. 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.5 votes
Thanks for the feedback. We will review this ask and get back to you.
- Don't see your idea?