Microsoft Dynamics 365 has become one of the most widely adopted enterprise platforms in Australia. It's not one product - it's a family: Business Central for SME ERP, Finance & Operations for enterprise ERP, Sales for CRM, Customer Service, Marketing, Field Service, and several others. They all sit on Microsoft's Dataverse platform and integrate with the broader Power Platform (Power Apps, Power Automate, Power BI).
The advantage is a deeply integrated Microsoft ecosystem. The challenge is that it's complex, it updates constantly (two mandatory wave updates per year), and customisations need ongoing management. This guide covers what Australian businesses need to know about keeping their Dynamics 365 environment healthy and supported.
The Dynamics 365 Ecosystem
Understanding what's in the Dynamics 365 family helps frame support and upgrade conversations:
Dynamics 365 Products
- Business Central - SME ERP (successor to Dynamics NAV). Finance, supply chain, project management, warehouse. Available as SaaS or on-premises.
- Finance & Operations - Enterprise ERP (successor to Dynamics AX). Large-scale finance, manufacturing, supply chain, HR. Cloud-only (Azure).
- Sales - CRM for sales teams. Opportunity management, forecasting, LinkedIn integration. Built on Dataverse.
- Customer Service - Case management, knowledge bases, omnichannel engagement. Built on Dataverse.
- Marketing - Campaign management, customer journeys, event management. Recently merged with Customer Insights.
- Field Service - Work order management, scheduling, mobile technician apps, IoT integration.
- Power Platform - Power Apps (custom apps), Power Automate (workflows), Power BI (analytics), Power Pages (portals). Deeply integrated with all D365 apps.
Managing Wave Updates
Microsoft releases two major wave updates per year. These are mandatory for cloud environments - you can defer for a limited time, but eventually they roll out. Here's how to manage them:
1. Review the Release Plan
Microsoft publishes detailed release plans months before each wave. Focus on changes to the specific D365 apps you use, deprecated features, and new capabilities that might overlap with your customisations.
2. Early Access Testing
Microsoft offers early access to wave updates in sandbox environments several weeks before GA. Use this window to:
- Test custom plugins and workflow assemblies
- Verify JavaScript web resources on forms
- Check Power Automate flows that reference entity attributes
- Run Canvas and Model-driven apps through key scenarios
- Test integrations with external systems
- Validate Power BI reports and dashboards
3. Remediation
Common issues after wave updates:
- Deprecated APIs - Web API endpoints or SDK methods that have been removed or changed
- Form behaviour changes - Fields, tabs, or sections that render differently or have new validation rules
- Security changes - New security roles or modified default permissions that affect user access
- Performance - New features that are enabled by default and affect page load times or data retrieval
Solution management: Use managed solutions and proper ALM (Application Lifecycle Management) practices. Microsoft's Power Platform CLI and Azure DevOps integration make it possible to version-control and deploy D365 customisations properly. Stop making changes directly in production.
Customisation & Power Platform Management
The Power Platform has made it easy for non-developers to build apps, flows, and reports. That's both a blessing and a curse:
- Power Apps sprawl - Canvas apps built by business users without governance. No documentation, no testing, no lifecycle management.
- Flow complexity - Power Automate flows that start simple and grow into complex multi-step integrations without proper error handling.
- Plugin maintenance - Server-side plugins written in C# that need updating when Dataverse schema changes.
- Dataverse design - Custom tables, columns, and relationships that were added ad-hoc over time without a coherent data model.
- Environment management - Dev, test, UAT, and production environments that have drifted out of sync.
Best Practices
- Use managed solutions for all customisations - never unmanaged in production
- Implement ALM with source control (Azure DevOps or GitHub)
- Establish a Centre of Excellence (CoE) for Power Platform governance
- Document your data model and keep it current
- Set DLP (Data Loss Prevention) policies to control what connectors business users can use
Integration Management
Dynamics 365 integrates with dozens of systems. Common integration patterns in Australian businesses:
- Accounting - If using D365 Sales alongside a separate ERP (Xero, MYOB, NetSuite), you need quote-to-invoice data flow.
- E-commerce - Shopify, Magento, or WooCommerce order sync with D365 Finance or Business Central.
- Marketing - HubSpot, Mailchimp, or D365 Marketing connected to D365 Sales for lead and campaign data.
- Telephony - Teams calling, Genesys, or other phone systems integrated with D365 Customer Service.
- Banking - Bank feed imports and ABA file generation in Business Central or Finance.
- Microsoft 365 - Server-side sync for Outlook, SharePoint document management, Teams integration.
Each integration needs testing during every wave update. The most common failure mode is API changes that break existing connections silently.
How HELLO PEOPLE Can Help
We're a Perth-based software company with 18+ years of enterprise system experience across Australia.
Our Dynamics 365 Services
- Wave update management - Testing, impact analysis, remediation, and production verification for every release.
- Customisation development - Plugins, Power Apps, Power Automate flows, model-driven apps, and Canvas apps.
- Integration development - Connecting D365 to your ERP, e-commerce, marketing, and other systems.
- Power Platform governance - Setting up ALM, CoE toolkit, DLP policies, and environment management.
- Migration - Moving from legacy Dynamics (CRM, AX, NAV) to Dynamics 365 cloud.
- Managed support - Monthly packages covering admin, development, and release management.
Free D365 health check. We'll review your Dynamics 365 environment, customisations, integrations, and governance. Get in touch for an honest assessment.
Frequently Asked Questions
How often does D365 get updated?
Two major wave updates per year (April and October). Minor updates happen more frequently. Wave updates are mandatory for cloud environments.
Will updates break my customisations?
They can. Plugins, web resources, flows, and apps should all be tested during the early access window. The more customised your environment, the higher the risk.
Which D365 product do I need?
It depends on your business. Business Central for SME ERP, Finance & Operations for enterprise ERP, Sales for CRM, Customer Service for support teams. Many businesses use multiple D365 apps together. Talk to us and we'll help you figure out the right combination.
Summary
Dynamics 365 is a powerful ecosystem, but it needs active management. Wave updates, Power Platform governance, integration maintenance, and customisation lifecycle management are ongoing tasks. If your D365 environment has grown complex or you're not getting the value you expected - book a free assessment and we'll help you get it on track.