> It would be nice if you actually published a full document on how to fix it when it breaks
Start with these articles
https://learn.microsoft.com/en-us/windows-server/networking/ncsi/ncsi-overview
https://learn.microsoft.com/en-us/windows-server/networking/ncsi/ncsi-troubleshooting-guide
"Faking" NCSI causes more problems than it solves. When applications like Outlook and Teams, and numerous third parties believe there is internet connectivity when there really isn't, they will try their network operations and make the user wait for timeout. This is not a good user experience.
Of course not having internet isn't a good user experience either, but NCSI can't do anything about blocked firewall ports, proxies that don't properly whitelist the well-known msftconnecttest URI, captive portals that don't properly redirect or allow through NCSI probes after authentication.