Technology & architecture
Dynamics 365 architecture for maritime operations.
How Flex Maritime Logistics is put together on Microsoft Dynamics 365 Finance and Operations: Microsoft Entra ID for identity, the UML API framework for every external connection, Flex MessageQueue and Azure Service Bus for reliable messaging, and Fabric link or BYOD to keep analytics off the production ERP. Written for the IT and architecture teams who evaluate it.
Microsoft Entra ID · Identity and access across every layer
- Outside worldPartner systems, EDI and devicesBooking requests, container events, customs statuses, weighbridges
- API layerUML API frameworkContract, authentication, validation and business context per service
MessagingFlex MessageQueue and Azure Service BusEvery message queued first, logged, and reprocessed if it fails
RecordMicrosoft Dynamics 365 Finance and OperationsFinance, master data and control, with the maritime layer on top
- Flex Run
- Flex Connect
- Flex Performance
- Flex Intelligence
Data pathFabric link or BYOD to Power BIAnalytics without turning the production ERP into a reporting database
Microsoft cloud foundation
The Microsoft cloud foundation: Azure, Entra ID, Power Platform and Fabric.
Flex is designed around the Microsoft technology ecosystem, not just one application. Each customer architecture uses the parts it needs.
Dynamics 365 Finance and Operations
The enterprise ERP core: finance, master data, reporting and control. Flex adds the maritime processes on top.
Microsoft Dynamics 365 Finance and OperationsMicrosoft Azure
Cloud services around the ERP for integration, messaging, APIs, monitoring and data. Azure is not a second ERP.
Microsoft Entra ID
Identity for users, applications and agents, with authentication and controlled access to Dynamics 365 and connected services.
Power Platform and Dataverse
Power Apps, Power Automate, Power BI and Copilot Studio work with finance and operations data through connectors and APIs, without changing the core.
Power BI and Microsoft Fabric
Reporting inside Dynamics 365 workspaces, and a governed analytics platform where ERP, Flex and external data come together.
Microsoft 365
SharePoint Online for documents and the familiar Microsoft tools your teams already work in every day.
Open by design
The architecture is loosely coupled. Integrations run through defined service contracts, data leaves through supported Microsoft export paths such as Fabric link and BYOD, and specialist providers or partner solutions can be added or replaced without rebuilding the ERP core.
See our Microsoft and technology partners, or how the layers come together in Flex Maritime Logistics, our maritime software platform.
ERP architecture
Operations and finance in one transaction trail.
Business context such as vessel, voyage, service or customer can be carried into accounting through financial dimensions, with a trail back to the originating transaction.
Voyage profitability you can explain, in Flex PerformanceAPI and integration framework
Reusable connectivity, not one-off interfaces.
The UML API framework is one controlled layer between Flex, Dynamics 365 and the outside world. It keeps the contract, authentication, validation and business context explicit, and every proven service goes into a library that makes the next integration easier.
Inbound
Into Flex and Dynamics 365
Events, status updates, documents and structured data that become part of the maritime process.
- Booking requests
- Customs statuses
- Container events
- Exchange rates
- Screening results
- Reefer events
Outbound
To customers and partners
Approved operational and financial information sent to other systems, services and digital channels.
- Shipment status
- Schedules
- Container information
- Documents
- Invoice data
- KPI data
UML API framework
Flex Maritime Logistics · Microsoft Dynamics 365
Each service contract specifies required fields, validation, authorisation, expected responses and error handling. External systems call those services rather than internal tables, so Flex can evolve behind a stable integration boundary. Message standards and partner connections are covered in EDI for logistics with Flex Connect.

Flex MessageQueue
Flex MessageQueue and Azure integration services.
Flex MessageQueue is our add-on for Dynamics 365 Finance and Operations that gives every integration one central, fault-tolerant buffer. Messages are stored in a queue before they are processed, so integrations are decoupled from direct system operations.
How a message moves
- 01
Receive
Orders, vessel information or logistics updates arrive over HTTP, SFTP or web services.
- 02
Queue
Each message is stored first, so a peak or an unavailable system does not cause data loss.
- 03
Process
Company-specific business logic per message type runs inside D365FO.
- 04
Monitor
Full logging shows the status of every message; failed ones can be reprocessed.
Why not only the standard frameworks? The Data Management Framework is built for batch processing of datasets, and the standard Message Processor Framework mainly supports inbound messages. Flex MessageQueue builds on these foundations and handles inbound and outbound integrations in one framework.
Azure integration services
We frequently use Azure Service Bus for reliable, asynchronous message exchange between Dynamics 365 and other applications: queues and topics keep messages safe when a recipient is temporarily unavailable, and subscriptions route only relevant messages. Other building blocks are chosen per architecture.
Service Bus
API Management
Functions
Logic Apps
Event Grid
Key Vault
Monitor
Application Insights
Data and analytics
Power BI, Microsoft Fabric and BYOD on one data foundation.
Dynamics 365 and Flex create operational and financial data every day. The analytics architecture decides how that data becomes trusted measures, trends and exceptions, without turning the production ERP into a reporting database.

