title: Azure DevOps Release changing appsettings.json Logging section
body: <p>I have a problem regarding Azure DevOps and release management.  First a little background - we use visualstudio.com along with build agents, release agents (running on different environment VMs) to manage our CI, builds, and releases. I am trying to troubleshoot logging on my non-development servers and have traced the problem back to missing elements in my appsettings.json file.  When I log into my production VMs and look at the appsetings.json file, I found that my Logging section looked like this:</p>
  
  <pre><code>"Logging": {
      "IncludeScopes": false,
      "LogLevel": {
        "Default": "Information"
      }
    },
  </code></pre>
  
  <p>While within my appsettings.json file within my build artifacts (the website .zip file) looks like this:</p>
  
  <pre><code>"Logging": {
      "IncludeScopes": false,
      "LogLevel": {
        "Default": "Debug",
        "System": "Information",
        "Microsoft": "Information"
      }
    },
  </code></pre>
  
  <p>My logging issues are fixed when I go on the server and change the appsettings.json Logging section to match what is should be according to the appsettings in the build .zip.  </p>
  
  <p>My question is - <strong>what is it within the Azure DevOps release pipeline (formerly VSTS) that is changing the appsettings.json Logging section</strong>?  I have verified that my release definition has no variable substitutions for the logging section.</p>