SharePoint Reviews

Lists, documents, wiki pages and being able to create sites/subsites are valuable features.

The fact that our operational process improvement initiatives continue to be assigned on a lower priority in our portfolio management, it has given rise to the use of SharePoint as a platform to run its day-to-day operational processes. Specifically, we moved away from using MS OneNote.

It has its limitations. We are unable to use this tool to "archive" data and run queries to generate hindsight information.

I have been using this solution since 2011.

I have not encountered any stability issues.

I did experience some scalability issues; this could be more because of trying to use SharePoint as a BI tool, which it is not designed for.

As it is internal, there is some knowledge that they are unaware of which makes it necessary for me to go check with third party sites (such as wikis) for answers.

Initially, we were MS OneNote.

All I did was request for a site to be created and then the rest of the configuration was up to me.

I am not involved with the purchasing decisions.

There are some features that I am looking for and that I am unable to find, for example creating nested IF functions.

I mostly use the solution for the creation and sharing of documents.

SharePoint is easy to collaborate with.

The solution's support services and GenAI could be improved and made faster and more knowledgeable.

I have been using SharePoint for more than two years.

I rate the solution’s stability eight and a half out of ten.

SharePoint is a scalable solution.

I rate the solution a seven or eight out of ten for scalability.

The solution’s initial setup is straightforward and doesn't take much time.

Our IT team deploys the solution.

The solution has good integration capabilities. SharePoint supports remote work and team collaboration within our company. The solution's workflow data analysis and AI-driven content organization are good. I would recommend the solution to other users because of its reliability and AI features. SharePoint has helped our organization save time and money.

Overall, I rate the solution an eight to nine out of ten.

We use SharePoint to save client-specific and internal documents.

SharePoint has an option where you can open files on the browser, whereby more than five people can make amendments to one Excel online file. The best option on SharePoint is that it can be opened from your desktop. If I map the URL of SharePoint to my desktop, I can see the files on my desktop. That is a fantastic feature I don't see in many other service providers. SharePoint's interface is very good.

SharePoint’s scalability could be improved. I don't know how much an organization pays to scale SharePoint, but I have seen quite a few organizations opting out of SharePoint. The reason may be its scalability or because it is less cost-effective.

I have been using SharePoint for six to eight years.

SharePoint is a stable solution.

My organization is an enterprise business, and half of my organization is using SharePoint.

SharePoint's initial setup is not complex. It's good for any new customer to adapt and understand.

I advise users to think about SharePoint's scalability if they have a huge use case. Otherwise, SharePoint is a good option to save internal and external files.

Overall, I rate SharePoint a seven out of ten.

SharePoint allows us to access and to search for what we have in our repositories.

What I like about SharePoint is that they keep up with a lot of updates, and they bring out new features. I also like that the system is integrated with the Microsoft 365 suite of apps.

Document management and the ability to easily integrate single sign-on (SSO) are areas for improvement in SharePoint.

Integrating SharePoint with other software is what I'd like to see in its next release.

I've used SharePoint in the last 12 months. We use it internally in our organization.

The stability of SharePoint needs improvement, because once you start to get a large amount of data, it becomes very unwieldy, and it takes a long time to index. There are much better products for content management and knowledge management, when compared to SharePoint.

SharePoint is not as scalable, particularly when implementing larger projects. It's good for small-scale implementation.

I haven't personally contacted the technical support for SharePoint. It's our support team who contacts them.

I used HPE Content Manager, formerly TRIM software, which used to be owned by TRIM here in Australia. We used TRIM a lot, then it was bought out by HPE, HPE has now been bought out by Microsoft.

Our organization chose SharePoint because they wanted to become accredited with Microsoft. They saw that Microsoft was the industry leader, so everyone wanted Microsoft. They saw Microsoft as the way forward, at the time.

The initial setup for SharePoint was complex. Anything from Microsoft is complex.

We implemented SharePoint in-house. We had a team that had experience with SharePoint when we decided to use it as our content management system. We had the skills from implementation and from attending numerous Microsoft training courses.

