What's New in BizTalk Server 2016

Read about what's new in BizTalk Server 2016.

New in BizTalk Server 2016

Feature	Description
Support for newer platforms	BizTalk Server 2016 adds support for the following Microsoft platforms: - Visual Studio 2015 - Windows Server 2016 - SQL Server 2016 - Office 2016 Hardware and Software Requirements for BizTalk Server 2016
Feature Pack 3	Includes Office 365 adapters to work with Email, Calendar and Contacts. Install the feature pack See what's included, and configure its features
Feature Pack 2	Improvements include closer integration with API Management, an Azure Event Hubs adapter, backup to Azure blob storage account, support for Service Bus partitions, and more. Install the feature pack See what's included, and configure its features
Feature Pack 1	Includes support for automatic deployment using VSTS, send tracking data to Azure Application Insights and Power BI, advanced scheduling options on receive locations, and more. Install the feature pack See what's included, and configure its features
SQL Server 2016 AlwaysOn Availability Groups	Support includes: - Using on-premises and in Microsoft Azure IaaS virtual machines - Using for production workloads - Provides a high available (HA) solution in Microsoft Azure High Availability using SQL Server AlwaysOn See distributed transactions for Always On AG for any SQL-specific requirements and features.
BizTalk Server Azure VMs in production	BizTalk Server Azure virtual machines are now fully supported for production environments. Using SQL Server 2016 AlwaysOn, a highly available solution is now possible. High Availability using SQL Server AlwaysOn
Logic App adapter	Connect to your Logic Apps hosted in Azure, and get access to all the connectors including Salesforce, SharePoint, CRM Online, and more. For example, you can receive an order in BizTalk Server, connect to your Logic App, and update Salesforce. Logic App adapter
File adapter	Connect to an Azure storage file share. You can receive files from the Azure file share, and send messages to an Azure file share. Configure the File adapter
FTP adapter	SYST command is no longer required. When you configure the FTP adapter on a receive location or send port, there is a property called FTP Server Type. Using this property, you choose the FTP server you want; which determines if SYST is required. As a result of this change, there are more "supported" FTP servers. Configuring the FTP adapter
SFTP adapter	SFTP adapter is re-engineered to use WinSCP to connect to SFTP; which allows support for more SFTP servers. Client-side logging and additional encryption ciphers are also new. SFTP adapter
Allow import of tracking settings	When importing a binding a file, you can choose to import (or not import) the tracking properties enabled on your orchestrations, send ports, and so on. This is a global setting (set at the Group level) so you can set this feature in your different environments. For example, you can import the existing tracking properties for your Development environments, and don't import the tracking properties for your Production environments. See BizTalk Settings Dashboard, Group Page in the UI guidance and developers API namespace reference.
Shared Access Signature (SAS)	You can use SAS authentication for the Service Bus connection with the BasicHttpRelay, NetTcpRelay, BasicHttp, and WebHttp adapters. WCF-BasicHttpRelay adapter WCF-NetTcpRelay adapter WCF-BasicHttp adapter WCF-WebHTTP adapter SB-Messaging adapter now includes the steps to get Access Control (ACS) values using PowerShell.
Ordered delivery on dynamic ports	Applies to the adapters that support ordered delivery on static send ports. You can enable the ordered delivery option in the BizTalk Administration console. How to Configure Transport Advanced Options for a Send Port Ordered Delivery of Messages
SHA-2 hash functions	SHA-2 is fully supported, including: BizTalk can consume SHA2-signed certificates across all of its components, including SSL messaging in the HTTPS, FTPS, POP3, and the WCF adapters Supports the following Advanced Encryption Standard (AES) exchange system for signature keys in AS2, RosettaNet, and the MIME/SMIME encoder: AES128 (default) AES192 AES256 Supports the following SHA2-based MIC calculations for AS2: SHA256 (default) SHA384 SHA512 Supports the following SHA2-based digest methods in RosettaNet: SHA256 (default) SHA384 SHA512 SHA1 certificates continue to work for backward compatibility Configuring Validation (AS2) Configuring Acknowledgements (MDNs) (AS2) How to Configure the MIME-SMIME Encoder Pipeline Component
Compile your maps	Choose to compile your maps using XslTransform or XslCompiledTransform Set map compilation and output settings
Schema window	In the BizTalk mapper, you add/replace a source schema and a destination schema. When you do this, the Type Picker window is now resizable. This change allows you to expand the window, and see the full name of your schema. How to resize the schema picker, and expand and collapse the schema trees
Adapters and Accelerators	Improvements and changes include: The SAP adapter supports classic RFC SDK, and the .NET Connector in the SAP binding properties. Install the SAP Connector for .NET, which is available at the SAP Service Marketplace (service.sap.com/connectors). During the install, be sure to select Install Assemblies to GAC. WCF-SAP adapter support for the SAP .NET Connector provides additional details. BizTalk Accelerator for HL7: The MLLP adapter on a receive location now supports the option to initiate an outbound connection to a remote LOB listener.
Import/export parties	Changes include: - The import and export option is separated from the Application. For example, you can export a party without exporting the application. You can import a party without importing the application. - Can choose which parties, business profiles, and agreements you want to import or export - Can continue to import/export the business-to-business artifacts as you do in BizTalk Server 2013 R2, BizTalk Server 2013, and BizTalk Server 2010. Use binding files to import or export
BizTalk Administration	In addition to a more modern look and feel, some additional changes include: - Configure the settings for multiple hosts/host instances simultaneously. For example, you can set the .NET CLR settings for multiple host instances simultaneously. - Use the new Search feature to filter and find artifacts in your application, such as schemas, resources, and more. - When troubleshooting suspended messages, you can save multiple suspended messages simultaneously to a file. Using the BizTalk Server Administration console
Additional updates	The BizTalk Accelerator for HL7 (BTAHL7) starts the connection to a Line of Business server (LOB), and pushes messages over the connection. The LOB waits for the connection, and then sends the messages. In previous BizTalk Server versions, the HL7 MLLP receive adapter waits for the LOB server to connect to HL7, and then send messages. The LOB connects to HL7, and then sends messages. Office web components (OWC) is now optional in the installation, and listed separately in Programs The orchestration instance ID is added to the XLANG FireEvent trace output

Deprecated & Removed List

Program	Status	Replacement
RFID Mobile	Removed	None
RFID Server	Removed	None
SharePoint SSOM/Web Service adapter	Removed	Use the CSOM (Client Side Object Model) option. Windows SharePoint Services Adapter Appendix B: Install the Microsoft SharePoint Adapter
SOAP adapter	Deprecated	WCF-BasicHttp Adapter
Old SQL adapter	Deprecated	WCF-based SQL adapter in the BizTalk Adapter Pack
UDDI	Removed	None

Important

Some of these deprecated features may be found in newer versions of BizTalk. In these scenarios, consider the following:

• The feature may be used internally within BizTalk, and is not meant to be used by customer solutions. It is not supported in customer solutions.
• The interfaces may have been modified by Microsoft, and may not be publicly available.

Next steps

Hardware & software requirements
Setup & install prerequisites
Install BizTalk