I would encourage everyone to now use this page instead to submit their feedback on BizTalk Server : https://biztalk.uservoice.com



As Microsoft Connect is not currently accepting feedback for Microsoft BizTalk Server, this page is setup for raising suggestions for improvements to the product.

Other Resources

Administration

  • API App Addins. See here.
  • Better (easier) "no downtime deployment" story than the side-by-side approach (see chapter 2 Pro BizTalk 2009). 
  • The BizTalk Best Practice Analyser for the warning "Thread pool setting of host instance {0} of host {1} does not exist." is looking in the wrong place for this configuration setting.  This setting is no longer stored in the registry but in the [BizTalkMgmtDb].[dbo].[adm_HostInstanceSetting] database table.  See here.

Platform

  • Visual Studio 2017 support for BizTalk 2016 projects.  There are lots of improvements that would be great for BizTalk developers to take advantage of.
  • Microsoft assistance to help the BizTalk Deployment Framework. I suspect there are many customers put off from upgrading to BizTalk Server 2016 until there is BTDF support for this version of the platform.   See here

Adapters

  • Wider support for SSO in out-of-the-box adapters - See here and here.
  • Registering extensions in the WCF-CustomIsolated adapter handler doesn't work. See here.
  • SB-Messaging - integration with Azure Key Vault so BizTalk can utilize rolling keys.
  • Provide out-of-the-box adapters for:
    • AMQP - see here
    • Azure Blob Storage
    • Azure File Storage

Pipelines

  • Do we really need the pipeline designer? - See here.

Pipeline Components

  • Json Encoder/Decoder should use newer version of Newtonsoft.Json with same PublicKeyToken. See here.

Schemas

  • Ability to consume/publish Swagger - See here.
  • Visual Studio support for Json Schemas similar to Xml Schemas (validate, generate instance, validate instance, etc).
  • Ability to suppress build warnings (e.g. "<Schema> - Target namespace is empty" when we are supplied a schema with no namespace).

Maps

  • Support for XSLT 2.0 (there is even a version 3.0 now).
  • Ability to suppress build warnings (e.g. "no incoming link, constant value, or default value").

BAM

  • See "BAM Pitfalls with BizTalk Server 2013" wiki article:
    • Make the BAM Add-In work with 64-bit versions of Excel.
    • Do not use BAM.xla which comes with BizTalk Server 2013
    • BAM Portal doesn’t like SQL Server in Mixed Authentication Mode
    • Use BAM Portal with Internet Explorer 10 in Compatibility Mode

ESB Toolkit

  • Export of itineraries to xml files as part of the project build - See here.

See Also

Another important place to find a huge amount of BizTalk related articles is the TechNet Wiki itself. The best entry point is BizTalk Server Resources on the TechNet Wiki.