Upgraded readme.md (#265)

* bf cli doc header

* updated readme.md

* update readme.md

Author: Eyal

AzureCli.md

@@ -0,0 +1,91 @@
+# Azure CLI
+
+Botservice Extension is an Azure CLI extension that provides support for managing bots and channels on the Azure Bot Service.</br>
+
+## Prerequisites
+
+Get a [valid Azure subscription](https://azure.microsoft.com/en-us/free/).
+Install the [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest).
+
+## Installation
+Remove the azure bot extension if it's already installed.  
+`az extension list`  
+`az extension remove -n <extensionname>`  
+Install the bot service extension as follows -  
+`az extension add -n botservice`  
+
+**NOTE:** Please ensure you have Azure CLI version >= 2.0.45 installed to get the latest botservice extension. You can verify your AZ CLI version via `az -v`.
+
+# Managing a Bot
+
+## Creating a Bot
+Login into your Azure account via CLI:
+
+`az login`
+
+Ensure that you are using the right subscription for creating your bot:
+
+`az account show`
+
+If needed, change your subscription:
+`az account set --subscription <your-subscription-name>`
+
+You need a resource group (existing or new) to create your bot and related assets. If needed, create a new resource group:
+`az group create -l <resource-group-location> -n <resource-group-name>`
+
+Now create your bot:
+`az bot create -k webapp -g myResourceGroup -n myBot`
+
+If you did not specify Microsoft app credentials during creation, you will be asked to login again so that we can create those credentials on your behalf.
+> Tip: To avoid specifying the resource group, use `az configure --defaults group=myResourceGroup`.
+
+You can get your bot credentials and information using the `--msbot` option:
+`az bot show --msbot -n myBot -g myResourceGroup`
+
+Pro Tips:
+1) To avoid having to type your bot name and resource group name every time, use
+`az configure --defaults botname=myBot group=myResourceGroup`
+
+2) If you are stuck at any point, add a `-h` to the command to help you out.  For example:
+`az bot create -h`
+
+## Modifying a Bot
+The following workflow assumes that you have your bot name and resource group name configured by default using 
+`az configure`.  
+
+A typical bot workflow is connecting your bot to msbot, downloading the source code, and then publishing back to Azure with changes.
+
+First, connect your bot to msbot. You can get the MsBot CLI at [here](https://github.com/Microsoft/botbuilder-tools/tree/master/MSBot).
+`az bot show --msbot | msbot connect Azure --stdin`
+
+This will update your .bot file with all the information needed by other botbuilder tools to access it.  Now download the source code:
+`az bot download`
+
+This creates a folder with your bot name in the current directory (use `--file-save-path` to override the target folder), and downloads the bot source code into that folder. If you created your bot using `az bot create`, then the source code will be an echo bot project. It contains post-deploy scripts and build scripts to help deploy it back to Azure. Modify this template code as needed.
+
+To publish your code back to azure, from within the bot directory (use `--code-dir` to override the source folder) run:
+`az bot publish`
+
+## Updating Bot Properties
+Use the `az update` command to update your bot's description, message endpoint, etc.  
+For this, the command expects you to supply the right property and value that needs to be updated.  To update your bot's description:
+
+`az bot update --set properties.description="my new bot description"`
+
+## Deleting a Bot
+`az bot delete` deletes your bot.
+
+Please note that deleting your bot only deletes the bot resource. It does not clean up other resources provisioned during the creation of your bot like storage account, web site, etc.
+
+# Managing Bot Channels
+The Azure bot extension supports addition, removal and display of properties for all kinds of channels supported by the Azure Bot Service.  Refer to [Bot Service Channel Management](https://docs.microsoft.com/en-us/azure/bot-service/bot-service-manage-channels) for the necessary parameters needed to configure each channel.
+
+The CLI supports various commands for each channel.  Type `az bot <ChannelName> -h` to learn more.  For example,
+`az bot webchat show -n myBot -g myResourceGroup` shows the parameters in the webchat channel for the bot.  If you used `az configure` to set bot name and ResourceGroup, you can call `az bot webchat show`.
+
+To remove a channel from a bot, use `az bot directline delete`.
+
+# Known Issues and Limitations
+These are the known issues and limitations that the CLI has right now.  
+1) Creation of msa app id and password is not supported for hotmail.com accounts.
+2) `az bot publish` fails for a c# solution , when the project is open in visual studio. To work around this for now, please close the solution before doing a publish.

README.md

