Biztalk Services

This forum is closed
Biztalk Services is officially deprecated. End of Life for this service is is 5/31/18.
Please visit Logic Apps for building integrated solutions.

  1. Support Visual Studio 2013 in Windows Azure BizTalk Services SDK

    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.

    266 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  20 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add support for prepackaged integration flows (cloudstreams)

    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.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. It shouldn't be necessary to host BizTalk Adapter Service in cloud-to-cloud integration scenarios

    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:
    http://social.msdn.microsoft.com/Forums/en-US/456b51d5-dc5e-43c3-9169-4c4a2bcc03c3/is-it-necessary-to-host-the-biztalk-adapter-service-on-runtime-using-azure-sql?forum=azurebiztalksvcs

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Extend agreement functionality with property promotion on Transport

    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.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  Anurag Dalmia responded

    We are working on enabling this functionality. Thanks for your feedback.

  5. Improve Test Map capacities

    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.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Assembled EDI message has incorrect content-type

    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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add the SWIFT accelerator schema's

    similar to the prepackaged integration workflows suggestion, at minimum it would be good to have the SWIFT schema's available in the service.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. improve the help text

    After login in the azure dashboard we can create VM, DB, etc. Just before we click the "create button" there is a help text that is displayed.
    My suggestion is to improve this text.

    For example, calling:
    new -- app services -- biztalk service -- create
    will show the help text "create a new biztalk service".

    This text says nothing I don't already know. It is useless.
    Sure I can search online for what a biz talk service is, but it could be a URL to the proper Microsoft help page about the entity in question, in this case the…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Biztalk Log4Net

    Has anyone used log4net with Biztalk? We are currently looking into using it and are trying to access pros/cons, and whether or not it would meet our needs.
    I have used Log4Net with BizTalk (https://goo.gl/LLkGF8), but i will say that out of the box i ran into issues. Every call out of BizTalk results in the current orchestration getting dehydrated (serialized) so any type you use in BizTalk would have to be serializable and the log4net logger was not.
    If you absolutely have to use log4net there is a wrapper that Scott Colestock wrote Assuming you are not…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. BizTalk xpath extractor bug

    Received a 500 error when I'm trying to get the name of the root element
    using this xpath: "local-name(/*)"

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Lessen the time it takes to create a BizTalk service

    Its taken more than 12 hours to create a BizTalk service and it still hasn't accomplished what I wanted

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. portal.azure.com vs manage.windowsazure.com?

    When I select "create" for a new BizTalk Service on the portal, I am redirected to manage.windowsazure.com, even though when creating a new instance of, for example, a web service, I remain in the portal (as I would expect). Moreover, and maybe this is a bug rather than a feature request, when the BizTalk Service is successfully created, and I can see it in manage.windowsazure.com, it doesn't appear in the portal at all - it just says "no biztalk services to display". Do I really have to keep switching to the manage pages to handle BizTalk stuff?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

Biztalk Services

Categories

Feedback and Knowledge Base