Installation Biztalk 2013 in production

hi all,
I have to install biztalk server 2013 in production env.(here we have 2 biztalk servers running on 2 different servers connected to SQL server 2012 on another server which is already installed)
Disable IPv6
Turn off Internet Explorer Enhanced Security Configuration
Turn Windows Firewall Off
Configure the Application Event Log
Enable Internet Information Services 
Running the BAM Portal in a 64-bit Environment
Configure the SMTP Server
Verify Your Installation
Install Microsoft Office Excel 2013.
Configure SQL Server Database Mail feature 
Install and Configure BizTalk Server 2013 
Verify Your Installation
Configure BizTalk Server 2013
Validate Mail account used by BizTalk to send BAM Alerts
Installing BizTalk Adapter Pack
Install Microsoft BizTalk Adapter Pack(x64)
Install Microsoft BizTalk Adapters for Enterprise Applications
Add adapters to BizTalk Administration Console
Configure BizTalk Server SQL Jobs
Backup BizTalk Server (BizTalkMgmtDb)
DTA Purge and Archive (BizTalkDTADb)
MessageBox_Message_Cleanup_BizTalkMsgBoxD
Configure BizTalk Server Windows Services 
 Are this steps correct for installation please suggest
Thanks
Thanks,

Hi Sachin,
There are some steps missing from your list, some like:
enable  network DTC access
Enable network  COM+ access on all BizTalk servers and any remote SQL Server instances used by BizTalk Server
Enabling BAM Add-in from Excel ( Excel installintion is not enough, you have to enable BAM Add-in from Excel)
Configure
Notification Services, if you use BAM alerts.
Configure Windows Groups and Service Accounts before installation.
Install Active Directory domain services for the various BizTalk Server groups and accounts.
Clustering MSDTC
Install SQL Server Failover Clustering
etc.....
Can any beat Microsoft's installation document on this context, refer to "Installing BizTalk Server 2013 and BAM in a Multi-Computer Environment" document. Download the document from here.
Installation Guides Related to BizTalk Server 2013
When you click "download" button, select "Installing BizTalk Server 2013 and BAM in a Multi-Computer Environment.docx" for your purpose.
This document details all the steps required for the successful multi-server BizTalk installation as your requirement.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Similar Messages

  • Compilation error after installling BizTalk 2013 CU2

    Hi,
    I started getting the below error in the orchestration project
    "non-readonly field/property access is limited to distinguished fields on class-based messages"
    it was failing at this line RequestMessage.DocumentElement.LocalName == "Fault".
    Here RequestMessage is a message of type System.Xml.XmlDocument. 
    It was working again after I uninstalled BizTalk 2013 CU2. Has anyone faced this problem and what was the solution .
    Looking at the release notes of CU2 at
    http://support.microsoft.com/kb/2892599/en-gb it says about a fix to XpathMutator class
    "FIX: XpathMutatorStream class does not work as expected when you execute Xpath statements against XmlDocuments in BizTalk Server 2013"
    Probably this is causing the compilation error. Can we raise this with the BizTalk Product team if someone else has also faced this issue ?
    Regards,
    Mahesh

    What subsequent CU's? There hasn't been any CU's for BizTalk Server 2013 since CU2 which was released in Oct. 2013 (almost 1 1/2 year ago now!)
    http://support.microsoft.com/kb/2555976
    Morten la Cour

  • Visual Studio 2013 - which edition for a BizTalk 2013 installation ?

    Hi there, 
    What is the lowest edition of VS2013 that will do for BT2013 ? 
    Is it necessary to go for ultimate or is one of the test editions enough ?

    If you're checking  the lowest Visual Studio edition for saving cost, then Professional edition should do.
    FYI:
    For BizTalk 2013, it Visual Studio 2012. And for Visual Studio 2013 is for BizTalk 2013 R2 (not 2013)
    And as pointed out, "Test Professional" is not for testing.
    Have a look here for the comparison for features among the Visual studio editions.
    http://www.visualstudio.com/en-us/products/compare-visual-studio-products-vs.aspx
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • Test/Verify Biztalk 2013/Windows 2008 R2 installation

    Hi
    I have experienced problems with MSDTC on a new two server development box (virtual server)
    BizTalk 2013/MSSQL 2012 on Windows 2008 R2
    MSDTC failed connection when receive locations was started
    Seems to be fine now DTC tester is working ok
    I'd like to check how the installation is doing on a more regurlar basis
    Any ideas, some scheduled action, a service or something
    Thanks  /Peter

    Peter,
    You can consider few options:
    Since you dont have any trace of MSDTC failure in your new installation, instead of looking for an trace, you can look for its reaction like suspend message and configure an alert to
    be send to you (or to support team)
    Normally any MSDTC related failures on a running instance would result in a eventlog entry, and again you can configure for an alert for this event log entry.
    Another option is you can create a batch file to run the DTCPing tool and it can output an log file. Your automation script can interrogate or send the copy of the log file to you.
    Also in MSDTC, you can enable tracing options, where you have options like “Trace Aborted Transaction” (In the same tab you can also choose the log file location). So you can create an
    automated process to send you the log file (may be by email) when the log file is created or periodically.
    As said, Messagebox view can be scheduled to run and it can capture the MSDTC failures. And this report can be emailed to you.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • Microsoft BizTalk Adapters for Host Systems Missing with BizTalk 2013

    Hi All,
    I am using BizTalk 2013 and looking  for Microsoft BizTalk Adapters for Host Systems but cannot find it on Installation disk.
    Do any one has idea how to go ahead with this .
    Thanks
    Abhishek

    Hi Abhishek,
    As far as what we can experience, there is not standalone download for
    BizTalk 2013 Adapters for Host Systems 2013. Its part of the
    Host Integration Server 2013 installtion.
    HIS 2013 installation
    document’s official
    “Existing Product Upgrade
    This release supports an in-place upgrade of earlier versions of HIS. The Host Integration Server 2013 setup automatically
    upgrades your existing configuration. The following releases are supported for automatic upgrade.
    Host Integration Server 2009
    BizTalk Adapters for Host Systems 2.0
    When you run the installation setup for
    Host Integration Server 2013, we will get the information like the following. In my server I already have
    BizTalk Adapters for Host Systems 2.0 (as per the requirement),
    hence this installation wizard tries to upgrade it to make it compactable with 2013.
    When you proceed with the installation, this will install/upgrade the BizTalk adapter to 2013.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • Upgrade BizTalk 2013 Standard Edition to Enterprise edition

    Hi All,
    I wanted to upgrade from BizTalk 2013 Standard Edition to BizTalk 2013 Enterprise edition. Could you please let me know the steps that I need to follow or the point me to any related documentation.
    Thanks and Regards,
    Ujjwal
    -Ujjwal

    Back-up of databases
    BizTalk application.
    Backup the binding, parties, policies, vocabularies.
    BTSNTSVC.config file.
    Backup the Enterprise Single Sign-On secret
    This would help you if in case of any rollback
    When run the installation package for
    Enterprise edition, the install will detect
    the exiting version and guide you to upgrade. The install will also ensure the
    installed BizTalk application is not be affected.
    Use the back-ups if anything goes wrong. 
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • BizTalk 2013 - BAMAlerts service crash

    Hi,
    I am deploying BizTalk into a new clean Production environment. My topology is the following:
    - 2 SQL Server machines (clustered)
    - 2 BizTalk application servers (with BTS runtime)
    - 1 BAM server
    I have everything deployed and working well except for the BAMAlerts service crashing a minute after it starts on the BAM server.
    The software installed on the BAM server is:
    Windows 2008 R2 x64
    SQL Server 2012 SP1 x64 with the  following features:
    Reporting Services (Native)
    SQL Server Data Tools
    Client Tools Connectivity
    Integration Services
    Management Tools – Basic
    Management Tools – Complete
    SQL Server 2012 SP1 Cumulative Update 9
    BizTalk Server 2013 x64 with the following features:
    Portal Components
    Business Activity Monitoring
    Administrative Tools and Monitoring
    Additional Software
    Enterprise Single Sign-On Administration Module
    Enterprise Single Sign-On Master Secret Server
    BAM Alert Provider for SQL Notification Services
    BAM Client
    BAM-Eventing
    Office Excel 2013 (x86)
    Once the BizTalk binaries are installed I installed Windows Update suggested patches including  the update for BizTalk Server 2013 (KB2830546).
    I then went on and configured the relevant features. Configuration worked well but the BAMAlerts service crashes 1 minute after starting with the following error:
    Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "". ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection
    to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    I verified the following:
    A database mail profile was created on the SQL Server instance and it works (I can use it to send emails)
    Using the BAMAlerts service account I am able to connect to the SQL Server instance using Named Pipes or TCP/IP, call BizTalkMgmtDb.dbo.adm_Group_GetBAMServerAndDBName or query tables
    I installed SQL Server 2005 Notification Services x64 in order to see if it helps but no success.
    I installed BizTalk 2013 Cumulative Update 2 but it did no help either.
    The worse part is that I hit the same issue when setting up our UAT environment, tried a number of things and ended up with a setup that works but I am not able to reproduce that success in Prod...
    Following is the full error message:
    Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "". ---> System.Data.SqlClient.SqlException:
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
    Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
    at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
    at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
    at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
    at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
    at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
    at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
    at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
    at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
    at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
    at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
    at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
    at System.Data.SqlClient.SqlConnection.Open()
    at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteQuery(String cmdText, CommandType cmdType, Transaction transaction)
    --- End of inner exception stack trace ---
    at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteQuery(String cmdText, CommandType cmdType, Transaction transaction)
    at Microsoft.BizTalk.Bam.AlertHost.AlertHost.Run()
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Threading.ThreadHelper.ThreadStart()
    Thanks
    Emmanuel

    Known issue, you need BizTalk Server 2013 CU1:
    http://support.microsoft.com/kb/2838133/en-us
    (See hotfix 2832137)
    Morten la Cour

  • BizTalk 2013 Integration with JDE EnterpriseOne 9.1

    Hi Guys,
    I want to connect to JDE EnterpriseOne 9.1 using the out of box Enterprise JDE adapter provided by BizTalk.
    I have done standalone installation of JDE EO on my machine.
    I have gone through the tutorial and found that I would need Connector.jar, Kernel.jar and JDEDynAccess.jar.
    However, I have found Connector.jar and JDEDynAccess.jar but somehow I don't see Kernel.jar in the installation folders of JDE EO.
    Where should I get the specified file?
    Thanks in advance...
    Dhiraj Bhavsar

    I hope I am not the only person on the planet who is trying to implement this solution (Integrating JDE using Adapter). :-(
    Does BizTalk 2013/R2 support with JD Edwards EnterpriseOne 9.1?
    Thanks & regards,
    Dhiraj Bhavsar

  • Deployement in biztalk 2013

    Hi all,
    I am migrating biztalk server 2010 to 2013.
    Using visual studio conversion wizard i have converted all applications into 2012.
    Can any one please help me out how to deploy the application in biztalk 2013 as i am new to it.
    and what would be the best approach.please suggest in steps
    Thanks
    biztalk007

    Now you got the source code migrated to Visual Studio 2012. Deployment of the BizTalk application hasn’t changed much from BizTalk 2006 onwards. Since BizTalk Server
    2006 the product formalizes the notion of a BizTalk Application that allows working with these artifacts as a single unit. A BizTalk application wraps all of the pieces required for a solution into a single logical unit, making it the fundamental abstraction
    for management and deployment.
    Read the following article on BizTalk application deployment and best practices:
    Deploy
    BizTalk Applications using MSI files – Concept and Best practices
    Also read this TechNet-Wiki’s excellent article on this topic:
    Recommendations
    for Installing, Sizing, Deploying, and Maintaining a BizTalk Server Solution
    Also when you’re considering the best practices for deploying the BizTalk applications in BizTalk 2013, consider about the automating the deployment. There are various
    tools available to achieve the deployment automation, but my favourite is Deployment Framework for BizTalk (BTDF). With the latest version supporting BizTalk 2013, it’s a great tool in your arsenal.
    Deployment Framework for BizTalk (BTDF)
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • BizTalk 2013 choice for "999" file type missing in Party Agreement configuration

    Ok guys--this makes no sense. In BizTalk 2010, we were able to select the 999 file type in the party Config/Agreement section, specifically in the "Envelopes", "Local Host Settings" & Transaction Set List" sections under
    "Transaction Set Settings". I could see if this was a 997 file type as that should be deprecated under 5010, but this is 999, the new format.
    Since my experience with 2013 is limited, can anyone tell me if there is a service pack or CU we missed when this was setup that might include this? A setting somewhere perhaps?
    Any assistance is appreciated--thanks in advance---
    Tom

    Confirmed as bug / oversight in Biztalk 2013 -Ugh
    Hello Scott,
    We did an in-house repro and realized that this does not work.
    It seems in BizTalk Server 2010, we had 999 listed under the
    supported transactions list, but it is somehow not listed in BizTalk Server 2013.
    We have raised a ticket to the Product Group to review this and make the required change. However, we do not have an ETA by when this change will be implemented.
    Thanks,
    Kshitij
    Scott K Berger

  • Biztalk 2013 R2 ESB toolkit support and Licence issues

    Hi,
    Currently we are using Biztalk 2013 R2 standard version and have not installed/configured ESB toolkit yet. Now i am exploring the options to use the ESB toolkit as it is pretty good for the exception management and it comes with nice portal as well.I have
    used the ESB in the past with Biztalk 2010 so i have a favor for the toolkit.
    But one of our consultant said that the ESB toolkit is not supported by Microsoft for the standard version and it is supported only with enterprise version of Biztalk. He also mentioned that once we configure ESB with standard version Microsoft does not
    support ESB and also the entire Biztalk server So i am afraid of that and thought of validating the information with right people.
    Can someone please answer the below questions for me?
    Can we use ESB toolkit with Biztalk standard version? If so how about support from Microsoft? Does Microsoft support at least production server OR not?
    Do we need enterprise version only for this?
    I used ESB with Biztalk 2010 in the past and though there are minor issues i personally like it . But what are your thoughts of using ESB?
    Here are the technologies we are using
    Biztalk 2013 R2, Visual studio 2013 and SQL server 2014. Just to mention Visual studio is not available in test and production servers.
    Thanks
    JB

    Hi,
    Why you want to use BizTalk Standard Edition in Production Environment?
    BTS Standard only run on a single BizTalk server with a maximum of two CPUs, maximum of five "BizTalk Applications",
    However, Enterprise does not have such limitations
    Yes, it is not supported and it has not been extensively tested by Microsoft on Standard Edition, but it doesn't mean you can’t
    install it.
    From BizTalk
    Server: ESB Survival Guide has this requirement:
    BizTalk Server 2010 Enterprise/Developer Edition
    Understanding is:
    ESB toolklit uses one of the five applications that can be deployed on BizTalk 2010 Standard Edition
    ESB toolkit will work on BizTalk 2010 Standard Edition, but it's not supported
    Requirements for ESB 2.2 with BizTalk 2013 is not specified as such, but I suspect the same limitation applies.
    Refer: BizTalk
    ESB Toolkit 2.1 on BizTalk Standard Edition environment , does it work ?
    Rachit
    Please mark as answer or vote as helpful if my reply does

  • BizTalk 2013 R2 - Oracle client connectivity

    In integration of BizTalk 2013 R2 with Oracle database
    1)  is there only  any particular version client that BTS 2013 R2 supports.
    2) Do I need to know what version of Oracle db client is using before I install oracle client - (should support BTS2013 r2)
    3) For example, client has older version of Oracle Db say 8g and if I install Oracle client 11g will that work  with my BTS2013 R2 ?
    4) Is it mandatory to always install both 32 bit and 64 bit  client ?
    MBH

    Please follow the below steps (worked for me):
    1-    
    You can install it by running setup available in
    ODAC1110720.zip which can be downloaded from oracle site.
    2-    
    Install ODAC1110720 on the new OracleClient home.
    3-    
    Click
    Next on Welcome screen
    4-    
    Keep selecting
    Oracle Client 11.1.0.7.20 version to install
    5-    
    Keep selecting
    Oracle Client 11.1.0.7.20 version to install
    6-    
    Select
    D:\app as Oracle Base where Oracle Client is installed on your system and click
    Next:
    7-    
    Keep the default port and click
    Next to proceed:
    8-    
    Click
    Exit on successful installation
    If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • BizTalk Server Developer 2013 Vs BizTalk 2013 R2

    I would like to know that if user production environment is BizTalk 2013R2.
    Can I use "BizTalk Server Developer 2013" for my development? Does they compatiable?

    Yes it’s possible.
    BizTalk 2013 R2 support both .NET Framework 4.5 and .NET Framework 4.5.1 not just 4.5.1.
    Artifacts from BizTalk 2013 are .NET 4.5 and they are compatible with BizTalk 2013 R2 environment and hence they can be deployed in BizTalk 2013 R2 – Technically it’s possible.
    Refer the platform supported section in this MSDN article.
    https://msdn.microsoft.com/en-us/library/jj248703.aspx
    Then the question comes, would I do this? I will not. But if you don’t have an option, you got to use BizTalk 2013 in BizTalk 2013 R2, then I can. And for future development I would use BizTalk 2013 R2 environments for BizTalk 2013 R2 deployment.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • BizTalk 2013 R2 - WC-Custom Adapter SAP-Binding: Unhandeld exception on failure tests

    Dear Mr./Ms.
    We have set up a test environment with BizTalk 2013 R2 Developer edition.
    And we have also set up the SAP adapter following this blog
    https://sandroaspbiztalkblog.wordpress.com/2015/03/04/biztalk-server-20132013-r2-step-by-step-wcf-sap-adapter-installation-guide/#comments
    .But instead we used a WCF-Custom adapter with SAP-Binding
    Everthing works fine if BizTalk can connect to SAP. But if we do some failure test, like giving in a wrong password. We get next error in the event viewer:
    Application: BTSNTSvc64.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Runtime.CallbackException
    Stack:
    at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredAsyncResult.SignalFinished(System.Object, System.Exception)
    at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredOutboundChannel`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].AsyncRequest(System.Object)
    at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
    at System.Threading.ThreadPoolWorkQueue.Dispatch()
    We would expect that we get some kind of authentication error and a suspended message. But Instead the host instance crash and message stays in process. Thanks in advance.
    Kind regards
    Benny Verhamme
    benny verhamme signed

    We would expect that we get some kind of authentication error and a suspended message. But Instead the host instance crash and message stays in process. Thanks in advance.
    Hi Benny,
    Thanks for your feedback in BizTalk forum.
    As you mentioned above, we will receive an unhandled exception when we did something wrong during the procedure. I'm afraid that this is "by design", if this request is urgent for you, you could consider contact support directly(http://support.microsoft.com
     ).   Thanks for your understanding.
    Best regards,
    Angie
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • BizTalk 2013 Azure VM (IaaS) High availability

    Hi,
    We have a 2 BT , 1 SQL configuration for the BizTalk Environment. BizTalk 2013 VMs and SQL 2012 VM provisioned from the gallery.  Since there is a limitation on having a highly available SQL tier (for BizTalk) on Azure, we are evaluating a possible
    replacement of the Azure setup with a on-premise setup which will guarantee highly available environment(as the SQL tier will be highly available too and with the SSO service). Wanted to know your thoughts on the below topics.
    1) Is the BizTalk 2013 Azure (IaaS) used widely in production scenarios today (given the limitation for HA). If yes, what could be the mitigating solution
    2) Is the roadmap for Microsoft (BizTalk Server related) going to address this scenario. 
    Appreciate your inputs in this regard which would help us to make an informed decision to switch back to on-premise.
    Thanks,
    Ujjwal
    -Ujjwal

    Theoretically since SQL Always-ON or database mirroring is not supported with BizTalk, SQL Server Azure virtual machines do not support Failover Cluster Instances.
    But ensure by selecting “Availability Set” your virtual machine will be deployed to different fault domains and update domain thus ensuring that your application is available during network failures, hardware failures, and any planned downtime. This increases
    the case of server/service high availability. And with these features unavailability of the server in Azure is very less.
    But if you’re one of those customers you still want to ensure they don’t let any chance of failure (or don’t afford for any failure) and still look to implement failover Cluster Instances, then simple answer is SQL Server Azure virtual machines do not support
    Failover Cluster Instances. If you ask about mitigation plan, then ensure you have selected “Availability Set” while provisioning the servers.
    To answer to you couple of specific questions:
    1) Is the BizTalk 2013 Azure (IaaS) used widely in production scenarios today (given the limitation for HA). If yes,
    what could be the mitigating solution - Ican't
    answer BizTalk as Iaas is widely used, this question has to be asked to Microsoft directly. And regarding the mitigation plan, as mentioned provisional your server across fault
    domains and update domain minimize the down time or increases the high availability.
    2) Is the roadmap for Microsoft (BizTalk Server related) going to address this scenario.   -  As of now SQL Always-ON or database mirroring are not supported for BizTalk and roadmap remains same.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Maybe you are looking for