Books by Mark Beckner.
Fifteen titles on the Microsoft integration stack — arranged here by the problem you're holding, not the year they shipped.
EDI & health care
Claims and enrollment are where EDI stops being tolerant — formats set by regulators, deadlines set by law. Four books cover the X12 work end to end, from 837 claims to the supply-chain documents the same engine handles.
Pro EDI in BizTalk Server 2006 R2
Written for the release where BizTalk finally shipped its own EDI engine — 2006 R2 retired the licensed add-on and brought party management and X12 handling into the product. Covers trading-partner setup, envelopes, acknowledgments, and maps, through to a production exchange. For teams standing up their first serious EDI operation on the platform.
On AmazonBizTalk 2010 EDI for Health Care: 837 Solutions
A working build of claims processing on BizTalk 2010: 837 professional and institutional claims in, acknowledgments back out, HIPAA 5010 throughout. Written as the 4010-to-5010 mandate landed, for payers and clearinghouses that had to change formats with production traffic still flowing.
On AmazonBizTalk 2013 EDI for Supply Chain Management
The commercial side of X12 on BizTalk 2013: purchase orders, ship notices, invoices, and the trading-partner plumbing between suppliers and the retailers they answer to. For teams replacing a VAN-and-spreadsheet workflow, or a legacy translator, with something maintainable.
On AmazonBizTalk 2013 EDI for Health Care: 834 and 837 Solutions
Extends the claims work to 834 enrollment — the transaction the ACA exchanges made urgent in 2013 — alongside updated 837 handling. For anyone wiring carriers, exchanges, and administrators together on deadlines regulators set.
On Amazon
BizTalk Server
Three editions of the Recipes series and the specialist volumes around them: building on BizTalk, running it, and eventually moving it somewhere supported.
BizTalk 2006 Recipes – A Problem-Solution Approach
The first of the Recipes series: hundreds of problem-solution entries across orchestrations, maps, pipelines, and adapters, written as BizTalk 2006 hit mainstream enterprise adoption. For developers who needed a working answer faster than the documentation could give one — the format the series kept for a decade.
On AmazonPro RFID in BizTalk Server 2009
BizTalk RFID was Microsoft's bid to make sensor data an integration concern — device management, tag-read events, and the plumbing that turns them into business processes. A record of the platform's edge, written for the warehouses and plants that actually ran it.
On AmazonBizTalk 2010 Recipes – A Problem-Solution Approach
The Recipes formula on BizTalk 2010: the rebuilt mapper, updated EDI and AS2 support, and the platform's steadier failover story. Same shape as the 2006 edition — the problem you have, then the solution that works, code included.
On AmazonBizTalk 2013 Recipes – A Problem-Solution Approach
The final Recipes edition, covering BizTalk 2013's turn toward the cloud era — REST support, Azure Service Bus adapters, the ESB toolkit in the box. Still organized by problem, because that is how the work arrives.
On AmazonUpgrading and Migrating to BizTalk Server 2016
By 2017 most BizTalk work was not greenfield; it was moving aging 2006-to-2010 environments somewhere supported. The playbook for that move — assessment, side-by-side migration, redeploying artifacts, and what to do with the pieces that will not come along. The part upgrade documentation skips.
On Amazon
Dynamics & integration tooling
The CRM-shaped work: programming against Dynamics, and moving data into it with the tooling projects actually owned.
Microsoft Dynamics CRM API Development
Programmatic access to Dynamics CRM 2011, online and on-premise: the organization service, queries, plug-ins, and the patterns for tying CRM to the systems around it. For developers handed a CRM implementation and the requirement that it talk to the rest of the business.
On AmazonUsing Scribe Insight: Developing Integrations and Migrations
Scribe Insight moved a remarkable share of the era's CRM data, and most people who ran it learned by trial. This documents the toolset properly — connections, DTS design, error handling — and the migration patterns for getting legacy data into Dynamics without hand-building an ETL layer.
On AmazonAdministering Microsoft Dynamics 365 in the Cloud
The cloud subscription changed a Dynamics administrator's job from servers to service settings: instances, security roles, storage, and updates that arrive on Microsoft's schedule. An operations manual for that new shape of the job, written as on-premise deployments wound down.
On Amazon
Cloud platforms
Where the integration work went after the middleware era — data movement and collaboration as managed services, in Azure and Microsoft 365.
SharePoint Online Development, Configuration, and Administration
SharePoint without the farm: configuring, customizing, and running SharePoint Online inside Microsoft 365. For administrators and developers carrying a decade of on-premise habits into a service Microsoft now operates.
On AmazonQuick Start Guide to Azure Data Factory, Azure Data Lake Server
The data movement that used to live in SSIS packages and BizTalk maps, rebuilt as managed Azure services. A fast on-ramp to Data Factory pipelines, Data Lake storage, and the warehouse behind them, for teams making their first move off on-premise ETL.
On Amazon
On the work itself
The Coder's Path to Wealth and Independence
The one title here without a line of code: how a working developer builds an independent practice — clients, rates, reputation, and the discipline of staying billable without an employer behind you. Written from the practice this site describes.
Also published
MSDN MagazineBuild a Robust EDI Solution with BizTalk Serverlearn.microsoft.comMSDN MagazineProcessing Health Care Claims with BizTalk Server 2010learn.microsoft.comMSDN MagazineHarnessing the Power of the Dynamics CRM 4.0 API from Silverlight 4learn.microsoft.comMSDN MagazineBatching EDI Data in BizTalk Server 2010learn.microsoft.comBylinesEntrepreneur · ComputerWorld · CMSWire · SD Times
The books came out of the work. The work continues.
Start a conversation