Feature Comparison Matrix of SharePoint 2013 and SharePoint 2010 of Foundation, Standard, Server Enterprise

Feature Comparison Matrix

SharePoint 2010
SharePoint 2013
Foundation Server Std. Server Ent. Foundation Server Std. Server Ent.
Sandbox Solutions included included included
App Catalog & Marketplace included included included
Team Sites included included included included included included
Work Management included included
Personal Sites included included included included
Newsfeed included included
SkyDrive Pro included included
Community Sites included included
Task List Aggregation included included
Follow Content & People included included
Basic Search included included included included included included
Out-of-the-box FAST Search included included
Out-of-the-box FAST PDF Search included included
Content Management
Content Management included included included included
Records Management included included included included
Managed Navigation included
Cross-site Publishing included included
E-discover, ACM, Compliance included
Business Intelligence
Excel Services, PowerPivot included included
Scorecards & Dashboards included included
Business Solutions
Access Services included included
Visio Services included included
Form Based Applications included
Workflow included included included included included included
SharePoint 2013 Workflow included included
Business Connectivity Services included included included included included included
Design Manager included
Channels (master pages) included
WYSIWYG SharePoint Designer included included included
Native support for iOS/Android included included included
Mobile Views included included included included included included

SharePoint 2010 vs. 2013 Scalability Boundaries & Limits

SharePoint 2010
SharePoint 2013
Foundation Server Std. Server Ent. Foundation Server Std. Server Ent.
Web Application Limits
Web Application Not published 20 per farm
Content Databases 300 per web app 300 per web app
Site Collections 250,000 per web app 250,000 per web app
Content Database Limits
Number of Content Databases 300 per web app 500 per farm
Content Database Size (general usage) 200 GB 200 GB
Content Database Size (all usage) 4 TB 4 TB
Content Database Items 60 million items 60 million items
Site Collection Limits
Site Collections Not published 2,000,000 per Farm
Site Collection Size Max size of content database Max size of content database
List and Library Limits
File Size 2 GB 2 GB
Documents 30,000,000 per library 30,000,000 per library
Major Versions 400000 400,000
Minor Versions Not published 511

MySites and the MySite Host in SharePoint 2013

MySites and the MySite Host: The MySite feature in SharePoint 2013 now acts as a tool to help users navigate the collections of content, data, tasks and people in SharePoint. As MySite owners, they can create micro-blogs and follow/share company news feeds, people, conversations and entire sites, and more.

This article describes how to configure My Sites in a SharePoint Server 2013 and how to configure all required settings and features related to it.

  1. Create a new Web application
  2. Create a My Site site collection
  3. Add a wildcard inclusion managed path to the web application
  4. Enable self-service site creation for the web application
  5. Configure My Site settings for the User Profile service application
  6. Enable the User Profile Service Application – Activity Feed Job

Create a new Web application

For optimal performance and security, we can create the My Site site collection in a dedicated web application. You have an option to configure it in any existing web application.

To create a new web application:

  1. Log on to APP1 with the Service account.
  2. On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.
  3. On the Central Administration Home page, click Application Management.
  4. On the Application Management page, in the Web Applications section, click Manage web applications.
  5. In the Contribute group of the ribbon, click New.
  6. On the Create New Web Application page, in the IIS Web site section, click Create a new IIS web site, and then type MySitesWebApp in the Name box.
  7. In the Port box, type any desired port
  8. In the Public URL section, type: http://servser name:<port>.
  9. In the Application Pool section, click Create a new application pool, and then type MySitesWebAppPool.
  10. In the Application Pool section, Click Configurable and confirm that the service account displays.
  11. In the Database Name and Authentication section, in the Database Server box, type: SQL2008R2.
  12. In the Customer Experience Improvement Program section, click No.
  13. Leave all other settings and selections default and then click OK to create the new web application.

Create a My Site site collection

The My Site Host site collection is a site collection that uses the Enterprise site template named My Site Host.

To create a My Site site collection:

  1. In Central Administration, click Application Management, and then click Create site collections.
  2. On the Create Site Collection page, in the Web Application section, next to Select a web application. The web application http://Server Name :<port> is shown for Web Application.
  3. In the Title section, type MySitesCollection.
  4. In the Template Selection section, in the Select experience version list, select 2013.
  5. In the Select a Template section, on the Enterprise tab, click My Site Host.
  6. In the Primary Site Collection Administrator section, type corp\user1.
  7. Click OK.
  8. The MySitesCollection site collection is created and you can now navigate to the new top level site.

Add a wildcard inclusion managed path to the web application

The wildcard inclusion managed path is the path under which separate site collections are created for My Site. Creation of the site collection occurs the first time that a user views the user’s My Site. This functionality is available only when self-service site creation is also enabled. Enabling self-service site creation is discussed later in this article.

To add a wildcard inclusion managed path to the web application:

  1. In Central Administration, click Application Management, and then click Manage Web applications.
  2. On the Web Applications Management page, select MySitesWebApp.
  3. On the Web Applications tab, in the Manage group, click Managed Paths.
  4. In the Define Managed Paths dialog box, in the Add a New Path section, in the Path box, type: /tlg and then click Add Path.
  5. Click OK.

Enable self-service site creation for the web application

Self-service site creation enables the automatic creation of a separate site collection for users when they first view their My Site.

To enable self-service site creation for the web application:

  1. In Central Administration, in the Application Management section, click Manage Web applications.
  2. On the Web Applications page, MySitesWebApp.
  3. On the Web Applications tab, in the Security group, click Self-Service Site Creation.
  4. In the Self-Service Site Creation Management dialog box, in Site Collections, select On.
  5. In Start a Site, select: Prompt users to create a team site under: and then type: /tlg in the URL box.
  6. Leave all other settings as their default, and then click OK.

Configure My Site settings for the User Profile service application

After you have a My Site Host site collection and wildcard inclusion managed path configured for My Sites, you can update the My Sites settings in the User Profile service application. Most of these settings are configured during initial deployment and only change infrequently during maintenance operations afterward.

To configure My Site settings for the User Profile service application:

  1. In Central Administration, in the Application Management section, click Manage service applications.
  2. In the Name column, click: User Profile service application.
  3. On the Manage Profile Service page, in the My Site Settings section, click Setup My Sites.
  4. In the My Site Host section, type http://Server Name:<Port>
  5. In the Personal Site Location section, type the wildcard inclusion managed path: /tlg to replace the Personal path shown by default.
  6. Leave all other settings default, and then click OK.

Enable the User Profile Service Application – Activity Feed Job

The User Profile Service Application – Activity Feed Job creates system generated posts in the feeds for the following events:

  • Following a tag
  • Tagging an item
  • Birthday celebration
  • Job title change
  • Updates to Ask Me About
  • Posting on a note board

You can add any more fields that is relevant for your organization.

To enable the User Profile Service Application – Activity Feed Job:

  1. In Central Administration, click Monitoring, and then click Review job definitions.
  2. On the Job Definitions page, in the View list, select Service. The Service list appears. If the Service list does not display User Profile Service:
    a) In the Service list, click No selection.
    b) Click Change Service.
    c) On the Select Service page, use the arrows in the upper-right corner to locate User Profile Service, and then click it. The Job Definitions page updates with the User Profile service jobs.
  3. Click the activity feed job for User Profile Service Application – Activity Feed Job.
  4. On the Edit Timer Job page, in the Recurring Schedule section, select Minutes, and then type 30 in the Every minute(s) box.
  5. Click Enable and then OK.

Configure Following settings for My Sites

Use this procedure to configure the following settings for My Sites.

To configure the following settings for My Sites,

use the following procedure to configure the following for My Sites:

  1. In Central Administration, in the Application Management section, in the Service Applications group, click Manage service applications.
  2. In the list of service applications, select the User Profile service application.
  3. In the My Site Settings group, click Manage Following.
  4. On the Manage Following page, in the Maximum number of followed people box, type 500.
  5. In the Maximum number of followed documents box, 250.
  6. In the Maximum number of followed sites box, type 250
  7. Click OK. 

Mobile SharePoint 2013 now features optimized viewing capabilities and productivity enhancements is better than SharePoint 2010

Now a days mobile view feature support is primary requirement by all customers.

Compatible Devices: SharePoint 2013 now supports a plethora of devices, including Windows, Apple iOS and Android smartphones, and MAC and Windows PCs. It also offers much better support for Web browsers.

Feature Optimization: SharePoint Server 2013 now features optimized viewing capabilities and productivity enhancements across various mobile platforms (Windows; iOS; Android). New features to support mobile devices include:

  • Updated browser UI: A lightweight Contemporary view now joins the previously available Classic and Full-Screen UI browser interfaces.
  • Flexible site rendering: Rather than the single default mobile view used in SharePoint 2010, SharePoint sites can be optimized for different mobile devices and platforms.
  • Geo-location: SharePoint Server 2013 supports a geo-location field type that enables lists to be geo-aware (among other capabilities).
  • SharePoint Server 2013 supports push notifications (to applications that support them) of site updates, such as the addition of a list or an update to an item. Notifications can occur through the Microsoft Push Notification Service or platform-specific notification services.

Apps in SharePoint 2013

Introducing SharePoint Apps

Microsoft is moving to the cloud as quickly as the market will allow, and this means that their architecture is shifting towards a software-as-a-service model. As far as I can tell, the end-goal is to have a model where businesses pay a monthly subscription fee for their users to access a SharePoint instance that is owned and operated by Microsoft. When you think of the infrastructure, support, maintenance, and upgrades that come along with SharePoint then it’s not necessarily a bad proposition for many companies.

One problem with a hosted model, however, is that SharePoint is a lot more useful when it can be completely customized around the particular needs of a business. Out of the box, SharePoint’s functionality is certainly useful, but most organizations rely on custom SharePoint applications to realize the full potential of the platform. In a hosted environment, this is problematic because custom code runs in a shared environment; not all custom code is good code, and bad code can quickly bring a server to its knees and upset a number of different customers using that server.

With this in mind, Microsoft set out to create an extensibility point in SharePoint 2013 that would allow customers to build their own solutions for SharePoint without hurting the hosted model whenever a customer’s code was found to be ‘executionally challenged’. They came up with a model called a SharePoint App, which is simply a solutionwith no SharePoint server side code.

What Do You Mean No SharePoint Server Side Code? Seriously, I mean there is no server-side code that is executed by the SharePoint server. A SharePoint

App is essentially a solution that can only include HTML, CSS, JavaScript, Silverlight XAP files, images, and any other static files.

Client side coding is  appreciated now 🙂

However, you can’t include an assembly with custom code because that would need to be executed on the server.

Of course, this leads to the question ‘how do you build something useful without server side code in SharePoint?’

What are the Three SharePoint 2013 App Deployment Models?

Before we get into the details of how it’s possible to build useful apps without SharePoint server side code, we need to go over the three deployment models for SharePoint 2013 Apps:

  • SharePoint-hosted
  • Self-Hosted
  • Automatically Provisioned Azure Web Application

SharePoint-Hosted App

A SharePoint-Hosted App is an application made entirely of static files that reside directly in your instance of SharePoint. When you add an application to one of your sites, SharePoint deploys the files in your App to a special App domain where your App lives. When a user accesses your App, they are redirected to a page that lives in the App domain and from which, presumably, they can use your App. There is absolutely no server-side code allowed in this model.

Self-Hosted App

A Self-Hosted App is an application where the files for the application exist on an external server (e.g. you are hosting those files yourself somewhere outside of SharePoint). When a user accesses your application, they are redirected to a page on this external server where the application resides. In this model, you can run server-side code, but it has to be run on the external server. There is still no way to run custom code on the SharePoint server. One of the benefits of this model is that the external server does not need to be a Windows server: SharePoint is really just redirecting users to a web page, so you can use any operating system and application server you want as long as it can fulfill web requests. You could be a PHP developer with a Linux machine and still make SharePoint apps.

Another interesting reason to use this model is that it puts you in complete control of upgrades. Since you own the server, you can deploy updates and have them applied immediately for all of your clients. In the other models, the user has to take some action to upgrade because you do not have access to the server on which the App is hosted.

Automatically Provisioned Azure App

An Automatically-Provisioned Azure App is an interesting concept that requires a bit of a back story to describe. First, I believe this type of App is designed to be run only from Microsoft’s hosted SharePoint environment, so its primary audience is really software vendors looking to sell to SharePoint online customers. The other two App model options are available in the hosted SharePoint environment as well as on a SharePoint 2013 corporate install.

Now, if you are a software vendor creating an App for SharePoint you have a choice to make that will affect your budget. If you make a SharePoint-Hosted App, then you cannot run server side code, but you also do not have to pay for a server on which to host your app. If you opt for a Self-Hosted App, then you can run server side code but you are responsible for paying for that server to host your app.

An Automatically-Provisioned Azure App is the best of both worlds. It is an App that is designed to be deployed to Azure. This means that it will be hosted outside of SharePoint and can run custom code. However, when a SharePoint Online user adds the App to their SharePoint instance, SharePoint Online tells them that the App needs to be provisioned to Azure, and if they opt to let that happen then the Azure instance will be billed to their SharePoint Online account. So you get all of the capabilities and flexibly server side code without any of the costs associated with hosting it yourself. This was clearly a brilliant plan hatched by the accountants at Microsoft.

Building Useful Apps without Server Side Code on SharePoint

The Client-Side Object Model (CSOM) was one of the areas into which Microsoft poured a ton of work. SharePoint 2010 had a very limited set of functionality, but the CSOM in SharePoint 2013 really allows you to execute just about any operation you can think of. As you can imagine, you must have a fully-functional client-side API when you are trying to encourage people to move away from using server side code.

There are three ways that you can access CSOM functionality, so the deployment model that you are using for your SharePoint 2013 app will determine he option that you choose.

  • .NET / Silverlight API
  • JavaScript API

SharePoint-Hosted App

If you plan to use a SharePoint-Hosted deployment model, then you are limited to static files. However, static files can include JavaScript and Silverlight XAP files that run dynamic code on the client side. As such, you are likely to employ the JavaScript API if you’re coding on an HTML / ASPX page or the Silverlight runtime if you decide to deploy a Silverlight XAP file. You can technically use the REST API from JavaScript and Silverlight if you so wish, but the other APIs are a better fit.

GimmalSoft opted for the SharePoint-Hosted App model because our Gimmal Drop Zone App for SharePoint 2013in the Office Store actually started out as a Silverlight component for SharePoint 2010 and was a natural fit for converting into a SharePoint 2013 app.

Self-Hosted App

A self-hosted App can take on a number of forms because it can run on any number of different operating systems with any number of different application servers. If you opt for this deployment model, then I assume you want to run server-side code. If you are hosting on a server that runs ASP.NET, then it is a natural fit to use the .NET API. If you are running a LINUX / UNIX system then the REST API is going to be a better fit because most non-Windows servers really don’t run .NET code. JavaScript and Silverlight are available in any deployment model, but these are both client-side and not server-side technologies.

Azure Provisioned App

Azure is a .NET technology, so it makes the most sense to use the .NET API when implementing an Azure-provisioned application. Once again, note that you have the option of using any CSOM API mode that you want in an Azure application, but the .NET CSOM assemblies are the best fit, considering that Azure is running on the .NET platform.

What About Authentication and Authorization?

Now that Microsoft has exposed just about every SharePoint 2013 operation from the CSOM, you have to ask yourself how you keep every idiot, who can code against the JavaScript API, from bombarding your SharePoint instance with malicious requests to delete all of your data? Fortunately, Microsoft has placed a fairly extensive layer of security around the SharePoint 2013 app model.

A SharePoint 2013 App requests a specific set of permissions when they are installed. If the current user has the ability to grant the App those permissions, then the application can be installed. If the user cannot grant that level of access, then the application cannot be installed. It’s really as simple as that.

SharePoint-Hosted Apps have the benefit of using built-in security because they operate on the same domain where the files are hosted. Self-hosted and Azure-Provisioned Apps require the use of OAuth for security purposes.

Will My SharePoint 2010 Applications Still Work in SharePoint 2013?

Yes. Many organizations have tens of millions of dollars invested in custom applications for SharePoint, and if those applications did not port then Microsoft is keenly aware that upgrading from 2010 to 2013 would be a pretty hard sell. There really wasn’t a fundamental change in how full-trust farm solutions and partial-trust sandbox solutions work, so they still exist and are still supported. If you know how to develop in SharePoint 2010, then you should be able to seamlessly move to SharePoint 2013 using farm and sandbox solutions. The App model, however, is a new way to develop and opens up possibilities for selling a SharePoint 2013 App to the masses via the Office Store and for preparing for the day when SharePoint is entirely based in the cloud

Architectural Changes in SharePoint 2013

Following are the changes in the architecture of SharePoint 2013:

1. Shredded Storage:

 The goal here is to make changes equal to the size of the change, not size of the file. Let’s have a look at how it works in SharePoint 2010 and 2013 to understand the purpose.

How It Works in SharePoint 2010:

When a file is updated via Cobalt, only the bits that have changed are sent over the wire from the client to the SharePoint WFE. However, because SharePoint lacks the concept of incremental updates to SQL it is forced to:

  1. Pullthe entire file to the WFE
  2. Merge the changes into it
  3. Write the entire file back to SQL

How It Works in SharePoint 2013:

  1. The file is broken into pieces and stored in SQL
  2. On update only the shredded blobs that correspond to the updated bits are touched
  3. No more round tripping entire files to the WFE and back

 2.SQL Improvements:

 In SharePoint 2013, Microsoft has tried to make significant improvements in server performance. They have reduced scenarios that might invoke full table scans. Also, there have been lots of improvements around finding docs for link fix-up and alert handling. They have reduced data redundancy for some features using advanced indexing features provided by SQL 2008 R2. The major change in architecture is to support wide lists, i.e. lists where a single item spans multiple rows in the database to hold the data.

3.Cache Service:

 There is a new distributed cache service in SharePoint 2013 based on Windows ServerAppFabric Distributed Caching. It is used in features like authentication token caching and My Site social feeds. The same time it should be noted that SharePoint 2013 uses caching features that cloud-based cache (Windows Azure Cache) does not support at this time, so only local cache hosts can be used. Also, importantly, SharePoint ONLY supports the version of caching that it ships – you cannot independently upgrade it.

The config DB keeps track of which machines in the farm are running the cache service. It is all provisioned by the SharePoint setup. A new Windows service – the Distributed Cache service – is installed on each server in the farm when SharePoint is installed.


4. Request Management:

 The purpose of the Request Management feature is to give SharePoint knowledge of and also to have more control over incoming requests.

Having knowledge of the nature of incoming requests – for example, the user agent, requested URL, or source IP – allows SharePoint to customize the response to each request.

The goals of request management (RM) are as follows:

  • RM can route to WFEs with better health, keeping low-health WFEs alive.
  • RM can identify harmful requests and deny them immediately.
  • RM can prioritize requests by throttling lower-priority ones (bots) to serve higher-priority ones (end-users).
  • RM can send all requests of specific type, like search for example, to specific machines.
  • Isolated traffic can help troubleshoot errors on one machine.
  • RM can send heavy requests to more powerful WFEs.



SharePoint 2013 uses the routing and pools to manage the request. Routing rules route requests and are associated with Machine Pools. Machine Pools mainly contain servers. Servers use weights for routing – static weights and health weights. Static weights are constant for WFEs; health weights change dynamically based on health scores.

5.Service Application Changes:

 There are a few new service applications in SharePoint 2013:

App Management Service: allows you to install SharePoint apps from the Office Marketplace or the App Catalog.

SharePoint Translation Services: does simple language translation of Word, PPT, and XLIFF files into HTML.

Work Management Service: provides task aggregation across systems such as SharePoint, Exchange and Project.

Azure Workflow Server is new and not exactly a service app but similar. Provides an externalized host using REST and OAuth to run workflows.

Also, Office Web App and Web Analytics are no longer a service application. Web Application Companions (WAC) is now a separate product altogether and not a service application. You can create a WAC farm that can support multiple SharePoint farms. You can view files from a number of different data sources, including: SharePoint, Exchange, Lync, File servers. 3rd parties can integrate with WAC to provide access to documents in their data stores, e.g. EMC document, IBM FileNet, OpenText, etc.

6. Other Considerations:

Stretched farms are no longer supported in SharePoint 2013. “Stretched” means different data centers with less than 1ms latency. All servers in the farm must be in the same data center now. For 100% fidelity in 100% of features, all content must reside in the same farm.

SharePoint 2013 has a lot of exciting new features and it will be interesting to see how the SharePoint Product Team at Microsoft continues to build and package but the features and solutions within 2013 should give you and your organization added confidence in the fact that you have selected a solution that Microsoft is backing with its full support and has tagged SharePoint as its flagship product.

Business Connectivity Services – Consuming OData in BCS using an App External Content Type

Business Connectivity Services – Consuming OData in BCS using an App External Content Type

Looking on how data can be consumed from an Open Data protocol (OData) data source.

First of all what is OData.

 The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock data and free it from silos that exist in applications today.

OData does this by applying and building upon Web technologies such as HTTP,Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.SharePoint 2013 uses visual studio 2012.

Create a project

Choose the project type App for SharePoint 2013:


Using the Wizard, select the “SharePoint Hosted” as seen below:


This should setup the initial project structure and the project looks something as shown below:


Add an external content type

4After creating initial project, add a new external content type.

Right-click the project and choose Add, there is a new menu item called “Content Types for an External Data Source…“. Click it:

In the following wizard, enter the service URL for the OData provider.


Theexample uses the public tv.telerik.com/services/odata.svc OData service:

In the next step in the wizard, select for which data entities,the external content types need to be generated. Choose the entities to work with and continue by pressing Finish:
“Create list instances for the selected data entries (except Service Operations).” must be checked so the tools can create external list automatically.


After the above step, there are few additions in the project that the Visual Studio 2012 has been so kind to help out with.A Telerik Video external content type with it’s associated ListInstances (one per entity, in my case only one for Video) that it was also kind enough to create since the checkbox in the previous dialog ticked.


Looking in the Feature explorer, it can be seen that the default Feature now contains artifacts along with the newly created List Instance and External Content Type.


In the newly created List Instances, the following XML has been generated for us:


As it can be seen, the ListInstanceDataSource node contains information about connecting to our newly created BCS entity. Perfect.Just to make sure that we can deploy thesolution, hit F5 and make sure that VS2012 deploys your project properly


Validate so that application works

 Navigate to the site and validate that the new App is properly deployed and showing:


Click the app and make sure the result of very basic and “hello world”-ish app:


Display the new external list!

“Create list instances for the selected data entries (except Service Operations).”? Well the reason for that is that we want Visual Studio 2012 tools to create this list for us so we don’t have to do that ourselves.

With the newly deployed BCS external content type app, with it’s created list, you can access the content of the list on the following URL (you’ll need to check your Elements.xml for your ListInstance element in order to find out your url:


Navigate to this URL and you’ll see this view:


New Features of SharePoint 2013

Branding improvements:

SharePoint 2013 offers an improved process for designing a public-facing internet site or an internal-facing intranet site with pixel-perfect branding.

It minimizes the amount of SharePoint knowledge to design and brand a SharePoint site successfully.



It is Microsoft’s cloud storage mechanism for consumers.

SkyDrive helps to work with documents in SharePoint – save, sync, share and collaborate and, what is more, to get the documents offline in the Windows Explorer, Office applications and so on.


Records management and compliance:

SharePoint 2010’s records management features had improved from SharePoint 2007’s.

SharePoint 2013 Preview has enhanced compliance simply by extending retention policies to SharePoint sites.

This also applies to any Exchange Server 2013 Preview team mailboxes associated with those sites.


Cloud App Model:

Share Point 2013 introduces a Cloud App Model that enables to create apps.

Lists, libraries, calendars, workflows and site pages are called “Apps” now. These can be easily added to the SharePoint site.

An app may also surface a remote web application and remote data in SharePoint.

There are a lot of benefits of such solution vs classic one.

Users now can have one of the following views:

Contemporary view – is available to Mobile Internet Explorer version 9.0 or later versions for Windows Phone 7.5, Safari version 4.0 or later versions for iPhone 4.0, and the Android browser for Android 4.0 or later versions.

Classic view – is identical to the mobile browser experience of SharePoint 2010.

Full-screen UI -Full desktop view of a SharePoint site on a smartphone device.


SharePoint 2013 Search:

Search in SharePoint 2013 now includes several enhancements, custom content processing with the Content Enrichment web service, and a new framework for presenting search result types.

SharePoint 2013 additionally adds new Content Search Web Part – which makes search experience even more effective.


Business Connectivity Services:

In SharePoint 2013 BCS (Business Connectivity Services) are improved and enhanced in many ways, including OData connectivity, external events, external data in apps, filtering and sorting, support for REST and others.

Web content management:

The web content management improvements in SharePoint 2013 simplify how to design publishing sites and enhance the authoring and publishing processes of the organization.

It also contains new features that use enterprise search to surface dynamic web content on publishing sites.


Mobile devices:

SharePoint Server 2013 offers new, optimized viewing experiences across different mobile platforms. Additionally, there are several features that are available to help improve both worker productivity and usability on the device.


New in Application services:

New for SharePoint is the Machine Translation Service, which translates sites, documents and streams for multilingual support.SharePoint 2013 also includes Access Services and a new data access model.

SharePoint 2013 has now Word Automation Services which you can use to convert files and stream to other formats. PowerPoint Automation Services are also new for SharePoint.

SharePoint, additionally, provides data analysis tools, like PerformancePoint Services and Visio Services that enable business intelligence and powerful new features in Excel Services.



Showing SharePoint’s increasing presence in the world of litigation, eDiscovery improvements have been added that, unfortunately, are probably sorely needed. They include a new site template, the eDiscovery Center, which creates a portal for managing cases—you can access cases to search, hold content and export content.

Microsoft has added improvements to in-place holds, including site-level preservation; the ability for users to work with content that’s preserved; and the ability to define the scope of preservation via a query filter.The results of your eDiscovery search—including documents, wiki pages, Exchange email messages and tasks and export them into a review tool.


Social computing:

The social computing and collaboration features in SharePoint 2013 offer an improved administration and user experience, in addition to new functionality for enterprise users to share and collaborate with others in their organization. The introduction of Community Sites offers a forum experience to categorize discussions around subject areas, and to connect users who have knowledge or seek knowledge about subject areas. Additionally, the new Community Portal enables a search-driven result page of communities for users to discover and explore from a link on their My Sites.

Improvements to My Sites offer a more intuitive workflow for users to develop their personal profiles, store content, and keep up-to-date with activities of interest through the use of the new micro blog and feeds experience.