Bridge Communications

Saturday, February 11, 2017

Extending Microsoft Teams for Developers - Part II

Today we will extend our look into how to publish content into Microsoft Teams using the Office 365 connector model and webhooks.  Make sure you have your webhook url handy for last week, because we will use it again.

Creating an Office 365 Connector SDK Class

You can create your own, or you can use the one Microsoft has posted in Github and extend it like I am going to.

Here are the classes include

As you can see the Message class is a combination of the sub classes and it also holds are method for posting with a parameter of our webhook url.

Here is a sample piece of code that creates a simple console app, defines the message, then posts it to our Teams channel.

You can see the result here, it's a bit a of train-wreck to put it mildly.

The reason it looks bad, isn't because we did anything wrong, rather Teams just doesn't quiet render the data properly, yet, as I am told they are aware of it, and working on a solution.

As you can see here if we posted the same thing to Office Groups, we get more like what we would have expected.

So what works and what doesn't work so well in teams?

Basic message with title and text
Section using the fact class *minus the image, it's cut off

Not Working
Section of images
Potential Action (The blue button that takes us to a website)

Since it works so much better today in Office Groups, next week I'll show you how to create a group and add a webhook you can post to directly to Microsoft Outlook.

Doug Routledge, C# Lync, Skype for Business, SQL, Exchange, UC, 
Full Stack Developer  BridgeOC Bridge Operator Console
Twitter - @droutledge @ndbridge

No comments:

Post a Comment

Any spam comments will be deleted and your user account will be disabled.