In part 1 of this series, I talked about some of the license reporting features in Office 365. The big takeaway from that article is simple: many Office 365 admins want to know how many users have installed Office 365 Pro Plus, and on which devices, but the Office 365 reporting tools don't provide a good way to see that data.
Well, we’ve installed and configured AD FS 3.0 and we have created the first relying party trust for our SharePoint 2013 farm. All that remains now is to complete the configuration of our new Trusted Identity Token Provider and configure SharePoint to use it, which we will be doing in this article.
In my last post we took a high-level view of the various authentication processes and how they work. In this post, we’ll take the next step in our discussion of claims-based authentication and talk about Active Directory Federation Services - or AD FS, version 3.0.
I should know what claims authentication is and how it works inside and out, up ways and down, backwards and forwards. I should… but I’m ashamed to admit that until about 18 months ago I could talk my way through it, I knew “kind of” how it all worked and I could make it all work together but I didn’t really understand the under the hood of how it all works together as much as I probably should have.
Cloud computing is becoming more affordable than ever, thanks to growing competition among some of IT's most recognizable brands. We are talking about, of course, Amazon and Microsoft, two businesses with two popular cloud solutions. Amazon Web Services and Azure constantly come to mind when firms think of adopting cloud technologies.
I challenge you to a challenge of all challenges… Yes, you read that right, incorrect grammar and all.
The other day, I had the epiphany that I actually like working with SharePoint and building out business solutions with workflows. Umm…who was I kidding; I really just like using Nintex and figuring out how to make business automation better.