We'd like to be able to upload from MS Excel to deploy tasks and use drop-down lists to collect further information. We need to set up tracking tasks from scratch. In other words, we would like to create tracking tasks by templates embedded or uploaded directly. 

Make progress elaboration without boundary.  If you have another format of data file, it can support text. Additional functions for a next-generation iteration could include a better project file format. They should add dependencies for project schedule updates when one task schedule has been changed. 

View full review »

There's a challenge with desktop applications synchronizing with online documents in real-time. If someone is working on a document in the desktop version of Excel, for example, and someone else is editing the same document online, the changes won't sync immediately. That's the only real challenge we've encountered.

View full review »

It has worked very well for me. It seems like they've improved everything. I don't have any cons about it as such, but I don't think they have a talk-to-text, speech-to-text, or speech-to-type. That would be cool for accessibility.

View full review »

There are challenges related to permissions and file visibility within SharePoint, particularly when less experienced users are managing sites. One issue is that when users mistakenly hide files or set permissions incorrectly, it can lead to files becoming inaccessible, requiring intervention from Microsoft support to resolve. It takes a long time, sometimes around two months, to resolve the query. Instead, they could provide enough background information on how to use the product for beginners to improve this area.

View full review »

Perhaps it would be possible to add more design tools to improve the platform. While the current design is good, other similar platforms, such as Wix.com, offer better design tools. Wix.com is a website-building site that specializes in this area. Microsoft could take inspiration from them and incorporate similar tools.

The initial setup is complex and has room for improvement.

The documentation is poor and has room for improvement.

View full review »

The limitations and boundaries must be extended. Often, the documents pile up and reach the limit provided, and we need to archive them. It would be good if the capacity were increased.

View full review »

For my role, it personally covers all my requirements. 

View full review »

The solution doesn’t support PDF signatures on Android. My staff has tablets and phones. We couldn’t sign the documents on Android. It was quite problematic.

View full review »

Too many versions being released in a short time period. Too much time being devoted to migration planning.

View full review »

• The linkage between items, such as the blog. It does not integrate into communities or team sites, it's totally separate in its own environment. Tags and @mentions are not connected to them either. They feel very disconnected. Our leaders would like to use blogs but since they aren't connected to anything else they aren't a great solution.
• We are on premise so the mobile experience is also very lacking since users need to use a VPN on their device in order to utilize things.
• There aren't any metrics provided out of the box. I have to ask for just the number of new users each month and it takes days. There should be more data that we can use available to us as admins.

View full review »

SharePoint Online could improve the user interface and when modifying any of the user interfaces can be challenging. Additionally, there are challenges with the detail in the analytics user interface and the overall customization could improve. 

In the next release of the solution, they need to fix the user interface. It is not user-friendly for a generic user. It should be easier because in some of the applications it's quite easy to assign the permission, you only need to use the right click of the mouse and select the permission that we need to assign. However, in SharePoint, it's a bit complex.

View full review »

The product must provide more automation. We must be able to automate tasks instead of doing them manually. The product must enable customization of features. It must allow integration with other systems. Integrating the tool into databases like Oracle or Microsoft SQL and pulling data from SharePoint would be helpful.

View full review »

The product can be improved in the following aspects:

• In order to put certain customizations in place requires the downloading and installation of SharePoint Designer 2013. For large organizations where security has the majority of devices locked down, downloading and installing applications is not a simple process. It would be nice if some of the SharePoint Designer functionality could be baked in/part of the edit page functionality.
• The reporting functionality needs improvement, to combine multiple lists (for the most part) requires a solution outside of SharePoint. It would be great if there was an option to combine lists that have the exact same layout (fields and order of fields) so that the combined lists could be summarized and reported on.

View full review »

SharePoint should not provide frequent updates.

View full review »

Intranet/website publishing tools and features are kludgy and sometimes defy logic.

The ribbon interface is not intuitive. Information rights management is difficult. It is not standards based.

The custom .net usage in fact requires Windows Azure, which takes the complexity to another level. Also, you need to build this into your existing business systems to make full use of the features.

Regarding publishing, there seems to be a gap with HTML 5 publishing tools and/or tools like Dreamweaver and such, which lack strategy, synergy and standards, from my point of view.

Also, searching for information appears based on Bing and that is utterly useless. One needs to bolt a Google search engine onto your solution for optimum results.

