This is part three in a three part series on Authorization Code Flow with Microsoft Identity. If you haven't started at Part 1, I would suggest you do as it would make more sense than starting from here. One thing that was pointed out in the previous post, though, was that any id token for... Continue Reading →
This is part two in a three part series on Authorization Code Flow with Microsoft Identity. If you haven't started at Part 1, I would suggest you do as it would make more sense than starting from here. Previously I had written about how to use Azure Functions to create an OAuth 2.0 Authentication Code... Continue Reading →
This is part one in a three part series on Authorization Code Flow with Microsoft Identity. You can also follow through to Part 2 and Part 3. Single Page Applications (SPAs) are a great. For me, they are cheap front-end as they are just static files that don't need a whole web server/service and there... Continue Reading →
One of my little projects is a static website running on Azure CDN, with a custom domain endpoint enforcing HTTPS traffic only. This caused a little issue when attempting to reach the URL via http, as my sister-in-law kept doing. Now when I set this up, I assumed that any HTTP requests would redirect to... Continue Reading →
Recently, we came across the following issue when attempting to sign a VSTO Add-In with a code-signing certificate: An error occurred while signing: Unknown error "-2147012865" Any search of the error message brought up related answers but not ones specific to this particular error number. Although I can't be sure of the error number, I... Continue Reading →
Out of the box, SharePoint Online allows someone to authenticate through either the older claims-based authentication or the newer modern authentication. This post shows you how to know if claims is blocked for third-party applications.
When Azure Front Door was first released, it allowed you to have one backend host route to a multitude of different services based on the routing path. The addition of the Rules Engine provides so much more possibility.
"Authentication failed, it is either not correct, or expired, or does not have the correct permission" when attempting to copy files to blob storage in Azure Pipelines.