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. 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,576 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Support .NET Core with CSOM

    Support .NET Core with CSOM

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

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

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

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

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

    161 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Prior to Modern Pages, we used to connect web parts to send data from one part to another. E.g., select a document from a document library w

    Prior to Modern Pages, we used to connect web parts to send data from one part to another. E.g., select a document from a document library and display a preview of it in a Page Viewer web part. It's so annoying that SharePoint no longer has that feature. Modern Pages seem to be less Modern than they should be. It's like a beginner's web page instead of something you can actually do real work in.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    You should be happy to hear that we are working on this capability and it’s already supported with 3rd party web parts. More details will be released using our guidance and social media channels during the first quarter of 2019.

  • Don't see your idea?

Feedback and Knowledge Base