SharePoint in either server or cloud offerings is itself very complicated in terms of all the moving parts to consider, which takes time to figure out regarding feature sets and use cases for them.

It would be nice to see a top-notch web-publishing tool that a five year old could use to go with the suite of Office online applications with much better integration with serious 3rd party search tools.

It’s nice to have server or Azure based options, but a hybrid cloud that offers both needs some work. Neither HPE or Dell are competent with their appliance offerings in the CPS space that could be offered as a package, if customized and developed into a single SKU appliance-based platform with all the goodies inside the rack.

Plug, play and connect…customize, develop and deploy. Repeat...

View full review »

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.

View full review »

Well, for SharePoint Online, the add-on features which are free tend to expire within a month or earlier. It would be great if these free add-on features would last longer or last permanently.

View full review »

For this version, assigning permissions should be more intuitive.

An improved user interface would be beneficial. Achieving our goals in a multi-vendor project was not an easy task because of the 2010 UI.

I’m not sure if SharePoint 2013 makes it easier to assign specific access for folders. I found a lot of help online that was mostly for 2013.

We should have the ability to create customized permissions for user groups much easier than it is today. For example, being able to specify which lists and folders a group can access. In 2010, there is no easy way to do this.

View full review »

The way to change the version of the files in SharePoint should be improved. The method of synchronizing files from local to the cloud can also use improvement. 

I would also like to see improvements in the interface, speed to load the page, mark favorite directories, synchronize the most recent, and the least accessed files automatically do the archiving. I would like to have an option at the first sync to choose more locations on your computer.

View full review »

The solution lacks collaboration features so that I am unable to collaboratively create and work on a document with others. The second element that is lacking is compliance or records management so that certain documents, of a legal nature, for example, are only accessible to certain users. I would really like to see that kind of feature.

From a compliance perspective like GDPR  and if the document or data contains personally identifiable data PII data, the SharePoint feature for records management should allow to identify the data being PII data and also provide feature for GDPR wherein the customer is asked for confirmation if needs to be stored and how the data and documents will be used and for what purpose.

If the customer does not confirm should not allow storage of documents and data that contains personal information should not be stored without customers consent. It should allow for archiving feature post the period for which the customer has given the consent for the data and document to be stored  is over should allow to delete the data and document.

Looking for GDPR and other compliance features built into the product as a workflow

View full review »

This solution would benefit from the implementation of enhanced online forms and template development capabilities.

View full review »

The UI could be more flexible out of the box. With coding, you can customize the look and feel to your heart's content, but configuration without coding is limited.

View full review »

From my experience, it’s not the product needing improvement, but the way organizations deploy the enterprise solution. When 2007 SharePoint came around, there was no documentation and information given by Microsoft on their website. You were on your own, basically, looking at blogs and relying on others' failures. Now, there is no excuse to have a badly configured SharePoint farm and or using best practices to make sure your configuration is solid.

There are organizations who deploy this solution enterprise-wide with no training for users or administrative IT support, which is also a big area that needs improvement. Although SharePoint is fairly easy to use, you still want to get total buy-in on the product, so training helps bridge the gap to get that buy-in to use the product going forward. It also helps to show how users can make the most of the solutions and services SharePoint has to offer. Coming up with a couple of how-to demonstrations and even a site with some bells and whistles the users can play with always helps with getting support of the new solutions and services.

Organizations are also not providing governance as to how the user community will use the solution within the organization. Governance is the most important aspect of getting the solution configured for your organizations use. Providing rules for everyone who plans to use the services of SharePoint 2013 is the key to success. Also, bringing representatives from all departments as stakeholders into a working group to meet, vote and share information about what they would like to do with the new tools is also key. You can avoid duplicate efforts for development and other pitfalls that may fall outside of your governance plan by including other departments. This way, your new SharePoint farm does not get the wild, wild west treatment where everyone is doing their own thing.

After working and supporting over 100 companies, I can honestly say only two companies had governance documents in place at their organization, with working stakeholder groups to support the solutions and services. Remember, governance helps with looking at restricted and accepted practices within the solutions and services provided by, in this case, SharePoint 2013. It's just like going to the Office 365 site and looking at exactly what I can and cannot do within the cloud offering, which could be based on data sizing and other parameters I might be looking for to support my organization.