SharePoint is probably cheaper than dedicated, larger, and more useful content management systems, so you could get a return on investment from it, as long as you keep your infrastructure and everything up to date, and move to the new version when you have to.

You have to pay for a license to use SharePoint, and any extended support from Microsoft is expensive. For example: if you have SharePoint 2013 and it reaches its end of life and goes out of support, you can migrate to SharePoint online, and that's a benefit, but you'll have to pay for extended support.

I evaluated Lotus Notes and HPE Content Manager.

In terms of what features I found valuable in SharePoint, I haven't found many. I had come from IBM and was very entrenched with Lotus Notes and the Lotus Notes environment. I love Lotus Notes. When IBM sold Lotus, we started to move away from Notes, and I didn't like it, and then I was made redundant. Now I've been outside of IBM, having to use Microsoft, and I hate it.

My advice to people looking into using SharePoint for the first time is for them to 
look at how much data they have, and also look at the volume their data and data holdings are going to grow to. They should look at how long it would take to get to that point, then look at their ROI, and whether they would need to upgrade to another product in the near future. I'd say "Yes. Go for it.", but they should also look at the future, and how it would be long term.

I'm rating SharePoint a seven. Yes, it's good for organizations to start on knowledge management, but you'd have to look at how quickly you think your data will grow, and how soon it would take to get to that point, because it can become unwieldy.

Our company is a consulting partner of Microsoft. We're a service integrator that works in both the private and Australian Federal Government sectors.

I have been using SharePoint for over twelve years. 

It's a big solution comprising many services similar to an active directory installation with connections to Skype, Exchange services, metadata services and stuff like that, it can do basically everything you need in order to deliver something like a Twitter website or similar solutions. So I do not think that anything rivals SharePoint on the market. Maybe if a lot of effort is placed upon some WebLogic solutions, this may happen. But, this would need a lot of customizing.

So if you want to have something like a business, or if you want to have something like a product catalog and you are selling something like Amazon, you want to uniquely identify your product like Amazon does it with its ASIM numbers and these to be identified with a name. So the service identifying these unique ASIM in numbers with their names which might be localized in English, German, Dutch or other languages. These are being identified by a managed Metadata service. Amazon does something very similar to Metadata and SharePoint. So, that's the basic technology everyone needs for this web service experience and order to identify the same object with different names.

The metadata services, the WCF service integration and the Voxel feature are three most valuable elements of this solution. The Voxel feature, for obvious reasons, because you want to implement business processes and you do not want them to stop if the machine stops so they have to be automatically started. This is What the Voxel feature in SharePoint does. The managed Metadata allows you to define your own notions or terms denoting notions within your companies. And I if I want to disarm them, or disarm power supplies of different types, I need something to denote the names pointing to entities, any program can identify.

Perceptively it does what people used to do with the pens and pencils, on paper. For Millennials, by taking a note of what to do on the paper or stone or whatever they have been using and let anyone else read it and execute with it. So what any back flow or business process you have did legal one for King Nebuchadnezzar 2,700 years ago or for any business where you are taking a phone call, we two are doing right now and writing down something or I have to remind myself to do whatever and sent that over to pop and be while having receipts from department A and have to digitally sign it and send out the paper. It streamlines everything for us.

All of this business processes, people have been performing solely within their minds. Maybe automatized with the structural feature, but it depends on all the metadata that has been stored within the managed metadata, service, user profile data or whatever. So you can not just say, "Oh, I want to send a car" to whom do you want to send it to. Which car do you want to send? So, all of these parameters have to be stored somewhere else. This is what drives the business process and SharePoint solution allowing you to automatize them.

