title: Impersonate Domain User with Integrated Pipeline
body: <p>In an local Intranet environment, are we doomed to use "Classic" pipeline mode in our App Pool if we want to use Impersonate our Windows domain users, or is there a new way to declaratively "run as" them (so-to-speak)?</p>
  
  <p>My goal is to use Windows Authentication for local web applications on my Intranet so users can authenticate and run apps under their active directory account (principle). Every time I try this (Using the NetworkService identity of course), I get this error:</p>
  
  <p><img src="https://i.stack.imgur.com/xf5ud.png" alt="screenshot of error message"></p>