SharePoint Reviews

For intranet and file sharing and internal communications.

Yes, especially reducing the print paper and having a very quick response, and reducing the time between department and people.

Sharing and workflow.

Special implementation and development should be easy.

Stability is OK.

Scalability is OK.

Partner was not good. They did not have so much experience.

FileNet and Documentum.

Very hard.

Vendor and partner.

I did not measure, but it is useful.

Pricing is very high.

No.

No.

To initially set up as part of a records management initiative. The company I was working for needed to better track and support how and where documents are located. 

While there were plenty of out-of-the-box solutions for records management projects, this probably under-utilized aspect of SharePoint can help better track documents and retention. 

Ease of implementation. Certainly, IT needs to give appropriate access to a sandbox, but learning is easy and quick.

Microsoft seems to always be making changes. Sometimes you will get a message saying some aspect of what they deliver is being discontinued and often you simply never had time to explore what it had to offer in the first place. 

Majority of our employees (around 800) all have Office 365 E3 Enterprise licences. Using at first purely email and Skype, we have now created a SharePoint Intranet and all users now use OneDrive.

Teams are now being linked to SharePoint document libraries and embraced by many of our departments. Yammer is now the centre communication tool for company-wide information. We are starting to find the benefits of Power BI, Forms, and Stream.

It has allowed improved auditing and opened up the cloud. Considerable in-house savings. We are able to add IRM and DLP to company information. This has made the auditors happy.

We have given users a common platform and increased reporting. Information is now available instantly to managers on all devices. 

The ability to take Excel files and make them dynamic SharePoint lists with instant reporting capabilities has been a major benefit. Teams are now heavily used in how all our departments work.

Skype/Teams are now the main way our company communicates internally. OneDrive and SharePoint provide a secure, fully auditable way of storing information.

You still need a bit of expertise to add branding. It is still important to have Super Users to keep moving sites forward. 

The company needs to make sure that their policies are dictating how information is stored and used, instead of letting SharePoint take control. 

Annoyingly, many new Office 365 apps always end up being only US locale for the first year of their life. Microsoft needs to realise that most of their customers are not in the USA. 

I have found team sites offer much value to our organization. As a consulting company, it allows multiple consultants to collaborate on a team project for a customer.

We use SharePoint for companywide document management.

Although workflow is limited in SharePoint, we have used it for many onboarding processes, PTO requests, etc.

SharePoint has streamlined many processes and provided additional organization for our company. It has become a central location for both documents and productivity.

I would love to see a more robust workflow. There are 3rd party products such as Nintex and K2 that can be used, however I would like to see it built-in.

I’ve used SharePoint for 2 years.

Stability issues have been found with the database. From the infrastructure side, most people use dedicated databases for SharePoint so a simple reboot usually fixes the communication issues.

SharePoint is extremely scalable but requires planning ahead of time. You must answer some questions about your environment to determine how many servers and what SharePoint function(s) they will serve to meet the demands of your organization.

I have never used Microsoft technical support for SharePoint in particular, but Microsoft support is very good.

We used to use simple file shares and emails.

SharePoint can be very complex to setup initially (both infrastructure and back end design and implementation). The more scalable the environment, the more complex the setup will be. Generally speaking, a 3rd party consultant will be needed to implement the solution.

There are two options with SharePoint. They have an on premises and a cloud solution.

We did not look at alternatives.

Hire and communicate with a 3rd party consultant.

• Ability to collaborate with others in organization
• Ease of use
• Customization

All employees can view necessary interactions/documents, great task management and contact management functions.

Document libraries and document management could be improved.

I have used SharePoint for two years.

We have not encountered any stability issues.

We have not encountered any scalability issues.`

We have never required support.

We did not have any previous solutions.

There are free versions that satisfy most needs.

The features that I find most valuable are:

• Indexing
• Search
• BI
• Custom apps model
• Team sites
• My Site
• Integration with Yammer

SharePoint provides out-of-the-box data indexing and caching. BI is optional and driven by content population as well as external sources import. Custom App model is a platform allowing for a variety of home-grown or enterprise based solutions. We have a local team developing proprietary applications available via an in-house App store that is rolled out either globally across all pages, or individually per team site.

With the use of “My Site”, we were able to minimize our data center shared drive footprint and roll most user data into a searchable database. SharePoint provides file level,content security, and shifting data management to the customer.

With version management and recovery options, customers can easily restore files from the recycle bin. However, once files are removed, administrators are forced to turn to third-party tools. Administrative recovery and data management need more attention. File recovery is not made simple. Once files are discarded from within the SharePoint product, recovery turns into a long process of restoration from databases.

Alternatively we use a third party product by AvePoint called DocAve. It allows for an easy point and click recovery preserving original security permissions, which is not possible with direct database restoration. I would like to see a native Microsoft product do this.

We have used this product for two years.

With an on-premise, or even a hybrid model, local operations and platform teams are responsible for the uptime of the system. Most common issues are service halt, drive space management, and database corruption. All of this can be resolved easily with an Office 365 infrastructure migration.

Scalability was not an issue for us at the time of deployment. Capacity planning and resource management was done well. However, scalability issues with the current version is done much better than in previous versions

The quality of technical support depended on the support contract and severity of the issue. An enterprise level contract allows us to raise Priority 1 cases which are addressed on a 24/7 basis. Most issues were resolved promptly.

We upgraded from SharePoint 2007 and 2010. Data migration was the biggest culprit. The main reason for an upgrade was to provide easier platform management.

Deploying essential components was fairly straightforward. "MySite" page customization for multi-brand organization was a bit complicated due to the application of custom templates and role-based access control.

Do your homework and work closely with the vendor during capacity planning. Think a few years ahead.

We did not evaluate other products. However, also invested into WordPress and Kentico CMS under the MS Azure PaaS environment.

Make sure the product meets your business needs. Once you make that decision, rollout the proper internal marketing and adoption of the product. Workshops are available by Microsoft along with adoption recommendations.