A few weeks ago I posted that I am going to be in Prague in early December for ESPC 2019 speaking on SharePoint Framework development.

In just four simple steps, this post will show you how to automate the build, test & deployment to SharePoint Online of any SharePoint Framework project using Azure Pipelines.

Last week I wrote how I migrated my site from a dynamic CMS to a static site generated using Hugo. The site & all supporting processes are hosted in Microsoft Azure. In this post, I will explain how the site is automatically built and deployed when I either push new/updated content as well as on a scheduled basis. This is all implemented using Azure DevOps pipelines.

Last week I wrote how I migrated my site from a dynamic CMS to a static site generated using Hugo. The entire site and all supporting processes are hosted in the Microsoft cloud, specifically Azure DevOps & Microsoft Azure. In this post, I will explain how the site is hosted in Microsoft Azure. This assumes the static files have already been built so you will see how it's exposed to the world.

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!

Hey local peeps, interested in a great Azure community FREE event? Join me this Saturday for the Jacksonville, FL installment of the Global Azure Bootcamp 2018.

Over a decade ago I left the corporate world to join another company and start teaching developers about SharePoint.

Thoughts from the Microsoft Ignite 2016 Conference Last week Microsoft held their second Ignite conference in Atlanta, Georgia with just 23,000 of their closest friends.