The governance document is used for on-premise implementations, so you can design, install and configure your internal farm based on those configuration parameters laid out in your governance documentation. After you get the governance rules in place, you then create a design document that will capture all configurations within the farm. This will layout how the SharePoint farm should be configured based on SQL, SharePoint, backup, restore, DR and any other third-party tools and configurations.

The next document would then be your installation guide, which is based off of the design document. This shows how all the components mentioned in the design document will be installed and configured based on the design document's configuration parameters. This is just a quick summary of what needs to be done before you do anything with installation of software. Following best practices and other Microsoft documentation for all these documents and the installation of the software is the key to success with this enterprise solution.

View full review »

• Workflows.
• Performance.
• Content Migration and sharing.
• Reporting.
• User experience and design response.

View full review »

I think that the current version of the product is actually quite good, but it's not always easy to find solid training and reference information, especially from Microsoft. Typically, third parties have better offerings than Microsoft, but it still requires a bit of searching to find the most relevant and easily absorbed material.

View full review »

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

View full review »

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.

View full review »

SharePoint designer workflows can be buggy sometimes without any apparent reason. Also, customization can be somewhat burdensome.

View full review »

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.

View full review »

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.

View full review »

The documentation can be improved, so it is easier to use for non-technical people. The documentation was clear only after full training was completed, not for starters.

View full review »

As usual, Microsoft’s licensing structures don’t really seem to fit the needs of their products. This leads to always paying for a project you will never use fully or always be adding to. Also, the product does not perform 100% when used outside of a Microsoft based browser, Chrome, Firefox, etc. It’s getting better, but the architecture is still behind. This is largely the case for mobile as well.

View full review »

Submitting document changes function needs to be improved.

It is hard to identify deltas in documents especially ones with drawings.

The process of updating a document on the fly takes a while to download and update.I am used to robust versions of management systems and hence end up using Apache Subversion (SVN) rather than SharePoint for version management.

I would also like to see who makes the changes inside the documents, that are managed.

View full review »

The user profile synchronization feature is cumbersome to configure and at least initially had some stability issues. Since then, it has improved in stability, but is still not a straightforward installation.

View full review »

I would focus on improving:

• Integration with other enterprise products.
• Simpler API.
• Enhanced ability to report against structured and unstructured data in the environment.
• More flexible security or training: I have noticed in organizations I joined that they lock down SharePoint so much, there is very limited functionality. As a result, teams in the same organization move to other collaboration tools when they would not need to.
• Enhanced ability for users to back up and restore at various levels of the architecture.
• Have SharePoint and Office 365 expand so that additional third-party products for document management are not necessary.

View full review »

• Better collaboration, and team sites (social flavour) mobile enabled

• More and improved integration capabilities into the eco-system of solutions available.

View full review »

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.

View full review »

• SharePoint should provide more out-of-box templates. They should add more site templates like blog templates, forum templates, and so on.
• They should stabilize the platform more.
• Document management requires some performance tweaks as well.

View full review »

It is not very intuitive to most users. It can be customized, but it requires a SME with a great deal of experience and training.

I would like to see Microsoft build better site templates to help kick start those new to the SharePoint environment. Better documentation, training, and tutorials would also help as well.

View full review »

• Data and use analysis
• Load balancing
• Common theme
• Better editing tools: The editing tools are still not up to par with all the existing hi-tech & GUI editing tools:
  
  • To name a few: Real-time trapping, dynamic previews, auto-theme regeneration, animation features, 3D features, color grading & saturation, real-time snapshot replication & deduplication, multi-platform and software language adoptability, file-level security & encryption feature, content security capability
  • Hardware Limitations: Responsiveness to multi-gesture input devices (similar to the ones used in the Iron Man movies or the Minority Report), robotic assistance (thumb print, eye retina scan, voice recognition, etc.)
  • WCAG: auto-accessibility compliance capability & assistance

I have seen bits & pieces of these features from different software companies, but none have actually put them all together, yet.

One day – someday – with the fast developments in technology, the best is still to come.

View full review »

The areas of this solution that need improvement are the relationships between lists, cross-site web parts, and page-building tools.

View full review »

• Ease of use.

• Improvement on the user interface (UI).

View full review »

