Configuring Agreements from a BizTalk perspective

  • Article

 

Important

Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.

If you're brand new to Logic Apps, then we suggest getting started here:

Configuring EDI messaging in the Microsoft Azure BizTalk Services Portal is different when compared with BizTalk Server TPM Portal. Following is an overview of the Microsoft Azure BizTalk Services steps to configuring in the Microsoft Azure BizTalk Services Portal:

  1. Log in to the BizTalk Services Portal. The first time you log in, you are prompted to register you/your company’s BizTalk Service deployment. You can then add “partners.” BizTalk Server “Party” and BizTalk Services “Partners” section discusses these steps.

  2. When “partners” are created in the BizTalk Services Portal home page, a profile is automatically created for every partner. You can also create new profiles or update the existing profile. BizTalk Server “Profile” and BizTalk Services “Profile” section discusses this information.

  3. Create an X12 or AS2 agreement between the partners. General Settings, Receive Settings, and Send Settings are configured. BizTalk Server “Agreement” and BizTalk Services “Agreement” section discusses this information.

  4. When complete, deploy the agreement. BizTalk Server “Enable” and BizTalk Services “Deploy section discusses this information.

This topic acts as a guide for configuring EDI components in BizTalk Services compared to BizTalk Server.

BizTalk Server “Party” and BizTalk Services “Partners”

A “party” in BizTalk Server is called a “partner” in BizTalk Services. The following tables compare the “party” settings in BizTalk Server with the “partner” settings in BizTalk Services.

Represent you or your company to send messages or receive messages

This table lists the different tasks involved when registering you or your company’s BizTalk Service deployment. It lists the “party” tasks in BizTalk Server and the replacement “partner” settings in BizTalk Services.

Task

BizTalk Server

BizTalk Services

Create the “partner”

In BizTalk Administration, create a new Party and check Local BizTalk processes messages received by the party or supports sending messages from this party.

This option establishes you or your company as the service provider. This is the only time you check this option when creating a party.

How to Create a Party provides the details.

The first time you log in to the BizTalk Services Portal, you register you/your company’s BizTalk Service. This is the only time you enter the BizTalk Service. Once configured, the BizTalk Service cannot be deleted.

Configuring EDI, AS2, and EDIFACT on BizTalk Services Portal provides the details.

Optionally, enter additional details, like your name, phone number, e-mail address, etc.

In BizTalk Administration, open your party properties and add Additional Properties.

How to Create a Party provides the details.

The very first time you log in to the BizTalk Services Portal, you register you or your company’s BizTalk Service. You can later add additional details.

Configuring EDI, AS2, and EDIFACT on BizTalk Services Portal provides the details.

Send

In BizTalk Administration, open your party properties and select Send Ports. This associates the send port(s) with your service provider party.

How to Create a Party provides the details.

The “send” is configured when an agreement is created between two partners. Specifically:

  1. Create the partners using Manage Partners and Profiles in Azure BizTalk Services.

  2. Create an agreement between the partners using Create Agreements in Azure BizTalk Services.

  3. Configure the send settings using X12 Send Settings (Create an X12 Agreement in Azure BizTalk Services) and AS2 Send Settings (Create an AS2 Agreement in Azure BizTalk Services).

Certificate

In BizTalk Administration, open your party properties and select Certificate.

How to Create a Party provides the details.

The certificate is associated with you or your company’s profile.

When a partner is created, a profile is automatically created. A certificate can then be added to the profile. Specifically:

  1. Create a partner.

  2. Add a profile.

  3. Add a certificate to the profile.

See Manage Partners and Profiles in Azure BizTalk Services.

To summarize:

  • To add you or your company as a service provider in BizTalk Server, create a party and check the Local BizTalk processes messages received by the party or supports sending messages from this party option in the party properties. See How to Create a Party.

  • To register you or your company’s BizTalk Service, log in to the BizTalk Services Portal for the very first time and enter your properties. See Configuring EDI, AS2, and EDIFACT on BizTalk Services Portal.

Add “partners”

This table lists the task involved when creating a partner. It lists the “party” task in BizTalk Server and the replacement “partner” settings in BizTalk Services.

Task

BizTalk Server

BizTalk Services

Create the “partner”

In BizTalk Administration, create a new Party. Do NOT check Local BizTalk processes messages received by the party or supports sending messages from this party.

How to Create a Party provides the details.

In the BizTalk Services Portal home page, click Partners. Manage Partners and Profiles in Azure BizTalk Services provides the steps.

To summarize on how to create a “partner”:

BizTalk Server “Profile” and BizTalk Services “Profile”

“Profiles” exist in BizTalk Server and BizTalk Services. The following table compares the “profile” settings in BizTalk Server with the “profile” settings in BizTalk Services.

Add a profile

This table lists the task involved to add or edit a profile. It lists the “profile” tasks in BizTalk Server and the replacement “profile” settings in BizTalk Services.

Task

BizTalk Server

BizTalk Services

Create/edit a profile.

When a party is created in BizTalk Administration, a profile is automatically created. The profile properties include:

  • General: Includes Name, Description, and Additional Properties.

  • Identities: Includes an identity qualifier, like Mutually Defined ZZ.

Configuring Business Profile Properties provides the steps to add/edit a party profile.

When a partner is created in the BizTalk Services Portal, a profile is automatically created. Click the partner name to edit similar properties:

  • Profile name

  • Description

  • Identities

  • Certificates

  • Templates

Manage Partners and Profiles in Azure BizTalk Services provides the steps to add and edit a partner profile.

To summarize on how to create a profile:

BizTalk Server “Agreement” and BizTalk Services “Agreement”

“Agreements” exist in BizTalk Server and BizTalk Services. The following tables compare the “agreement” settings in BizTalk Server with the “agreement” settings in BizTalk Services.

X12 Agreements

Add an Agreement: X12 General settings

This table lists the different tasks involved when adding an agreement and configuring “General” settings. It lists the “agreement” tasks in BizTalk Server and the replacement “agreement” settings in BizTalk Services.

Task

BizTalk Server

BizTalk Services

Create an agreement: General

A profile is required to create an agreement. In BizTalk Administration, right-click the profile and create a new agreement. This option displays the following properties:

  • General Properties: Includes the agreement name, the X12 protocol, the First Party, the Second Party, enabling the agreement and logging.

  • Contact Information: The contact details.

  • Additional Properties: Include any name-value pair.

Configuring General Settings (X12) provides the steps to edit these properties.

No identifiers are configured in the General properties in BizTalk Server.

A profile is required to create an agreement. In the BizTalk Services Portal home page, click Agreements and then click the X12 tab. The General tab is opened and displays the following properties:

  • Agreement name

  • Agreement Description

  • Hosted Partner

  • Hosted Partner Qualifier and Value (ISA5 and ISA6).

    In BizTalk Server, ISA5 and ISA6 are configured in the agreement receive and send properties.

  • Guest Partner

  • Guest Partner Qualifier and Value (ISA5 and ISA6).

    In BizTalk Server, ISA5 and ISA6 are configured in the agreement receive and send properties.

  • Track Send side message properties

    In BizTalk Server, errors can be logged when EDI reporting is enabled.

  • Track Receive side message properties

    In BizTalk Server, errors can be logged when EDI reporting is enabled.

See Create an X12 Agreement in Azure BizTalk Services.

To summarize on how to create an agreement:

Add an Agreement: X12 Receive settings

Warning

If you click another tab while creating the agreement, the agreement settings are not saved.

This table lists the different tasks involved when adding an agreement and configuring “Receive” settings. It lists the “agreement” tasks in BizTalk Server and the replacement “agreement” settings in BizTalk Services.

Task

BizTalk Server setting

BizTalk Services replacement

Receive Properties Location

When you click OK in the Agreement General Properties, two new tabs display: First Party->Second Party and Second Party->First Party.

The Second Party->First Party is the Receive.

Important

In this scenario, First Party is the Service Provider; which means Local BizTalk processes messages received by the party or supports sending messages from this party is enabled for the First Party.

In the BizTalk Services Portal home page, click Agreements, click the X12 tab, and then Create Agreement. The General Settings are opened, which are previously described. When the General Settings are added, click Continue to display the Receive properties.

Important

This agreement in BizTalk Server translate to two separate agreements in BizTalk Services:

Agreement 1: First Party is the Hosted Partner.

Agreement 2: Second Party is the Hosted Partner.

 Interchange Settings 

Task

BizTalk Server setting

BizTalk Services replacement

