Microsoft 365 Microsoft Teams Microsoft Office365 Microsoft Azure Microsoft Graph Microsoft Flow Microsoft SharePoint
Yannick (a Microsoft Office Development MVP) is born and raised in SharePoint, starting out his career almost 10 years ago when SharePoint 2010 was still new and shiny. The changing reality of the cloud made him expand his knowledge to the whole of Office 365 and Azure, but SharePoint and Microsoft Teams are still his focus areas. He is a Managing Partner and Cloud Solution Architect at Qubix, a Belgium-based consultancy firm, responsible for the technical underpinnings of products and solutions. Problem solving and development are his passion, still working day to day with code. He always asks the important questions: How does it work? What do you want to achieve? Do we really need development for this? Where's the coffee?
You've spent months developing your awesome application for Microsoft Teams, but it's of no use if it is only available for your development team. Time to look at all ways to package and deploy your Microsoft Teams application from development phase, over initial testing with a limited group and corporate distribution, to distributing as an ISV to the outside world. We'll also touch on the developer attestation and app certification process as a means to increase the trust in your application, get a more visibility in the app store and reach more users.
"Microsoft Teams is a platform", what does this even mean? You keep hearing that you should integrate your application in Microsoft Teams, but you have no idea how to get started? Customers keep asking you to integrate capabilities of Microsoft Teams in their existing applications, but it's still unknown territory?
This and more is what we'll be answering with an overview of the Microsoft Teams developer story, you'll be itching to start and bring your own experiences to Microsoft Teams.
What experience would bring value to my users? Which development framework to use? What UI framework to use? These are just a couple of questions that come up in that design phase of your new Microsoft Teams application. We'll run through 10 most common things you need to consider when architecting your application, discuss the pro's and con's of each and provide you with the knowledge to make informed decisions next time you are architecting an application for Microsoft Teams.