Level 300. SPFx solutions can easily access SharePoint and Graph data using page context permissions—but what happens when you need to connect to external APIs, protect sensitive credentials, or perform operations that require elevated permissions? Azure Functions provide the secure backend layer your SPFx solutions need for production-grade scenarios. In this session, you'll learn how to architect secure SPFx solutions using Azure Functions: - Beyond Page Context: When and why you need a separate API layer for your SPFx solutions - Secure by Design: Protect API keys, connection strings, and sensitive data using Azure Key Vault and Entra ID authentication - Flexible Triggers: Build on-demand APIs for SPFx calls or scheduled functions for background processing - Real-World Patterns: See production examples handling third-party APIs, data aggregation, and complex operations You'll see working examples, understand authentication flows between SPFx and Azure Functions, and learn deployment strategies that work in enterprise environments. Whether you're integrating with external systems, processing data at scale, or building solutions that require elevated security, Azure Functions provide the architecture pattern you need. Stop exposing credentials in client-side code. Start building SPFx solutions with enterprise-grade security.
This is the partner session to my Battle Tested Data session, covering the one part of data connectivity that the other session does not have time for. That said, it is a completely stand-alone session, soattending the other session is not required.
As a Microsoft MVP in M365 Development and Microsoft Graph, Don has spent the last 20 years working with companies of all sizes, helping them maximize their productivity in SharePoint, Office 365 and Azure. With over 30 years of programming experience, Don's passion for coding is centered around the complete Microsoft ecosystem of cloud technologies. He loves working the entire development stack, from database design to the user interface, including no code/low code solutions in the Power Platform. Prior to working full-time as a software developer, Don spent 20 years as a pilot in the Air Force, accumulating over 4500 hours in various aircraft, including the T-1A, E-3B/C, and T-38.