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

    162 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    131 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add --nobuild flag to gulp serve

    Observed behavior
    ---------------------
    When using a monorepo manager, like for example @microsoft/rush, the rush build command bundles all projects which are referenced in the monorepo - including SPFx projects.
    When running gulp serve in (one of) the SPFx project(s), the bundle gulp command rebuilds the project. This is an unnecessary step, which would be nice if we could disable.

    Proposed solution
    --------------------
    Add a --nobuild flag support to the gulp serve command so we can start the local web server without rebuilding the SPFx code.

    80 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  4. Extensions: Application Customizer get page all components data (List, Documents, Search etc..)

    Provide a way to get data about all components that present on page in ApplicationCustomizer like SearchBox, Search, Documents Library, Lists, Navigation bar etc.

    The idea is to have full control on user interaction with components.

    In example I want to make an additional action when user clicks on folder, file, list item, navigation item, search result item etc...

    Ideally to have access to domElement and data model of component.

    106 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    169 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow Site Collection App Catalog location be configurable

    We live in a tenant where we have over 25 different companies. When it comes to customizing and supporting the tenant catalog is too broad, but the site collection catalog adds support nightmares with syncing and managing the apps and installs in each one. It would be great if the site collection admin could choose an additional Site Collection app catalog to pull from. This would allow for us to manage company specific apps in a Company site collection catalog much like the tenant catalog while still getting site specific catalog items from the site collection catalog. In this model,…

    53 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  7. Create SPFx webparts inside or from another SPFx webpart or extension

    As described in https://github.com/SharePoint/sp-dev-docs/issues/3110

    Untill SPFx version 1.4.1 there was an option to use the ClientSideWebPartManager to create webparts from another webpart. Currently we are working some time already on a custom 'widgetzone' with an easy dragging and dropping grid layout (Muuri, https://haltu.github.io/muuri/), user zones and a lot of other awesome stuff which isn't supported by the default SharePoint grid. (which is off course understandable)

    Currently I am not seeing another path to make this possible, so for now we have to stick on the SPFx 1.4.1 release. I do understand this is something not many companies will encounter,…

    57 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  8. Ability to use App-Only calls to create modern sites

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

    342 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. SPFx Webpart - Have custom group in Modern Pages

    Currently there are no ways we can have a group created for custom SPFx webparts developed. We have to use the existing groups mentioned here, https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries#predefined-modern-groups. Need to have ability to have custom groups for Webparts

    45 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  10. More links to footer / fat footer

    It would be really nice to get more links to the footer to be able to create this kind of "fat footer". Current footer only allows 8 links/headers, but we would love to see footer where you:
    1. can choose the layout (columns/rows)
    2. can have header (styled/bolder/font size) with or without link and the add n-number or links below it.

    So something like this (3 columns x 2 rows example):

    HEADER1 | HEADER 2 | HEADER 3
    link1 link1 link1
    link2 link2 link2
    link3 link3 link3

    HEADER4 | HEADER 5 | HEADER 6
    link1 link1 link1
    link2 link2 link2 …

    22 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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…

    356 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  12. Ability to deploy MS Flow Definition through .sppkg, similiar to how we can provision list and libraries.

    The deployment of SPFx components along with associated list and attached flow can be done with-in a single package so that minimum exclusive configuration is required for any developed solution.

    51 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  13. Official documented Api needed to fetch modern Pages View count

    SharePoint modern pages Social bar View count apparently does not use Search Managed property ViewLifeTime or ViewsLifeTimeUniqueUsers. Fiddler traces shows that some Internal Apis are used to fetch modern pages social bar view count. It would great if Microsoft release Public documented API so that custom SPFx web parts/extension in need of modern page view count, could utilize the API

    49 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Create roledefinitions and groups from SiteDesign

    Please add functionality to create roledefinitions, create custom groups and assign roledefinitions to groups.

    11 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow certain parts of a Modern page to be hidden

    Outside of the standard areas of a Modern page that can be customized through apps (top placeholder, bottom placeholder, and web parts), we would love the ability to hide other parts of the page in order to achieve a customized look and feel.

    We are selectively hiding features such as:
    - Hub nav
    - "Composite header" which includes:
    - Site logo
    - Site title
    - Top nav
    - Follow/Share buttons
    - Search box

    We are relying on injecting override CSS with our Application Customizer Extension. This is not a reliable method as it's not supported. Certain html id values such…

    15 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    220 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 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.

  18. Office UI Fabric as web components

    Office UI Fabric is an awesome library, which contains a lot of components and UI elements. It's a great library to build UI experiences for SharePoint and Office 365.
    The downside is, that the most feature-rich version of the library built with React. If you want to use this library, you should use React without much options. There is Office UI Fabric JS out there, however it's not actively supported and developed as React one. Also it's difficult to reuse it in other frameworks. Office UI Fabric is must-have library in almost any SharePoint Framework solution.

    SharePoint Framework has framework-agnostic…

    57 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  19. spfx-extension should allow customization of a CommandSet for a page.

    We'd like to add additional buttons/commands to the CommandMenu when a user is viewing pages in our SharePoint online tenant. I thought creating an extension using spfx would allow this but it appears limited only to ListViews.

    9 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  20. API support for followed sites

    There's an undocumented API (https://tenant.sharepoint.com/_vti_bin/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

    122 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3 4 5 16 17
  • Don't see your idea?

Feedback and Knowledge Base