An Azure service that automates the access and use of data across clouds without writing code.
Hello @Wagner Matthias
Yes, the old Microsoft/Integration GitHub path you referenced is currently unavailable. At the moment, I also can't find an official Microsoft announcement stating whether the repository has been permanently removed, relocated, or made private, so I wouldn't assume that a new GitHub location exists unless Microsoft publishes one.
For Microsoft-supported BizTalk EDI schemas, the supported source is the schema package included with BizTalk Server, not the old GitHub repository.
If you have BizTalk Server installed with Developer Tools and SDK, look under:
C:\Program Files (x86)\Microsoft BizTalk Server <VERSION>\XSD_Schema\EDI
and run: MicrosoftEdiXSDTemplates.exe
This self-extracting package contains the EANCOM, EDIFACT, HIPAA, and X12 schema sets.
One detail worth clarifying is what you mean by the “latest EDIFACT schemas.”
BizTalk's packaged schemas represent the EDIFACT versions/releases that Microsoft provides and supports with that BizTalk Server build. They should not necessarily be interpreted as a continuously updated mirror of every newer UN/EDIFACT directory published by UNECE.
The EDIFACT schema naming convention is: <Encoding><Version><Release><Doctype>, for example: EFACT_D98B_ORDERS. BizTalk also uses the EDIFACT version, release, and message type from the interchange to find the appropriate deployed schema.
Therefore, if you're looking for a particular newer EDIFACT directory/message, for example, D.23A ORDERS, D.24A INVOIC, D.25A DESADV, etc., please provide the exact directory release and message type. We can then determine whether that schema is included with the current BizTalk package or whether you need to obtain/create it separately.
Also, if you upgraded BizTalk Server, MicrosoftEdiXSDTemplates.exe is replaced with the version associated with the newer BizTalk installation. I recommend backing up the previous package if you still require its older schemas.
For Azure Logic Apps, once you have the appropriate XSD, you can upload and use it through the Logic Apps schema functionality, as the moderator mentioned.
References:
Post-configuration steps: Install EDI schemas
Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.