How the AX 2012 integration and UX estate — AIF document services, the .NET Business Connector, Enterprise Portal, Role Centres, the Excel add-in, and SSRS reports — maps surface by surface to D365 data entities, OData, custom services, business events, workspaces, Electronic Reporting, Power BI, Dataverse, dual-write, and Microsoft Fabric; with a disposition table, effort classes, and ownership assignments.
An AX 2012 estate's integration and presentation surface is often larger and more varied than its owners realise. There are AIF document services exchanging XML with suppliers and logistics partners. There are .NET Business Connector callers embedded in desktop tools, Excel macros, and middleware that were built a decade ago.
The Application Integration Framework (AIF) is AX 2012's primary integration surface for structured document exchange. AIF uses document services — X++ classes that define the structure of a business document (purchase order, sales order, invoice, journal) — combined with adapters (file system, MSMQ, HTTP, WCF) and exchange channels that…
The .NET Business Connector is a managed .NET assembly (Microsoft.Dynamics.BusinessConnectorNet.dll) that external applications load in-process to call AX business logic directly. It provides a typed interface to AX sessions, companies, and method calls without going through the AX client. Common callers include:
Enterprise Portal runs on SharePoint (typically SharePoint 2010 or 2013) and provides web-based access to AX functionality through web parts — ASP.NET components that render AX forms, lists, and reports in a browser. EP is used for:
SSRS operational reports — deployed through the AOT, rendered by SQL Server Reporting Services. These include pick lists, packing slips, invoices, purchase confirmations, and hundreds of operational outputs.
AX 2012 estates commonly run analytical queries directly against the transactional SQL Server database — ad-hoc queries, SSAS cubes, and ETL jobs that extract data for data warehouses. D365 F&O is a cloud-managed SaaS service; the transactional database is not exposed for direct query.
The following table classifies every AX 2012 integration and UX surface by its D365 disposition, effort class, and primary owner. Use it as the starting framework for the integration workstream plan.
D365 OData endpoints are subject to platform throttling. High-volume integrations that call OData once per record will breach the throttle ceiling under production load. Design rules:
The AX 2012 integration and UX estate — AIF, the Business Connector, Enterprise Portal, Role Centres, SSRS, Management Reporter, the Excel add-in, and direct SQL — maps surface by surface to a D365 architecture that uses fundamentally different mechanisms for the same business purposes.