The TFVC Clock Is Ticking

Avatar photo by Denis Zhurba on 3 minute read

Why Now’s the Time to Move Your Dynamics 365 F&O Code to Git

Big news: If your team manages Microsoft Dynamics 365 Finance & Operations code in Team Foundation Version Control (TFVC), the ground is gently shifting beneath it. As of February 2026, Microsoft has begun steering new F&O customers away from Lifecycle Services (LCS) toward the Power Platform Admin Center (PPAC), and PPAC’s unified application-lifecycle model is built on Git. TFVC simply isn’t part of that future.

That doesn’t mean anything breaks tomorrow, but it does mean the path forward increasingly runs through Git, and the teams that make the move early get to do it on their own timeline, calmly and deliberately, rather than under pressure of a deadline.

TFVC still works but the momentum has moved on

TFVC isn’t disappearing overnight, and your code is safe where it is today. But it’s been in maintenance mode for years. Microsoft has stopped adding features, disabled new TFVC repository creation by default, and is winding down its legacy check-in policies. Every new investment in Azure DevOps, including security, performance, and the growing wave of AI-assisted development tooling, now goes to Git.

Git, meanwhile, has become the everyday standard for roughly 93% of developers, according to a Stack Overflow survey. Microsoft moved its own largest codebases, Windows and Office, to Git years ago. Modernizing now simply brings your F&O development in line with the way the rest of the industry, and Microsoft itself, already works.

What the move actually unlocks

Migrating to Git is far more than a version-control swap. It modernizes how your team builds, reviews, and ships F&O code. Moving now means you’re aligned with the platform direction well before it matters.

  • Stronger governance. Pull requests become the single gate for every change, with enforced reviewers, linked work items, and automated build validation creating a complete, auditable history.
  • A path to AI-assisted development. GitHub Copilot, including the emerging Copilot for X++, is Git-native. It’s where the productivity gains are heading.
  • Modern, secure pipelines. As part of the move, legacy “classic” pipelines give way to YAML pipelines that live alongside your code, version-controlled and reviewable like everything else.

Built for the realities of F&O

Finance & Operations has a unique project structure, and it’s fair to ask whether Git fits it cleanly. It does — and the F&O-specific details (repository configuration, build infrastructure, workspace mapping) are well-understood, solved patterns, not unknowns. A well-run migration validates the entire build-package-deploy flow in parallel, keeps your existing TFVC repo intact as a rollback path, and trains your developers before the switch — not after.

Let’s move forward, together

The cost of moving to Git is modest and front-loaded. The upside compounds over time through a development practice aligned with Microsoft’s roadmap, ready for AI tooling, and positioned for the savings and governance modern teams expect. The clock is ticking on the old way. The calmest time to move is while it’s still your choice, not your deadline.

Hitachi Solutions has guided Dynamics 365 Finance & Operations teams through TFVC-to-Git migrations using proven patterns built for the realities of F&O. Contact us to see how we can help you modernize your timeline and set your team up for everything Microsoft is building next. Learn more about our Managed Services program here.