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.
ngrok is a fantastic tool, that I use on an everyday basis when building solutions cloud. It allows me to host and debug an application locally and at the same time host the website or API’s with a publicly accessible https endpoint. As I work quite a bit with Microsoft Teams development this is essential when building bots (Azure Bot Service cannot talk to localhost) or building out Teams Tabs with SSO.
When you’re working with building applications or services there’s always a need to store configuration. For Azure there’s a great service called Azure App Configuration that allows you to securely store, manage and retrieve configuration settings. It’s a perfect service for both smaller and larger projects and it keeps your configuration in control, and of course secured and audited. When I’m building solutions using node I typically start with storing my configuration in a local .
Such a great week this is, after being accepted into the Microsoft Regional Director community earlier this week, today marks the 11th time I’m awarded with the Microsoft MVP for Office Apps & Services. Dear Wictor Wilen, We’re once again pleased to present you with the 2020-2021 Microsoft Most Valuable Professional (MVP) award in recognition of your exceptional technical community leadership. We appreciate your outstanding contributions in the following technical communities during the past year:
I’m incredibly proud to announce that I’ve been accepted into the Microsoft Regional Director program. The Microsoft Regional Director (RD) program is a global community of passionate technology thought leaders, where Microsoft once a year appoints a small set of leaders as Regional Directors, to serve on a two years basis. It’s a fantastic opportunity for me to play a small role in this group of people - that I look up to as leaders, superstars, humans.