Update authenticating-to-github.md

docs/getting-started/authenticating-to-github.md

@@ -7,10 +7,14 @@ Before you authenticate, you must already have a GitHub or GitHub Enterprise acc
 - For more information on creating a GitHub account, see "[Signing up for a new GitHub account](https://help.github.com/articles/signing-up-for-a-new-github-account/)".
 - For a GitHub Enterprise account, contact your GitHub Enterprise site administrator.
 
-> **Note:** If your organization is on the [Business plan](https://help.github.com/articles/organization-billing-plans) and has enabled SAML single sign-on, or an [Enterprise account] you must create and authorize a personal access token to access protected content. For more information on creating personal access tokens, see "[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line). The required scopes for the personal access token are: `user`, `repo`, `gist`, and `write:public_key`.
+> **Note:** If your organization is on the [Business plan](https://help.github.com/articles/organization-billing-plans) and has enabled SAML single sign-on, you must create and authorize a personal access token to access protected content. 
+>You will also need to create a personal access token for signing in with GitHub Enterprise if your version is less than 2.12.2 and username/password login is disabled. For versions greater than 2.12.2 you can login with OAUTH.
 
 > For more information on authenticating with SAML single sign-on, see "[About authentication with SAML single sign-on](https://help.github.com/articles/about-authentication-with-saml-single-sign-on)."
 
+> For more information on creating personal access tokens, see "[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line). The required scopes for the personal access token are: `user`, `repo`, `gist`, and `write:public_key`. 
+
+
 1. In Visual Studio, select **Team Explorer** from the **View** menu.
 ![Team Explorer in the view menu](images/view_team_explorer.png)
 2. In the Team Explorer pane, click the **Manage Connections** toolbar button.
@@ -19,12 +23,12 @@ Before you authenticate, you must already have a GitHub or GitHub Enterprise acc
 ![Connect to GitHub in the manage connections dropdown in the Team Explorer pane](images/connect_to_github.png)
 4. In the **Connect to GitHub dialog** choose **GitHub** or **GitHub Enterprise**, depending on which product you're using.
 
-- **GitHub option**:  
-  ![Connect to GitHub dialog view](images/connect-to-github-dialog.png)
-  - To sign in with credentials, enter either username or email and password.
-  - To sign in with SSO, select `Sign in with your browser`.
+**GitHub option**:  
+![Connect to GitHub dialog view](images/connect-to-github-dialog.png)
+- To sign in with credentials, enter either username or email and password.
+- To sign in with SSO, select `Sign in with your browser`.
 
-- **GitHub Enterprise option**:  
-  ![Connect to GitHub Enterprise dialog view](images/connect-to-github-enterprise-dialog.png)
-  - To sign in with credentials, first enter GitHub Enterprise server address. Once a valid server address is entered, a `Token` field appears and a valid token can be entered to sign in.
+**GitHub Enterprise option**:  
+![Connect to GitHub Enterprise dialog view](images/connect-to-github-enterprise-dialog.png)
+- To sign in with credentials, first enter GitHub Enterprise server address. Once a valid server address is entered, a `Token` field appears and a valid token can be entered to sign in.
   - To sign in with SSO, first enter the GitHub Enterprise server address. Once a valid server address is entered, select `Sign in with your browser`. Follow the steps to authenticate with your SSO provider.