Hybrid connections are a feature of BizTalk Services and offer connections that look like virtual networks from point to place because a server is connected to Azure resources in your environment. If they differ, it is because the entire server is not available for Azure, but only a connection to a specific resource on that server. In addition, the connection is initiated by Azure and is therefore not useful for local resources that need to initiate a connection with an Azure resource. Today, these connections are only available for websites and mobile services, and therefore in a BizTalk solution that is most useful when you need to make a local BizTalk resource available for an Azure site or mobile service. Windows Azure BizTalk Services enables business scenarios such as electronic data exchange and enterprise application integration. It provides integrated support for the management of EDI agreements between partners, as well as the installation of EAI bridges with local industrial terminals using the BizTalk adapter service, as well as using comprehensive visualization tools. In addition to network-level solutions to connect your environments, there are several app-level options to connect your BizTalk application in Azure to your local resources: Hybridconnections and Azure Service Bus. Hybrid connections allow you to connect to local databases and HTTP resources via regular link sequences and URLs via Azure websites and mobile services. The service bus offers message relay and mesh messaging options that allow you to go through firewalls and network address translators. One of the advantages of cloud computing and the use of services like Azure Virtual Machines is that it can use the infrastructure services of a large data center.
Virtual discs are stored in Azure Storage, which has redundant copies of data locally and, as an option, geo-emerging copies. Despite the many features that aim to limit your downtime, some precautions are still needed, especially when it comes to SQL data. One of the download options for the SDK is to download the EDI diagrams. The compressed archive is about 340MB, so you should probably extend the file to a separate drive, as you only have to provide the specific diagrams you use in your solution. For example, if you only work with X12 commands and corresponding confirmations, you simply provide the 850 and 855 diagrams instead of the hundreds of diagrams included in the download. EDI diagrams can be added directly to your project without having to change them. If your requirements for a particular type of document differ (and if not), you can change the schema to change the settings, z.B the required fields, or to change a type of data or field validation setting. As in BizTalk Server, you can also deploy multiple versions of the same scheme using different name spaces, and then set up the corresponding name space for the contract settings. This allows you to use clear definitions of requirements for certain business partners. I advise 20th place on this, unless you absolutely cannot avoid it, because it creates many more artifacts that need to be managed and introduces into your solution the complexity that can be avoided at best if possible.
The reality of integration will, of course, dictate that this is not always possible. Like the basic Azure BizTalk service solution, Visual Studio 2012 is a development for an EDI solution. The only artifacts you develop for the EDI part of your solution are diagrams and transformations, while your bridges and chords are defined in the portal.