3.0.1 is ready for release.

MethodsAndPractices · Jul 11, 2018 · bf984c5 · bf984c5
1 parent 74d588f
commit bf984c5
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/.docs/Add-VSTeamAccount.md b/.docs/Add-VSTeamAccount.md
@@ -76,7 +76,7 @@ Note: You must run PowerShell as an Adminstrator to store at the Machine level.
 PS C:\> Add-VSTeamAccount -Account mydemos -Token $(System.AccessToken) -UseBearerToken
 ```
 
-Will add the account and use the OAuth Token provided by VSTS when you check the *Allow scripts to access OAuth token* checkbox on the phase. Using this method removes the need to create a Personal Access Token. Note -Token is just an alais for -PersonalAccessToken.  
+Will add the account and use the OAuth Token provided by VSTS when you check the *Allow scripts to access OAuth token* checkbox on the phase. Using this method removes the need to create a Personal Access Token. Note -Token is just an alais for -PersonalAccessToken.  The token is scoped to only allow access to the account running the build or release. To access other accounts you will have to use a personal access token.
 
 ## PARAMETERS
 

diff --git a/README.md b/README.md
@@ -22,6 +22,8 @@ Bearer auth will allow you to use the OAuth token created by VSTS during your bu
 Add-VSTeamAccount -Account mydemos -Token $(System.AccessToken) -UseBearerToken
 ```
 
+The token is scoped to only allow access to the account running the build or release. To access other accounts you will have to use a personal access token.
+
 ### 3.0.0
 
 There is a breaking change with calls to Add-VSTeamKubernetesEndpoint. The acceptUntrustedCerts and generatePfx parameters have been changed from boolean to switch. So any calls that contained: