Session Abstract

The Microsoft 365 ecosystem is great for extensibility and creating applications that deeply integrate different Microsoft 365 products to fulfill complex business needs. But projects can quickly become complex simply due to multiple API versions or the need to support multiple M365/Office application versions. Some customization models and tools are very well documented, maintained and supported, making the development process a breeze, but this is not always the case and previous experience is what can help developers avoid painful mistakes from bad decisions. I this session, I will share lessons learned from the field on my experience building a complex Outlook add-in that integrates with SharePoint and allow users to manage files without ever opening a SharePoint page. What worked well and not so well. Product and API limitations that impacted application design and development. The tools that proved reliable and really made development easier. The lessons I learned can help you avoid common pitfalls and build a better solution.

Joel Rodrigues

I am a M365 developer with over 10 years of SharePoint and M365 development experience. Focusing mostly on creating SharePoint solutions, and having worked with all versions since SharePoint 2007, I prefer SharePoint Online as it allows me to use the latest available tools to build interesting solutions. I am passionate about the M365 development ecosystem and the amazing community.