SharePoint
Feedback by UserVoice

SharePoint Dev Platform

Welcome! This is your place to suggest ideas or vote for ideas for improving the SharePoint Dev Platform.

Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more

How to submit a new idea


  1. Check if it's already been suggested. If it has, vote for it.
  2. If it's new, submit it in 50 words or less.
  3. Gather support!
  4. If your idea receives over 100 votes in 90 days, we will respond.
    If not, we will close it.



Want to engage further? Please visit the SharePoint Community

Note: we have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. SharePoint 2016 On Premise _api/Web/Lists('listID')/subscriptions support (WebHooks)

    Please provide subscriptions API (_api/Web/Lists('listID')/subscriptions support (WebHooks)) SharePoint 2016 On-Premise which helps in webhooks, desktop notifications, mobile/push notifications and cross platform notifications to name a few.

    233 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    Webhook are supported in SharePoint Online and in SharePoint 2019 and even thought they’d absolutely also provide additional value on older versions, we cannot provide them without significant platform changes, which cannot be justified for the older versions.

  2. Add CSOM API to choose content database and quota when creating site collections

    In the April 2014 Cumulative Update for SharePoint 2013 (released on 7th of May 2014) you published the possibility to create site collections remotely via the CSOM API.

    Till today it's not possible to choose a desired content database where the site collection should be stored in or to configure a quota template.

    Senior Program Manager Vesa Juvonen from Microsoft wrote a detailed blog article about this topic and received a broad response from the community where many people need these missing features.

    See here: https://blogs.msdn.microsoft.com/vesku/2014/06/09/provisioning-site-collections-using-sp-app-model-in-on-premises-with-just-csom/

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Allow non-Typescript option in generator-sharepoint

    Although Typescript is perfectly fine, some organizations do not want to spend time acclimating their processes around it when they are comfortable writing in es2015 with webpack and normal linting.

    Some MS Pros even take it out after generating new projects! https://medium.com/@Mizzle__Mo/replace-typescript-with-es2015-for-sharepoint-framework-applications-4385d9071c4c

    It would be great if this could be an option in the generator-sharepoint. I'd be happy to venture a PR if you were to make the generator available on github.

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    We consider the TypeScript as the de-facto model for SharePoint Framework and you can absolutely use normal JavaScript functions in TypeScript, so there’s no challenges to use existing code with these solutions.

  4. Combining different extension Types

    Right now SharePoint Framework Extensions support three different types of extensions: ApplicationCustomizers, FieldCustomizers and CommandSets . Can we combine two extensions under one project. Example: Based on selected List items in the list, do some customization in the header bar using Application Customizer. Please suggest.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    This is absolutely supported and you can have as many extensions or web parts in single solution talking between each other. There are numerous options for the components to communicate with each other. One of such options is demonstrated in following sample in SharePoint GitHub – https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-rxjs-event-emitter. Since this is not really a new feature request, we will close the issue. Would suggest having questions and discussions in StackExchange, GitHub or in SP Tech Community.

  5. Need expansion of the number of characters that can be used in a REST Call from SharePoint Designer Call Action

    The number of characters available before the REST Call returns BadRequest is much too low. This is especially true when using SharePoint Designer Call action to copy a document from one library to another. Another option would be to configure the call for copyTo to use parameters so that the entire call is not required to be in one URL, instead the parameters could be added to a the parameter dictionary

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Cannot resolve schema file path in manifest.json using SPFx.

    When I create a new SPFx webpart, "$schema" path is wrong in WebPart.manifest.json. It must be "client-side-component-manifest.schema.json", but current is "clientSideComponentManifestSchema.json".

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thx for submitting this. This is clearly a bug and should have been already addressed with the v1.2 release. In future, if you have seen any specific bugs or random issues, we would recommend using https://github.com/SharePoint/sp-dev-docs/issues issue list to start a discussion with SharePoint engineering. Uservoice is mainly for the new feature requests and possible issues can, unfortunately, get hidden here. Thx anyway for the submission and please let us know in the issue list if you still have any questions.

  7. List-Library Settings Access via CSOM

    Provide extra capabilities to deal with SharePoint List settings using CSOM.

    Currently some of the properties of List are not accessible using CSOM.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, we need to have more specific requests around what’s needed. We would appreciate more specific properties which you need so that we can evaluate exposure of them one-by-one. Thx.

  8. Get-PnpTenantSite Enhancements

    Get-PnPTenantSite -Detailed -IncludeOneDriveSites
    We would like to have the following:
    • we would like to be able to target only onedrive sites and/or group sites
    • we would like the report to run quickly as per the GUI report in the admin console - that seems to run a similar query in about 2 min.
    • we would like a report to show all onedrives / groups / sites created after date

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input around the SharePoint PnP PowerShell. PnP CommandSets are however not part of the official product, so we support and have a discussion around them in the GitHub. In this case, would suggest creating a new entry to the issue list in the PnP-PowerShell repository at https://github.com/SharePoint/pnp-powershell/issues with these details. Asks are understandable and absolutely reasonable. Do also remember that PnP effort is dependent on the community contributions, so we cannot guarantee on the timelines for addressing any requests.

    Thx for your suggestion and time taken for providing us your input.

  9. Foooooooopoooooooooole bot

    Project bizines teknolezhi and abar clencher and abar news
    a ND وقطب بزرگ اطلاعات از تمام شاخه ها و رشته ها

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. A30357714

    A30357714

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Add-ins  ·  Flag idea as inappropriate…  ·  Admin →
  11. Deploy Radzen

    Is it posible to deploy to Sharepoint a http://www.radzen.com/ app likewise lightswitch used to? Radzen is a rapid application development solution for Angular 2.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Add-ins  ·  Flag idea as inappropriate…  ·  Admin →
  12. Enable saving sites that contain SPFx web parts as templates

    Creating site templates that include preconfigured web parts on the landing page is a common requirement. We can add and configure classic OOB web parts on a landing page and save the site as a template, and we can do script injection customisations and save the site as a template. However, if a site includes an SPFx web part, we get the error message:

    "Sorry, this site can't be saved as a template. It contains apps that don't work in templates"

    This is currently a blocker in an area where a SharePoint Framework approach would otherwise be ideal.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    We do recommend having a look at the remote provisioning patterns (Site Designs or PnP Provisioning) which are future proof as the existing old save-site-as-a-template is not really something we recommend to be used as such.

  13. Need a telephone number to learn how to repair smoke alarm

    Need telephone number to Kidde for troubleshooting smoke alarm.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. Use Vue.js instead of standard rendering

    It would be great to be able to (easily) use something like Vue.js instead of hacking around with XSL or rearranging forms with jquery on PreRender() etc. This would be great for Views too.

    Something like Vue.js would also be relatively comprehensible for power business users, not just developers. It could be abstracted too, to make it even easier.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not precisely something we’re planning to do right now. That refers more specifically on the vue.js usage. You can though use any JavaScript framework in SharePoint Framework implementation. We are looking to enable more flexibility on the list and library templating in future though.

  15. QuickLinks property of UserProfile is not available through CSOM/REST, need to have it!!

    We are writing custom service for replacing existing SharePoint ASMX web services with CSOM/REST APIs as part of Infopath remediation for our organization. Currently, there is a method “GetUserLinks” of User Profile service(asmx) which returns group of Quick Links for a given User Profile.

    We tried getting “QuickLinks” data via CSOM as well as REST API and though the property “QuickLinks” is present in the properties array, data against it is returned as an empty string. We are able to get values of other Properties like Department, Title etc. but only Quick Links is returned as Empty string.

    To eliminate…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. CSOM/REST - "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).

    Some list/library settings are available via CSOM. Others are available via the list property bag (although that approach is not desirable). However, there are even other advanced settings that don't appear to be accessible (read or write) via CSOM/REST. In particular, the advanced settings for "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).

    I'm looking at SharePoint 2013 when trying to do this, but I suspect the same problem occurs for SharePoint Online and SharePoint 2016.

    86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Add Web.Recycle method to CSOM

    The Web class in the CSOM lacks the ability to send a web to the recycle bin. Currently it's only possible to delete a web by using Web.DeleteObject() which makes restoring from recycle bin impossible.

    Please consider adding a Recycle() method to the Web class.

    156 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    We are looking into potentially to have this in the Microsoft Graph API surface. We have noted this ask in the feature backlog for Graph.

  18. Update the CSOM and REST APIs to allow email enabling of document libraries

    With CSOM you can currently set the needed RootFolder properties:

    rootFolder.Properties["vtiemailusesecurity"] = 1;
    rootFolder.Properties["vti
    emailsaveattachments"] = 1;
    rootFolder.Properties["vtiemailattachmentfolders"] = "subject";
    rootFolder.Properties["vti
    emailoverwrite"] = 1;

    but you can't update the EmailAlias of the parent List. The Rest API can't set the root folder properties or the EmailAlias.

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are moving to more towards the Groups inbox in the SharePoint Online to be the service for the emails. Storing emails in SharePoint libraries can cause certain challenges with the view limits etc. We are not looking to expose this capability using remote APIs. If you are using on-premises and would like to control these settings remotely, we would recommend to implement a custom web api for this specific usage.

  19. Expand CSOM code

    Expand CSOM code base so that SharePoint Online users are able to write the same code as on prem users.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input, but since this is too generic statement, item is closed. We are evolving CSOM based on the specific requests and scenarios provided from customers and partners. We are releasing new version of CSOM NuGet packages on monthly basis for SharePoint Online and keep on adding missing scenarios as part of the releases.

    Server side object model for SharePoint is massive and there are numerous areas which provide APIs in the farm level. Since CSOM is also used in SharePoint Online, we cannot provide this level of API reach with the CSOM side.

    We are addressing gaps in the site and site collection level APIs based on your input, so would suggest to provide input on missing capabilities and to include also the actual business scenario why the API is needed. This helps on prioritizing these requests in the future.

  20. Error in App Package (SPFX)

    I am getting an error in tutorial 3 of the SPFX. When adding the hello-world-webpart to the app catalog. Says "There were errors when validating the App Package. The package manifest doesn't contain a StartPage element in Properties." I have followed every instruction. Thank you

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base