Can Dynamics 365 configuration be version-controlled in Git?

Configuration in Dynamics 365 can be treated as source code, and for teams of a certain size, this is clearly recommended.

How it's done

A solution is exported and unpacked into many small files—one per component—which are stored in Git. This gives you a history, lets you see changes over time, and allows you to restore a previous state.

The benefit

You can determine who changed a form and when. You can roll back changes. And you can see what actually differs between testing and production, rather than guessing.

The price

It requires tools, an agreed way of working, and discipline. For one person making a few adjustments a year, it is overkill. For a team of three or more making regular changes, it is usually worth it.

Realistic expectation

Merging conflicts works less well than with regular code because the files are machine-generated. The solution is to avoid having two people work on the same component at the same time, rather than relying on Git to sort it out.