In my last post, Securing an Azure Function App with Azure AD - Works with SharePoint Framework!, I showed how you can secure a REST API deployed as an Azure Function App using Azure Active Directory (AzureAD). 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.

If you create an application or API that is secured with Azure AD, you are likely going to require a consumer of your application to provide an OAuth access token in order to access your application or API. The caller would have to obtain this token from Azure AD by first authenticating with Azure AD and then request a token for your application. But anyone can create an OAuth access token. It”s just a JSON object that has a set schema and then base64 encoded. There”s nothing secure about it.What legitimizes its use as a security token is that the creator of the token digitally signs the token with a public-private key pair. The creator of the token uses their private key and includes the result in the OAuth access token in the JWT (JavaScript Web Token) format. If you”ve elected to use Azure AD to secure your REST API, you have established a trust with Azure AD.

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 Azure AD 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 Azure AD 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!

In the SharePoint Framework v1.6.0 release, Microsoft introduced a new capability to the framework. After a long time in the developer preview state, that release gave developers the ability to call Azure AD secured APIs & endpoints through a proxy Azure AD application.

I’m excited to share this latest update to my course, Mastering the SharePoint Framework for developers.

After the last few weeks of three straight conferences, I’m not exactly thrilled to look forward to the next set of commitments I have, but here they are anyway.

This week I presented at Microsoft’s first Ignite Conference in Chicago, IL. This was by far the biggest conference I’ve attended or been a part of coming in at around 22,000 people.

Last week I presented at the Microsoft Build conference which was a special treat as it was the first Build conference I’ve attended.

Last week at the Microsoft Build conference & this week at Microsoft’s Ignite conference, I presented short express talks / theater sessions on using Node.

On the heels of Build, I’m heading straight to Chicago for microsoft’s Ignite conference. This is the third conference Ina row after SharePoint Evolutions in London, then Build in San Francisco so you’ll have to understand why I’m only sticking around until Tuesday afternoon.