Connectors
A connector is the transport layer of an integration: the code that moves messages between D365FO and the external location. In the framework, a connector is configured as a Connection type and implemented by a load class (for inbound) or used by an export class (for outbound).
The framework ships with sample connectors for:
| Connector | Typical use | Tutorial |
|---|---|---|
| Azure File Share | File-based exchange with on-premises or legacy systems | File-based integration |
| Azure Service Bus | Message/queue-based near-real-time integration | Service Bus integration |
| SFTP | File exchange with external parties (EDI, banks, 3PL) | Export to SFTP |
| REST / Web service | Direct API integration, inbound and outbound | Event-based export, Sales import |
| AI (LLM) | Recognizing unstructured documents (PDF) | PDF import with AI |
| Manual | Testing, troubleshooting, and user-driven imports | Used in every tutorial |
Credentials
Every connection type stores its credentials in one of three modes: Manual entry (plain text, for development), Encrypted, or Azure Key Vault (recommended for production). See Connection types.
Adding your own connector
Inbound connectors extend the message load infrastructure (DEVIntegMessagesLoad / DEVIntegMessagesLoadBaseType): the load class reads from the source and creates Incoming messages records with the payload attached. Because processing is completely separated from loading, a new connector automatically works with every existing message type.