Services.
Azure, Dynamics 365 CE, and the road off BizTalk — planned, built, and repaired by the consultant you actually talk to.
Migrations, Integrations, and Analytics on Azure.
The center of gravityWhere the integration work is heading, and where most of it now lands: the jobs that used to run through on-premises middleware, rebuilt as Azure services.
Data moving on schedules nobody trusts — overnight jobs, file drops, manual re-runs.
Azure Data Factory pipelines that are scheduled, monitored, and owned. The movement documented; the failures alerting a person instead of a folder.
Every system wired straight to every other, and every change breaking two of them.
Azure Service Bus between the endpoints — queues and topics that decouple the estate, so one system's outage stops being everyone's.
Business logic buried in code nobody can safely touch.
Azure Logic Apps for the orchestration layer: workflows the next person can read, change, and run without an archaeology project.
An integration estate with no owner since the last consultant rolled off.
Assessment before anything else — what exists, what runs, what matters — then the repair, sequenced. Rebuild only what earns it.
Dynamics 365 CE.
The deepest current practiceThe product Mark works with most at this point. CE work tends to arrive as configuration, integration, and data problems wearing a CRM label.
A CE org shaped by three vendors, all gone.
Customization and configuration set straight — security, business process flows, the data model brought back to how the business actually runs.
Data that has to move into CE — or out — without wrecking either side.
Migration through the APIs: legacy CRM in, reporting feeds out, duplicates resolved before they multiply.
CE that doesn't talk to the systems around it.
Integration between systems — built on the same Azure services above, so there is one pattern to maintain instead of five.
SQL and Reporting.
Underneath most of itSQL Server is a major component of much of the work above — usually the source, the destination, or both. It rarely arrives as its own project; it arrives inside one.
Two reports on the same question, disagreeing, and nobody able to say which is right.
The queries and the tables under them traced back to one version — so the number on the report is the number in the system.
A database quietly carrying the integration logic, years after anyone meant it to.
Stored procedures and jobs read and documented, then moved to where they belong — or left where they are on purpose, with the reason written down.
BizTalk, moved to Azure.
Migration onlyBizTalk is on its way out, and there is no like-for-like replacement — while health-care and supply-chain operations still clear production claims and orders through it nightly. The work is not keeping BizTalk alive. It is moving what BizTalk does onto Azure.
Production EDI still clearing through a BizTalk farm — 837s, purchase orders, acknowledgments.
The exchange rebuilt on Azure — Logic Apps, Service Bus, Data Factory — mapped from the orchestrations that exist, cut over without stopping the traffic.
A migration that stalled because nobody knows what the middleware actually does.
Artifact-level assessment first: what runs, what's dead, what depends on what. Then a sequence that never bets production on a guess.
How engagements work.
Direct
Every engagement is with Mark — no account managers, no hand-offs.
Alongside
When the work needs more hands, trusted specialists join him. Never instead of him.
Remote
From Colorado, with teams anywhere. Direct clients and placement-firm work both welcome.
Long-haul
Plan, build, repair, maintain. Most clients stay for years; several are past the decade mark.
Start aconversation.
Tell us what's stuck, half-built, or overdue. A senior consultant reads every note — and replies.
inquiries@inotekgroup.com/in/mbeckner