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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Support .NET Core with CSOM

    Support .NET Core with CSOM

    1,672 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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,631 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Allow us to develop custom modern forms with custom edit experience

    We would like to be able to create an SPFx form and associate it with the List/Content type Disp, Edit, New form so that no matter how a user finds a list item (search, OOB list view, custom list view, etc) they see our custom form. Currently our only option is to create a completely disconnected experience in which we write a custom list view that points to custom form pages.

    Alternatively support field customizers with edit model to enable custom field editing experience.

    1,388 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    31 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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…

    602 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 →
  5. 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

    358 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

    310 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 →
  7. Allow to use Office UI Fabric Icons and other fonts as Command Set icons

    It would be great if we are able to use font icons instead of url to images for Command Set extensions buttons icons.
    This allow 3d party extensions look more aligned with 1st party (same style, same icon color)

    209 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 →
  8. 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!

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

    202 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Great news – We are currently working on documentation and guidance around this option.

    Usage of app@sharepoint is supported option to enable write operations for the Managed Metadata with app-only policy.

    Official documentation will be updated in upcoming days and we’ll close this item as that will happen. Thanks everyone for your input and persistence around this.

  10. Provide support for LivePersonaCard in 3rd-party solutions

    The LivePersonaCard control, which renders a user's full profile card, can be loaded in a SPFx solution with LoadByComponentId. However, it is unclear whether this will be supported in the future.

    The PnP reusable controls has a Pull Request to provide developers with a LivePersonaCard control, but it is currently in holding pattern until it can be confirmed that LivePersonaCard (and LoadByComponentId) will be supported.

    Please empower 3rd party developers to build rich user-aware SharePoint solutions by providing solution for the live persona card.

    Cross-reference: https://github.com/SharePoint/sp-dev-fx-controls-react/pull/353

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

    181 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 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 ;)…

    179 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  13. Line up list item pagination with REST API using $top and $skip

    Actually, the only way to paginate list items using the new REST APIs is to use __next property. There's no way to have a full working pagination using $top and $skip token as for any other REST call.
    See my comment here:
    http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72.aspx

    175 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. API support for followed sites

    There's an undocumented API (https://tenant.sharepoint.com/vtibin/homeapi.ashx/ ) to follow sites and query data around those concepts. For corporate intranet scenarios, we often want to present the data a different way, surfacing native SharePoint capabilities. In order to add a "follow" button on an SPFX web part, we'd need an API to access that.

    Related GitHub issue https://github.com/SharePoint/sp-dev-docs/issues/1689

    168 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. 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…

    165 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 →
  16. Improved API feedback around throttling

    Currently working with the API's for drive, graph, sharepoint are very difficult due to the throttling that can be encountered.

    Each api offers different guidance to avoid throttling. Example are:
    1) use a special user-agent header
    2) respect the retry-after header

    Speaking with microsoft representatives they instruct us to perform major api processing in off peak hours. Additionally tenant's can have hard locks placed on them.

    This request is to get better information around tenant usage returned in the API's.

    1) If a tenant is hard locked, tell us in a distinct message so that don't just hammer the requests…

    153 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. SPFx Key/Value Pair Properties that support Read/Write

    Provide a SharePoint Framework mechanism/API that allows for Site or Site Collection Read/Write of Key/Value pair properties for use in SPFx related configuration and customizations. Similar to how the property bag was used in classic.

    One use case is for storing configurable properties or even user personalization configurations written and read by an SPFx solution.

    This is one of many uses cases that would make this feature valuable, so in addition to your vote, please feel free to comment with additional ways in which this feature could provide additional value.

    150 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    thinking about it  ·  4 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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

    140 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 →
  19. Deactivate feature using site scripts and site designs.

    There is a verb to activate feature. Sometimes we require to deactivate features which are not required while creating sites. Can there be a separate verb for deactivating features? Also activateFeature but it works only at web level features. Can we have it extended to activate at site collection level?

    138 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Web parts: Allow them to be unit testable

    Trying to unit test web parts results in an error 'Cannot find module "@ms/sp-telemetry"'. This can be due to using SharePoint dependencies e.g. 'SPHttpClient' when creating the React component. This totally blocks being able to unit test web parts, please fix this.

    '@microsoft/sp-build-web' Seems to have been updated to remove the previously included testing modules, these do not have to be added back in, to resolve this issue, as we are able to find the most suitable testing modules to replace these.

    This issue has been reported by other users:
    https://github.com/SharePoint/sp-dev-docs/issues/526
    https://github.com/SharePoint/sp-dev-docs/issues/1076
    https://github.com/SharePoint/sp-dev-docs/issues/243

    132 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 17 18
  • Don't see your idea?

Feedback and Knowledge Base