Microsoft Entra ID

In my last post, Securing an Azure Function App with Entra ID - Works with SharePoint Framework!, I showed how you can secure a REST API deployed as an Azure Function App using Microsoft Entra ID. This comes in quite handy when you want to secure some custom server-side business logic that’’s called from a SharePoint Framework (SPFx) client-side solution. The SPFx docs show how to use APIs with permissions to the Microsoft Graph. This post will explain how to add custom permissions to the AzureAD application that is used to secure your Azure Function.

I recently published a new chapter in my Mastering the SharePoint Framework on-demand course for developers that included a section that showed how to call a REST API deployed using an Azure Function App and secured with Entra ID from the SharePoint Framework. When I was working on this chapter, it felt like the process of configuring an Azure Function App to be secured with Entra ID was harder and more complex than it should have been. Specifically, some of the things you do aren’t explained as well… so I decided to blog about it here!

Developers can declare permissions in SharePoint Framework projects, but it isn’t a good idea. In this article I explain why and suggest a better approach.

I’m excited to share this latest update to my course, Mastering the SharePoint Framework for developers. Today’s update, packaged as sprint 13, includes two new chapters and a few updates… and it’s a huge release… the biggest yet adding over 3 hours of new content! Sprint 13 also marks a milestone: the Fundamentals Bundle of the course is now content complete! This means all planned chapters are now published. I will continue to make edits to existing chapters updating content when circumstances warrant, but at this time no new chapters or lessons are planned.

At Microsoft Build and Ignite, a Node.js web app demo integrated TypeScript, AzureAD, ADAL, & Office 365 APIs to run on any platform.

Explore the Client Credentials Grant Flow for Microsoft Entra ID - perfect for service apps with no user interaction.

Microsoft introduced ADAL JS, a library supporting OAuth2 implicit flow, allowing client-side solutions to leverage Microsoft Entra ID for authentication.

As an app developer, I share my interest in Microsoft Entra ID (formerly Azure AD) & OpenID Connect for app auth. Join my Pluralsight course to learn more.

Blog post discussing three OAuth2 authentication flows supported by Microsoft Entra ID: Authorization Code, Client Credentials, and Implicit Grant.

The authentication dance can be the hardest part of working with Office 365 APIs. Check out the Pluralsight course on authentication and discovery.

I discovered changes in the Azure portal Active Directory applet while getting screenshots, later clarified as hints of future updates.

Microsoft Entra ID (formerly Azure AD), supports two types of application authentication configurations - single and multi-tenant. Learn what’s different.

Learn from my experience as I share tips & insights on how to authenticate and obtain access tokens for Office 365 APIs.

Walkthrough leveraging Microsoft Entra ID Authentication Library & Open Web Interface for .NET to offload authentication to Microsoft Entra ID for web apps.

I discuss the importance of having a OAuth2 access token for Microsoft 365 and explain how to obtain it using Microsoft Entra ID.

Learn to manually create a Microsoft Entra ID app for Office 365 integration with Andrew Connell’s step-by-step guide.

The second post in a three-part series on creating an Azure app for Office 365 APIs using a wizard in Visual Studio 2013

My site offers tips and insights on Microsoft Entra ID and authentication for Office 365 APIs to help fellow developers navigate identity complexities.

Microsoft released Research Project Code Sample on OfficeDev Github, showcasing best practices for creating apps with Office 365 & SharePoint Online.