Identifiers

  • Authorization qualifier (ISA1)

  • Value (ISA2)

  • Security qualifier (ISA3)

  • Value (ISA4)

  • Sender Id Qualifier (ISA5)

  • Value (ISA6)

  • Receiver Id Qualifier

  • Value (ISA8)

The Protocol page has the equivalent settings:

  • Authorization qualifier (ISA1)

  • ISA2

  • Security qualifier (ISA3)

  • ISA4

The X12 General Settings have the equivalent settings:

  • Hosted Partner Qualifier (ISA5)

  • Hosted Partner Value (ISA6)

  • Guest Partner Qualifier (ISA7)

  • Guest Partner Value (ISA8)

Note

In BizTalk Server, the receive agreement and send agreement can have a different pair of sender and receiver identities (ISA 5, ISA6, ISA7, ISA8). In BizTalk Services, the identity pair is the same for receive and send agreements.

Acknowledgements

  • TA1 Expected

  • 997 Expected

The Protocol page has the equivalent settings:

  • TA1 Expected: Returns technical (TA1) acknowledgment to the interchange sender (based on the Send Settings for the agreement).

  • 997 Expected: Returns functional (997) acknowledgment to the interchange sender (based on the Send Settings for the agreement).

Envelopes

Configured in Send.

No equivalent configuration.

Character set and separators

Character set to be used: Basic, Extended, or UTF8/Unicode.

No equivalent configuration.

Local Host Settings

  • ACK control numbers (STO2)

  • Reset to lower limit when out of bound

  • Route ACK to send pipeline on request-response receive port

  • Mask security/authorization/password information in context property

  • Inbound batch processing option

No equivalent configuration.

Validation

  • Interchange Control Number

    Check for duplicate ISA13 within the following number of days

  • Group Control Number

  • Transaction Set Control Number

The Protocol page has the equivalent settings:

  • Interchange Control Number

    Check for duplicate ISA13 every days

  • Group control number

  • Transaction set control number

Batch Configuration

Configured in Send.

No equivalent configuration.

Send Ports

Configured in Send.

No equivalent configuration.

 Transaction Set Settings

Task

BizTalk Server setting

BizTalk Services replacement

Transaction Set List

  • Support Transaction Sets from the List

  • Exclude Transaction Sets from the List

No equivalent configuration. On the other hand, the equivalent is implicit because only the message types configured in the X12 Agreement (Receive Settings, Schemas) are allowed. Messages corresponding to other message types are suspended.

Validation

  • Default

  • Transaction Type

  • Edi Type Validation

  • Extended Validation

  • Allow Leading & Trailing Spaces & Zeroes

  • Trailing Separators

The Protocol page has the equivalent settings:

  • Split Interchange as Transaction sets: Equivalent to checking Default check box in BizTalk Server.

  • Preserve Interchange: Equivalent to not checking Default check box in BizTalk Server.

Advanced Settings (Validation) in the Protocol page has the following equivalent settings:

  • Transaction Type

  • Edi Type Validation

  • Extended Validation

  • Allow Leading & Trailing Spaces & Zeroes

  • Trailing Separators

Local Host Settings

  • Convert implied decimal format Nn to base 10 numeric value

  • Create empty XML tags if trailing separators are allowed

The Protocol page has the equivalent settings:

  • Convert implied decimal format Nn to base 10 numeric value

  • Create empty XML tags if trailing separators are allowed

Envelopes

Configured in Send.

No equivalent configuration.

To summarize on how to add X12 Receive settings:

Add an Agreement: X12 Send settings

Warning

If you click another tab while creating the agreement, the agreement settings are not saved.

This table lists the different tasks involved when adding an agreement and configuring “Send” settings. It lists the “agreement” tasks in BizTalk Server and the replacement “agreement” settings in BizTalk Services.

Task

BizTalk Server setting

BizTalk Services replacement

Send Properties Location

When you click OK in the Agreement General Properties, two new tabs display: First Party->Second Party and Second Party->First Party.

The First Party->Second Party is the Send.

In the BizTalk Services Portal home page, click Agreements, click the X12 tab, and then click Create Agreement. The General Settings are opened, which are previously described. When the General Settings are added, click Continue and then click the Send tab to display the Send properties.

Interchange Settings

Task

BizTalk Server setting

BizTalk Services replacement

