DevOps Articles

Upcoming Change: NTLM Removal in Git (libcurl) – Impact to Azure DevOps Server Customers

Microsoft is set to disable NTLM authentication in Git and libcurl, which impacts users of Azure DevOps Server. This decision arises from ongoing security concerns around the NTLM protocol, which has presented vulnerabilities over the years. Administrators and developers relying on Azure DevOps will need to consider this shift as it could lead to authentication challenges in their workflows.

As this transition approaches, users are encouraged to update their authentication methods. The recommended alternatives include using personal access tokens or OAuth, which offer a more secure and modern approach to managing credentials. These changes reflect the industry's move towards more secure authentication practices, ensuring sensitive information remains protected.

Developers should remain vigilant by reviewing their current projects and infrastructure to identify any dependencies on NTLM. The guidance from Microsoft serves as a proactive measure, allowing teams to adapt to this change without disrupting their ongoing projects. Embracing these practices not only enhances security but also aligns with the best practices in the DevOps community focused on continuous improvement and resilience in software development.