Applies to: Office 365
Topic Last Modified: 2014-12-11
SharePoint Online is a collection of Web-based tools and technologies that help your organization store, share, and manage digital information. Built on Microsoft SharePoint Server 2013, this hosted service is ideal for working on projects, storing data and documents in a central location, and sharing information with others. The following features support developers who want to build apps and solutions to extend SharePoint functionality.
To see if a Developer feature is available in a certain SharePoint solution, see Developer feature availability across SharePoint solutions.
|For a complete list of SharePoint features, see SharePoint feature availability across solutions|
Build web databases and publish them to a SharePoint site. SharePoint visitors can use your database application in a web browser by using SharePoint permissions to determine who can see what. And you can start with a template so that you can start collaborating immediately. Learn more about how to build and publish an Access database to SharePoint.
Publish your apps to an internal corporate catalog, hosted on your SharePoint deployment, to make them available to users who have access to that SharePoint deployment. Learn more about publishing apps for Office and SharePoint.
Cloud-hosted apps for SharePoint include at least one remote component and may also include SharePoint-hosted components. Learn more about hosting options for apps for SharePoint.
The App Management Service database stores licensing information for all of the apps for SharePoint.
SharePoint now provides the capability of using alerts for external lists, just as they have been used for traditional lists. A user can subscribe to be alerted when data changes on an external list. Learn more about external events and alerts in SharePoint 2013.
With the addition of the new App model in SharePoint, Business Connectivity Services (BCS) can now scope external content types at the App level instead of at the farm level. This gives great flexibility to App developers by allowing them to use external data inside their Apps. Learn more about app-scoped external content types.
Business Data Webparts are special web parts that work with external data. They are used like standard SharePoint web parts, but are based on external content types, which are XML descriptions of connections to the external data.
An external list is a special kind of SharePoint list that displays data from an external data source. It is built on an external content type that describes the data source, and allows users to work with the data in a familiar SharePoint interface. Learn more about external content types.
The OData connector is new for SharePoint. It allows for Business Connectivity Services (BCS) to use a RESTful OData endpoint as a data source for external lists, Business Data WebParts, and custom user interfaces.
Not available to SharePoint Online customers. Business Connectivity Services (BCS) provides a special WebParts page called Profile pages. Profile pages allows for BCS to display details of the external data in addition to its related external content types.
Not available to SharePoint Online customers. Business Connectivity Services (BCS) uses a complimentary client and server-side architecture that allows for Office clients, such as Outlook and Excel, to work directly with external data exposed to SharePoint through external content types. Learn more about Business Connectivity Services Client Runtime.
The Secure Store provides single sign on capabilities to Business Connectivity Services (BCS). Using Secure Store, SharePoint Administrators can map user account credentials to external system account credentials so that data can be secured. Learn more about Secure Store Service.
Tenant-level external data logging allows for logging of transactions that affect specific SharePoint tenancies.
You can customize your site without any special tools or coding expertise just by using the site settings. For example, you can change the look, title, and logo, change the navigation links, change the contents of a page, or change the appearance of views for lists and libraries. Learn more about customizing sites.
Client-side rendering provides a mechanism that you can use to produce your own output for a set of controls that are hosted in a SharePoint page. Learn more about customizing a field type using client-side rendering.
Not available to SharePoint Online customers. SharePoint Server 2013 customers can create their own site definitions that customize and extend standard SharePoint site templates. Learn more about creating custom site definitions.
Not available to SharePoint Online customers. SharePoint Server 2013 customers get a quick and easy way for users to make their site requests and to start using their sites quickly.
Use an Office 365 Developer Site as a development and testing environment to shorten your setup time and start creating, testing, and deploying your apps for SharePoint. Learn more about signing up for an Office 365 Developer Site.
A form view is basically a view that contains controls. A Forms Based Application lets the user create and use one or more forms within the application. Learn more about Forms Based Applications.
Not available to SharePoint Online customers. SharePoint Server 2013 customers can create full-trust solutions. Also called farm solutions. Unlike apps for SharePoint, farm solutions contain code that is deployed to the SharePoint servers and makes calls to SharePoint’s server object model. These assemblies always run with full trust. Farm solutions should be used for customizations of SharePoint administrative functions, such as custom timer jobs, custom Windows PowerShell cmdlets, and extensions of Central Administration. Learn more about building farm solutions in SharePoint 2013.
Forms Service provides a Web browser form-filling experience in SharePoint, based on form templates that are designed in InfoPath. Learn more about InfoPath Forms Services.
To handle events in an app for SharePoint, developers can create remote event receivers and app event receivers. Remote event receivers handle events that occur to an item in the app, such as a list, a list item, or a web. Learn more about handling events in apps for SharePoint.
A sandboxed solution, compared to a farm solution, enables site collection administrators to install custom solutions in SharePoint Foundation 2013 without the involvement of a higher-level administrator. Learn more about Sandboxed Solutions in SharePoint.
The Design Manager enables a step-by-step approach for creating design assets that you can use to brand sites. Upload design assets—images, HTML, CSS, and so on—and then create your master pages and page layouts. Learn more about SharePoint 2013 site development.
Using SharePoint Designer, advanced users and developers can quicky create SharePoint solutions in response to business needs. Learn more about SharePoint Designer for developers.
The SharePoint Store provides a convenient location for developers to upload new app solutions that are aimed both at consumers and businesses. Learn more about publishing apps for Office and SharePoint.
SharePoint legacy workflow functionality, compatible with .NET 3.5. Learn more about workflows in SharePoint Foundation.
Use out of the box workflows included with SharePoint to model common business processes.
SharePoint 2013 workflows are powered by Windows Workflow Foundation 4 (WF), which was significantly redesigned from earlier versions. Perhaps the most prominent feature of the new workflow infrastructure is the introduction of Azure as the new workflow execution host. Learn more about what’s new in workflows for SharePoint 2013.
Use the following Developer feature availability tables to compare Office 365 plans to SharePoint on-premises solutions.
To compare Microsoft hosted Office 365 plans, see Developer feature availability across Office 365 plans.
To compare SharePoint Online standalone plans—which do not include any other Microsoft Online services, such as Exchange Online or Lync Online, see Developer feature availability across standalone plans.
To compare on-premises solutions—where an organization installs and deploys SharePoint themselves, see Developer feature availability across on-premises solutions.
To view feature availability across Office 365 plans, standalone options, and on-premise solutions, see SharePoint Online Service Description.