Identifiers

  • Authorization qualifier (ISA1)

  • Value (ISA2)

  • Security qualifier (ISA3)

  • Value (ISA4)

  • Sender Id Qualifier (ISA5)

  • Value (ISA6)

  • Receiver Id Qualifier (ISA7)

  • Value (ISA8)

The Protocol page has the equivalent settings:

  • Authorization qualifier (ISA1)

  • ISA2

  • Security qualifier (ISA3)

  • ISA4

No equivalent configuration for the following BizTalk Server settings:

  • Sender Id Qualifier (ISA5)

  • Value (ISA6)

  • Receiver Id Qualifier (ISA7)

  • Value (ISA8)

Acknowledgements

  • TA1 Expected

  • 997 Expected

  • Include AK2 loop for accepted transaction sets

The Protocol page has the equivalent settings:

  • TA1 Expected: Returns technical (TA1) acknowledgment to the interchange sender (based on the Send Settings for the agreement).

  • 997 Expected: Returns functional (997) acknowledgment to the interchange sender (based on the Send Settings for the agreement).

  • Include AK2 Loop

Envelopes

  • ISA11 Usage: Choose Standard identifier or Repetition separator

  • Control version number (ISA12)

  • Usage indicator (ISA15)

The Protocol page has the equivalent settings:

  • ISA11 Usage: Choose Standard identifier or Repetition separator

  • Control Version Number (ISA12)

  • Usage Indicator

In BizTalk Server, you select the transaction type. In BizTalk Services, you select the schema for which these envelope settings should be applied.

Character set and separators

  • Character set to be used

  • Data element

  • Component element separator (ISA16)

  • Segment terminator

  • Suffix: None, CR, LF, CR LF

  • Replace separators in payload with

The Protocol page has the equivalent settings:

  • Character Set to be used

  • Data Element Separator

  • Component element separator

  • Segment Terminator

  • Suffix

  • Replace separators in payload with

Local Host Settings

  • Interchange Control Number (ISA13)

  • Group Control Number (GS06)

  • Transaction Set Control Number (ST02)

The Protocol page has the equivalent settings:

  • Interchange Control Number (ISA13)

  • Group Control Number (GS06)

  • Transaction Set Control Number (ST02)

  • Prefix: Equivalent to the starting number.

  • Suffix: Equivalent to the ending number.

Validation

  • Interchange Control Number

    Check for duplicate ISA13 within the following number of days

  • Group Control Number

  • Transaction Set Control Number

No equivalent configuration.

Batch Configuration

New Batch:

  • Identification: Batch name and Batch description

  • Filter

  • Release: Schedule, Maximum number of transactions sets in, Maximum number of characters in an interchange and External release trigger

  • Activation: Start immediately

  • Termination: No end date, End after and End by

The Batching page has the equivalent settings:

  • Name

  • Description

  • Count: Similar to Release.

  • Deploy: Equivalent to Activation. When the Agreement is deployed, the Batch is started.

  • Delete Batch: Equivalent to Termination. When a Batch is deleted and the Agreement is redeployed, the Batch is removed.

Send Ports

Send ports

The Transport page has the equivalent settings, which include sending the message to Service Bus, BizTalk Services bridge, Microsoft Azure blob destinations, an HTTP URL, an FTP server or an AS2 transport.

Transaction Set Settings

Task

BizTalk Server setting

BizTalk Services replacement

Transaction Set List

  • Support Transaction Sets from the List

  • Exclude Transaction Sets from the List

No equivalent configuration. On the other hand, the equivalent is implicit because only the message types configured in the X12 Agreement (Send Settings, Schemas) are allowed. Messages corresponding to other message types are suspended.

Validation

  • Default

  • Transaction Type

  • Edi Type Validation

  • Extended Validation

  • Allow Leading & Trailing Spaces & Zeroes

  • Trailing Separators

The Protocol page has the equivalent settings:

  • EDI Validation: Equivalent to Edi Type Validation in BizTalk Server.

  • Extended Validation

  • Allow leading/trailing zeroes

  • Trailing separator

No equivalent configuration for the following BizTalk Server settings:

  • Default

  • Transaction Type

  • Default

Local Host Settings

Configured in Receive.

No equivalent configuration.

Envelopes

  • Default

  • Transaction Type

  • Version/Release

  • Target namespace

  • GS1

  • GS2

  • GS3

  • GS4

  • GS5

  • GS6

  • GS7

  • GS8

The Protocol page has the equivalent Schemas option.

To summarize on how to add X12 Send settings:

AS2 Agreements

Add an Agreement: AS2 General settings

This table lists the different tasks involved when adding an agreement and configuring “General” settings. It lists the “agreement” tasks in BizTalk Server and the replacement “agreement” settings in BizTalk Services.

Task

BizTalk Server

BizTalk Services

Create an agreement: General

A profile is required to create an agreement. In BizTalk Administration, right-click the profile and create a new agreement. This option displays the following properties:

  • General Properties: Includes the agreement name, the AS2 protocol, the First Party, the Second Party, enabling the agreement and logging.

  • Contact Information: The contact details.

  • Additional Properties: Include any name-value pair.

Configuring General Party Properties (AS2) provide the steps to edit these properties.

No identifiers are configured in the General properties in BizTalk Server.

A profile is required to create an agreement. In the BizTalk Services Portal home page, click Agreements and then click the AS2 tab. The General tab is opened and displays the following properties:

  • Agreement name

  • Agreement Description

  • Hosted Partner: Equivalent to First Party.

    AS2 Identity: Equivalent to AS2-From and AS2-To in BizTalk Server.

  • Hosted Partner Qualifier and Value.

  • Guest Partner: Equivalent to Second Party.

    AS2 Identity: AS2 Identity: Equivalent to AS2-From and AS2-To in BizTalk Server.

  • Guest Partner Qualifier and Value.

  • Track Send side message properties

    In BizTalk Server, errors can be logged when EDI reporting is enabled.

  • Track Receive side message properties

    In BizTalk Server, errors can be logged when EDI reporting is enabled.

See Create an AS2 Agreement in Azure BizTalk Services.

To summarize on how to add AS2 General settings:

Add an agreement: AS2 Receive settings

Warning

If you click another tab while creating the agreement, the agreement settings are not saved.

This table lists the different tasks involved when adding an agreement and configuring “Receive” settings. It lists the “agreement” tasks in BizTalk Server and the replacement “agreement” settings in BizTalk Services.

Task

BizTalk Server setting

BizTalk Services replacement

Receive Properties Location

When you click OK in the Agreement General Properties, two new tabs display: First Party->Second Party and Second Party->First Party.

The Second Party->First Party is the Receive.

In the BizTalk Services Portal home page, click Agreements, click the AS2 tab, and then Create Agreement. The General Settings are opened, which are previously described. When the General Settings are added, click Continue to display the Receive properties.

Identifiers

  • AS2-From

  • AS2-To

Equivalent to AS2 Identity in the General Settings.

Validation

  • Use agreement settings for validation and MDN instead of message header

  • Message should be signed

  • Message should be compressed

  • Message should be encrypted

  • Check Certification Revocation List on receipt of message

  • Check for duplicate messages within the following number of days

Following are the equivalent configuration settings:

  • Override receive side agreement settings with those in the incoming AS2 message

  • Message should be signed

  • Message should be compressed under

  • Message should be encrypted

No equivalent configuration for the following BizTalk Server settings:

  • Check Revocation List

  • Check for duplicate messages

Acknowledgements (MDNs)

In BizTalk Server, the following acknowledgment options are telling the sending party to include the MDN. Another way of saying this is that receiving party is “requesting” the MDN.

  • Process inbound MDN into MessageBox for routing/delivery options

  • Request MDN

  • Request signed MDN

  • Request asynchronous MDN, including the Receipt-Delivery Option URL

  • Receipt-Delivery Option URL

  • Resend AS2 message if MDN not received

  • Override send port settings

  • Disposition-Notification-To

In BizTalk Services, acknowledgment messages are sent from the managed partner to the unmanaged partner (based on the Transport URL in the Send Settings). MDN options include:

  • MDN Text

  • Send MDN

  • Send signed MDN

  • Send asynchronous MDN

  • Receive URL Settings, which includes the URL scheme (HTTP or HTTPS) and the URL Suffix. This option is equivalent to the Receipt-Delivery Option URL in BizTalk Server.

No equivalent configuration for the following BizTalk Server settings:

  • Process inbound MDN into MessageBox for routing/delivery options

  • Resend AS2 message if MDN not received

  • Override send port settings

  • Disposition-Notification-To

Local Host Settings

  • General

  • Receiver MDN Settings

  • HTTP Settings for Messages

  • HTTP Settings for MDNs

  • Sender Message Tracking(NRR)

  • Receiver Message Tracking(NRR)

No equivalent configuration. Tracking is enabled at the General Settings.

Signature Certificate

  • Override group signing certificate

No equivalent configuration. Certificates are added when a partner is configured. See Manage Partners and Profiles in Azure BizTalk Services.

Send Ports

Configured in Send.

In the Route Settings tab, you can route to the following:

  • BizTalk Services bridge

  • Microsoft Azure blob

  • Service Bus

To summarize on how to add AS2 Receive settings:

Add an agreement: AS2 Send settings

Warning

If you click another tab while creating the agreement, the agreement settings are not saved.

This table lists the different tasks involved when adding an agreement and configuring “Send” settings. It lists the “agreement” tasks in BizTalk Server and the replacement “agreement” settings in BizTalk Services.

Task

BizTalk Server setting

BizTalk Services replacement

Send Properties Location

When you click OK in the Agreement General Properties, two new tabs display: First Party->Second Party and Second Party->First Party.

The First Party->Second Party is the Send.

In the BizTalk Services Portal home page, click Agreements, click the AS2 tab, and then click Create Agreement. The General Settings are opened, which are previously described. When the General Settings are added, click Continue and then click the Send tab to display the Send properties.

Identifiers

  • AS2-From

  • AS2-To

Equivalent to AS2 Identity in the General Settings.

Validation

  • Message should be signed

  • Message should be compressed

  • Message should be encrypted

  • Check Certification Revocation List on receipt of message

  • Check for duplicate messages within the following number of days

Following are the equivalent configuration settings:

  • Enable Message signing

  • Enable message encryption

  • Enable message compression

No equivalent configuration for the following BizTalk Server settings:

  • Check Revocation List

  • Check for duplicate messages

Acknowledgements (MDNs)

In BizTalk Server, the following acknowledgment options are telling the sending party to include the MDN. Another way of saying this is that receiving party is “requesting” the MDN.

  • Process inbound MDN into MessageBox for routing/delivery options

  • Request MDN

  • Request signed MDN

  • Request asynchronous MDN

  • Receipt-Delivery Option URL

  • Resend AS2 message if MDN not received

  • Override send port settings

  • Disposition-Notification-To

In BizTalk Services, this setting configures the agreement to send MDN receipts to the sender on the original AS2 message after the message has been delivered. MDN options include:

  • Request MDN

  • Request signed MDN

  • Request asynchronous MDN

  • Transport Settings: This option is equivalent to the Receipt-Delivery Option URL in BizTalk Server.

No equivalent configuration for the following BizTalk Server settings:

  • Process inbound MDN into MessageBox for routing/delivery options

  • Resend AS2 message if MDN not received

  • Override send port settings

  • Disposition-Notification-To

Local Host Settings

  • General

  • Receiver MDN Settings

  • HTTP Settings for Messages

  • HTTP Settings for MDNs

  • Sender Message Tracking(NRR)

  • Receiver Message Tracking(NRR)

No equivalent configuration. Tracking is enabled at the General Settings.

Signature Certificate

  • Override group signing certificate

No equivalent configuration. Certificates are added when a partner is configured. See Manage Partners and Profiles in Azure BizTalk Services.

Send Ports

Send ports

No equivalent configuration.

To summarize on how to add AS2 Send settings:

Summary Overview:

BizTalk Server “Enable” and BizTalk Services “Deploy

In BizTalk Server, when an Agreement is configured, you Enable the agreement in BizTalk Administration by right-clicking the Agreement and clicking Enable. In BizTalk Services when the Agreement is configured, you Deploy the agreement in the BizTalk Services Portal home page by clicking Deploy.

To summarize deploying the agreement:

  • In BizTalk Server, you Enable an agreement in BizTalk Administration. See How to Enable or Disable an Agreement.

  • In BizTalk Services, you Deploy an agreement in the BizTalk Services Portal.

See Also

Configuring EDI, AS2, and EDIFACT on BizTalk Services Portal
EDI, AS2, and EDIFACT Messaging (Business to Business)