From transaction to decision
01 · Capture
D365 and Flex record the transaction.
02 · Make available
Fabric link, BYOD or another supported pattern.
03 · Combine
Add external, historical or enterprise data.
04 · Model
Governed definitions, dimensions and measures.
05 · Consume
Power BI, KPIs, alerts and intelligence.
- 01
Microsoft Fabric & OneLake
Data engineering, warehousing, real-time analytics and Power BI in one platform. Microsoft supports linking Dynamics 365 and Dataverse data, including finance and operations data, with Fabric and OneLake.
For combining ERP, Flex and maritime data in a broader governed platform.
- 02
BYOD / Azure SQL
Bring your own database exports selected data entities into a customer-controlled Azure SQL database, with scheduled full and incremental exports.
For existing warehouse investments, SQL access or batch integration.
- 03
Power BI inside D365FO
Power BI content can be embedded in Dynamics 365 workspaces, filtered by company and context, with navigation from insight to the underlying transaction.
For seeing the numbers where the work happens.
Separate transaction processing from analytical consumption. We select a supported pattern that matches latency, volume, governance and reporting needs.
The maritime KPIs and Compliance Center built on this foundation are part of Flex Performance for shipping KPIs and reporting.
Documents and DMS
Store documents where they belong. Work with them where you need them.
The business transaction is the starting point. Documents stay linked to the booking, shipment, container, B/L, claim or invoice they belong to, while the authoritative file can live in SharePoint Online or an external DMS.
Business record
Booking · shipment · container · B/L · claim · invoice
Document integration
Reference · metadata · API or connector · access rights
Repository
SharePoint Online · Azure storage · M-Files · OnBase · other DMS
SharePoint OnlineNative in Dynamics 365
Dynamics 365 supports SharePoint Online as a storage location for document types. The document stays accessible from the business record.
M-FilesIntegration scenario
Identifiers, metadata, links or files are exchanged so the content can be retrieved from the Dynamics 365 and Flex context.
OnBase or another DMSIntegration scenario
The specialist platform manages documents, retention and workflows; Flex keeps the business context. The exact experience depends on the connector.
Three questions we answer in solution design
01 · Store
Where does the authoritative file live?
02 · Link
Which business record does it belong to?
03 · Govern
Who may access it, and which retention rules apply?
Security and identity
Microsoft Entra ID and role-based security in Dynamics 365.
Security starts with the Microsoft platform and continues through the design of Flex, integrations and intelligent workflows. Users, applications and AI agents get only the access their role requires.
- 01
Identity
Microsoft Entra authentication, application identities and controlled access.
- 02
D365 authorisation
Roles, duties, privileges, permissions and data security policies.
- 03
Integration boundary
Governed APIs, permitted tools, approved data and human approval.
- 04
Traceability
Logging, monitoring, review and exception handling.
Access follows responsibility
Role-based access
Security roles aligned with responsibilities and processes, not broad unrestricted access.
Segregation of duties
Conflicting duties can be defined, and role assignments that break those rules identified or prevented.
Data security & reporting
Extensible data security restricts access to subsets of data; security reports show effective access.
AI agents get the same boundaries
Each agent is identified, authorised for specific data and services, constrained by guardrails, approved by people where policy requires, and recorded.
Security and certifications
Built on Microsoft security.Audited in our own organisation.
- Certified information security
- ISO 27001
- Certified quality management
- ISO 9001
Technology FAQ
Common questions about the architecture.
01What does the Dynamics 365 architecture behind Flex look like?
Microsoft Dynamics 365 Finance and Operations is always the core, for finance, master data and control. Flex Run, Flex Connect, Flex Performance and Flex Intelligence add the maritime layer on top. Around it, each customer architecture uses the parts it needs: Microsoft Entra ID for identity, Azure integration services such as Service Bus for messaging, Power BI and Microsoft Fabric for analytics, Power Platform for apps and automation, and SharePoint Online or another DMS for documents.
02What happens when an integration fails or a peak arrives?
Flex MessageQueue, our add-on for Dynamics 365 Finance and Operations, stores every inbound and outbound message in a queue before it is processed, so a peak or an unavailable system does not cause data loss. Full logging shows the status of each message, and failed messages can be reprocessed.
03Is the production ERP also our reporting database?
No. We separate transaction processing from analytical consumption: Power BI inside Dynamics 365 workspaces, Fabric link, or BYOD to your own Azure SQL database, chosen to match latency, volume, governance and reporting needs.
04Where are documents stored?
Where your governance requires. Dynamics 365 supports SharePoint Online as a storage location for document types, and Flex can integrate with an external DMS such as M-Files or OnBase. The document stays linked to the booking, shipment, container, B/L, claim or invoice it belongs to.
05How much customer-specific development is required?
We start with Microsoft standard and reusable Flex capability, validate the fit and configure first. Extensions are added only where they are justified. The UML Maritime Accelerator Method is built around that principle.

Check the architecture against your own landscape.
Bring your current systems and interfaces. We map them onto Dynamics 365, Flex and the integration layer with your IT team.