Unless you have worked with a SharePoint business analyst, designer or power user, managing individual sites does require training to understand the components of the site settings and content. Folks usually start using SharePoint as a file repository without any structure. It can be overwhelming when you have 1,000's of document that a user has to parse through if just looking for a specific title. Without a consistent framework consisting of a standard nomenclature established in the initial strategy of rolling out SharePoint, using SharePoint as a file share becomes unruly.

View full review »

Google Docs has two abilities that SharePoint should support as well:

• The ability to work in the same document at the same time would be a huge improvement. During my MBA studies, we used Google Docs for this. Unfortunately Google Docs doesn’t convert well to MS Word to add the finishing touches.
• Just like Google spreadsheets within Google Docs, I would like to be able to fill an Excel spreadsheet through a form posted on SharePoint. SharePoint has list views that can do something similar, but I want it to do more, tightly integrated with Excel. This would improve the document collaboration options for spreadsheets.

View full review »

The allowed size of document libraries and lists, i.e., the number of items allowed, needs to be increased. This was already improved in the latest 2016 version of SharePoint.

Also, there need to be more options to brand solutions without needing developers. This would be good for end users.

View full review »

It tends to be unstable and slow when accessing different features.

View full review »

We are mainly using third-party tools for it, at the moment, for automating processes. In the new version, for 2019, I know that some of the processes are finally in SharePoint. They are a now using third-party tools for it.

Also, the integration with Outlook could be improved.

View full review »

Little quirks that make it difficult at times to fine-tune some items. The usual Microsoft items where 90% of the product is great, but that 10% makes little things difficult to work with. It is hard to pin down, but Microsoft has you do things their way, when their way is not the best for our needs.

• Developer code: Some areas of SharePoint require you to have a .NET developer code so that it works correctly.
• Numbering: We have production support tickets that we wanted to number in a certain way. However, SharePoint could not do it until we got our .NET developer to create a workaround for the numbering system.
• Sorting: We needed some sorting done, and this required coding. This additional coding is only about 10% of our projects, but it is still there. Thank goodness we can do that when we need to.

View full review »

• The suite is complicated to set up, complicated to maintain, complicated to work with. Cognos requires a bigger and more skilled centralized BI team.
• Cognos Insight, the self-service, desktop dashboarding and analysis tool designed is not quite at the same level of the competition like Tableau or Qlikview.

View full review »

Latest versions of this product have addressed the functionality issue on non-Windows devices.

View full review »

The user interface, although extensible, leaves much to the imagination when compared to modern websites. Companies, like ourselves, are able to transform the front end into anything, but this consulting process sometimes scares off would be clients. Adoption remains a challenge (not really a product fault). Lastly, the workflow remains a kind of ugly sister. Improvements have been made in the form of “flow” (only available on Office 365). But, all in all, companies normally have to invest in third-party tools, such as K2 / Nintex, if they really want to create enterprise-grade workflow processes.

View full review »

• Cloud and Office 365 integration with Outlook could be more stable, and an external company collaborator’s connections can be iffy.
• Custom site provisioning and management
• Migration from On-Premise to the Cloud has no automation tools to help in migrating the enterprise content, and so this requires throttling the bandwidth to guard against attack.
• New application models are too complex - in Office365 you are sharing the whole SP farm with all Microsoft customers in a region so fixes take too long.
• Deploying apps in some cases have limitations because you have no access to the admin console.

View full review »

SharePoint is extremely bare bones when purchased. To really bring it into a functional state, it will require decent configuration and extensions for what you need. It comes with the basics like site creation, lists, libraries, and things of this nature. However, if you need more functionality, you will need to either go to Microsoft for those additional functionalities or to a 3rd party that provides it. This is where the cost for SharePoint balloons.

Depending on the version, there are server requirements so if you're not up-to-date on software, this will also increase the price of the service. For the functionality you get at this price point, it leaves a lot to be desired.

View full review »

• Workflow engine
• Video streaming and huge file retrieving and uploading
• It does not support video streaming and huge file retrieving and uploading
• The workflow engine cannot support business needs.

View full review »

I would like a simpler, more cost-effective solution for connecting data sources with workflows and BI tools, or data mining tools. There are different tools for data mining and for data evaluation, but you have to be a skilled programmer to tie them together. There is no simple and low-cost method to do this, provided that development time is a cost factor.

