Skip to main content

Office 365: Blog

New SharePoint CSOM version released for SharePoint Online – February 2018

We are happy to announce the availability of new SharePoint Client-Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. This release again contains updates on the existing SharePoint and Project CSOM assemblies, mainly on Site Designs and upcoming Hub Sites capabilities. Notice that some of the below new capabilities do NOT work in normal tenants until the capability is truly released and enabled. There will be separate communications around availability fo the new capabilities when they are available.

You can find the latest CSOM package for SharePoint Online, including the Project Online CSOM assembly, from the NuGet gallery with an id of ‘Microsoft.SharePointOnline.CSOM‘. We are also working on updating the redistributable package at some point, but you can already right now start using some of these new capabilities in your solutions. We do recommend you to use the NuGet Package to gain access to the latest version, rather than downloading the SDK to your machine.

The version of the newly released CSOM package is 16.1.7414.1200. Previous versions of the NuGet have not been removed so that your existing solutions will continue working without issues and you can decide when the new version is taken into use. Notice that even though the NuGet version is increased to 16.1.7414.1200, actual assembly version of the released assemblies is 16.1.0.0. You can also check the version of the assemblies from the File Version attribute, which aligns with the NuGet version.

CSOM NuGet at VS2017 NuGet manager

SharePoint Online Management Shell has been also updated to match with this CSOM release. You can find a new set of cmdlets listed in this article.

Notice that since this NuGet package is targeted to SharePoint Online, you cannot use it directly in on-premises environments (SharePoint 2013 or 2016). This is because of the server side dependencies of the APIs. CSOM versioning model and dependency to your target environment are clarified in following blog post – Using correct Client-Side Object Model (CSOM) version for SharePoint customizations. We have released separate NuGet packages for on-premises. See following blog post for additional details – SharePoint CSOM versions for on-premises released as NuGet packages.

New properties and methods across assemblies

Here’s a raw list of all the changes in the classes, properties and methods within this package.

Microsoft.SharePoint.Client

Following properties, classes and methods have been added.

  • public property Microsoft.SharePoint.Client.Site.SocialBarOnSitePagesDisabled

Microsoft.Online.SharePoint.Client.Tenant

Following properties, classes and methods have been added.

  • public class Microsoft.Online.SharePoint.TenantAdministration.HubSitePermission
  • public property Microsoft.Online.SharePoint.TenantAdministration.HubSiteProperties.Permissions
  • public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.HubSiteId
  • public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.IsHubSite
  • public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.OwnerName
  • public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.SetOwnerWithoutUpdatingSecondaryAdmin
  • public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.SocialBarOnSitePagesDisabled
  • public class Microsoft.Online.SharePoint.TenantAdministration.SPOTenantInstance
  • public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.ApplyAppEnforcedRestrictionsToAdHocRecipients
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.ApplySiteDesign
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.GetTenantInstances
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.SetWebTheme
  • public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.SocialBarOnSitePagesDisabled
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.UpdateUserTypeFromAzureADForAllSites
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.UpdateUserTypesFromAzureADForSite
  • public enum Microsoft.Online.SharePoint.TenantAdministration.TenantSiteScriptActionOutcome
  • public class Microsoft.Online.SharePoint.TenantAdministration.TenantSiteScriptActionResult
  • public property Microsoft.Online.SharePoint.TenantAdministration.Internal.SPOWebAppServicePrincipalPermissionRequest.PackageApproverName
  • public property Microsoft.Online.SharePoint.TenantAdministration.Internal.SPOWebAppServicePrincipalPermissionRequest.PackageName
  • public property Microsoft.Online.SharePoint.TenantAdministration.Internal.SPOWebAppServicePrincipalPermissionRequest.PackageVersion
  • public property Microsoft.Online.SharePoint.TenantAdministration.Internal.SPOWebAppServicePrincipalPermissionRequest.TimeRequested
  • public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.ApplyAppEnforcedRestrictionsToAdHocRecipients
  • public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.SocialBarOnSitePagesDisabled

New PowerShell cmdlets in SharePoint Online Management Shell release

Following cmdlets have been added to the latest release of SPO Managment Shell. Notice that some of the below commands do NOT work in normal tenants until the capability is truly released and enabled. There will be separate communications around availability fo the new capabilities when they are released

  • Add-SPOHubSiteAssociation – Associating a site to a hub site
  • Invoke-SPOSiteDesign – Apply Site Design to existing site
  • Remove-SPOHubSiteAssociation – Remove hub association
  • Set-SPOWebTheme – Set theme to existing site
  • Update-UserType

PowerShell documentation has been also moved to docs.microsoft.com platform and will be updated more frequently in the future.

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint Engineering, Microsoft – 23rd of February 2018

filter-icon