Logic Apps and EDI (VI)

Continuing with my series about Logic Apps and EDI, today I will start a "sub-series" about how to use PowerShell and the API Rest, to deploy EDI artifacts to our Enterprise Integration Account.
This post continues the Logic Apps and EDI series of post, that I began weeks ago:

• Logic Apps and EDI (I)
• Logic Apps and EDI (II)
• Logic Apps and EDI (III)
• Logic Apps and EDI (IV)
• Logic Apps and EDI (V)

For full reference, check the Microsoft documentation for Logic Apps:

• REST API
• PowerShell reference

In this post I explain how to deploy our EDI artifacts using PowerShell. We can retrieve information, modify and deploy all our EDI solution Enterprise Integration artifacts with these PowerShell commands:

# SCHEMAS
Get-AzureRmIntegrationAccountSchema
New-AzureRmIntegrationAccountSchema
Set-AzureRmIntegrationAccountSchema

# MAPS
Get-AzureRmIntegrationAccountMap 
New-AzureRmIntegrationAccountMap
Set-AzureRmIntegrationAccountMap

# PARTNERS

Get-AzureRmIntegrationAccountPartner

New-AzureRmIntegrationAccountPartner 

Set-AzureRmIntegrationAccountPartner

# AGREEMENTS

Get-AzureRmIntegrationAccountAgreement

New-AzureRmIntegrationAccountAgreement

Set-AzureRmIntegrationAccountAgreement

For each artifact, we have 3 commands: 

• Get-AzureRmIntegrationAccountXXX: to get information about the artifact
• New-AzureRmIntegrationAccountXXX: to deploy new one
• Set-AzureRmIntegrationAccountXXX: to modify an existing one

For example, to deploy a new partner and then get all the information:

Or we can get all the maps and schemas from our Integration Account:

Or even modify the partners of an agreement:

To deploy new Maps, Schemas and Agreements, is easiest to pass the new file content with the arguments: AgreementContentFilePath, MapFilePath or SchemaFilePath.

This is an example: