What is our primary use case?
Our organization primarily uses
SharePoint as a document management system. It serves as a storage and collaboration platform for our users, allowing us to co-edit documents and easily share files externally. We have controlled the number of sites and use it mostly as a document repository, rather than exploiting its advanced features.
What is most valuable?
The most valuable features of
SharePoint include the ability to co-edit documents in the Office suite, particularly Excel and Word. It is also easy to share files externally and sync them locally on computers, which is convenient for users.
What needs improvement?
There is room for improvement in the integration capabilities of SharePoint, as the suite of APIs is convoluted and complicated to use. The APIs are limited and not all functionalities are supported. Also, Microsoft forces users to upgrade their license to access proper auditing information, which is essential and should be included in any license.
For how long have I used the solution?
I have been working with SharePoint for about five years within this company, and I have used it in different capacities over the last twenty years.
What was my experience with deployment of the solution?
The initial deployment of SharePoint was done with the assistance of a third party for configuration. We have not made significant changes after setup, controlling the environment by limiting the number of sites and functionalities.
What do I think about the stability of the solution?
While SharePoint is generally stable, there have been instances, such as issues with the search index, where it took Microsoft a considerable time to resolve. Microsoft's support can be slow, taking 24 hours to respond, and often more actions are required on their end.
What do I think about the scalability of the solution?
SharePoint presents limitations regarding scalability, particularly with the volume of data, as it is a SaaS solution with undisclosed constraints, making it unreliable at times for large volume operations.
How are customer service and support?
The technical support from Microsoft for SharePoint is often slow and rated a three out of ten. There is a lack of detailed and timely responses, and support is not always transparent with the solutions.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Before SharePoint, we used
OpenText, but our clients wanted to collaborate using SharePoint, which led us to switch. We also evaluated solutions like
Dropbox, but client preference pushed us to SharePoint.
How was the initial setup?
The initial setup involved a third party for configuration, and we have managed it with limited changes since, focusing on controlling the number of sites.
What about the implementation team?
We worked with a third-party implementation team to configure SharePoint during the initial setup phase.
What was our ROI?
We have not calculated a return on investment for SharePoint as our company is not skilled in calculating ROI. However, we know we have improved processes and collaboration.
What's my experience with pricing, setup cost, and licensing?
The pricing and licensing for SharePoint are considered expensive, especially when Microsoft forces users to upgrade to higher licenses for basic functionalities like auditing. This upgrade requirement feels unjustified.
Which other solutions did I evaluate?
We evaluated solutions such as
Dropbox and previously used
OpenText before switching to SharePoint.
What other advice do I have?
Locking SharePoint down simplifies its use, but for more sophisticated requirements, I recommend looking into solutions like OpenText that offer more flexibility. Overall, I rate SharePoint a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other