Merge pull request #88843 from ecfan/patch-3

B2B content cleanup

Author: ktoliver

articles/logic-apps/logic-apps-enterprise-integration-overview.md

@@ -1,81 +1,59 @@
 ---
-title: B2B enterprise integration overview - Azure Logic Apps | Microsoft Docs
-description: Build automated B2B workflows for enterprise integration solutions with Azure Logic Apps and Enterprise Integration Pack
+title: B2B enterprise integration - Azure Logic Apps
+description: Learn about building automated B2B workflows for enterprise integration by using Azure Logic Apps and Enterprise Integration Pack
 services: logic-apps
 ms.service: logic-apps
 ms.suite: integration
-author: divyaswarnkar
-ms.author: divswa
-ms.reviewer: jonfan, estfan, LADocs
-ms.topic: article
+author: ecfan
+ms.author: estfan
+ms.reviewer: jonfan, divswa, LADocs
+ms.topic: overview
 ms.assetid: dd517c4d-1701-4247-b83c-183c4d8d8aae
-ms.date: 09/08/2016
+ms.date: 08/01/2019
 ---
 
-# Overview: B2B enterprise integration scenarios in Azure Logic Apps with Enterprise Integration Pack
+# B2B enterprise integration solutions with Azure Logic Apps and Enterprise Integration Pack
 
-For business-to-business (B2B) workflows and seamless communication with Azure Logic Apps, you can enable enterprise integration scenarios with Microsoft's cloud-based solution, the Enterprise Integration Pack. Organizations can exchange messages electronically, even if they use different protocols and formats. The pack transforms different formats into a format that organizations' systems can interpret and process. 
-Organizations can exchange messages through industry-standard protocols, 
-including [AS2](../logic-apps/logic-apps-enterprise-integration-as2.md), 
-[X12](logic-apps-enterprise-integration-x12.md), 
-and [EDIFACT](../logic-apps/logic-apps-enterprise-integration-edifact.md). 
-You can also secure messages with both encryption and digital signatures.
+For business-to-business (B2B) solutions and seamless communication between organizations, you can build automated scalable enterprise integration workflows by using the Enterprise Integration Pack (EIP) with [Azure Logic Apps](../logic-apps/logic-apps-overview.md). Although organizations use different protocols and formats, they can exchange messages electronically. The EIP transforms different formats into a format that your organizations' systems can process and supports industry-standard protocols, including [AS2](../logic-apps/logic-apps-enterprise-integration-as2.md), [X12](logic-apps-enterprise-integration-x12.md), and [EDIFACT](../logic-apps/logic-apps-enterprise-integration-edifact.md). You can also secure messages with both encryption and digital signatures. The EIP supports these [enterprise integration connectors](../connectors/apis-list.md#integration-account-connectors) and these industry standards:
 
-If you are familiar with BizTalk Server or Microsoft Azure BizTalk Services, 
-the Enterprise Integration features are easy to use because most concepts are similar. One major difference is that Enterprise Integration uses integration accounts to simplify the storage and management of artifacts used in B2B communications. 
+* Electronic Data Interchange (EDI)
+* Enterprise Application Integration (EAI)
 
-Architecturally, the Enterprise Integration Pack is based on "integration accounts". These accounts are cloud-based containers that store all your artifacts, like schemas, partners, certificates, maps, and agreements. You can use these artifacts to design, deploy, and maintain your B2B apps and also to build B2B workflows for logic apps. But before you can use these artifacts, you must first link your integration account to your logic app. After that, your logic app can access your integration account's artifacts.
+If you're familiar with Microsoft BizTalk Server or Azure BizTalk Services, the EIP follows similar concepts, making the features easy to use. However, one major difference is that the EIP is architecturally based on "integration accounts" to simplify the storage and management of artifacts used in B2B communications. These accounts are cloud-based containers that store all your artifacts, such as partners, agreements, schemas, maps, and certificates. 
 
-## Why should you use enterprise integration?
+## Why use the Enterprise Integration Pack?
 
-* With enterprise integration, you can store all 
-your artifacts in one place -- your integration account.
-* You can build B2B workflows and integrate with third-party 
-software-as-service (SaaS) apps, on-premises apps, and custom apps 
-by using the Azure Logic Apps engine and all its connectors.
-* You can create custom code for your logic apps with Azure functions.
+* With the EIP, you can store all your artifacts in one place - your integration account.
+
+* You can build B2B workflows and integrate with third-party software-as-service (SaaS) apps, on-premises apps, and custom apps 
+by using Azure Logic Apps and connectors.
 
-## How to get started with enterprise integration?
+* You can create custom code for your logic apps with Azure functions.
 
-You can build and manage B2B apps with the 
-Enterprise Integration Pack through the Logic App Designer 
-in the **Azure portal**. You can also manage your logic apps with 
-[PowerShell](https://docs.microsoft.com/powershell/module/az.logicapp).
+## How do I get started?
 
-Here are the high-level steps you must take before you can create apps in the Azure portal:
+Before you can start building B2B logic app workflows with the EIP, you need these items:
 
-![overview image](media/logic-apps-enterprise-integration-overview/overview-0.png)  
+* An Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
 
-## What are some common scenarios?
+* An [integration account](../logic-apps/logic-apps-enterprise-integration-create-integration-account.md) with the artifacts that you want to use
 
-Enterprise Integration supports these industry standards:
+* To create maps and schemas, you can use the [Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0](https://aka.ms/vsmapsandschemas) and Visual Studio 2015.
 
-* EDI - Electronic Data Interchange
-* EAI - Enterprise Application Integration
+After you create an integration account and add your artifacts, you can start building B2B workflows with these artifacts by creating a logic app in the Azure portal. If you're new to logic apps, try [creating a basic logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md). To work with these artifacts, make sure that you first link your integration account to your logic app. After that, your logic app can access your integration account. You can also create, manage, and deploy logic apps by using Visual Studio or [PowerShell](https://docs.microsoft.com/powershell/module/az.logicapp).
 
-## Here's what you need to get started
+Here are the high-level steps to get started building B2B logic apps:
 
-* An Azure subscription with an integration account
-* Visual Studio 2015 to create maps and schemas
-* [Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0](https://aka.ms/vsmapsandschemas)  
+![Prerequisites for creating B2B logic apps](./media/logic-apps-enterprise-integration-overview/overview.png)  
 
-## Try it now
+## Try now
 
-[Deploy a fully operational sample AS2 send & receive logic app](https://github.com/Azure/azure-quickstart-templates/tree/master/201-logic-app-as2-send-receive) that uses the B2B features for Azure Logic Apps.
+[Deploy a fully operational sample logic app that sends and receives AS2 messages](https://github.com/Azure/azure-quickstart-templates/tree/master/201-logic-app-as2-send-receive)
 
-## Learn more
-* [Agreements](../logic-apps/logic-apps-enterprise-integration-agreements.md "Learn about enterprise integration agreements")
-* [Business to Business (B2B) scenarios](../logic-apps/logic-apps-enterprise-integration-b2b.md "Learn how to create Logic apps with B2B features ")  
-* [Certificates](logic-apps-enterprise-integration-certificates.md "Learn about enterprise integration certificates")
-* [Flat file encoding/decoding](logic-apps-enterprise-integration-flatfile.md "Learn how to encode and decode flat file contents")  
-* [Integration accounts](../logic-apps/logic-apps-enterprise-integration-accounts.md "Learn about integration accounts")
-* [Maps](../logic-apps/logic-apps-enterprise-integration-maps.md "Learn about enterprise integration maps")
-* [Partners](logic-apps-enterprise-integration-partners.md "Learn about enterprise integration partners")
-* [Schemas](logic-apps-enterprise-integration-schemas.md "Learn about enterprise integration schemas")
-* [XML message validation](logic-apps-enterprise-integration-xml.md "Learn how to validate XML messages with Logic apps")
-* [XML transform](logic-apps-enterprise-integration-transform.md "Learn about enterprise integration maps")
-* [Enterprise Integration Connectors](../connectors/apis-list.md "Learn about enterprise integration pack connectors")
-* [Integration Account Metadata](../logic-apps/logic-apps-enterprise-integration-metadata.md "Learn about integration account metadata")
-* [Monitor B2B messages](logic-apps-monitor-b2b-message.md "Learn more about monitoring B2B messages")
-* [Tracking B2B messages in Azure Monitor logs](logic-apps-track-b2b-messages-omsportal.md "Learn more about tracking B2B messages in Azure Monitor logs")
+## Next steps
 
+* [Create trading partners](logic-apps-enterprise-integration-partners.md)
+* [Create agreements](../logic-apps/logic-apps-enterprise-integration-agreements.md)
+* [Add schemas](logic-apps-enterprise-integration-schemas.md)
+* [Add maps](../logic-apps/logic-apps-enterprise-integration-maps.md)
+* [Migrate from BizTalk Services](../logic-apps/logic-apps-move-from-mabs.md)