- SOLUTIONS & SERVICES
By Mike Alsup
Jun 07 2015
This post summarizes several announcements and developments from recent Microsoft events, especially Ignite in May in Chicago and how they impact ECM. Let’s start with several overall observations on the Microsoft vision for ECM:
Files, sites, portals, and content management are four key SharePoint 2016 and Office 365 focus areas for the ECM market and generally.
Microsoft is expanding the ability of SharePoint to manage almost any type of content:
“Millions of users and billions of documents” was a quote I heard at Ignite about the scaling of Office 365. Microsoft has been listening to customers as they identified the specific reasons that migrating to Office 365 is difficult.
Microsoft is positioning OneDrive for Business as the replacement for network file shares. “4 lines of Powershell script” was mentioned several times as all that was needed to migrate File Shares to OneDrive for Business. Office 2016 and Outlook 2016 store documents by default in OneDrive for Business. This approach seemed to me as somewhat reminiscent of the 1990’s browser wars with Microsoft competing by “removing the Oxygen from the room”. For many organizations, OneDrive for Business will be a natural evolution path from Share Drives, but with many more capabilities for content governance built into the platform. Taking advantage of these capabilities will come from planning and architecting deployments, primarily through portals and site provisioning processes.
Microsoft has made a huge investment to provision SharePoint sites that are more standard and consistent. Site creation will no longer be as heavy an operation. It will be “smaller and faster” and much easier to use in SharePoint site architecture models, both on-premises and in Office 365. These portals will be provisioned through pre-defined templates that will be chosen by users and will reflect the site model that best addresses the users’ requirements. It will be harder for a user to know if they are using Office 365 or on-premises sites, because both SharePoint Server and Office 365 sites and services will be exposed through the same Portals.
“NextGen” portals are how the features and capabilities of ECM will be presented in Office 365. NextGen portals blur the feature and function distinctions between SharePoint on-premises and in Office 365 platform services. Microsoft is emphasizing “Ready to go” portals for common site models, such as Knowledge Management portals.
A key feature of these portals is that there will be a wide variety of site templates to choose from. Organizations will establish site templates with baked-in metadata inheritance, an information lifecycle, and a wide array of content governance services, such as records management. I expect that many of the templates and governance services will incorporate capabilities provided by Microsoft ecosystem partners, and the site provisioning processes will enable them to be easily and transparently provisioned by users.
Content (Traditional ECM, not WCM)
Microsoft is rediscovering the demand in their customer base for ECM at the high end of the market. The new SharePoint leadership team includes longtime Microsoft SharePoint team members who designed and built the original ECM capabilities in SharePoint 2010, and they have a deep appreciation of the ECM and RM problems to be solved.
In other announcements:
Many organizations at Ignite were looking for the enterprise platform confidence to replace silo’d legacy ECM solutions. A question Microsoft is trying to address for these customers is how best to build robust enterprise hybrid ECM solutions to replace traditional document management solutions from vendors such as Documentum, Open Text, Hyland and FileNet.
The answer that Microsoft has ended up with is to emphasize the value of the many integrated components of Office 365, portals, and hybrid solutions. If content migrates seamlessly during its lifetime from Outlook and Yammer and OneDrive to SharePoint on-premises or to Office 365 sites, with full content governance and social and Office Graph support, and with full records management, business intelligence and archiving support, why would anyone need to archive their content outside of this stack? Especially when most of the archiving approaches require that they be integrated into every site, either on-premises or in Office 365, through the enterprise site provisioning processes. This runs counter to the Microsoft direction of simplified user site provisioning from pre-built site templates.
Demonstrations by Microsoft Legal and Corporate Affairs (LCA) at both Ignite and Legal Tech of their Matter Center solution illustrates their path forward to enterprise-wide ECM solutions. They showed how Microsoft lawyers and legal assistants are enabled to collaborate on legal documents through legal processes from inside Word and Outlook almost exclusively. The LCA users remain in Office 365 and a variety of processes and services are exposed via App’s and services that comply with the new Office 365 App Model. Microsoft indicated that they will be partnering with some of the legal add-in vendors to add the vertical capabilities required in the legal industry. This is the Microsoft ECM solution model: portals, a massively powerful and scalable cloud platform, and partners with vertical expertise, software and solutions.
The consensus I have gotten from customers is that the SharePoint and Office 365 2016 vision is really good but there remains much work to be done. Everyone thinks Microsoft is doing the right thing moving to the cloud and enabling integrated solutions to be implemented using the Office 365 App Model. Most analysts I spoke to believe that these developments strengthen Microsoft’s ECM positioning and enable it to increase its market share. They point out that Google, Box and Dropbox are competing effectively in these markets.
Microsoft plans to deliver a public beta of SharePoint Server 2016 in the fourth quarter of this year. The product is planned for “general availability” release in the second quarter of 2016, but a “release candidate” version will precede the final product.
It looks like another exciting year in the Microsoft stack for users, vendors and customers alike.