Microsoft Dynamics 365 in service companies: what the ecosystem solves and where operational inefficiency persists

Over the past few years, Microsoft has built an articulated response to the problem of professional services companies: an ecosystem that connects financial ERP with project management, human resources, business relationships and productivity tools.

Dynamics 365 Finance for the accounting core, Dynamics 365 Project Operations for project management, Power BI for reporting, and Teams and Outlook for collaboration.

It's a solid proposition. And Microsoft knows it: Gartner recognized it as a leader in the Magic Quadrant for Cloud ERP for Service-Centric Enterprises in November 2024 [1]. For many service organizations, the Dynamics ecosystem covers the entire cycle, from business opportunity to billing, with real efficiency.

But there is a type of service company where even that complete ecosystem leaves an operational gap that organizations end up solving with parallel tools: those whose projects are not generic projects, but files with their own logic, specific regulation, external parties that are part of the process and deadlines that have legal or accreditation consequences. This is the case of certification and inspection bodies, regulated auditing firms or organizations with formal verification processes.

This article analyzes what the Dynamics ecosystem solves with real strength, where are the documented limits of Dynamics 365 Project Operations and what is the gap that remains unfilled for organizations with this type of operation.

What the Dynamics ecosystem solves well

The financial layer with native integration into the Microsoft environment

Dynamics 365 Finance manages accounting, financial reporting, project cost control, and tax compliance in multiple jurisdictions with real maturity. The native integration with Power BI allows you to build up-to-date financial dashboards without the need to consolidate spreadsheets.

For the CFO of an organization with operations in several countries, that's a concrete operational advantage.

Project Management with Dynamics 365 Project Operations

Dynamics 365 Project Operations was designed specifically for companies that work on projects: it connects sales, planning, resource allocation, time recording and billing on a single platform [2].

For consulting firms, engineering firms or IT companies that manage time and material or fixed-price projects, Project Operations is a functional answer that eliminates the need for external project management tools not connected to the ERP.

Integrated collaboration with the Microsoft 365 ecosystem

Native integration with Teams, Outlook and SharePoint reduces friction between project management and daily team communication. The professional does not have to change context to record an interaction, update the status of a project, or review associated documentation.

The documented limits of Dynamics 365 Project Operations

Where analysis becomes more nuanced is within the boundaries of Project Operations, which are real and documented both by the clients themselves and by independent consultants in the Microsoft ecosystem.

The dual-write architecture: powerful integration with real technical friction

To integrate project management (which lives in Dataverse, the Power Platform data platform) with finance (which lives in Dynamics 365 Finance), Project Operations uses an architecture of Dual-write: Data is synchronized between two systems in real time [3].

In theory, this provides a unified view. In practice, it means that the team navigates between multiple applications to complete a single project workflow, creating training complexity, synchronization risks, and a more fragmented user experience than the unified platform discourse suggests.

Customers with implementations in mode Stocked —which include material tracking and inventory costs associated with the project— report deficiencies in financial monitoring by period and in planning (Scheduling) for large scale projects [3].

And Project Operations doesn't natively integrate with Dynamics 365 Business Central, Microsoft's ERP for the Mid-market. Organizations that have built their financial core on Business Central don't have a direct path to Project Operations without a migration project or additional integration.

The gap between non-generic sectoral processes

Project Operations was built for the generic professional services project: a business opportunity that becomes a contract, generates assigned tasks and resources, and produces billable deliverables. For that model, it works well.

But there is one type of project that does not fit that model and that Project Operations was not designed to manage: the file with its own regulatory logic. An ISO certification file, an audit of compliance, a verification of emissions under CSRD or a technical inspection report.

These projects have characteristics that differentiate them from the generic project and that no standard project management tool covers natively:

• The phases are not freely configurable tasks: they are determined by the applicable standard, standard or regulation.
• The assigned auditor or inspector is not interchangeable: they must have the specific technical qualification accredited for that type of certification.
• The customer is not only the recipient of the deliverable: he is an active part of the process, providing documentation, answering questionnaires and validating results in intermediate phases.
• And deadlines are not internal commitments: they are regulatory obligations whose non-compliance has consequences on the entity's own accreditation.

The predictable result: the 20% of productivity that ERP does not recover

81 percent of IT leaders say that data silos block their digital transformation initiatives [4].

In service organizations with complete Microsoft architectures, that silo is no longer between financial ERP and project management—Project Operations reduces it significantly. But it persists between project management and industry-specific operational processes.

The gap in workflows between what the ecosystem manages and what teams need to do destroys up to 20% of productivity even in organizations with implemented ERP [5].

In service companies with regulated processes, that 20% is concentrated in three specific areas:

Monitoring the actual status of the file

Project Operations knows that a project exists, what resources are assigned to it and what times have been recorded. But it does not know if the client has submitted the pending documentation, if there is an open non-compliance that is blocking progress or if the regulatory deadline for the file is at risk.

That information—which is what the Chief Operating Officer needs to manage team load and portfolio risk—lives in the auditor's email or in a follow-up spreadsheet that someone updates manually [9].

Documentary coordination with the external client

In certification, auditing or inspection processes, the customer submits documentation at different stages of the process. That documentation needs to be reviewed, can generate comments, and the status of the review must be visible to both the internal team and the customer.

Project Operations does not have a native client portal for this type of document exchange. The exchange occurs by email, with the loss of traceability that this implies in a context where traceability is a requirement for accreditation.

77% of medium-sized companies manage their monitoring and coordination processes via email [6], and in organizations with ENAC accreditation or equivalent, that pattern is not only inefficient: it is a risk in the next accreditation evaluation.

Operational reporting for management

