A common interview question for SharePoint professionals is to ask the candidate what they hate about the product. This is a great interview question because it’s fun, it’s open-ended, and it allows people to open up about their experiences with SharePoint. And let’s face it, there’s a lot to hate about SharePoint.

In part 1 of this blog I discussed Service Principals and Role Assignments in Azure and walked through how to set them up. In this blog we’ll put the concepts to work by creating a couple of simple integrations against Azure.

Sometimes when we work with Azure we use automated processes and tools to interact with cloud resources there. These processes and tools need a way to authenticate to Azure to do their work. Often they will use a service principal to do this.

I recently had a client enable Multi-Geo functionality in SharePoint Online in order to satisfy some regulatory requirements, and they were finding that the search-driven experiences we had built for them did not seem to be multi-geo aware, and asked me to come up with a solution. Having never seen multi-geo in the wild before I jumped at the chance to tackle an interesting problem and set about looking for a solution.

I came across a very strange issue this week trying to locally debug TypeScript Azure Functions in Visual Studio Code. The F5 debugger invocation was throwing a failure with the message “No such file or directory”.

In SharePoint, things happen, and often we need to trigger other things in response to those events.

Next you can update your site name, avatar and other options using the _config.yml file in the root of your repository (shown below).