The extensibility landscape of Microsoft 365 can be convoluted and confusing. In this session I will explore real world user scenarios that were automated by artfully combining various extensibility methods of the Microsoft 365 platform into one cohesive solution. My goal for this session is to have you start imagining how you can take solutions well beyond just a web part or just an application customizer into more robust fully functional end to end solutions. We'll do that by discussing a problem statement, analyzing the different ways we could leverage the platform, discussing the final architecture, and when appropriate diving into bits of code where the implementation details are important.

When programming with ReactJS, which is a common choice when developing using the SharePoint Framework, how you architect your components can often be confusing. This introductory session will walk through designing your components to mirror a common design principle called "Atomic Design" which was invented by web designer Brad Frost. This design pattern breaks web design into small chunks that when combined build beautiful solutions with reusability at its core. We'll go into how to translate that design principle into component development which can help reduce code size, improve reliability and quality, and just make your life easier. As part of our examples, we'll be leveraging the HTWOO community built Fluent UI framework.

Your intranet is the entry point to all your company tools and resources. This can be anything from an external website or solution, a custom application, etc. How to centralize all these different tools and applications is one of the most common questions Sympraxis Consulting gets from clients. Typically, organizations will manually add links to these resources using various web parts across many sites. There is no way out of the box to search your environment for these links. This introduces individual management of enterprise resources, which can cause challenges when there are company changes. For example, if your company uses Workday for their finances but then decides to switch to Oracle, you’ll have to manually adjust all the different links to Workday within your intranet. If all those links are centralized it is scalable and much easier to manage as the owner of that link can instead edit in one place and have it reflected everywhere.   In this session, we'll take a holistic view of the technology through the lens of the Maturity Model for Microsoft 365 and gain an understanding of current state vs. desired state can help organizations in these important ways:   - Define current state and limitations with out of the box web parts - Understand and compare options for solving your organizations quick links issues through extension - Identify the pros and cons of each approach

Mature organizations that use Microsoft 365 often need to run custom workflows when events happen in Microsoft 365, like updating list items, adding users, updating groups, or changing files. When there's only a single list or library, or other single event items, it can make sense to use a tool like Power Automate or an Azure Logic Apps. However, these tools require connecting a workflow to a specific entity (list, library, drive) making these solutions difficult to manage when there are many of the same types of items to monitor. Enter stage left: Webhooks. To be clear, webhooks are not a power user tool; they require the ability to architect and manage cloud resources and write enterprise level code. But the benefits and scalability make it well worth the time investment! In this session you'll learn about: • What webhooks are and what are some of the common use cases they can help solve • What common architectural pattern for managing your subscriptions and events looks like • What cloud services are commonly used to support the common architecture • What boilerplate code looks like to establish and manage subscriptions and react to event notifications • Where and how you might implement custom handlers for establishing what subscriptions are needed and what happens when an event is fired. Don't miss this opportunity to learn how to manage workflows at scale to reduce risk and simplify management!

The SharePoint framework introduced 'libraries' as a project type, and although useful for very small development projects not ideal for bigger enterprise solutions and ALM strategies. This session is going to cover end to end building a library with standard web-based building blocks, using Azure Dev Ops to create a private code artifact, and then consuming that library and others together within a SharePoint framework solution while hosting the artifacts in an Azure CDN (or bundling it in if that's more appropriate). This is powerful reusability that allow you to manage the lifecycle of different components in a way that mimics all the other packages you might consume when building your solution.