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.
Today I thought that I should step out of my normal blogging content and share some of my personal pet project and hobbies. I always been keen of tinkering, testing and building things - being software, hardware, or our house or garden. Over the last few years I’ve been trying to make as much things as possible “smart” in our houses, and particularly in my home office. This home automation project consists of tons of different third party options, but also quite a few devices and gadgets that I built myself.
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.
Today I handed in my Orange badge to Avanade and signed out of my Avanade account. It’s been a six and a half year long adventure where I had the opportunity work with amazing colleagues and exciting clients. I’ve been given the opportunity to grow my career and skills in directions I did not think about, and I’m very proud of what we achieved and what we delivered to clients.
I’ve been using Ring cameras for several years now and a while back they introduced the option to have the cameras take snapshots periodically. This is awesome as you can fire up the Ring app and see a timelapse of your cameras. However, this only works in the app, you can’t export a timelapse! But, as a proud geek this should not be a problem to me and can be solved!
Yesterday Microsoft released the anticipated set of scripts required for you to add the Microsoft Viva Connections app to your Microsoft Teams environment. It’s a very simple approach that only requires you to download a PowerShell script, install the latest Microsoft SharePoint Online PowerShell module and then answer a set of questions, and voila you have the Viva Connections Desktop app ready for installation in Microsoft Teams. Note: as the time of writing this and testing the PowerShell script, I was not able to download the required SharePoint Online PowerShell module and received an error while running the script.
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.