Latest Posts

Update 10/25/2017: This article originally appeared on ITUnity.com but as that site has been decommissioned I’ve republished it here. In the Connecting to SharePoint Online using the SharePoint CSOM API with Windows PowerShell article you learned how to get started using the SharePoint CSOM API to connect to your SharePoint Online Site Collection with Windows PowerShell.

Update 10/25/2017: This article originally appeared on ITUnity.com but as that site has been decommissioned I’ve republished it here. As a developer working with earlier versions of SharePoint, specifically SharePoint 2007 and earlier, your options for working with SharePoint from off-server client applications was pretty limited.

Update 10/25/2017: This article originally appeared on ITUnity.com but as that site has been decommissioned I’ve republished it here. In the Introduction to the SharePoint Online Management Shell article you learned how to get connected to your SharePoint Online tenant using the SharePoint Online Management Shell and in the Exploring the SharePoint Online Cmdlets article you were introduced to the list of available cmdlets along with some details on the less commonly used cmdlets.

Update 10/25/2017: This article originally appeared on ITUnity.com but as that site has been decommissioned I’ve republished it here. In the article, Introduction to the SharePoint Online Management Shell, you learned about the SharePoint Online Management Shell and you saw how to use it to connect to your SharePoint Online tenant.

Update 10/25/2017: This article originally appeared on ITUnity.com but as that site has been decommissioned I’ve republished it here. With Office 365 now on SharePoint 2013, we finally have the long-awaited, and long-overdue support for using Windows PowerShell to manage SharePoint Online environments.

Earlier this summer I mentioned that I’d start blogging about some of my scripts that I have in my toolbox and I guess I’m a little behind in that but I guess better late than never.

Have you ever been looking through the SharePoint ULS logs trying to troubleshoot one issue or another and come across entries such as this: [Forced due to logging gap, Original Level: <TraceLevel>] <Some message> {0} I was recently working with a client who noticed an message like this in the ULS logs and was baffled by the fact that the {0} was not being replaced with the relevant data referred to in the message text.

I haven’t really done much blogging lately so I figured I’d try and get back into it by sharing some scripts from my collection. Over the years I’ve created tons and tons of little scripts here and there to help me solve one problem or another – whether it be some upgrade related thing or a content or build migration or just some random snippet to help me figure out what the heck is going on with my code or with SharePoint in general – I’ve got a ton of them just scattered all over the place.

For quite a while now I’ve been pointing out the lack of cmdlets that are available for working with Office 365 and SharePoint 2013 (SharePoint Online) and I’ve mentioned several times that someone should really do something about that and that I’d love to be that person if only I had the time.

So today I was doing some SharePoint 2013 app development against my Office 365 SharePoint 2013 tenant and I needed to view the HTTP traffic from the site in order to troubleshoot some issues I was having and I stumbled across something I found very interesting when I looked at the header details in Fiddler: