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

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

  3. Update SharePoint 2019 with the latest SPFx Drop

    Update SharePoint 2019 with the latest SPFx Drop. Most of the SharePoint Customers still have an OnPremises Farm. If you want customers to adopt this pattern it must be available in both environments. Staying on drop 1.4.1 in SP 2019 is the death of SPFx

    68 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Let me provide some additional context of this to explain why we cannot do this. In short, it’s not just about supported SharePoint Framework version, it’s about dependency on all out-of-the-box web parts and UX implementation.

    We would love to provide updated SPFx support for SP2019, but this is unfortunately impossible due the server-side dependencies and restriction.
    SharePoint 2019 was created by forking SharePoint Online code while back. At the time the used SharePoint Framework for the out-of-the-box web parts and UX layer was SPFx 1.4.x with the related server-side dependencies, which is then setting the used SPFx version even for now. As SharePoint 2019 is using more than 2 years older out-of-the-box UX layer than SharePoint Online, there is unfortunately now way for us…

  4. Add CSOM Method to Release File Locks

    We need the ability to unlock files via CSOM (with an App Only token) via the SPFile.ReleaseLock method. The flow would be similar to what we can accomplish on-prem:

    $web = Get-SPWeb http://webUrl
    $list = $web.Lists['Documents']
    $item = $list.Items[0]
    $lockId = $item.File.LockId
    $item.File.ReleaseLock($lockId)

    This prevents needing to open support cases for long-lived lock files in scenarios where the end user is having connectivity issues causing long exclusive locks to be created, potentially locking the end user out of their own file.

    81 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 →
  5. [MODERN PAGES] Add web for adding CSS and Javascript on Sharepoint Modern Pages

    Add support for adding CSS and Javascript on Sharepoint Modern Pages.

    Here is an example implementation on github, but certainly my organisation will not implement it (straight out of github project), unless Microsoft can push this capability to Sharepoint:
    https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor

    Please see this image for more details, where I am trying to suggest adding a new Web Part for Scripts+CSS:
    https://i.imgur.com/dtpIzdY.png

    This capability is available in old Sharepoint Pages, so hopefully it should be easy to push in Modern Pages (which I really like to use).

    Regards

    160 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  ·  Site Scripts & Site Designs  ·  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.

    Challenge of allowing site owners to embed scripts or CSS is huge security risks which that model enables without centralized coordination/approval at tenant level.

    This model was widely adopted in the classic SharePoint from the site owner perspective, but it also caused clear security risks for any tenant where the script embedding was enabled.

    SharePoint Framework was designed to address this security concern by only enabling embedding scripts to the modern pages if this is enabled in tenant level by installing a solution which allows that. If this capability is needed – you can absolutely develop your own script embedding web part, but Microsoft is not planning to enable this security issue in modern SharePoint.

    We are not also planning to enable embedding CSS styles…

  6. Enterprise Deployment of SharePoint Framework Apps in an On Premise Platform

    There is currently no good way to do enterprise level automated deployments of an SPFX addin into a SharePoint 2016 on Premise environment..

    Consider a case where there are 1000 site collections and we would need to deploy an SPFX app to all sites automatically. Currently there is no way to perform this deployment in an automated fashion. It is not possible through powershell, csom, c# or in an administrative UI.

    Having this ability would solve a large hole in capabilities with SharePoint Framework

    148 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    This capability might be enabled in the upcoming vNext on-premises release, but as we are not planning to backport this new feature to SharePoint 2016 level, as requested in the UserVoice entry, we are closing this request.

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

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

  10. 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…)
  11. 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  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Closing as this is not an enhancement. It’s a potential issue in existing capability and reporting these in UserVoice is not the right way to get things sorted out.

  12. Not intuitive AT ALL. WHy so many steps to publish!?!!!

    Scrap the whole program and think through how to set up the functionality of Sharepoint. All I'm trying to do us publish my site and it is unnecessarily complicated. Nothing is intuitive, would take a month to tell you everything. Scrap all the code and rebuild the entire program from scratch...so it makes sense. Remove all of the "Overthinkers" from program engineering staff (have them work on something else). To many redundant, over thought out processes that make simple processes too complicated. I feel like I am forced to look through 10 drawers of beautifully detailed knives and I desperately…

    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 →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, there was no concrete or actionable input on this one.

  13. Extensions: Support Development in Local Workbench

    Today, application extensions in SPFx (command sets, application customizers & field customizers) can't be tested within either the local or SharePoint Online hosted workbench. This is a bummer and a big step backwards to such a cool aspect to the development story with SPFx.

    I get that you need a list to work with, but at a minimum, the workbench could have a static list with static data and no other functionality for us to test the customizations on.

    My wish is that Microsoft adds support to the workbench for extensions before GA.

    105 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 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 have investigated this option and have concluded that only decent development experience for the SPFx extensions can be provided within the live sites, as instructed in the extension tutorials.

    As we are planning to deprecate the local workbench starting with the version 1.12.1, we are not looking into provide this feature in future.

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

  15. Provide VSTS Build Template for SPFX

    Add a VSTS Build Template to VSTS. So it is easy to build a spfx app with all needed steps and the tooling in the right version.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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…)
  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. 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…)
  19. 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…)
  20. 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.

← Previous 1 3 4 5
  • Don't see your idea?

Feedback and Knowledge Base