Describe the core capabilities of the finance and operations apps
This domain covers the shared platform behind Dynamics 365 Finance, Supply Chain Management, Commerce, Human Resources and Project Operations. The exam wants you to recognize platform-wide features - organization model, security, user interface, reporting, integration and Lifecycle Services - and to know which tool belongs to implementation versus daily use.
Organization, data and lifecycle
- Legal entities are the only organizations that own a ledger and must be created for each company. Operating units - business unit, cost center, department, value stream, division - support reporting and are arranged into organizational hierarchies per purpose.
- Data entities expose business data for the Data management framework (import, export, recurring integrations). Dual-write synchronizes with Microsoft Dataverse for Power Platform apps.
- Lifecycle Services (LCS) is the implementation-lifecycle tool: methodology, environments (Tier 1 sandbox, Tier 2+ multi-box), asset library, issue search and support incidents. It is not where end users do daily work.
User interface, security, reporting
The UI uses a navigation pane, action pane, filter pane, list pages, fact boxes and role-based workspaces. Personalization and saved views are user-level changes; customization means extensions. Security flows from roles → duties → privileges → permissions, with segregation-of-duties analysis. Reporting options include SQL Server Reporting Services reports, Financial reporting, embedded Power BI, and Electronic reporting for regulatory formats. Office integration covers Open in Excel, the Excel add-in, export to Excel and Word templates for documents.
Worked example
A US subsidiary is added to an existing group. You create a legal entity, attach the shared chart of accounts and fiscal calendar, assign account structures, add a tax registration and number sequences, then assign security roles. Customers are loaded through the Customers V3 data entity in Data management - never by writing to tables directly - and only then are transactions posted.
Traps that cost marks
Operating units cannot own a ledger. LCS is implementation tooling, not an end-user application. Personalization is not customization. Data entities are not tables, and dual-write is not the same as Data management.