Troubleshooting Logic Apps X12, EDIFACT schema not found issues

As you attempt to encode an outgoing B2B message with Logic Apps, you sometimes get a 400 Bad Request response with the error message: Message cannot be serialized since the schema http://Contoso.X12810.MSLI.Schemas.AP.X1200401810#X12_00401_810 could not be located. Either the schema is not deployed or multiple copies are deployed. Which we are improving for cases that there…


SOAP services support in Azure Logic App

Fresh off the press, native support for SOAP services in Logic App! This feature builds upon the custom OpenAPI connectors recently released for Logic Apps. You now have the option to create SOAP connectors in Logic Apps, by importing a WSDL file instead of an OpenAPI / Swagger definition. Specifically you can try the Fazio…


Azure Logic App X12 replacing separator characters in payload

Using the B2B X12 connector for Azure Logic App, sometimes the input xml values in the payload has reserved characters which conflict with the X12 encoding that you are attempting. X12 agreement with your external partner defines a segment separator character which then cannot be present as well in the value of the segment. By…


Logic App and B2B Integration Account monitoring solution right from the Azure portal

New in the Azure Marketplace you can now create a Logic App or Integration Account OMS monitoring solution right from the Azure portal, simply searching by the keywords “Logic App”: The Logic Apps Management solution was released to public preview earlier this month (see this blog post).  


Using Google OAuth 2.0 authorization server in Azure API Management

While trying out API Management’s in-preview SOAP to REST capabilities against Google’s AdWords API, I needed to enable Google’s OAuth 2.0 authorization in APIM to connect to the API. While each separately has good documentations and samples, I didn’t find the intersect of someone putting together to two. So here it is, how to use Google…


Logic App, B2B diagnostics logging, monitoring and alerting documentation newly expanded

The documentation writer and our engineering team has recently scrubbed for quality and expanded for holistic coverage our documentation of both Logic App and B2B integration diagnostics logging, monitoring and alerting. The improved documentation was released just last Friday at: Monitor Logic App status Monitor B2B messages Track B2B messages in OMS Query OMS for B2B…


Logic Apps, VNET and other network connectivity

As Logic Apps is a multi-tenant PaaS offering, there isn’t a server instance dedicated to you that you can host or connect to your own VNET. You do have multiple options for network connectivity of Logic Apps: Use Azure API Management as it can be configured to work across VNET. Proxy the calls from Logic…


Whitelisting and Logic Apps

As B2B services move from on-premises servers to Azure Logic App, a recurring question is how to do both inbound and outbound (by the partner) whitelisting with such PaaS approach. On-premises this was easy because each enterprise obtained its own static IP, IPs or IP range. In Azure or any public cloud, the IPs are now…


Logic App Flat File Encoding and Decoding documentation references

For engineers without a BizTalk Server background, the Flat File encoding and decoding may prove a steep ramp up as it is a mature technology with a number of parameters in the XML schema (XSD) describing any given Flat File. The schema used for Logic App Enterprise Integration Flat File Encoding and Decoding is the same as…


EDIFACT Disaster Recovery PowerShell cmdlets

With the upcoming Disaster Recovery trigger and action for the EDIFACT connector, the existing PowerShell cmdlets in Logic App have been updated to handle EDIFACT control numbers as well. This is the relevant excerpt from the change log: […] * LogicApp * New parameters for Interchange Control Number disaster recovery cmdlets: – Optional -AgreementType parameter (“X12”,…