Dynamics 365

Dynamics 365 is a suite of interconnected business applications that spans ERP and CRM functionality. The main modules include Business Central (accounting, inventory, project management for SMBs), Finance (enterprise financial management), Supply Chain Management, Sales, Customer Service, Field Service, and Marketing. Each module can be licensed independently or combined.

The platform is built on Microsoft Dataverse (formerly Common Data Service), which provides a shared data layer across all Dynamics 365 apps and integrates tightly with the Power Platform (Power BI, Power Automate, Power Apps). This means data flows naturally between your CRM, ERP, and reporting tools without complex middleware.

Business Central is the most relevant module for small to mid-sized businesses. It handles core accounting, inventory, purchasing, and project management. It's essentially the cloud successor to Dynamics NAV (Navision), which had a strong following in the mid-market for decades. The larger Finance and Supply Chain modules are aimed at enterprises with more complex needs.

Dynamics 365 licensing is notoriously complex. Each application has its own per-user, per-month pricing, and there are different licence types depending on the level of access needed.

Business Central, the most relevant module for SMBs, starts at around $80/user/month for Essentials (core financials, supply chain, project management) and $110/user/month for Premium (adds manufacturing and service management). Team Member licences for light users are about $8/user/month.

For Sales, pricing ranges from roughly $65/user/month at the Professional tier up to $135/user/month for Enterprise. Customer Service follows a similar structure. AI features through Copilot typically add $50/user/month on top.

The real cost picture includes implementation, which runs $30,000 to $85,000+ for SMBs depending on complexity, plus ongoing support and maintenance. Microsoft also offers a first Dynamics 365 app at full price with subsequent apps at a reduced rate, which helps if you're buying multiple modules. Budget for the total cost of ownership, not just the licence fees.

Vendor lock-in risk is significant and growing. Dynamics 365 is designed to work best within the Microsoft ecosystem, and many of its advantages come from tight integration with Azure, Office 365, and the Power Platform. The more you lean into these integrations, the more costly and complex a migration becomes.

Microsoft's recent moves to deprecate independent data export tools (Export to Data Lake, BYOD limitations) in favour of their own analytics platforms (Fabric, Synapse Link) increase this dependency. Your transactional data is exportable through the API or Excel, but your workflow automations, custom apps, Power Automate flows, and reporting dashboards are deeply tied to the Microsoft stack.

For businesses that are already committed to Microsoft as their technology partner, this lock-in may be acceptable. The ecosystem is broad enough that you can do most things within it. But if you value the flexibility to mix and match best-of-breed tools, or if you might want to switch platforms in 3-5 years, factor the switching cost into your decision.

Microsoft needs no introduction. Founded in 1975 and publicly traded on NASDAQ, it's one of the most valuable companies on Earth with over 220,000 employees. The Dynamics product line dates back to 2001 when Microsoft acquired Great Plains Software, followed by Navision in 2002. These acquisitions formed the foundation of what became Dynamics 365 when Microsoft unified its ERP and CRM products under one cloud-based brand in 2016.

The Dynamics 365 business is growing strongly. Revenue increased 24% in FY2024, and the broader Dynamics services market is projected to grow at roughly 13% annually through 2030. Microsoft is investing heavily in AI capabilities through Copilot integration across the platform. This is about as stable and well-resourced as business software gets. The company isn't going anywhere, and the product line has clear strategic importance within Microsoft's portfolio.

The Dynamics 365 API is built on Microsoft Dataverse and uses OData-based REST endpoints. It's a mature API that covers virtually all functionality across the platform, and Microsoft has invested heavily in documentation through Microsoft Learn.

Rate limits are structured differently depending on which part of Dynamics 365 you're working with. Business Central allows around 40,000 API requests per user per day for licensed users. Finance and Operations apps use a sliding-window approach that caps at roughly 6,000 requests per 5-minute window. In practical terms, these limits are adequate for normal operations but can become a constraint if you're doing large data migrations or heavy batch processing. You'll need to build in retry logic and queue management for high-volume scenarios.

The Power Platform provides a lower-code integration path through Power Automate (workflow automation) and custom connectors, which can be a good option for simpler integrations that don't justify full API development. For more complex needs, the Dataverse API gives you fine-grained control.

Webhooks are well-supported through Dataverse. You can register webhook endpoints that fire on create, update, and delete events for any entity. Setup is straightforward through the Plugin Registration Tool or Power Platform admin centre. There's a 60-second timeout on webhook calls, so your receiving endpoint needs to be responsive. Business Central also supports subscription-based webhooks for its API resources.

Data portability is a mixed bag. On the positive side, you can export data to Excel, CSV, and XML from most areas of the application, and the API gives you programmatic access to pull your data out. Dataverse data can be synced to Azure Data Lake or Microsoft Fabric for analytics and archival.

However, Microsoft has been shifting its data export strategy. The Export to Data Lake feature for Finance and Operations was deprecated in 2023 and fully decommissioned in March 2025, pushing users toward Azure Synapse Link or Microsoft Fabric. The Bring Your Own Database (BYOD) option is increasingly limited too. This means your data export path is becoming more dependent on Microsoft's cloud ecosystem, not less.

For a straightforward exit scenario, you can get your core data out through the API or Excel exports, but complex configurations, workflows, and customisations won't come with you. The deeper you go into the Microsoft ecosystem, the harder it becomes to leave.

Documentation quality is genuinely good. Microsoft Learn provides extensive, well-organised documentation covering the API, development patterns, customisation, and deployment. There are code samples, tutorials, and architecture guides available.

Sandbox environments are available for both Business Central (cloud-hosted, included with your licence) and other Dynamics 365 apps (through the Power Platform admin centre). You can copy production data into a sandbox for realistic testing, which is a real plus for development work.

The downside is complexity. The Dynamics 365 development ecosystem spans multiple tools and frameworks: AL language for Business Central extensions, X++ for Finance and Operations, and the Power Platform for low-code development. There's a lot to learn, and the tooling can feel fragmented if you're used to simpler platforms. Visual Studio Code with the AL extension is the primary development environment for Business Central work. Overall, experienced developers will find the platform capable but demanding. Newcomers should expect a significant ramp-up period.