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.

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.

I suggest you ....

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add managed metadata term store operations to REST API

    Currently term store operations are only available via JSOM. It would be nice to see this added to the REST API as well.

    1,527 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Just a note to let you know that we’re building your suggestion now. We do apologize for the delay on getting this moving, but we are now working on exposing term store operation properly with REST API/Microsoft Graph. We will be covering any updates on the API status, before the actual release, in the SharePoint Dev community calls. Thanks, everyone for your input around this capability.

  2. Support .NET Core with CSOM

    Support .NET Core with CSOM

    1,155 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Provide CSOM and REST API for recurring calendar events

    There is no obvious way to get details about a recurring calendar events through the CSOM or REST API.

    When querying a calendar list only one item is returned for the calendar recurrence item. Only one field identifies this is a recurring item. the fOccurrence field is a boolean field.

    When using the server side object model, properties are available to expand recurring calendar events to get the individual recurring items.

    The only way to do this for client applications is to go back to using list.asmx which is not great and I'm not sure how long this will be…

    543 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Field Customizer Evolution: Forms, Quick Edit Mode

    Please, consider next enhancements to Field Customizer (and Modern List UI):
    1. implement modern Quick Edit mode
    2. Add "edit" mode to field customizer
    3. Make field customizers (both view and edit modes) applicable on forms, panels, quick edit mode, etc.

    521 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  5. When creating an SPFx Extension for a custom header, provide a configurable property that allows the composite header to be hidden

    When developing a SharePoint Framework Extension to display a custom header and/or footer, the SharePoint Composite Header can be very redundant to the custom header.

    The Composite Header (css classname is 'ms-compositeHeader'), is what SharePoint provide out of the box and includes the square site logo, site name and navigation.

    When creating your own custom header that includes all of these things and possibly more, the existence of the Composite Header is redundant and can be confusing for users...(Ex: redundant navigation).

    While CSS can be used to hide this, such a technique is not playing within the rules of only…

    363 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to use App-Only calls to create modern sites

    Provide support to create modern sites using App-Only calls.

    351 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. List.NavigateForFormsPages support in CSOM

    Currently it's not possible to set the List.NavigateForFormsPages property through CSOM as it is in the server API.

    321 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Extensions: Application Customizer - Additional Placeholders Requested

    Today we get PageHead & PageFooter... would like to have BEFORE/AFTER DIV's for `QuickLaunch` & `PlaceholderMain`

    Cross-reference:
    https://github.com/SharePoint/sp-dev-docs/issues/625

    291 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! We’re reviewing your suggestion. We are looking into closely on the input from the community around this and more specifically around the needed scenarios for the placeholders so that we could also potentially provide also specific customizers based on your requests – rather than just having an empty placeholder. Stay tuned!

  9. Allow publishing of content type hub content types via CSOM

    You cannot currently use CSOM to publish content types in a content type hub in O365. Right now you must imitate the page post back to do it.

    284 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. REST API citizenship! (surface, roadmap and change log)

    Besides the lack of detailed documentation around the REST API, given its importance as a major entry point for apps, it needs to be treated with more respect as a service offering. It's currently being updated in CUs and on SharePoint online without any notification of the changes being made (such as the $metadata endpoint appearing - was it in the August 2013 CU for on-prem?). We either need it to be released in a non-breaking change model (URL versioning such as the Twilio model), or messaging needs to be improved so we know when things are going to be…

    247 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thank you for your input. REST APIs are absolutely critical for the SharePoint Framework and for other customizations. We are working on improving the existing documentation and to ensure that you can more efficiently take advantage of the SharePoint REST APIs in your development.

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

    230 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Add support of SharePoint Framework solution packages to the AppSource Store

    The latest adjustments in the Microsoft Store police allows store's add-in to works with conjunction with another add-in that is available only from the provider. The solution package (.sppkg) build with SharePoint framework is not classified as 'add-in'. Thus, we cannot add add-in in the Store that depend on SPFx solution and there is no way of delivering customizations to the modern page.
    I can offered two options for solving this issue: 1) Adjustment of point 4.18 (https://docs.microsoft.com/en-us/office/dev/store/validation-policies#bk_4) from the Store policy to allows SPFx modifications 2) ApPSource store to start allowing .sppkg solution packages to be added

    229 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! We’re reviewing your suggestion. We are absolutely looking into making this happen sooner or later, so that you can more easily distribute your customizations for Office 365 customers.

  13. Provide the ability to write to Managed Metadata via app-only policy

    App-only policy in the SharePoint App Model is very restricted regarding Taxonomy operations. Even if an app is granted full control over the tenant, it lacks the permission to do anything but read operations on Taxonomy. Please provide the ability to create Groups, Term Sets and terms using app-only policy.

    194 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Extensions: Property Pane / SideBar Placeholder (Right)

    Please provide a well-known placeholder for the property pane or better a similar placeholder that let us create a sidebar.

    Having this ability would let us create powerful sidebars/toolbox extensions. This would be a super cool enhancement!

    187 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  15. Provide flag to enable\disable event firing from Remote Event Receivers

    Provide option to enable\disable event firing from Remote Event Receivers in SharePoint Online (CSOM/API) similar to SSOM - EventFiringEnabled

    177 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Provide clear support statement for SPFx with IE

    Right now there is no clear statement regarding the supportability of IE with SPFx. Since IE 11 is still supported for O365 and SharePoint Online, customers assume that it is supported with IE as well.
    Currently SPFx is impossible to use with IE because of performance issues and very bad memory leaks in IE. The more content and web parts are on a modern page the worse it gets. Thus, I suggest that you either fix those issues, or make a clear statement that SPFx is not supported with IE anymore. This would really help customers in making their decisions.

    174 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add information management policy management to CSOM

    Add support for managing information management policies, and especially retention policies, on content types and in libraries using CSOM. These are the objects largely in the Microsoft.Office.RecordsManagement.InformationPolicy assembly, such as the Policy, PolicyItem objects, etc.

    167 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. API for "Create Team from Template" with Site Design

    We can do templating on SharePoint, through Site Designs and Site Scripts. We now also have the option to "Create a Microsoft Teams from Template".
    Unfortunately, both do not work together. We either have a templated SharePoint site with a generic Teams or a templated Teams with generic SharePoint site.

    I would love the possibility to combine both templating options. Preferrably with an API from day 1.
    This would give us an end to end templating scenario, where we can create preconfigured Teams with a preconfigured SharePoint site. (In the future, hopefully with a preconfigured Planner etc as well ;)…

    162 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Allow extending SharePoint Admin Center using SPFx

    It would be nice to have the ability to extend some of the functionality in the SharePoint Admin Center. Specifically, the ability to deploy SharePoint Framework Web Parts into the Admin Center (via an App Page?). Currently, the community builds lots of SPFx Web Parts to fill the gaps in the Modern UX.

    Such Web Parts include:
    Theme Manager
    Site Design Studio/Manager

    These are SPFx solutions that have been built to help better manage our environments through a UX experience (as there isn't one via First Party). It would be nice to have a centralized location where these SPFx solutions…

    159 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. Import XsltListViewWebPart definition

    It is actually possible to import the definition of a XsltListViewWebPart via LimitedWebPartManager in CSOM. However, not all properties are supported. Important properties like XmlDefinition, Toolbar, ViewStyle, .. are being ignored. There's no possibility to have everything set correctly not even manipulating the backed view after importing the WebPart. Please read also this discussion:
    http://sharepoint.stackexchange.com/questions/90433/add-document-library-xsltlistviewwebpart-using-csom-or-web-services

    158 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3 4 5 17 18
  • Don't see your idea?

Feedback and Knowledge Base