There are some automatic solutions for this task, such as Team Foundation Server, which is built on SharePoint. These tools can learn specific errors that are being made, using data mining techniques, and they are able to target these errors for correction. Having this capability built in, and customizable for the customer would be of great interest.

I would like to see support for Visual Studio to connect to SharePoint and have a wizard to connect data processes to iHubs, like an analysis server or data mining model, to an output, and to have a smart way of creating workflows. Microsoft will tell you that they already have that for SharePoint online, it's called "Flow", but it is not customer compatible.

View full review »

The user experience is very poor. Configuration for new aspect means usually buying add-ons or a very high level of customization.

View full review »

• Processing data from multiple site collections is not easy as they reside in different databases. 
• The management of the product/back-end is complex.

View full review »

• During uptime under our network, it is hard to find info when content is hefty.
• It should have a Google-caliber search ability and a model-based GUI.

View full review »

Notification templates should be editable without coding. Also, summary notifications should be customizable too.

View full review »

The integration of Office document editing and publishing with the wiki component that we use for creating our how-to section needs to improve. At the very least there should be an easy way to integrate images into the wiki through the drag and drop option.

We also have many other tools that create their documentation in the form of HTML pages, sometimes with hundreds of pages. We should be able to directly integrate those into our site, not just through a link but to truly integrate this content as if it was native.

View full review »

There is a limitation on the number of files that can be uploaded.

View full review »

I would like to see the following:

• More freedom given to a power user
• Feature development on a site collection level without the need for farm-level rights

View full review »

It was a shame to see the SharePoint Design being deprecated, as this was a great way to create very customizable workflows.

View full review »

The user interface should improve. It is still a bit clunky for the new user to navigate around.

View full review »

The product could be more intuitive both from an administrative point of view and from an end user point of view.

View full review »

• Workflow management module
• The web page editor
• The reporting tools

View full review »

• Advise users to update the content.
• Maybe allowing users to change their background and text by themselves.

View full review »

As we are still on an older version, it is difficult to answer this. Primarily, the mobile experience is wanting in SharePoint 2010.

View full review »

• WYSIWYG needs improvement.
• Performance and UI can improve.
• Mobile rendering is not up to the mark.

View full review »

Document libraries. At the moment, they still lack the flexibility you get in conventional Windows file systems. However, it has lots of features that make it a good replacement.

View full review »

Various wikis are very limited; there is no integrated solution for communicators; master pages are too limited and require a developer; and libraries are sometimes useless.

Wikis are not simple enough and too hard to use. There could be auto links, for example, like you can implement in Confluence. A wiki should have an integrated table of contents and auto link to already available terms in the wiki, like Wikipedia works.

An integrated communicator would be an asset. You could use it to ask documentation owners when it will be available in the platform. It would work something like Facebook messenger.

Master pages are just too hard to manage because everything in SharePoint is linked. One level on one page might be a different level in another page; so you need time and failures before you succeed.

In general, it is a good product, but it has limited support and too much expertise required.

View full review »

• Ease of use
• Out-of-the-box experience
• Learning curve

For the most part, the tool is useable, but there are many end users who still find it difficult overall. As a developer, I am able to find my way through the interfaces with time, but it takes too much time to learn these things and remember where they are. As an end user, I can understand why some people altogether give up in frustration.

View full review »

It does too many things and some of them seem impossible to set up.

One of the features that I could not get set up was the access interface. It had many steps and I just couldn’t get it to work. It should be easier to build access applications to do some of the things we want to get done.

View full review »

There is always room for improvement. Workflow is something that can become more intelligent. I can't say to what extent intelligence can added, but I think there is always a scope for making it more intelligent.

View full review »

It should have a lighter interface.

View full review »

Almost all of the areas of the product have room for improvement; some more than others.

• At a high level, mobile, custom development/testing frameworks, BCS, external services integration, and BI may need to catch up more as compared to the other feature sets.
• SharePoint is a combination of multiple products working together. It has come a long way, and the improvements are being pushed at a much faster pace than they used to be earlier. This fail-fast approach of adding features quickly instead of a longer release cycle is a much better way to develop a product in my opinion.

View full review »

I would like to see improvements in the interface. There is a somewhat convoluted way to change lists, columns, and even the site landing page.

Being new to Sharepoint, it wasn't obvious how to do things and where one actually starts. The recent Microsoft interface improvements are good.

