Squid v4 Configuration with Windows Server

I have a functioning Squid v4 installed on a Debian Linux Bullseye server and need an expert to adjust its authentication settings. The essential requirements for this project are: - Deep understanding of Squid v4 configuration - Knowledge in working with Debian Linux Bullseye - Experienced in setting up communication between Squid v4 and AD in Windows Server 2022 The scope incorporates tweaking the current Squid v4 configuration to fix a problem for NTLM authentication with the Windows Server 2022 AD. Proficiency in managing Linux servers and understanding of AD authentication is a must for a successful project completion. Direct, clear communication skills are also a plus. Our task is very definitive and can be just a few minutes if you are familiar with this. The Squid server is essentially working with the Windows Server AD already because applications on Windows clients can connect to the Internet via the Squid server. The only thing that doesn't work is the browsers (e.g. Chrome) on Windows clients. I have attached 2 screenshots: 1) The proxy authentication prompt from Chrome (not working); 2) The proxy config screen from one of the apps on the Windows client (working flawlessly). As you can see, the proxy authentication from Chrome doesn't prompt the domain so we expect to enter the domain\user for the user name but this is not working. Our IT are not an inherent expert in Squid so we believe we need to pay someone to fix this issue.