My first blog post on this site was about MOSS 2007. That was 2012, and even then I was dealing with a platform that was simultaneously incredibly powerful and incredibly frustrating to integrate with. Over the years I’ve gone through every wave of “now you can get SharePoint content into your app.” CSOM. Provider-Hosted Apps (and if you’ve read my post about the TLS 1.2 and SameSite cookie nightmare, you know how much fun that was). REST APIs. Microsoft Graph. Every time, it felt like you were fighting the platform. You wanted documents with versioning and permissions, and SharePoint wanted you to use its UI. SharePoint Embedded changes that, and honestly, it’s about time.

A simple upgrade…

Sometimes we still have to support some legacy code. And provider-hosted apps in SharePoint are one of the pains we still have to maintain. Since the announcement of Microsoft to only allow TLS 1.2 connections to Office 365 starting June 2020 we started to update legacy provider-hosted apps.

With releasing the SPAdminBot almost a week ago, I got some great response. But I also forgot to mention some items in my previous blog post. The steps to take on how to install this in your own Azure environment and use your own bot ID’s. In this post, I will go through the detailed steps on how to get the SPAdminBot up and running.

I’ve started a new open source project called the SharePoint Admin Bot or SPAdminBot for short. Why you ask? Because I got tired of doing and seeing people do the same tasks over and over again on SharePoint Online and Office 365. For something simple like creating a site collection you would always have to go into the admin portal and click through multiple pages to get the job done. These kinds of simple tasks can be easily done by a bot.

Last week I had the privilege of giving a session in New York City during it’s SharePoint Saturday event. This great event was hosted by Peter Ward, Tim Ferro, Tom Daly and a whole team behind them. They did a great job hosting this event in this great city. It was my first time to New York so it was a little overwhelming in the beginning.

When setting a userprofile property backed by a term set in CSOM we use this snippet (sample from Office Dev PNP)

This is already the 5th part of our series. In this post will install SharePoint 2010 on our development environment. To shake this up a little lets not install this like we installed SharePoint 2013 but let’s use AutoSPInstaller (http://autospinstaller.codeplex.com/). You can also use this for the installation of SP2013 of you like.

This is the 4th series of my post on how to set up a SharePoint Hyper-V virtual farm. In the previous posts we prepared our different servers, installed SQL and SharePoint 2013. In this post we will configure SharePoint 2013 with PowerShell. Like i already said in the previous post there will be some benefits of doing it this way. If you use the standard configuration setup wizard then SharePoint will create the databases and services for you. This also means that you don’t have control over their names, passwords or the accounts they run under.

This is the third part of my blog post on how to set up a development farm for SharePoint.

This is the second part of my post how to set up a SharePoint development Farm. The first part can be found here Part 1