- Empowers Citizen Developers: Removes dependency on IT, and promotes the citizen developer concept. A no-code customization approach allows the employees to meet their complex business requirements, from interface enhancements to complete SharePoint software solutions.
- Accelerates Time to Market: Since the point-and-click configuration consumes significantly less time than writing, debugging, and compiling codes, the end-user functionalities can be developed in a rapid quick time. Comparatively measured, customized SharePoint solutions can be created 6x to 8x faster. This helps enterprises meet their development SLAs.
- Brings High User Engagement: Allows enterprises to extend SharePoint capabilities beyond what is natively possible by developing apps that fit the business needs, improve navigation, enhance the UI, and drive high user adoptions.
- Simplifies the Upgrade Process: Mitigates the challenges associated with the upgrade process. Custom coded applications involve hard-coded references to server names, databases, or URLs which might not run effectively on another platform. As the custom SharePoint apps built with no-code development tools need the least coding, they can work seamlessly in the new platform.
- One can drag the web apps to a page and configure
- It does not require any extensive knowledge or any kind of development expertise
- No professional qualification required
- Meet various range of requirements
- Go to any length in managing any number of projects
- User friendly with regards to support, maintain and upgrade in order to assure long-term value and ROI
- It provides value addition to businesses as it is highly customizable, as a matter of fact, it can be configured for any virtual need or any vertical
- The solution permits extreme granular permissions like edit, view only, delete/create files, and similar more and information hierarchy access for better secure sharing, it gets more critical when external users are brought in to collaborate
- The brand-able interface lets one to project a highly professional image, both internally and externally when collaborating with external partners
- Customize the appeal with the help of pre-packaged skins or one can create a custom skin
- Export list view data into formats like PDF, Microsoft Word, Microsoft Excel, or CSV formats
- Configure parent-child relationships in a two-level hierarchical list view
- Create complex filters and sort list view data in relevant ways
- Unlimited grouping
- Point and click roll up of data in multiple lists
- Point-and-click CAML filtering editors for both list items and folders
- Customize chart elements like fonts, labels, backgrounds, canvas, logos, tooltips etc.
- 30 plus chart types to meet with various visual, BI and dashboard requirements
- Apply the pre-packaged skins so as to customize the appeal
- Hide or show various menus dynamically as per user’s group or permissions
- Minimum administrative overhead, maximum productivity, no upgrade or patching headaches. And the onus for downtime goes to Microsoft.
- End users would demand just one more site collection on SharePoint Online. Power users would demand just one more APP. Infrastructure Managers started moving their network drives on OneDrive for Business. Sweet!!!
- And then comes chaos. Chaos on what content goes where? When to use OneDrive for Business? When to use SharePoint Site? And most importantly, when not to use SharePoint? To add to the confusion, questions like what content goes on premise? what content goes online? How do we search? Where do we search? What gets priority?
- Avoid content chaos.
- Consistent user experience.
- Enforce standardization and best practices.
- Eliminate redundancy and ambiguity in content life cycle process.
- Establish a consistent mechanism to identify whether SharePoint Online, SharePoint On Premise or OneDrive for Business is the right tool for given classification of content.
- Governs storage and compute power.
- Improve find ability.
What is a Governance Plan?Governance Plan is more than a document. Its a complete guide that keeps IT & Business goals as central focus and defines policies, processes, people and tools to effectively manage the SharePoint environment. IT points to resources, templates and guides to execute tactical and operational activities related to SharePoint.
- Policies – The governance plan needs clearly articulated policies. These policies have to be in line with business, legal and compliance needs of an organization.
- Processes – The governance plan would require processes to enforce policies, escalate in case of non-compliance and process to request for overriding of policies along with service level agreements to complete the processes.
- People – The governance plan would require clear definition of people (roles) involved, their responsibility, escalation matrix, operational level agreements and authorization matrix.
- Tools – No all policies can be enforced manually or via a document. It is imperative to define tools to execute various processes. E.g. Backup tools, compliance tools, etc.
- IT Governance: This segment defines policies and processes around IT Infrastructure like storage, backup, restore, high availability, disaster recovery and content security. It also deals with identity, authentication and access management plan.
- Information Governance: This segment defines policies and processes around content and how it is organized and presented to end users and content owners. It also deals with taxonomy and hierarchy of content along with its findability.
- Application Governance: SharePoint is as much of a platform as it is content management system and customization using API and services is possible. It is imperative to have Application Governance defined to ensure user experience, system performance and customization standards are consistent and adhered to. It also deals with application life cycle management and dev ops procedures to minimize disruptions.
- Governance and Site Types: Different type of sites require different policies. And in case of hybrid, the importance varies depending upon whether the content is on premise or cloud. Published sites have tighter governance over information and application management than team sites, personal sites and OneDrive for Business. Generally, the larger the number of people who get information from a particular type of site, the more tightly it is governed, and vice versa. This is shown in the following graph. For example, if your intranet home page is available for everyone in your organization, it’s generally much more tightly governed than the site for the accounting department, which is more tightly governed than most group or team sites, and so on. Personal sites are generally the least governed types of sites.
Governance Operating FrameworkGOF or Governance operating Framework is the various area of SharePoint Operations where Policies & Processes are defined. The following diagram depicts the Governance Operating Framework for which the Governance Team would establish policies and processes. In my subsequent blog post, I would create a sample governance plan taking the below into consideration. In case of hybrid environment, it is imperative to have these broken down for clear demarcation between SLAs and processes for On Premise and Online environments.
Best Practice for Governance Plan
- Goals: An effective governance plan anticipates the needs and goals of your organizations business functions and IT teams. IF you have a goal defined, you will have a metric to measure it.
- Uniqueness: While the intent is to standardize processes, the governance plan has to be unique to your organization. Templated one size fits all plans are useless and misdirect governance team energies towards tweaking processes other way round.
- Classification: Classify your business information. Build Taxonomy or Buy Taxonomy that’s tailored to support your business needs.
- Educate: Establish training and education plans. It is imperative that every SharePoint user is educated to organization’s policies and processes.
- Phased out approach: Governance plan is an ongoing initiative. And you many not achieve perfection on day one. Plan phases. Start with small governance team. Build the foundational policies and processes. Aim high but execute in phases.
The RTM release of SharePoint 2016 in March was an important milestone for SharePoint Product line as a whole which include new capabilities for end users, IT professionals, administrators and architects. And this release is a next step towards hybrid capabilities across on premise and Office 365 after a cumulative update for SharePoint 2013. Let’s look at what’s new in SharePoint 2016 and what’s deprecated.
MinRole allows you to install and configure the role that you want in particular for that server in the farm. Not only from an installation standpoint that it would configure the required features for that role but also from administrative standpoint it would make sure that the roles the server belongs to are complaint. You can at any point of time convert to new roles if required. You can look at the services to verify compliance status.
- A document library could go upwards of 25 million documents with a threshold of 5000 view threshold beyond which SharePoint would start throwing weird messages unless you index your columns. While the technical threshold still remains for performance reasons, SharePoint would auto create index columns and the user won’t have to worry about explicitly adding index.
- Support for ODF document is added.
- Files are now shared via durable links which is combination of site id and document id. Will not break the link if file name changes.
- Filename length and other character restrictions are removed. However, Restricted characters such as % and # are still not allowed in file names.
- Project Server is now consolidated into SharePoint content database.
- You can now rename files, create new files, and share files from within the WOPI iframe on the browser page.
- You can now preview images and videos in SharePoint Server 2016 document libraries.
You can now apply themes to your Suite Navigation.
User Profile Management
- User Profile page will now include content from Delve and Open Graph API.
- Forefront Identity Manager is now no longer included in user profile sync service application. Unidirectional sync is available though.
- Using Microsoft Identity Manager to sync identity is now supported.
Blogging feature now supports drag and drop of images and enhance user experience.
Performance & Security Improvements
- Reliability improvements to Distributed Cache.
- SharePoint Logging API allows easier ability to record and report on analytics and telemetry across a whole range of objects in the farm.
- Fast Site creation based on copying a master template Site Collection from the database level using “SPSite.Copy” function
- SMTP connections now support TLS.
- SAML claims based authentication will be preferred though NTLM/Kerberos would still be supported.
- SharePoint Server 2016 now provides the same data loss prevention capabilities as Office 365.
The compile time for customized XSLT files used for Content Query, Summary Links, and Table of Contents Web Apps is improved.
- eDiscovery and Legal Hold will now traverse SharePoint Online in O365
- Search Service can query SharePoint Online in O365 and provide a single ranked results set with integrated relevancy (no separate verticals)
- Consolidation of Social features to ensure followed on premise and online content appears in a single social profile
- Delve and Office Graph API can surface content from on premise services along with content in O365 (will be released for 2013 this year)
Item level encryption using Azure AD Rights Management Services
High Availability & Scalability
- Patches would be much smaller.
- Patching would support nearly zero downtime to the farm and no disruption to the users.
- Content DBs would scale to terabytes. (although I would prefer it much smaller and structured)
- Maximum upload size has increased from 2 GB to 10 GB.
- Index partitions support upto 500 million maximum items.
- BITS now replacing FSS over HTTP and Cobalt to reduce IO between servers and bandwidth to the end user
Traffic Management endpoint automatically routes user requests based on server health.
- There is no direct upgrade path from 2010 to 2016 (sites and databases must be running in 2013 mode)
The upgrade process is the same as 2010 to 2013 (2013 databases are attached to a new 2016 Farm and are upgraded)
- SharePoint Foundation is not supported.
- No Stand Alone option which installs SQL Express. Only Supports use of SQL Server.
- Forefront Identity Manager is no longer included. Instead support for Microsoft Identity Manager is encouraged.
- SharePoint Designer will not be shipped with SharePoint 2016. Instead, support for SharePoint 2013 Designer will continue.
- Duet Enterprise for Microsoft and SAP cannot be deployed with SharePoint 2016.
- Excel Services and its associated business intelligence capabilities are no longer hosted on SharePoint Server. Excel Services functionality is now part of Excel Online in Office Online Server (this is the next version of Office Web Apps Server), and SharePoint users can use the services from there.
- The Tags and Notes feature is deprecated in SharePoint Server 2016. Users can no longer create new tags and notes or access existing ones. However, an administrator can archive all existing tags and notes by using the Export-SPTagsAndNotesData cmdlet.
SharePoint 2016 comes with number of features that were either missing in SharePoint 2013 or half-baked. While there are financial implications due to some of the deprecated features, Microsoft has certainly poised SharePoint for growth and user adoption.