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. Add support to create list / document library based on custom template to REST API

    If I save list as template I cannot use this template to create new list via REST API because it does not accept template name as input parameter: This is possible in CSOM by passing ListTemplate parameter (https://sharepoint.stackexchange.com/questions/255947/creating-a-document-library-from-custom-template-with-folder-structure-inside-us)

    In REST it is possible just to pass ListTemplateTypeKind as BaseTemplate parameter and there is no parameter for custom template name so it is not possible to create new list/library based on custom template (https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/working-with-lists-and-list-items-with-rest)

    59 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 enabling this scenario with modern list templates and Microsoft Graph, but are not planning to expose this in CSOM or in REST APIs… and with old classic list templates.

  2. Add modern webservice API functionality to supported API as graph

    There are two modern webservices used in SharePoint for getting followed sites, frequented sites, news posts, etc for the current user. As asked about on Github (https://github.com/SharePoint/sp-dev-docs/issues/1689) and as mentioned in this uservoice (https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/34075903-api-support-for-followed-sties) a bunch of folks would like to have some kind of official support/usage for this. If this is not possible, we would like to ask to add these functions to Graph / SharePoint REST

    74 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.

    Followed sites is already supported in Microsoft Graph API.

    Frequent and news pots are not, but are being looked for, but as this item is bundling numerous items, we cannot track them separately. Those items are however looked for. To enable specific item tracking, please submit items one-by-one.

  3. Add bulk update custom user properties to on-premises

    Please add bulk update custom user properties to on-premises so that we can eliminate FIM/MIM and streamline the process of getting HR and other external data into user profile properties in SharePoint on-premises

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Open source the CSOM

    Please open source the CSOM code. This would allow community to add features like throttle support, .net core and others. Microsoft could update it from time to time to add new support for new APIs etc... also.

    It would allow the community to port it to platforms and runtimes that MS are not yet able commit time to doing.

    24 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 still committed on providing .NET Standard version of the CSOM, but are not planning to change the engineering processes to have CSOM released as an open-source version.

    This change would require significant changes on how the engineering processes work and would have impact on the agility of providing capabilities through CSOM and REST APIs. As we are investing heavily on the Microsoft Graph API surface, we are not planning to allocate resources to this work.

  5. Scrap "client side web parts". You can do all this with normal javascript so why complicate it?

    Scrap client side web parts are just HTML and JavaScript but require the developer to install configure and use a whole suite of old hat wannabe command line software. This is a step back to the ancient art of command line cryptic development. Really, even notepad more advance then this.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We do acknowledge that moving from classic JavaScript development to more structural industry standard patterns require some changes in your development process, but we absolutely want to standardize and move SharePoint development models aligned with what other platforms do. This changes might feel huge and even step backward, but it’s highly beneficial for the larger customizations. With the SPFx and client-side web parts you also get centralized control and governance, which is not there with random embedded JavaScript models like with Script Editor web part. We absolutely understand your feedback, but looking into adoption numbers (metrics of usage) of the SPFx, there’s really no reasons for us to turn back from this journey which we started a few years back.

  6. new-pnpsite

    Allow creation of modern sites using the cmdlet "New-PnPSite" using an Azure App ID. Currently this errors with "App-Only is currently not supported".

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    App-only creation fo modern sites are not currently supported, so New-PnPSite cmdlet cannot also do this. This cannot be solved until the native API supports app-only, so we would rather recommend updating the request towards supporting this capability in general, not only specific with new-pnpsite.

  7. Add CSOM support for Document Set settings on content type

    Please consider adding support for setting/retrieving doucment set properties on a content type. We need to be able to set properties like Shared columns, Welcome page and Welcome page view on the document set.

    162 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 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.

  9. 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…)
  10. 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…)
  11. 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.

  12. 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…)
  13. 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…)
  14. 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…)
  15. 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.

  16. 103 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.

    If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.

  17. Add API that checks if user is in group

    Right now there is no API to check that. If you add a security group into a SharePoint group, there is no way to check if the current user is a part of the SharePoint group: The user is not listed in the group.Users and the SharePoint group is not listed in the user.Groups. The 3 APIs that allowed to do this in full trust code are missing from CSOM so we need an alternative.

    102 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 not looking into doing this operation on server side of SharePoint as it would require resolving the members based on Azure AD groups.

  18. Content type remote event receivers

    Remote event receivers can currently, in SharePoint Online, not be added to content types (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.contenttype_members.aspx). This makes it somehow tedious to catch events that are fired from items of a specific content type is added/updated/deleted. Having the possibility to add an event receiver to a content type would make this scenario easier to implement.

    97 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.

    This could be something which could be in the Microsoft Graph APIs, given the direction with Project Syntext and Topics, but no confirmation on the plans there.

  19. Add the possibility to set the Owner when creating a SharePoint Group using REST API

    It is currently not possible to set the Owner of a SharePoint Group using REST API or maybe I don't have right syntax...

    89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Programmatic way to configure search with CSOM

    There's currently no better way to configure search indexed and managed properties than export/import configuration. It's a huge pain when building search related apps and a black box, we need something better

    99 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.

    We are potentially looking into having Microsoft Graph API operations for the search configuration in the future, but we cannot currently share any ETA for this and capability will not be provided through classic CSOM APIs.

← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base