Microsoft Office SharePoint Server Reviews

In SharePoint, you have two functionalities from my perspective. One is from a newsletter perspective and the other is from a team perspective For example; you have the SharePoint Teams and then you have the SharePoint Newsletter.

SharePoint Teams allows you to create a concept as a team, whereas SharePoint you create a workspace in Power BI and also you create a channel in Microsoft Teams. That's the beauty of the full component of Office 365. When you create things, you also can expand the same functionality for the additional applications that are out of there. The SharePoint News is used when you want to create newsletter updates on SharePoint.

On the point of the design is a design capability. They're there for you to put hyperlinks to other pages if it was your HyperText Markup Language or web page, so the idea or the service is to do a little bit in that direction. A good advantage is that you can create lists in SharePoint.

Basically, you have a full list and the beauty of that is that you can have a Power app that works with it. For example; you could develop a Power app that could be connected to that same SharePoint list. Your Power app will be your front end, where you input your data. Then your SharePoint will get that data into that SharePoint list. It means that you could use the Power BI connected to that SharePoint list to develop your front end, including the visualization of your reports.

Then, you could embed that Power BI report inside of the SharePoint for the end-users to consume. Inside of that SharePoint, they could see the report and they could see the information. Essentially, it is the full suite of Office 365 with the advantage of using the SharePoint database as your list. This is an example of one way that you could use it.

One of the strongest points for Microsoft applications is that they have a very big community.

Document management and records management features are the most valuable.

It is a bit restrictive to develop in the cloud version. A lot of features are in the cloud now, and you have to develop on the outside. As far as the platform and the programming side of things are concerned, it is moving more towards configuration management rather than programming. When we are doing solutions, we are basically just configuring it to make solutions happen rather than actually using the Visual Studio code and developing from scratch in the cloud. It is almost like creating an app. You have created an app for your phone, but the app doesn't really sit on your phone. It sits somewhere on a server, and the database sits on another server. The app is just pulling and pushing information. The whole development has changed. We used to install things directly on the server and then run the application from the server. Now, it is more of a modular architecture.

Our primary use case is mostly collaboration. We use it for document sharing and things of that nature.  

I would say the collaborative part of the product is the most valuable. You can just send a link to to content to other people. You can get stuff done in one place and keep it centralized rather than attaching documents into a emails. Working this way just makes the job function a little bit easier.  

With SharePoint, we have done multiple types of projects. It's a complete ECM, Enterprise Content Management piece. We have implemented something like Power App forms for big oil and gas companies based out of Houston. Power App forms for outages can work in offline mode, which is helpful. We also use it to work on tablets and mobile phones as well and that kind of stuff.

There's a lot of features that are quite useful. Building Flow and Power Apps is great. Eventually, we started to use it for platforms too, however, now it's gone, it's not there anymore. SharePoint Online, both classic and modern versions, we have worked with extensively and so we know it very well.

The implementation and configuring of the resolution are very easy in the online version.

It's really good because with its collaboration we are able to connect with people and we are able to share our documents online. We are also able to share on the fly when we have a call with the Microsoft Teams.

It is really helpful now because, with COVID, everyone is working from home. This product is very useful for us. We can chat and visit any time using Teams.

The most valuable feature is that it is very usable. I can navigate it, I can have a media call, I can have a call with my project team, so we can chat with every team kind of like WhatsApp. Any time there are projects or other things, we can chat in a secure way. It's automation-specific secure. 

I'm a product development manager and we are resellers of Microsoft Office SharePoint Server. 

I like the collaboration, the ability for multiple users to work on a single document and be able to firstly collaborate and share notes about the document, as well as being able to work on the document without losing the information. Previously, there was little control over who had the latest document and this was a big challenge for us, trying to consolidate all of the aspects together. This provides a way for us to work together. It's really important, collaboration is one of the key reasons we have the software.

Our primary use case of SharePoint is as a document library, or repository of files, for our project management sites which are basically communication sites. We're currently using the solution on-prem but have also used it on cloud. We have a vendor relationship with Microsoft and I'm a business system analyst

I like the way the solution was helpful in delivering project updates. I can incorporate my project timelines presented in web page format along with the KPIs. The documentation repository is within the same page too so you have the updates, the timeline status, and the documents which you can pull out. It means you can collaborate with others all in the one location.

Our primary use of this solution is for in-house staff. We have six SharePoint sites, each secured autonomously for access to content, and we have not at this time shared outside of our domain. When we have consultants or partners that need access then we provide them a local account.

One of the value adds from SharePoint is the version history of any given document, which when we first began using it was, I believe, ten versions by default and now it's gone to over one hundred with no extra effort. If somebody modifies something then you can go back a hundred versions of that document to see who did what and at what time. I think it even tracks on which IP address the changes were made. If there is a concern about rogue access using an authenticated account, we can go back in time and research that.