Third-Party & Non-Dynamics Integration: Connecting Salesforce, SAP, Shopify & More to D365

The Third-Party Integration Landscape

Dynamics 365 exists in a complex ecosystem. Most organizations don’t run D365 in isolation—it sits alongside Salesforce for enterprise CRM, SAP for manufacturing and supply chain, Shopify for e-commerce, Workday for HR payroll, and countless other mission-critical systems. The 2026 integration landscape is fundamentally different from five years ago: cloud-native connectors, Power Automate’s maturity, Azure Logic Apps reliability, and the rise of intelligent iPaaS platforms have made multi-system architectures the default rather than the exception.

This article covers the practical patterns and tools for integrating D365 with non-Microsoft systems. We’ll examine native connectors, when to use Power Automate versus Logic Apps versus enterprise iPaaS, and real-world scenarios from companies running hybrid Microsoft & non-Microsoft environments.

Shopify & Business Central: The Native E-Commerce Integration

The Connector Landscape

The Shopify connector for Dynamics 365 Business Central is one of Microsoft’s most mature pre-built integrations. It syncs core e-commerce data automatically: products, inventory levels, customer records, sales orders, and fulfillment status. For mid-market retailers and DTC brands, this is the path of least resistance.

What Data Syncs

Products & Catalog: Product master data flows from Business Central to Shopify. Item numbers, descriptions, SKUs, pricing, and categories sync bidirectionally. Shopify becomes the storefront; Business Central remains the source of truth for inventory and cost.

Inventory Sync: Inventory levels update in near-real-time (typically within 5-15 minutes). Business Central quantities automatically adjust based on Shopify orders; Shopify stock is reserved when orders are placed. This prevents overselling in distributed fulfillment scenarios.

Orders & Customers: When a customer purchases on Shopify, the order appears in Business Central within minutes. Customer records sync to D365 (name, email, shipping address, payment method). Sales order line items, discounts, and taxes flow through. This enables fulfillment teams to print picking slips directly from Business Central.

Fulfillment & Returns: Posted shipments in Business Central sync back to Shopify, updating order status automatically. Customers see tracking numbers in their Shopify account. Returns are handled via Shopify’s native returns management, with credit memos created in Business Central.

Setup & Configuration

Configuration is straightforward for retailers without complex requirements:

1. Install the “Shopify Channel” extension from AppSource into your Business Central environment
2. Generate Shopify API credentials (create a custom app in Shopify admin)
3. Authenticate the connector and map product categories, customer groups, and general ledger accounts
4. Configure sync frequency (hourly, daily, or manual) and choose which fields to sync
5. Run initial bulk sync for historical products and customers

The configuration interface is point-and-click; no custom code required. For most mid-market retailers, setup takes 1-2 weeks including data validation.

Limitations & When to Augment

The native Shopify connector handles 80% of standard retail operations, but organizations with complex requirements should plan enhancements:

• Multi-Channel: The connector focuses on Shopify. If you sell on Amazon, WooCommerce, or Etsy simultaneously, you’ll need additional integration infrastructure (see E-Commerce Beyond Shopify section).
• Custom Fields: Shopify custom metafields require Power Automate flows to map into Business Central custom fields.
• Advanced Inventory: The connector doesn’t handle lot tracking, serial numbers, or advanced warehouse management scenarios. Manufacturing businesses need additional Warehouse Management System (WMS) integration.
• Marketplace Fees: Shopify transaction fees, Shopify Payments, and third-party payment processing require separate general ledger mapping—the connector doesn’t automate this.
• Subscriptions: Shopify subscriptions (recurring orders) aren’t natively supported; augment with custom Power Automate flows to create recurring sales orders in Business Central.

D365 Commerce vs. Shopify + Business Central

Organizations often ask: should we use D365 Commerce instead? Here’s the practical distinction:

Choose Shopify + Business Central if: You want a best-of-breed storefront (Shopify is superior for UX, conversion, and marketing apps), your IT team is small, you prefer SaaS headache-free operations, and your product catalog is under 100,000 SKUs.

Choose D365 Commerce if: You need tight ERP-to-storefront integration, want a unified admin experience, have complex B2B portal requirements, or manage sophisticated omnichannel operations (stores + eCommerce + call centers).

Salesforce & Dynamics 365: The CRM-to-ERP Bridge

Integration Patterns

Salesforce and Dynamics 365 often coexist in large enterprises. Common scenarios include:

CRM-to-ERP (Most Common): Salesforce drives sales pipeline, forecasting, and customer engagement. When opportunities close, the order flows to Dynamics 365 for fulfillment, invoicing, and financial consolidation. This pattern works well when sales processes differ significantly from operations.

Co-Existence: Enterprise divisions run Salesforce for CRM and Business Central for finance & operations, with master data living in D365. This is common post-acquisition when legacy Salesforce deployments are preserved but centralized on Microsoft ERP.

Migration Planning: Companies moving from Salesforce CRM to D365 Customer Engagement typically run parallel systems for 6-12 months. Historical customer data syncs, transactions flow to legacy Salesforce until cutover, then D365 becomes the primary CRM.

Technical Integration Methods

Power Automate Salesforce Connector: Microsoft’s official Salesforce connector enables real-time flows without custom code. When an opportunity closes in Salesforce, a Power Automate flow creates a sales order in Dynamics 365. When an invoice is posted in D365, the flow updates the Salesforce opportunity status to “Closed Won” and updates revenue fields. This is the fastest path to integration and requires no middleware.

Custom Middleware: For complex data mapping or high transaction volume, organizations build Azure Functions or Logic Apps that transform Salesforce data structures into D365 models. Example: Salesforce “Quote” objects need to map to D365 “Sales Orders,” with line items, pricing rules, and tax calculations applied during the transformation.

Data Model Mapping: Salesforce and D365 use different data schemas. Salesforce’s Account/Contact/Opportunity model differs from D365’s Customer/Contact/Sales Order model. During implementation, define which Salesforce objects map to which D365 tables, and plan for field mapping (e.g., Salesforce Amount → D365 Order Total).

Real-World Example: SaaS to Services Delivery

A B2B SaaS company uses Salesforce to track software subscriptions and Dynamics 365 for professional services delivery and billing. When a customer buys a services engagement in Salesforce, a Power Automate flow automatically creates a project in D365 Project Operations, allocates resources, and sets project budget based on the Salesforce quote. As work is logged in D365, the flow updates Salesforce forecasted revenue. This automation eliminates manual order entry and keeps both systems in sync.

SAP & Dynamics 365: Enterprise Manufacturing Integration

The Azure Logic Apps SAP Connector

For organizations running both SAP and D365, the Azure Logic Apps SAP connector is the enterprise standard. It communicates via RFC (Remote Function Call), BAPI (Business Application Programming Interface), and IDoc (Intermediate Document) protocols—the native SAP integration methods.

Common SAP + D365 Scenarios

SAP for Manufacturing, D365 for CRM & Finance: This is extremely common in discrete manufacturing. SAP manages Bills of Material, production orders, shop floor scheduling, and material requirements. D365 Dynamics Customer Engagement handles sales pipeline and opportunities; D365 Finance & Operations manages accounts receivable, general ledger, and financial reporting. Master data (customers, products, GL accounts) syncs bidirectionally via Logic Apps.

D365 Replacing SAP Finance: Some organizations move finance from SAP to Dynamics 365 while keeping SAP for manufacturing. This requires a phased approach: goods receipt, production orders, and inventory transactions remain in SAP; D365 receives cost data and inventory postings via IDoc feeds. Accounts payable, accounts receivable, and GL all run in D365.

Master Data Hub: Large enterprises maintain a master data governance layer (often in a dedicated MDM system) that syncs to both SAP and D365. Customer master, product master, supplier master, and GL structure live in one place; Logic Apps distribute changes to both systems asynchronously.

Integration Architecture

A typical SAP + D365 setup looks like this:

1. Azure Logic Apps orchestrate the integration
2. SAP Gateway (Cloud Platform Integration / SAP Cloud Connector) manages authentication and security between Azure and SAP ECC/S/4HANA
3. IDocs or RFCs are the message format (IDocs for asynchronous batch transfers, RFCs for synchronous calls)
4. D365 API endpoints receive the transformed data
5. Error handling & retry logic ensures no transactions are lost
6. Monitoring dashboards track sync health

For organizations with SAP on-premises, Azure Hybrid Connection or VPN is required for secure connectivity. SAP Cloud Connector is the recommended secure bridge.

ServiceNow & Dynamics 365: ITSM & Customer Service Alignment

ServiceNow is the dominant ITSM platform; Dynamics 365 Customer Service is a rising competitor. Many enterprises run both:

• Incident Sync: Critical incidents in ServiceNow automatically create high-priority cases in D365 Customer Service for immediate escalation.
• Knowledge Base Sharing: Articles from D365 Knowledge Management sync to ServiceNow’s knowledge base so agents across both platforms access the same current information.
• Change Management: Service requests in ServiceNow can trigger approval workflows in D365 Dynamics, ensuring business rules are enforced across platforms.

Power Automate’s ServiceNow connector makes this straightforward. Configuration takes 2-4 weeks for basic incident/case sync.

Workday & Dynamics 365: HR & Payroll Integration

Workday owns enterprise HR & payroll; D365 HR handles some HR scenarios but isn’t a payroll system. Organizations using both need tight integration:

• Employee Master Sync: New hires in Workday create employee records in D365, updating org charts, cost centers, and project assignments automatically.
• Payroll Data: Salary information, tax withholding, and benefits flows from Workday to D365 Finance for payroll expense allocation.
• Absence & Leave: Workday leave data syncs to D365 to adjust project availability and resource planning.

Azure Logic Apps Workday connector (or the Workday API) is the integration mechanism. Most implementations take 6-12 weeks including testing and data validation.

Banking & Financial Systems Integration

Finance teams need tight integration with banking infrastructure:

Direct Bank Feeds: Many banks (Wells Fargo, Bank of America, Chase) offer direct bank feeds into Dynamics 365. Bank transactions download automatically into bank reconciliation, eliminating manual data entry and enabling real-time cash position visibility.

Payment Gateways: Organizations accepting online payments via Square, Stripe, PayPal, or FirstData need those transactions flowing into accounts receivable. Logic Apps or custom flows transform payment data into D365 cash receipts and customer payments.

ACH & Wire Transfers: For bill payment automation, Logic Apps integrate with ACH/wire transfer providers (FedWire, Nacha). When a vendor invoice is approved in D365, a flow submits the payment for processing, then reconciles when the transfer completes.

EDI & Supply Chain Partner Networks

Organizations with complex supply chains rely on EDI (Electronic Data Interchange) for trading partner communication. Azure Logic Apps B2B module handles this:

• X12 & EDIFACT: The most common EDI standards. Logic Apps transforms D365 purchase orders into X12 850 messages for suppliers and converts supplier’s X12 856 advance shipment notices into D365 expected receipts.
• AS2 Protocol: Logic Apps supports AS2 for secure trading partner file exchange, with built-in encryption and digital signatures.
• Trading Partner Management: Logic Apps includes a trading partner portal where suppliers register, exchange certificates, and configure their EDI agreements.

EDI integration typically takes 8-16 weeks per major supplier due to compliance requirements and data validation.

Shipping, Logistics & 3PL Integration

E-commerce and distribution organizations integrate with shipping carriers and 3PL (Third-Party Logistics) providers:

FedEx & UPS: APIs for shipment creation, label generation, and tracking. When D365 posts a packing slip, a flow creates shipment records with FedEx/UPS, generates labels, and updates tracking in D365 so customers see real-time information.

ShipStation: Popular among mid-market e-commerce companies. ShipStation syncs orders from multiple channels (Shopify, WooCommerce, Amazon, eBay) and creates shipments. D365 integration tracks fulfillment status and updates inventory.

3PL Systems: Companies like XPO, Geodis, and C.H. Robinson operate proprietary TMS (Transportation Management Systems). Custom Logic Apps integrations sync shipment requests from D365 and receive back tracking and delivery confirmation data.

E-Commerce Beyond Shopify: Multi-Channel Retail

Retailers selling across multiple channels face inventory and order management complexity:

Magento: Open-source e-commerce platform popular with large retailers. Magento REST API enables order and inventory sync via Logic Apps or iPaaS.

WooCommerce: WordPress-based e-commerce, common for SMB retailers. WooCommerce API syncs with D365 Business Central similarly to Shopify.

BigCommerce: SaaS competitor to Shopify with strong B2B capabilities. BigCommerce API integrates with D365 for order and catalog management.

Amazon Marketplace: Selling on Amazon requires SP-API (Selling Partner API) integration. Orders appear on Amazon, then sync to D365 for fulfillment. Multi-channel inventory management (real-time deduplication across channels) requires centralized orchestration, typically an iPaaS platform.

Multi-Channel Architecture: For retailers on Shopify + Amazon + WooCommerce + physical stores, a centralized order management system (often Celigo, which specializes in retail iPaaS) orchestrates inventory across all channels and creates orders in Business Central.

iPaaS Platforms: MuleSoft, Boomi, Workato & Celigo

When to Use iPaaS vs. Azure Native

As of 2026, Azure native solutions (Logic Apps, Power Automate) are excellent for point-to-point integrations and moderate complexity. iPaaS platforms excel when you have:

• 10+ source systems requiring orchestration
• Complex data transformation or business rule engines
• High transaction volume (1000s per day) requiring optimization and scalability
• Multi-tenancy requirements (SaaS companies integrating customer systems)
• Existing non-Microsoft cloud infrastructure (AWS, GCP) where Logic Apps isn’t available
• Teams preferring dedicated iPaaS support and governance

Platform Comparison

MuleSoft (Salesforce): Enterprise-grade iPaaS with advanced API management, data transformation, and event-driven architecture. Best for large enterprises; significant licensing cost. Strong in Salesforce-centric environments.

Dell Boomi: Cloud-native iPaaS with excellent connector library (1000+). Known for ease of use and rapid deployment. Popular mid-market choice. Competitive pricing.

Workato: Modern iPaaS with AI-assisted workflow builder. Strong in HR & finance scenarios. Growing adoption among mid-market companies. Good Dynamics 365 connectors.

Celigo (itegration.cloud): Specializes in Dynamics 365 & NetSuite integrations. Purpose-built for Dynamics scenarios. Excellent for retail, manufacturing, and B2B scenarios. Smaller connector library but deep Dynamics expertise.

Licensing & ROI

iPaaS licensing is typically per-transaction or per-user. For a mid-market company integrating 5 systems, Logic Apps usually costs $100-300/month; a dedicated iPaaS platform may cost $1000-5000/month but may reduce implementation time by 30-40%. Calculate ROI based on implementation labor and ongoing support costs.

AppSource & ISV Connectors

Microsoft’s AppSource marketplace includes 500+ pre-built Dynamics 365 connectors from independent software vendors (ISVs). These range from vertical-specific solutions (e.g., “Manufacturing ERP Connector for Plex”) to horizontal integrations (e.g., “Stripe Payment Processor”).

Advantages: Faster deployment, pre-built logic, vendor support, automatic updates.

Disadvantages: May not fit exact requirements, potential vendor lock-in, licensing costs stack with other software.

Best Practice: Always search AppSource first before building custom integrations. Many vendors have already solved your problem.

Integration Security & Governance

Authentication: Use OAuth, API keys, or managed identities rather than username/password. Logic Apps managed identities eliminate credential management.

Encryption: All data in transit should use TLS 1.2+. Data at rest should be encrypted in the source and target systems.

Audit & Compliance: Log all integration transactions for audit trails. Most organizations require 7-year retention for compliance (SOX, GDPR, etc.). Azure Monitor and Application Insights provide this visibility.

Change Control: Treat integrations like code—version control, peer review, staging environments, and production deployment gates should be standard.

Common Integration Challenges & Solutions

Challenge: Data Drift Between Systems When source and target data diverge (e.g., customer email changes in one system but not the other), reconciliation becomes complex. Solution: Implement master data governance and define a system of record for each entity type.

Challenge: Latency & Real-Time Requirements Some processes need sub-minute latency; others can tolerate daily batch synchronization. Solution: Use event-driven architecture (webhooks, message queues) for real-time, batch processes for tolerance scenarios.

Challenge: Exception Handling 5-10% of integrations typically fail (invalid data, network errors, business logic violations). Solution: Build exception queues, alerting, and manual resolution workflows. Don’t assume 100% success.

Challenge: Scaling Integration Load As transaction volume grows (10x in a year), point-to-point integrations become difficult to maintain. Solution: Plan for iPaaS or upgrade to Logic Apps Standard tier for better scalability.

Key Takeaways

• Most enterprise Dynamics 365 deployments require integration with 5-15 third-party systems. The integration landscape is mature and well-tooled.
• For simple point-to-point scenarios (Shopify + BC, Salesforce + D365), Power Automate is sufficient and cost-effective.
• For complex multi-system orchestration, iPaaS platforms (MuleSoft, Boomi, Workato, Celigo) are worth the investment.
• Always search AppSource first—many integrations already exist.
• Plan for exception handling, master data governance, and audit compliance from day one.