Improved discoverability of Windows Authentication setting by mentioning it on On-Premise git page

Author: mikita-haurykau

content/en/docs/refguide/version-control/on-premises-git.md

@@ -34,7 +34,11 @@ Make sure you have completed the following prerequisites:
 
 ## Supported Authentication Mechanisms
 
-Currently, Mendix only supports HTTP Basic authentication for Git service providers. With most providers, this takes the form of using of personal access tokens (PATs).
+Currently, Mendix only supports HTTP Basic authentication and Windows Authentication for Git service providers. 
+
+### HTTP Basic Authentication
+
+With most providers, this takes the form of using of personal access tokens (PATs).
 
 To use PAT (or another equivalent), you need to specify it in the **Password** field when Studio Pro requests credentials for the version control server:
 
@@ -45,6 +49,13 @@ Currently Mendix keeps PAT using operating system supported solutions:
 * For Windows, Mendix uses a credential locker mechanism, accessible to users by using Credential Manager.
 * For MacOs, Mendix uses keychains, accessible to users by using Keychain Access.
 
+### Windows Authentication
+
+Studio Pro can use Windows Authentication for Git service providers that support it. When you use Windows Authentication, you do not need to provide a password. 
+
+You can enable Windows Authentication in [Git Preferences settings](/refguide/preferences-dialog/#enable-windows-authentication).
+
+
 ## Setting Up the Environment
 
 This section describes how to configure a Git versioned app in Studio Pro. You need a Git server and an initially unversioned Mendix app.