Added UseMSStoreCLI.

Author: azchohfi

hub/apps/publish/msstore-dev-cli/ci-cd-environments.md

@@ -12,7 +12,7 @@ The Microsoft Store Developer CLI (preview) supports running in CI/CD environmen
 
 The firststep to achieve this it to install the Microsoft Store Developer CLI (preview) on your CI/CD environment. You can find instructions on how to do this [here](install.md).
 
-After installing the Microsoft Store Developer CLI (preview), you have to configure your environment to be able to run commands. You can do this by running the `msstore` command with the specific parameters that identify your partner center account (_TenantId_, _SellerId_, _ClientId_, _ClientSecret_).
+After installing the Microsoft Store Developer CLI (preview), you have to configure your environment to be able to run commands. You can do this by running the `msstore reconfigure` command with the specific parameters that identify your partner center account (_TenantId_, _SellerId_, _ClientId_, _ClientSecret_).
 
 It is very important to hide these credentials, as they will be visible in the logs of your CI/CD pipeline. You can do this by using **secrets**. Each CI/CD pipeline system have different names for these secrets. For example, Azure DevOps call them [_Secret Variables_](/azure/devops/pipelines/process/set-secret-variables), but GitHub Action calls them [Encrypted Secrets](https://docs.github.com/actions/security-guides/encrypted-secrets). Create one **secret** for each of the parameters (_TenantId_, _SellerId_, _ClientId_, _ClientSecret_), and then use the `reconfigure` command to setup your environment.
 
@@ -21,6 +21,8 @@ For example:
 ## Azure DevOps
 
 ```yaml
+- task: UseMSStoreCLI@0
+  displayName: Setup Microsoft Store Developer CLI
 - script: msstore reconfigure --tenantId $(PARTNER_CENTER_TENANT_ID) --sellerId $(PARTNER_CENTER_SELLER_ID) --clientId $(PARTNER_CENTER_CLIENT_ID) --clientSecret $(PARTNER_CENTER_CLIENT_SECRET)
   displayName: Configure Microsoft Store Developer CLI
 ```