@@ -1,43 +1,67 @@
+
+
+![Bot Framework CLI](./media/BFCLI-header.png)
+
 # BF Command Line Interface
 
 [![Build Status](https://fuselabs.visualstudio.com/SDK_v4/_apis/build/status/CLI/Botframework-CLI-CI-PR?branchName=master)](https://fuselabs.visualstudio.com/SDK_v4/_build/latest?definitionId=537&branchName=master)
 [![Coverage Status](https://img.shields.io/coveralls/github/microsoft/botframework-cli/master)](https://coveralls.io/github/microsoft/botframework-cli?branch=master)
 
 The new BF Command Line Interface (CLI) tool replaces the collection of standalone tools used to manage Bot Framework bots and related services. We have ported most tools and are in process of porting the rest. The new BF CLI aggregates the collection of cross-platform tools into one cohesive and consistent interface.
 
-The old tools will be deprecated in subsequent releases. All new investments, bug fixes, and new features will be implemented in the new consolided BF CLI alone.
+The old tools will be deprecated in subsequent releases. All new investments, bug fixes, and new features will be implemented in the new consolidated BF CLI alone.
+
+## Installation
+
+BF is based on the Node.js platform and the [OClif](https://github.com/oclif/oclif) framework where it inherits its command line parsing style, and plugin architecture platform. 
+
+You must download the following prerequisites:
+
+* [Node.js](https://nodejs.org/) version 10.14.1 or higher
+
+Install the tool using the following command: 
+
+~~~
+$ npm i -g @microsoft/botframework-cli
+$ bf
+~~~
 
 ## Available Commands
 The following commands are currently available:
 * [Chatdown](https://github.com/microsoft/botframework-cli/tree/master/packages/cli#bf-chatdown) 
 * [QnAMaker](https://github.com/microsoft/botframework-cli/tree/master/packages/cli#bf-qnamaker)
 * [Config](https://github.com/microsoft/botframework-cli/tree/master/packages/cli#bf-config)
-* [Luis](https://github.com/microsoft/botframework-cli/tree/master/packages/cli#bf-luis)
+* [Luis](https://github.com/microsoft/botframework-cli/tree/emimunoz/luis/packages/cli#bf-luis)
 
-### Future Commands
+#### Future Commands
 The following commands will be ported in upcoming releases:
 * LUIS (API)
 * Dispatch
 
 See [Porting Map](https://github.com/microsoft/botframework-cli/blob/master/PortingMap.md) for a mapping reference between old and new tools
 
+## Overview
 
-## Plugin Architecture
-BF CLI is based on [OClif](https://github.com/oclif/oclif) Framework and inherits its command line parsing style, and plugin architecture. 
+The  Bot Framework Command Line Interface (BF CLI) cross-platform tool is used to manage Bot Framework bots and related services. It is part the [Microsoft Bot Framework](https://github.com/Microsoft/botframework), a comprehensive framework for building enterprise-grade conversational AI experiences.  In particular, BF CLI provides fundamental functionality when used in conjunction with Continuous Integration, and Continuous Deployment (CI/CD) pipelines. 
 
-## Installation
+As you build your bot, you may also need to integrate AI services like [LUIS.ai](http://luis.ai) for language understanding, [QnAMaker.ai](http://qnamaker.ai) for your bot to respond to simple questions in a Q&A format, and more. The _[bf luis](./packages/cli#bf-luis)_ command is used to convert, and translate language definition _.lu_ files or generate corresponding source (C# or JavaScript) code. Then, use the [Luis Tool](https://github.com/microsoft/botbuilder-tools/tree/master/packages/LUIS)  to deploy the local files, train, test, and publish them as Language Understanding models within the LUIS service. If used to define QnAMaker question/answer Knowledgebase, use the _[bf qnamaker](./packages/cli#bf-qnamaker)_ command to create and manage QnAMaker assets both locally, and on the QnAMaker service. Please refer to the[ _lu_ library documentation](./packages/Ludown)  for extended discussion on how to work with .lu file formats. _Note: You may be familiar with the Luis command if you used the legacy [LuDown](https://github.com/microsoft/botbuilder-tools/tree/master/packages/Ludown) and [LuisGen](https://github.com/microsoft/botbuilder-tools/tree/master/packages/LUISGen) tools._
 
-BF is based on the Node.js platform. You must download the following __prerequisties__:
+As your bot grows in sophistication, use [Dispatch](https://github.com/Microsoft/botbuilder-tools/tree/master/packages/Dispatch) CLI  to create and evaluate LUIS models used to dispatch intent across multiple bot modules such as LUIS models, QnA knowledgebases, and assist in routing messages to backend bot skills.
 
-* [Node.js](https://nodejs.org/) version 10.14.1 or higher
+To test and refine your bot, you can use the new [V4 Bot Framework Emulator](https://github.com/Microsoft/BotFramework-Emulator/releases). The Bot Framework Emulator is a cross-platform [Electron](https://electronjs.org/) application that enables you to test and debug your bots on local machine or in the cloud.
 
-Install the tool using the following command: 
+Also, during early designs stages you may want to create mockup of conversations between the user and the bot for the specific scenarios your bot will support. Use [bf chatdown](./packages/Chatdown) command to author conversation mockup .chat files and convert them into rich transcripts and view the conversations in the the Emulator. 
+
+Lastly, with the [Azure CLI Bot extension](./AzureCli.md) (_az bot_ command), you can create, download, publish, configure channels with the [Azure Bot Service](https://azure.microsoft.com/en-us/services/bot-service/). It is a plugin that extends the functionality of Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest) to manage your Azure Bot Service assets.
 
-~~~
-npm i -g @microsoft/botframework-cli
-~~~
 
-To view detailed usage information see the [CLI ReadMe page](https://github.com/microsoft/botframework-cli/tree/master/packages/cli)
+### See Also
+* [Detailed Usage Information](https://github.com/microsoft/botframework-cli/tree/master/packages/cli)
+* [Bot Framework Homepage](https://dev.botframework.com/)
+* [Azure Bot Service](https://docs.microsoft.com/en-us/azure/bot-service/bot-service-overview-introduction?view=azure-bot-service-4.0)
+* [LUIS](https://docs.microsoft.com/en-us/azure/cognitive-services/luis/index)
+* [QnAMaker](https://docs.microsoft.com/en-us/azure/cognitive-services/qnamaker/)
+* [Bot Design Guidelines](https://docs.microsoft.com/en-us/azure/bot-service/bot-service-design-principles)
 
 ## Issues and Feature Requests
 Please file issues and feature requests [here](https://github.com/microsoft/botframework-cli/issues). 
@@ -68,3 +92,9 @@ provided by the bot. You will only need to do this once across all repos using o
 This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
 For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
 contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
+
+## Reporting Security Issues
+
+Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at [[email protected]](mailto:[email protected]). You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the [MSRC PGP](https://technet.microsoft.com/en-us/security/dn606155) key, can be found in the [Security TechCenter](https://technet.microsoft.com/en-us/security/default).
+
+Copyright (c) Microsoft Corporation. All rights reserved.