SharePoint 2016 is expected to bring a lot of new and improved features in this release, especially the ones that are already present on SharePoint Online to its On-Premises customers. Some of the features which were on the planned depreciation list have been removed. Refer to the list of all the features that has been either deprecated or removed from Microsoft. In the post, I am only going to focus on What BI Features are Removed in SharePoint 2016.
What BI Features are Removed in SharePoint 2016
Deprecated features are not necessarily completely removed. They are included in SharePoint Server 2016 for compatibility with previous product versions. So let’s look at what is deprecated or removed.
SQL Server BI Compatibility
The SQL Server 2014 add-ins for Power Pivot and Power View will not work with SharePoint Server 2016. You will not be able to deploy or use in SharePoint Server 2016. To deploy these add-ins you need to upgrade to SQL Server 2016 latest build (CTP 3.x Onwards).
Standalone Excel Services have been removed with Excel Online which is a part of Office Web Apps Server. As per the official documentation, the following has been removed:
- Trusted data providers
- Trusted file locations
- Trusted data connection libraries
- Unattended service account
- Excel Services Windows PowerShell cmdlets
- Opening of Excel workbooks from SharePoint Central Administration site
Performance Point in SharePoint 2016
Performance Point is still there in SharePoint 2016 but in dormant mode. The features are largely unchanged but will help existing customers to seamlessly migrate their existing PPS reports. The upcoming Power BI Dashboards based on PowerView should be a viable alternative. If you really want Performance Point, you need to go back to SharePoint 2013.
Silverlight is replaced with HTML 5
All your Excel PowerPivot and SSRS Reports are now being rendered in native HTML 5. This enables seamless integration with devices of all sizes and cross-platform compatibility.
The list might be bigger than what is mentioned here. Please refer to the official Microsoft documentation below: