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!

I recommend people avoid this option for granting their SPO tenant permissions to endpoints and services secured with Azure AD.

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

I’m looking forward to the premiere Microsoft SharePoint Conference 2019 in Las Vegas, May 19-24, 2019, at the MGM Grand.

Over the last two weeks, I have been presenting on the topic of the SharePoint Framework (SPFx) at a pair of SharePoint conferences (the European SharePoint Conference in Copenhagen & SharePoint Fest in Chicago).

You know what I don’t like about automated tests? Most of the time, we don’t automate them, we just instrument them.

The latest version of the SharePoint Framework (SPFx) released a few weeks ago, v1.7.0, uncovered a few issues between how the various Node.

On November 8, 2018 (last Thursday), Microsoft released v1.7.0 of the SharePoint Framework (SPFx). This release is filled with a lot of new things Microsoft has been talking about for a few months.

I’ve seen more and more questions since the folks at NPM added an automatic scan for vulnerabilities after every NPM install.

This month’s update on my Mastering the SharePoint Framework course features the transition from one sprint to the next.