View full review »

Not so much an improvement as a caveat: Due to the flexibility and power of the product, out of the box it can be daunting to use. Without some consulting work from a SharePoint expert, the product would not be quite as user friendly.

View full review »

Better wiki offerings.

View full review »

• UX
• Performance (especially Office 365): This is an issues when the sites are accessed from Asia/Australia, which is bad compared to accessing from the USA
• The mobile experience

View full review »

The cloud-local file synchronization application (OneDrive for Business). It is not as simple as expected, but it works.

View full review »

PowerShell for Office 365 is exceptionally limited. The CmdLets available for SharePoint Online are focused on site provisioning and permissioning, and do not include CmdLets for managing Items, documents, libraries, folders, default metadata, tagging, and views.

Development can be a challenge, especially as the development model and direction promoted by Microsoft rapidly evolves, and product components get deprecated. The App model is necessarily restrictive in what it allows to be done, in order to maintain the stability in the multi-tenancy environment. This leads to moving to either client-side object model development, or splitting the application with some functionality done on dedicated servers outside the cloud-based SharePoint environment.

View full review »

It would be nice if the platform made it easier to implement a complete document management process (digitalization, OCR, protocols, etc.) without the need to integrate software from different vendors.

View full review »

SharePoint Online is excellent as is, but licensing for the on-premises version is expensive.

View full review »

Special implementation and development should be easy.

View full review »

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. 

View full review »

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. 

View full review »

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.

View full review »

Document libraries and document management could be improved.

View full review »

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.

View full review »

Synchronization of files in OneDrive can take some time which can ‘annoy’ some users. View full review »

Despite the enthusiasm and very good promises offered by SharePoint, the usage of the power platform is limited, so that's an area for improvement, but I would suggest this just as a team feature.

It's hard to highlight other areas for improvement, but a better approach towards licensing power platform components for guest users would be great. SharePoint licensing costs could be lowered to introduce it to the outside guests of a tenant, then to supply them with power apps and power automate features.

A more straightforward integration with Azure, including better licensing in terms of using Azure components and functions, is also another area for improvement in SharePoint.

My advice for Microsoft, and this is something I'd like to see in the next release of  SharePoint, is for them to constantly improve training material. Currently, the training material is organized in a way where a new feature appears and is enforced, then they develop the training material for that new feature. What happens is that the total product or solution, e.g. SharePoint, then lacks overall introduction in terms of training. There should be a balance between the introduction of the tool and the introduction of the new feature. They should have comprehensive introductory courses for both Office 365 and SharePoint, instead of needing to Google for particular situations. I'm trying to get the knowledge bit by bit, so I'm losing the idea of the whole product, e.g. SharePoint is losing its essence. To get onboarded to any new product, it's important to get a good introduction into that product.

View full review »

Search can be improved a lot because we are always trying to compare it with Google Search. Beyond that, it would be helpful to tag the documents.

View full review »

Flexibility and extensibility, above everything, could be improved. Extending the functionality of SharePoint is painful, at the bare minimum. Complex .NET coding, testing, debugging is necessary to extend the native functionalities. Even with the new "apps" concept in SharePoint 2013, the difficulties in expanding it are present.

View full review »

I’ve personally experienced some difficulties in creating new pages, as this tool isn’t a web designer’s dream. Providing a list of existing pages that are named the same or similar to the new pages one might create would be helpful. Being able to toggle into those pages without exiting your original page would also be beneficial. I’ve also noticed limitations with copying and pasting fonts and images.

View full review »

The areas in which this product can improve are:

• The user experience can be simplified a bit more.
• The performance and customizability can also be improved.

View full review »

Search integration across SharePoint, Yammer, Teams, and OneDrive.

View full review »

We need the storage of the files, the documents right now are in the database. Maybe SharePoint has to improve the capability to store the information in file systems. In theory right now, it could do that. But, I understand that some functions are lost when you store the information in a file system, so maybe that's a way SharePoint can improve.

View full review »

It should have more user-friendly customization, as it still requires developers to get engaged and build sites.

I would like it to be more compliant with global regulations. There are certain features which could be included that currently are not there, such as compliance and record management capabilities.

View full review »

Replication needs improvement.

View full review »

SharePoint Designer enables creating workflows easily. However, they produce errors at times. There seems to be glitches which require workarounds to sort out. It is an amazing feature to have because workflows can fully automate processes that would otherwise be manual.

View full review »

The workflow engine. MS Workflow Manager is still in Version 1.0 and the future Microsoft strategy for this product is unclear.

Requirement dependencies of the initial setup and support could be very complex.

Companies often decide to buy workflow products such as K2 or Nintex because of larger features set and better stability.

View full review »

Areas with room for improvement:

• A more responsive UI: There is a set of user groups who want to use this application in their mobile devices. If SharePoint provides a responsive UI by default, then no extra efforts are needed to integrate the existing UI with a more responsive UI.
• The deployment process on multiple servers adds redundant work, mainly for configurations and creating site collections: Same-application deployment requires initial setup to be repeated for any new environment. For example, the very first time we need to set up each environment, we need to create the site collections and so on, and then deploy WSP packages.

View full review »

When we develop portals, we need to develop a lot of web parts that eventually go to a number of pages. These pages must be created manually. There should be some easy way to develop pages automatically via programing.

View full review »

Setting up permissions can be overwhelming. If this can be improved it would be great. Also Sharepoint search out-of-the-box needs improvement. View full review »

Integration with Outlook would be a major improvement. Staff also commented that it does not integrate despite being part of the Microsoft family.

View full review »

Migrating SharePoint sites can be a cumbersome process and it usually results in the incomplete migration of SharePoint sites and data.

View full review »

Administration is still very complex.

View full review »

No additional features are needed at the moment, except bringing some of the alerting functionality from the on-premise to the online version.

View full review »

Performance: The web page was sometimes not as fast as we'd like to see.

Application of custom CSS/visual styles was cumbersome and usually required a complete re-write of out-of-the box SharePoint site pages.

View full review »

SharePoint sometimes cannot handle the amount of co-editing that we do. Of course, this could be the user, not the tool.

View full review »

The product could be improved in a lot of way. It is so frustrating to get things to work as advertised.  

View full review »

• Improve the user-friendliness.
• Make it more intuitive.
• Make it more like a flow/BPM view style.
• More hints and make it more user-customizable.

View full review »

Allow more functionalities for the on-premise version. Do not force the move of content to a non-private cloud.

View full review »

Configuration and troubleshooting need improvement, especially regarding TFS integration.

View full review »

Analytics and reporting is an area with room for improvement.

It should provide more complex-process automation out of the box.

View full review »

There are multiple areas with room for improvement:

1. Scanning engine driver
2. Mobile integration (just launched by MS, yet to be seen)
3. Stability

View full review »

They need to integrate all the solutions, for example, Office 365, into SharePoint. The idea is to create a workplace for people in the company. There should be only one place - it could be Skype for Business, OneDrive - for the news, for internal information about the company, or new documents. This is the idea, to create an ecosystem for people in the company.

View full review »

I find the search feature in SharePoint foundation to be limited to the basic document properties. This is at odds to the type of customization that you can apply in the library. For example, we added a field to specify the department but found that the field had little or no bearing on the search results. We found it hard to determine how SharePoint uses the document properties in the search, and whether it uses anything beyond the document title.
Once we had a better understanding of Foundation's limitations, we updated our properties accordingly, with a strong focus on the document title property as a search term. This involved an extensive rework of our existing documentation structure and naming conventions to better suit SharePoint. Despite these changes, we still can't seem to get our version of SharePoint to return meaningful results, even when searching an exact document title.
I realize that this is a limitation of the version that we are using but I would like the Foundation search criteria to be more clearly defined so that document managers know what they are working with from the start.

View full review »

• E-forms
• Workflows
• BPMN

View full review »

For sure, it should offer customisation of data grids, which is not possible, as it seems to use some proprietary OCX control.

View full review »

Using SharePoint is difficult. It will fully use your system resources. 

View full review »

Co-authoring needs to be real time. View full review »

It is too heavy. MS should not have paid foreign coders dollars per each row of code. They wasted the stability and reliability in the end.

View full review »

We would like more security features, like automating. 

View full review »

• Links to Outlook and native storage of emails. 
• Emails stored now do not display metadata in native format.
• No good process to import emails from several users into a single comprehensive SP repository.
• The linkages to external record stores could be beefed up.

View full review »