Why does F# configuration binding work locally but fail when deployed to Azure App Service?

In local development, an F# console app loads appsettings.json and appsettings.Development.json, binds a section to a record with a single public constructor, and reads the expected values.

When the same app is deployed to Azure App Service, environment variables override the file‑based settings, and the bound record appears with missing or incorrectly typed values, causing the application to fail.

How does the order of configuration providers affect the final bound values when environment variables are present? What steps can be taken to guarantee consistent binding behavior across environments? Is there a way to inspect which provider contributed the final value for each bound property?