Today at //Build we at Microsoft announced that the long awaited support for Collaborative apps in Teams Personal Tabs and Messaging Extensions now is available for usage in Office.com, Outlook and Outlook on the web. This update to Teams apps is based on the new Promise based Teams JS SDK version 2.0 and the just published Teams Manifest 1.13. Announcing Yo Teams version 4 Through the Microsoft 365 Platform Community (PnP) we have also released a brand new (preview) version of yo teams that supports both this new Teams JS SDK as well as the updated schema.
Five years! It’s been five years seen I first published the Microsoft Teams apps generator - yo teams, and in a few days we also have the 5th anniversary for the official Microsoft Teams launch. It’s been five very interesting years that has changed how we collaborate and communicate. It all started long before March of 2017. I had the opportunity to work for an organization that was one of the early adopters of Microsoft Teams, and driven by my curiosity I immediately saw that with this new tool had some amazing opportunities to create even better experiences for my customers.
We’re getting closer to the holidays and we all like to both give and receive gifts at this time of the year. Here is an early Christmas gift from me, and the amazing Microsoft teams that’s been building out these new features, to all of you fantastic people out there. A few months ago Microsoft announced the capabilities where we can deploy Microsoft Teams apps and use them across other high-usage areas of Microsoft 365 and now those areas has been extended even further and covers Office.
When building applications for Microsoft Teams, the very first hurdle essentially all developers will try to jump over is the one with getting an access token to be able to communicate with Microsoft Graph. This is something that can be done fairly easy, if you know what to do, but requires you as a developer to connect a few dots. Over the last year this has become way easier, and there are a few great examples out there - you can find some great ones in the PnP Teams Samples.
When building software the most common scenario is that you have a team building the solution, application and/or service. You typically have front-end, back-end and full-stack developers, you have testers and designers, and more. However, working in a team is not always easy. Back in the days we could all have our software running locally and we just grabbed the latest version/commit and hacked away. For web applications the use of localhost worked just fine for almost everyone.
The growth of using Yo Teams - the Microsoft Teams Apps generator - has been tremendous over the last year, and I can really tell that it’s not just being used for development and testing by the number of questions and requests I get on how to make a proper deployment of the solution to Azure. In this post I will share how I most often do it. The initial version of Yo Teams shipped with simple instructions on how to do Git deploy of your application to Azure.
Hey, I’m back. Long time since I did some writing on this blog. But I needed to get this one out. As you all know I’m a huge fan of the Microsoft Teams extensibility model and now with the SSO support for Tabs, it’s even easier to create integrated experiences for your end users where they can consume data and information from the Microsoft Graph or LOB systems. I recently did a small appearance at the Microsoft 365 PnP webcast showcasing how to configure and scaffold a Microsoft Teams project that uses this new SSO Tab feature.
Happy Easter everyone, I have fantastic news. After seven preview versions (and even a skipped version - 2.6) the Microsoft Teams Apps Yeoman generator 2.7.0 is now available for you to use! Just like tons of others do; there’s been over 6.000 downloads of the generator, it’s generating a handful of new Teams projects every day and it’s done from all parts of the world! Join the movement! As usual it is just a simple npm command to install: