What Dynamics 365 Project Service Automation Actually Is (And Why It Matters Now)
Microsoft Dynamics 365 legacy applications include Project Service Automation, which was designed to help service-based organisations manage project lifecycles from quoting to invoicing. This system is now deprecated in the commercial cloud, requiring organisations to transition to modern alternatives.
Here is what you need to know at a glance:
- What it is: A project management application built on Microsoft Dataverse for tracking project-based services.
- Core functions: Project planning, resource forecasting, time and expense tracking, quoting, billing, and reporting.
- Current status: Fully deprecated in the commercial cloud as of 31 March 2025.
- New licence sales stopped: 31 October 2020.
- Who is exempt: Customers on sovereign cloud environments including GCC, GCC High, and DoD.
- Recommended action: Migrate to Dynamics 365 Project Operations as soon as possible.
For many businesses, managing complex project lifecycles without a well-configured system leads to familiar problems. These include resource bottlenecks, cost overruns, disconnected tools, and poor visibility across budgets and timelines. This application was Microsoft’s answer to those challenges for project-centric organisations. Understanding what it offered, and where it stands today, is critical whether you are still running it or planning your next move.
I am Warren Davies, founder of BeyondCRM. As CRM design specialists, we focus on tailoring systems to your industry, business size, operational complexity, and growth stage. We have guided organisations through transitions involving Dynamics 365 Project Service Automation, and we know what is at stake when legacy systems are left unaddressed.
The Core Capabilities of Dynamics 365 Project Service Automation
Dynamics 365 Project Service Automation provides a unified system to manage project delivery, resource scheduling, and financial tracking for professional services firms. It acts as the operational bridge that connects your sales pipeline directly to your project delivery teams.

This legacy platform was designed to manage the end-to-end lifecycle of project-based services. By unifying sales, resource management, project delivery, and billing, it helps service-oriented organisations keep delivery teams aligned with client commitments. Rather than relying on separate spreadsheets and disconnected scheduling tools, teams can track their activities inside a structured platform.
The application supports multiple billing models to accommodate different commercial agreements. These include fixed-price arrangements, time-and-materials contracts, and milestone-based invoicing. By centralising these contracts, project managers can track actual costs against estimated budgets.
Under a unified setup, when a sales representative wins a project contract, the system can automatically generate a corresponding project record. This transition reduces administrative delays and ensures that the delivery team has visibility of the agreed scope, estimated hours, and financial parameters.
Resource Management and Scheduling in Dynamics 365 Project Service Automation
Effective resource management requires balancing consultant availability, skill profiles, and project demands. The system uses a centralised scheduling engine that allows resource managers to search for and book consultants based on specific criteria. These criteria include role requirements, technical skills, and language proficiencies.
Within the system, a comprehensive skills catalog allows you to define characteristics and proficiency levels for every bookable resource. When a project manager outlines a project plan, they can define the resource requirements for each task. The scheduling assistant then analyses the database to suggest the most suitable resources who are available during the required timeframe.
This approach helps prevent over-allocation and ensures that the right expertise is assigned to critical deliverables. To optimise these capabilities, organisations often require advanced Dynamics 365 Customisation to align the skills catalog and approval workflows with their operational structures.
Financial Tracking and Invoicing
Financial governance is built directly into the core architecture of the application through a dual-pricelist model. This model separates internal cost rates from external sales rates, allowing organisations to calculate estimated gross margins.
Every resource role can be assigned multiple cost and sales price lists. These can vary based on the organisational unit delivering the work or the specific geographic region of the customer. The system supports multi-currency project delivery, translating resource costs and billing rates based on the project’s default currency.
For tracking financial performance, the system captures actual costs and revenues as team members submit their time and expense entries. These actual transactions are then used to generate draft invoices and support revenue recognition compliance. This helps organisations align with accounting standards such as ASC 606 and IFRS 15. For deeper financial integration, syncing these project actuals with a robust financial system like Dynamics 365 for Finance is highly recommended.
Technical Architecture and Configuration Components
The technical architecture of this application relies on Microsoft Dataverse to share database schemas, security models, and integration capabilities. This shared foundation ensures that project data is accessible across sales, service, and custom business applications.
At the heart of the system’s architecture are several key tables within Dataverse. These include the organisational unit table, the price list entity, and the project template tables. Together, these tables govern how resource costs are calculated, how project schedules are structured, and how financial transactions are recorded.
Understanding how these backend tables interact is essential for maintaining data integrity and ensuring accurate reporting. For a detailed technical breakdown, you can refer to the Microsoft guide on advanced organisational units.
Setting Up Organisational Units and Price Lists
Organisational units represent the internal divisions, practice areas, or regional offices within your business that have distinct cost structures for billable resources. Each unit is tied to a specific default currency and associated with cost price lists.
When configuring these units, it is crucial to understand the distinction between contracting units and resourcing units:
- Contracting units represent the division that owns the customer contract and manages overall billing.
- Resourcing units represent the division that provides the consultants to perform the project work.
If a project managed by your Australian division utilises an offshore developer, the system resolves the cost based on the resourcing unit’s cost price list. It then bills the client based on the contracting unit’s sales price list. To prevent financial reconciliation errors, we recommend setting up your organisational units as flat lists representing the leaf nodes of your cost-centre hierarchy.
Project Templates and Work Breakdown Structures
Project templates are reusable configurations that allow project managers to quickly initiate new engagements with predefined structures. These templates store the standard work breakdown structure, including task hierarchies, estimated effort, role requirements, and task dependencies.
By utilising a robust work breakdown structure, managers can view project schedules as interactive Gantt charts. The system calculates the critical path and models task dependencies, such as finish-to-start or start-to-start relationships. Effort distribution can be managed across time-phased grids. This allows project leads to see how hours are distributed across days, weeks, or months, rather than assuming a flat distribution. This structured planning helps ensure that project estimates remain realistic and achievable.
Current Status and the Sovereign Cloud Exception
Microsoft officially retired the legacy application in the commercial cloud on 31 March 2025, ending all technical support and security updates. Organisations still running this system must plan an immediate transition to modern alternatives to avoid operational risks.
For commercial customers, the journey toward deprecation began on 31 October 2020, when Microsoft stopped selling new licences for the application. Following years of phased transition support, the commercial cloud lifecycle has now reached its end.
However, there is an exception to this timeline. Customers operating within sovereign cloud environments, including GCC, GCC High, and DoD environments, are exempt from the 31 March 2025 deprecation. In these secure environments, the legacy application remains accessible and supported.
For the official product status and transition announcements, visit the What is Dynamics 365 Project Service Automation? – Microsoft Learn documentation.
Upgrading from Dynamics 365 Project Service Automation to Project Operations
The official upgrade path leads directly to Dynamics 365 Project Operations, combining legacy capabilities with modern scheduling and financial tools.
This modern successor integrates Project for the Web to deliver a more intuitive, web-based scheduling experience. It also introduces advanced features such as AI-driven expense management, interactive resource heatmaps, and tighter integration with Microsoft Teams for project collaboration.
Transitioning to this new platform requires a structured approach to data migration, security role mapping, and customisation refactoring. Engaging a specialist for Dynamics 365 Implementation Consulting helps ensure your historical project data, active contracts, and custom workflows are safely migrated to the modern architecture.
Frequently Asked Questions
This section provides answers to common questions regarding system stability, organisational structures, and data migration for organisations managing their transition. These answers help clarify key differences and technical options during your upgrade planning.
Can we still access the legacy application after the deprecation date?
While some commercial tenants may still technically load the legacy interface, Microsoft strongly advises against relying on a retired application. Any support tickets submitted for the commercial cloud version will be closed with instructions to upgrade. Future platform updates to the Power Platform could cause unpatched legacy customisations to stop functioning.
How do organisational units differ from business units?
Business units and organisational units serve entirely different purposes in Dynamics 365.
- Business units control security access, record ownership, and user permissions.
- Organisational units determine the cost rates and financial parameters of resources assigned to projects.
A consultant can belong to a single business unit for security purposes. However, their work can be costed through a specific organisational unit depending on the division delivering the service.
What integration options exist for legacy project data?
Legacy project data can be integrated with external ERP and HR systems using Azure Integration Services, data integration templates, or custom APIs. These integrations allow you to sync historical records, actual transactions, and resource availability across your enterprise.
For organisations with complex legacy setups, designing a secure data migration strategy is a key step in the upgrade process. You can find detailed technical guidance on managing these data structures in our Dynamics 365 Custom Development Complete Guide.
Transitioning Your Dynamics 365 Project Service Automation Environment
Transitioning away from a legacy project management system is a significant step that requires a pragmatic approach to CRM design. Ensuring your business systems are properly structured to match your operational scale, resource models, and financial processes is critical for maintaining control.
At BeyondCRM, we are CRM design specialists who focus on tailoring systems to your industry, business size, operational complexity, and growth stage. Whether you need to resolve complex resource scheduling challenges, optimise financial tracking, or plan a safe migration, our team is here to assist.
To ensure your business systems are fully optimised, you can explore our tailored Dynamics 365 Implementation Services or contact us today to discuss your transition strategy.