I wanted to download the lates BizTalk EDIFACT schemas from the official Microsoft GitHub but the repo is missing

Question

I wanted to download the lates BizTalk EDIFACT schemas from the official Microsoft GitHub but the repo is missing

Wagner Matthias 0

Microsoft had an open repository on GitHub for the BizTalk Schema XSD.

I noticed it yesterday, that the whole repository Integration is missing and not public anymore.

Is there an reason for it?

Full link to the XSD Schemas for EDIFACT:

https://github.com/Microsoft/Integration/tree/master/BizTalk%20Server/Schema/EDIFACT

I can't find any announcement about this, and even on Google, this repository still shows up when you search for BizTalk EDIFACT schemas.

Tejaswini Billakurthi 355 Reputation points Microsoft External Staff Moderator

2026-09-11T12:25:44.07+00:00
Hi @Wagner Matthias ,

Thank you for reaching out to Microsoft Q & A!

The referenced GitHub repository path is currently unavailable, and I couldn't find a public Microsoft announcement confirming whether the repository was removed, relocated, or made private.

To obtain the BizTalk EDI schemas, use the BizTalk Server installation package instead:

Install the Developer Tools and SDK component.

Navigate to C:\Program Files (x86)\Microsoft BizTalk Server \XSD_Schema\EDI.

Run MicrosoftEdiXSDTemplates.exe.

The self-extracting package provides EANCOM, EDIFACT, HIPAA, and X12 schema folders.

For Azure Logic Apps, upload the required EDIFACT XSD to an Integration Account under Settings > Schemas > Add. For Standard Logic Apps, you can also upload schemas directly to the Logic App resource under Settings > Schemas without using an Integration Account.

Microsoft documentation:

Post-configuration steps: Install EDI schemas

EDI document schemas

Add schemas to use with workflows in Azure Logic Apps

If the required schema is not present in the extracted package, please share the specific EDIFACT directory version and message type (for example, D.98A ORDERS or D.16A INVOIC).

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

2 answers

Your answer

Tejaswini Billakurthi 355 Reputation points Microsoft External Staff Moderator

2026-09-11T12:25:44.07+00:00

Hi @Wagner Matthias ,

Thank you for reaching out to Microsoft Q & A!

The referenced GitHub repository path is currently unavailable, and I couldn't find a public Microsoft announcement confirming whether the repository was removed, relocated, or made private.

To obtain the BizTalk EDI schemas, use the BizTalk Server installation package instead:

Install the Developer Tools and SDK component.

Navigate to C:\Program Files (x86)\Microsoft BizTalk Server \XSD_Schema\EDI.

Run MicrosoftEdiXSDTemplates.exe.

The self-extracting package provides EANCOM, EDIFACT, HIPAA, and X12 schema folders.

For Azure Logic Apps, upload the required EDIFACT XSD to an Integration Account under Settings > Schemas > Add. For Standard Logic Apps, you can also upload schemas directly to the Logic App resource under Settings > Schemas without using an Integration Account.

Microsoft documentation:

Post-configuration steps: Install EDI schemas

EDI document schemas

Add schemas to use with workflows in Azure Logic Apps

If the required schema is not present in the extracted package, please share the specific EDIFACT directory version and message type (for example, D.98A ORDERS or D.16A INVOIC).

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

Answer 1

Short Update from my side: I got now the XSD Schemas.

Solution:

Get from the old Business Portal from Microsoft the 2013 Biztalk Server Standard ISO. (Where you can also get Visual Studio)

Mount that ISO and search in it after: MicrosoftEdiXSDTemplates.exe (No installation from Biztalk needed!)

In that ZIP are all the XSD Schemas, you must just exectue that exe.

Please don't use the available 2016 Biztalk Server ISO, which you can find via google, because this ISO is missing that exe.

If you need newer XSD Schemas you can also try the Microsoft 2016 Biztalk Server Standard ISO from the old Buisness Portal.

Answer 2

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:

EDI Document Schemas

Post-configuration steps: Install EDI schemas

EDI Standards Support

EDI Document Schema Support

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.