to-dyn365-api
.NET 8 integration API bridging Travel Operations finance data (vendors, journals, settlements, payments) into Microsoft Dynamics 365 Finance & Operations via its OData endpoint.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | csharp |
| Frameworks | ASP.NET Core 8, MediatR, AutoMapper, FluentValidation |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2026-02-16 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Contact centre and CRM (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 2 release pipeline(s): \finance\backoffice\to-dyn365-api; \finance\backoffice\to-dyn365-api - stealth |
| Integration | rest, redis-streams, wcf |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loosely attached Bound into the core by 1 mechanism(s).
- Speaks WCF (client)
Detaches when its WCF surface gains a modern interface or its WCF calls move to one.
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
Ready with guardrailsClose: the deployment path exists, but specific checks are needed first, typically raising tests, auditing serialized data, or respecting a shared schema with expand and contract. Test coverage is thin; ZDD shifts the safety net onto automation.
- 2 system(s) depend on this repo; during a rolling deploy they will talk to old and new versions at once, so responses must stay compatible
- Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
- Serialized state or messages in flight (Redis or queues): new code must deserialize objects written by the previous version
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Audit serialized data: anything in Redis, queues or shared caches must deserialize cleanly across adjacent versions.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Ready to containeriseModern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).
- Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
- Log to stdout and expose a health check endpoint so ECS can supervise it.
- Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
- Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.
Recommended actions
No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.
Assessment notes
to-dyn365-api
Purpose
Integration API between Travel Operations back-office finance and Dynamics 365 F&O. Controllers cover vendors, vendor transactions/settlements, vendor payment journal lines (incl. settled invoices), general journals, sync operations and OData request logs; command/query layers translate to D365 OData calls with batching and paging helpers.
Tech stack
C# .NET 8 ASP.NET Core with API versioning, MediatR handlers, AutoMapper, FluentValidation, Correlate correlation IDs, PhenixAuth JWT, Swashbuckle plus an NSwag-generated Api.Client package, custom OData command/query projects generated from Metadata.edmx.txt, OAuth token authorizer for D365, New Relic agent API, xUnit tests.
Deployment
prod_application, release_count 2. YAML build.yml (shared azure-pipelines-templates, .NET SDK 8.x) builds the API and publishes Api.Client and Models NuGet packages; build pipeline to-dyn365-api feeds release pipelines \finance\backoffice\to-dyn365-api and its stealth variant. Hosted under /api/to-dyn365 on the Phenix services host.
Dependencies
Internal packages: TC.ConnectionBroker.* (Api, Mongo, Redis, Wcf), TC.Exceptions.WebApiClient, TC.Commission.Service.Api (backoffice-commissions-service, with a health check), TC.UserAccount.ServiceClient/Events (backoffice-useraccount-service), TC.Streams.* for Redis-stream eventing. External: Dynamics 365 F&O OData endpoint (tc-prod.operations.dynamics.com), Azure AD OAuth for D365 tokens, New Relic.
Data stores
No owned SQL database. MongoDB traveloperations_d365_logs for OData request/response logging (also queried back via an OdataLogController and vendor-update queries); Redis for streams.
Integration points
Inbound REST. Outbound OData/REST to Dynamics 365, REST to the commission service, WCF/eventing to the user-account service, and TC.Streams event processing over Redis streams (reacting to user-account change events to sync vendors).
Code health
Unit and integration test projects exist with reasonable handler coverage. README is untouched Azure DevOps boilerplate. A stray TravelOperations - Backup.Dynamics365.Api.csproj sits alongside the real project file. Last commit 2026-02-16.
Modernisation risks
Low: modern .NET 8, YAML CI, tests. Notable operational smell: the live config carries a comment that the production D365 client id "still doesn't work" so the test OAuth client key is used against the live D365 account — a credential-hygiene issue worth resolving. Otherwise the main risk is tight coupling to the D365 OData schema (checked-in EDMX metadata).