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. 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 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…)
  5. 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.

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

  7. Reverting to modern theme

    Hi,

    I changed a team site them to classic in SharePoint Online. I cannot find a way to revert back to modern look, I'm currently stuck with the classic look.

    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  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  8. alan

    edfg

    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 detailed enough for us to perform any action actions.

  9. nothing

    Update framework

    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 →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not detailed enough for us to perform any action actions.

  10. I would like to embed an unsecure site page in my Sharepoint page

    I would like to embed an unsecure site page in my Sharepoint page

    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, it’s not something we’re planning to do right now.

    This is actually a security feature in the browsers which are blocking mixing https and http requests on the same page and we cannot solve that for you in SharePoint side.

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

  12. 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 →
  13. 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.

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

  15. It should be possible to "save teamsite as a template"

    To save a site as a template used to be so easy! But now you need to be a developer to do this for modern teamsites or communication sites! Why??

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

    Classic save site as a template capability was designed in away which is no longer valid implementation style in the cloud.

    We are in a journey with the Site Designs and Site Scripts potentially provide end user driven export capabilities, which could be used to achieve similar outcome, but we are not planning to provide classic “Save site as a template” capability in the modern SharePoint sites.

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

  17. [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…

  18. 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…)
  19. Share the code for the OOB modern Webparts

    Please can you share the code for all the OOB webparts on the github SPFX repo?
    Developers can then use these as examples of the methodology and improve upon them. An important factor would be related to presentation as those not familiar with react have to understand how this works.

    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 Documentation  ·  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 however review and provide input on the SharePoint PnP / Dev community activities and we do suggest on having a look on the activities and open-source projects on this side. See http://aka.ms/sppnp

    We are not right now at least planning to share our code as such but will be using SP PnP as a channel to provide patterns and practices for developer activities.

  20. SharePoint online Templates

    How about having the ability to save templates for SharePoint content, sites and list, regardless if SharePoint is set publish or not.

    3 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 Add-ins  ·  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 as many of the templates simply cannot be saved as a template as the capability technically cannot be supported.

    We are looking into having native support for saving Site Designs from the existing modern sites and there is PowerShell / API level support for templating through SharePoint PnP (open-source) initiatives.

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

Feedback and Knowledge Base