Power BI connected to Dynamics 365 Finance offers real financial visibility. What the Director General needs—how many active records the team has, which are at risk of time, what is the actual use of specialized auditors, what capacity there is to make new commitments—does not come directly from Project Operations, because those sectoral operational data are not in the system [7].

Professionals spend an average of 9.3 hours per week on coordination and manual monitoring [7]. In service organizations with regulated processes, that time is precisely focused on producing the operational visibility that available systems do not automatically generate.

Dynamics 365 Project Operations solves the generic professional services project with real efficiency. What does not solve is the file with regulatory logic: the phases determined by standard, the auditor with accredited qualification, the client as an active part of the process and the deadline with accreditation consequences.

That offset is not a defect in Project Operations. It's the natural limit of any tool designed for the general use case.

Architecture that complements, does not replace

The answer is not to replace the Dynamics ecosystem —which manages the financial core and the generic project well— or to implement a large scale sectoral management system that requires another complex implementation project.

The answer is to build the missing sector-specific operational layer: a tool integrated with Dynamics 365 through its API that captures what the ecosystem doesn't capture.

In practice, this can mean a file management system with the specific phases of the organization's regulatory process, a client portal for traceable document exchange, an engine for assigning auditors by qualification and availability, and an operational dashboard that combines financial data from Dynamics with the actual status of each active file [9].

What these solutions have in common is that they don't replace the Dynamics ecosystem: they rely on it. The financial data is still in Dynamics 365 Finance. Generic resource management continues in Project Operations. The sectoral layer adds the operational visibility that existing systems do not generate [8].

41% of organizations have already created parallel, non-integrated tools to cover these gaps [8]. The difference between that situation and the right architecture is that parallel tools generate new silos, while a well-integrated satellite layer eliminates those that already exist.

Bibliographic references

Methodological note: all external statistics have been verified in their original sources. Reference [9] explicitly points to data based on Yellow Glasses' own experience, distinguishing them from data with an external primary source.

[1]Gartner. (2024). Magic Quadrant for Cloud ERP for Service-Centric Enterprises.Gartner Research, November 2024. https://www.microsoft.com/en-us/dynamics-365/products/project-operations — Microsoft is recognized as a leader in the Gartner Magic Quadrant for Cloud ERP for service-oriented companies, in the November 2024 edition. The report evaluates the execution capacity and comprehensive view of providers in the ERP segment for professional services companies.

[2]Microsoft Corporation. (2025). Dynamics 365 Project Operations: release wave 22024. Microsoft Learn. https://learn.microsoft.com/en-us/dynamics365/release-plan/2024wave2/finance-supply-chain/dynamics365-project-operations/ — Dynamics 365 Project Operations connects sales, project planning, resource management and finance in a single application. The integration architecture with D365 Finance uses dual-write, which means that the team must navigate between multiple applications (Sales and Finance) to complete project workflows. The standard price is $135 per user per month starting in October 2024.

[3]PlanAutomate (formerly Adeaca). (2026). What is Dynamics 365 Project Operations? Enterprise Project Management for Microsoft Dynamics 365 Finance. https://www.planautomate.com/faq-items/what-is-dynamics-365-project-operations/ — The dual-write architecture of Project Operations creates risks of data synchronization and a fragmented user experience between Sales and Finance. Customers with 'stocked' deployments report critical gaps in period financial tracking, costing and planning for large projects. D365 Project Operations does not natively integrate with D365 Business Central.

[4]MuleSoft/ Deloitte Digital/Vanson Bourne. (2024). Connectivity Benchmark Report 2024. https://www.deloitte.com/za/en/services/consulting/perspectives/2024-connectivity-benchmark-report.html — 81% of IT leaders say that data silos block their digital transformation initiatives. The average company manages more than 900 applications, of which only 28% are integrated. In service organizations with multi-system architectures, the silos between the financial ERP, the project management system and the sectoral systems are structural.

[5]ERP News. (2024). Electronic Workflow Process Gaps Kill an Estimated 20% of ERP Productivity. ERP News. https://erpnews.com/electronic-workflow-process-gaps-kill-an-estimated-20-of-erp-productivity/ — Workflow gaps between what ERP manages and what operational teams need to do destroy 20% of productivity in organizations with implemented ERP. In service companies, this gap is concentrated on operational project management and coordination with external clients.

[6]Aberdeen Group. Cited in: FounderJar. (2024). The Ultimate List of ERP Statistics for 2025. https://www.founderjar.com/erp-statistics/ — Only 23% of medium-sized companies use the workflow management features of their ERP. 77% manage their approval, monitoring and coordination processes via email or with non-integrated tools.

[7]McKinsey & Company. (2023). The State of Organizations 2023. McKinsey Global Institute. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-state-of-organizations-2023 — Professionals spend an average of 9.3 hours per week on coordination and manual monitoring processes. In service organizations where the work is on a project-based basis, this cost is concentrated on communicating the status of active projects and on locating dispersed documentation.

[8]PanoramaConsulting Group. (2024). The 2024 ERP Report. Panorama ConsultingGroup. https://4439340.fs1.hubspotusercontent-na1.net/hubfs/4439340/Reports/ERP%20Report/2024-erp-report-panorama-consulting-group.pdf — 80% of the mid-market has ERP in place. 41% of organizations have created parallel tools (shadow IT) to cover gaps that their ERP does not solve. In professional services companies, the processes of project monitoring, assignment of specialized resources and document coordination with clients are those that most frequently generate shadow IT.

[9]Methodological note YG. The gap described between the operational management of sectoral projects (certification files, auditing, specialized consulting) and the native capabilities of standard ERP and project management tools is consistent with the patterns observed by Yellow Glasses in service organizations during diagnostics prior to automation projects. The results vary depending on the sector, regulatory complexity and the number of external parties involved in each project.

‍

‍