[Node] Updates for Microsoft Teams support

* [Node-ReceiveAttachment] Update to support MS Teams attachments
* [Node] README updates on Microsoft Teams support

Node/cards-CarouselCards/README.md

@@ -57,6 +57,7 @@ To get more information about how to get started in Bot Builder for Node and Att
 * [Message.attachmentLayout](https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.message.html#attachmentlayout)
 * [AttachmentLayout](https://docs.botframework.com/en-us/node/builder/chat-reference/modules/_botbuilder_d_.html#attachmentlayout)
 * [Adding Attachments to a Message](https://docs.botframework.com/en-us/core-concepts/attachments)
+* [Carousel Layout in Microsoft Teams](https://msdn.microsoft.com/en-us/microsoft-teams/bots#carousel-layout)
 * [RichCards sample](../cards-RichCards)
 
 > **Limitations**  
@@ -67,6 +68,7 @@ To get more information about how to get started in Bot Builder for Node and Att
 > The features used in this sample are fully supported in the following channels:
 > - Skype
 > - Facebook
+> - Microsoft Teams
 > 
 > They are also supported, with some limitations, in the following channels:
 > - Telegram

Node/cards-RichCards/README.md

@@ -227,13 +227,14 @@ To get more information about how to get started in Bot Builder for Node and Att
 * [AudioCard](https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.audiocard.html)
 * [Message.addAttachment](https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.message.html#addattachment)
 * [Attachment](https://docs.botframework.com/en-us/node/builder/chat-reference/interfaces/_botbuilder_d_.iattachment.html)
+* [Cards and buttons on Microsoft Teams](https://msdn.microsoft.com/en-us/microsoft-teams/bots#cards-and-buttons)
 
 > **Limitations**  
 > The functionality provided by the Bot Framework Activity can be used across many channels. Moreover, some special channel features can be unleashed using the [Message.sourceEvent](https://docs.botframework.com/en-us/node/builder/chat-reference/classes/_botbuilder_d_.message.html#sourceevent) method.
 > 
 > The Bot Framework does its best to support the reuse of your Bot in as many channels as you want. However, due to the very nature of some of these channels, some features are not fully portable.
 > 
-> The Hero card, Thumbnail card, Receipt card and Sign-in card used in this sample are fully supported in the following channels:
+> The Hero card and Thumbnail card used in this sample are fully supported in the following channels:
 > - Skype
 > - Facebook
 > - Telegram
@@ -249,6 +250,27 @@ To get more information about how to get started in Bot Builder for Node and Att
 > On the other hand, they are not supported and the sample won't work as expected in the following channel:
 > - SMS
 >
+> The Receipt card and Sign-in card used in this sample are fully supported in the following channels:
+> - Skype
+> - Facebook
+> - Telegram
+> - DirectLine
+> - WebChat
+> - Slack
+> - Email
+> - GroupMe
+> 
+> They are also supported, with some limitations, in the following channel:
+> - Kik
+> 
+> On the other hand, they are not supported and the sample won't work as expected in the following channel:
+> - SMS
+> - Microsoft Teams
+>
 > The Animation card, Video card and Audio card used in this sample are fully supported in the following channels:
 > - Skype
 > - Facebook
+> 
+> On the other hand, they are not supported and the sample won't work as expected in the following channel:
+> - Microsoft Teams
+>

Node/core-CreateNewConversation/README.md

@@ -68,6 +68,7 @@ To get more information about how to get started in Bot Builder for Node and Dia
 > 
 > On the other hand, they are not supported and the sample won't work as expected in the following channels:
 > - Facebook
+> - Microsoft Teams
 > - DirectLine
 > - WebChat
 > - Kik

Node/core-GetConversationMembers/README.md

@@ -143,13 +143,16 @@ To get more information about how to get started in Bot Builder for Node, Conver
 > 
 > The features used in this sample are fully supported in the following channels:
 > - Skype
-> - Facebook
 > - Slack
 > - DirectLine
 > - WebChat
 > - Email
 > - GroupMe
-> 
+>
+> They are also supported, with some limitations, in the following channels:
+> - Facebook
+> - Microsoft Teams
+>
 > On the other hand, they are not supported and the sample won't work as expected in the following channels:
 > - SMS
 > - Kik

Node/core-MultiDialogs/README.md

@@ -229,6 +229,7 @@ To get more information about how to get started in Bot Builder for Node and Dia
 > The features used in this sample are fully supported in the following channels:
 > - Skype
 > - Facebook
+> - Microsoft Teams
 > - Slack
 > - DirectLine
 > - WebChat

Node/core-ReceiveAttachment/README.md

@@ -19,7 +19,7 @@ When attachments are sent to the bot they can be found in the message activity [
 This property exposes a list of [IAttachment](https://docs.botframework.com/en-us/node/builder/chat-reference/interfaces/_botbuilder_d_.iattachment.html) representing each of the files sent. The attachment object contains information on the [contentType](https://docs.botframework.com/en-us/node/builder/chat-reference/interfaces/_botbuilder_d_.iattachment.html#contenttype) of the file and a [contentUrl](https://docs.botframework.com/en-us/node/builder/chat-reference/interfaces/_botbuilder_d_.iattachment.html#contenturl)  which is a reference to the location of the attachment's content. In order to access the actual attachment file you will need to download the address from the contentUrl property.
 Check out the key code located in the [dialog handler](app.js#L26-L43) where the `message.attachments` property of the message activity is read to get the first attachment and download it.
 
-> Note: The Skype attachment URLs are secured by JwtToken; you should set the JwtToken of your bot as the authorization header for the HTTP GET request your bot initiates to fetch content. Below is the sample code that temporarily works around this issue and set the JwtToken on the HTTP request. You should be careful when you send the bot's JwtToken to a third party server and should always make sure to send it to trusted parties.
+> Note: The Skype and MS Teams attachment URLs are secured by JwtToken; you should set the JwtToken of your bot as the authorization header for the HTTP GET request your bot initiates to fetch content. Below is the sample code that temporarily works around this issue and set the JwtToken on the HTTP request. You should be careful when you send the bot's JwtToken to a third party server and should always make sure to send it to trusted parties.
 
 ````JavaScript
 function (session) {
@@ -28,9 +28,9 @@ function (session) {
     if (msg.attachments.length) {
 
         // Message with attachment, proceed to download it.
-        // Skype attachment URLs are secured by a JwtToken, so we need to pass the token from our bot.
+        // Skype & MS Teams attachment URLs are secured by a JwtToken, so we need to pass the token from our bot.
         var attachment = msg.attachments[0];
-        var fileDownload = isSkypeMessage(msg)
+        var fileDownload = checkRequiresToken(msg)
             ? requestWithToken(attachment.contentUrl)
             : request(attachment.contentUrl);
 
@@ -66,8 +66,8 @@ var requestWithToken = function (url) {
 // Promise for obtaining JWT Token (requested once)
 var obtainToken = Promise.promisify(connector.getAccessToken.bind(connector));
 
-var isSkypeMessage = function (message) {
-    return message.source === 'skype';
+var checkRequiresToken = function (message) {
+    return message.source === 'skype' || message.source === 'msteams';
 };
 ````
 

Node/core-ReceiveAttachment/app.js

@@ -24,9 +24,9 @@ var bot = new builder.UniversalBot(connector, function (session) {
     if (msg.attachments.length) {
 
         // Message with attachment, proceed to download it.
-        // Skype attachment URLs are secured by a JwtToken, so we need to pass the token from our bot.
+        // Skype & MS Teams attachment URLs are secured by a JwtToken, so we need to pass the token from our bot.
         var attachment = msg.attachments[0];
-        var fileDownload = isSkypeMessage(msg)
+        var fileDownload = checkRequiresToken(msg)
             ? requestWithToken(attachment.contentUrl)
             : request(attachment.contentUrl);
 
@@ -68,6 +68,6 @@ var requestWithToken = function (url) {
 // Promise for obtaining JWT Token (requested once)
 var obtainToken = Promise.promisify(connector.getAccessToken.bind(connector));
 
-var isSkypeMessage = function (message) {
-    return message.source === 'skype';
+var checkRequiresToken = function (message) {
+    return message.source === 'skype' || message.source === 'msteams';
 };

Node/demo-ContosoFlowers/README.md

@@ -668,6 +668,7 @@ To get more information about how to get started in Bot Builder for Node review
 > - GroupMe
 > 
 > They are also supported, with some limitations, in the following channel:
+> - Microsoft Teams (Receipt card not supported)
 > - Email
 > 
 > On the other hand, they are not supported and the sample won't work as expected in the following channels:

Node/demo-Search/README.md

@@ -173,6 +173,7 @@ To get more information about how to get started in Bot Builder for Node please
 > The features used in these samples are fully supported in the following channels:
 > - Skype
 > - Facebook
+> - Microsoft Teams
 > - Telegram
 > - DirectLine
 > - WebChat

Node/intelligence-LUIS/README.md

@@ -205,6 +205,7 @@ To get more information about how to get started in Bot Builder for Node and LUI
 > The features used in this sample are fully supported in the following channels:
 > - Skype
 > - Facebook
+> - Microsoft Teams
 > - DirectLine
 > - WebChat
 > - Slack