I would be liking to see the talk features included in SharePoint because Microsoft effectively discontinued this talk and put something like logic apps but only for Azure, and most German companies do not like Windows Azure because they do not want to put that data into a cloud where everyone can see it. So, there's a lot of distrust with Azure environments and you need something to have on premises as a similar solution. And this talk is something like a big playing ground. For instance, if you want to play monopoly and anyone wants to move the pieces but moving the pieces on street A to street B means you are changing your business process from, I have been starting tax declaration, to I've been finding it but not yet sending it out. So, if you wanted to have something like a business process be denoted as a board game, which is what Monopoly did in 1945, effectively.

It is very stable if you know what you are doing and make some precautions. Microsoft lists these precautions, but these precautions are not automatized. It would be nice to have precautions such as: disk size, backup checks, or whatever automized that can be integrated with the SCCM team foundations server.

Well, that's one of the strengths because it not just using soap web services where it sends some XML file to different machines, but it's using WCF, which is a version of a web service, web services being used if you have a different machine where you want to call a function. The type of machines we are using now are invented by Alan Turing, a guy from the hacking Enigma code and Robert Dennard, who invented RAM. These types of machines do not allow you to, all functions on the remote machine. If you want to do that, you have to send a hint which is what web services does.

I have been using the commercial technical support and they're always professional. It's not cheap, but they are always professional. So if there's problems to be solved, Microsoft tops off as excellent.

The initial setup was very complex. We had to keep in mind all of the backup solutions. It is kind of like remodeling a kitchen. You must think of all of the parts, the architecture, the electricity, the air flow, etc.

I think that SharePoint is the best on the market in terms of stability, quality and capability. I also suggest that if a company has chosen SharePoint, the company must have at least a two day training prior to implementation.

The cost is expensive, but worthwhile.

I have found SharePoint team sites to produce much more 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 company-wide document management.

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

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

SharePoint has workflow built into the software however it is very simplistic. Third party applications integrate with SharePoint to provide a more feature full workflow. For example, if I wanted to create a workflow for new employee onboarding process I could use SharePoint built in workflow. Doing so would provide me limited configuration options, no version control, only attach to one list, sequential workflow only, and not very customizable.

Using a third party you can create intuitive workflows, customize branding with CSS, easy drag and drop implementation, comprehensive workflows actions (loops, foreach, parallel actions, variables), and maintain retention history.

I would like to see it built-in the product itself.

I have used this solution for two years.

Some 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 in order to determine the number of servers and also as to what SharePoint function(s) they will serve for meeting the demands of your organization.

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

Initially, we were using simple file shares and emails for this purpose.

SharePoint can be very complex to set up initially both in terms of the infrastructure as well as the backend design and implementation. The more scalable the environment, the more complex the setup will be. Generally, third-party consultants will be needed to implement the solution.

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

We have not evaluated any other solution before this one.

You will need to hire and communicate with a third-party consultant.

Synergy with other applications in the MS Office suite. For example, with a single click from the MS Lync client, you can create an email in the Outlook client and vice-versa, amongst many other similar integrations between applications that previously did not speak to one another.

Collaboration became a lot easier. Meetings happened more frequently between colleagues across different locations sitting at their desks and not in special video conference rooms.

Better mobile optimization and a similar experience level across device types (desktop, tablet and phones). For most applications, MS SharePoint included, users are treated to different experiences across devices. For example, Excel works slightly differently (has fewer features/capabilities) on mobile when compared to the desktop experience. It would be nice to close this gap as much as possible, such that a user may have no qualms transiting between devices.

I have been using SharePoint for over four years.

We did not have any stability issues.

We did not have any scalability issues. It is as easy as adding new licenses for new users.

Technical support was not as good as expected. Sometimes request took upwards of three business days.

We used several single purpose software tools for each area of our need. We switched to MS SharePoint/Office 365 for a number of reasons, including: the seamless integration between the many apps in the suite; colleagues (users) are familiar with the MS office interface from Excel, Outlook, Word and PowerPoint and that shortens the learning curve considerably.

Setup was straightforward.

For non-profits, seek out non-profit licensing.

We evaluated eleven others.

It’s the best in the class, but make sure your existing solution doesn't already meet your needs before making the decision to go the MS SharePoint route.