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. Update the CSOM and REST APIs to allow email enabling of document libraries

    With CSOM you can currently set the needed RootFolder properties:

    rootFolder.Properties["vtiemailusesecurity"] = 1;
    rootFolder.Properties["vti
    emailsaveattachments"] = 1;
    rootFolder.Properties["vtiemailattachmentfolders"] = "subject";
    rootFolder.Properties["vti
    emailoverwrite"] = 1;

    but you can't update the EmailAlias of the parent List. The Rest API can't set the root folder properties or the EmailAlias.

    30 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  ·  Flag idea as inappropriate…  ·  Admin →

    We are moving to more towards the Groups inbox in the SharePoint Online to be the service for the emails. Storing emails in SharePoint libraries can cause certain challenges with the view limits etc. We are not looking to expose this capability using remote APIs. If you are using on-premises and would like to control these settings remotely, we would recommend to implement a custom web api for this specific usage.

  2. Expand CSOM code

    Expand CSOM code base so that SharePoint Online users are able to write the same code as on prem users.

    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  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input, but since this is too generic statement, item is closed. We are evolving CSOM based on the specific requests and scenarios provided from customers and partners. We are releasing new version of CSOM NuGet packages on monthly basis for SharePoint Online and keep on adding missing scenarios as part of the releases.

    Server side object model for SharePoint is massive and there are numerous areas which provide APIs in the farm level. Since CSOM is also used in SharePoint Online, we cannot provide this level of API reach with the CSOM side.

    We are addressing gaps in the site and site collection level APIs based on your input, so would suggest to provide input on missing capabilities and to include also the actual business scenario why the API is needed. This helps on prioritizing these requests in the future.

  3. Error in App Package (SPFX)

    I am getting an error in tutorial 3 of the SPFX. When adding the hello-world-webpart to the app catalog. Says "There were errors when validating the App Package. The package manifest doesn't contain a StartPage element in Properties." I have followed every instruction. Thank you

    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  ·  Flag idea as inappropriate…  ·  Admin →
  4. 103 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.

    If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.

  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.

    111 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  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add API that checks if user is in group

    Right now there is no API to check that. If you add a security group into a SharePoint group, there is no way to check if the current user is a part of the SharePoint group: The user is not listed in the group.Users and the SharePoint group is not listed in the user.Groups. The 3 APIs that allowed to do this in full trust code are missing from CSOM so we need an alternative.

    102 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 not looking into doing this operation on server side of SharePoint as it would require resolving the members based on Azure AD groups.

  7. Content type remote event receivers

    Remote event receivers can currently, in SharePoint Online, not be added to content types (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.contenttype_members.aspx). This makes it somehow tedious to catch events that are fired from items of a specific content type is added/updated/deleted. Having the possibility to add an event receiver to a content type would make this scenario easier to implement.

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

    This could be something which could be in the Microsoft Graph APIs, given the direction with Project Syntext and Topics, but no confirmation on the plans there.

  8. SharePoint APP with C#

    Make it possible to dev SharePoint Hosted Apps with C# (csom) just like JS.

    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  ·  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. Using C# based customizations in SharePoint Online in safe way was possible in isolated scenarios with Sandbox solutions, but this capability has been removed. SharePoint hosted apps are hosted in the SharePoint and there’s no way to provide code level isolation which would be required for these scenarios.

  9. Add the possibility to set the Owner when creating a SharePoint Group using REST API

    It is currently not possible to set the Owner of a SharePoint Group using REST API or maybe I don't have right syntax...

    89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. SP Designer 2016 release

    I think we need a new SPD release like a slipstream version, without 10+ updates and 2GB+ disk space requirements for the updates. It would be nice with a click2run installer which works if the Office 365 ProPlus (2016) already installed.

    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  ·  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 understand the value of SP Designer in older scenarios but are not planning to currently invest in the modernization of it for the SharePoint 2016 or SharePoint Online.

  11. 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  ·  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 through SP dev team. This falls more on the Windows server side enhancements and our team cannot, unfortunately, act on this as such. We do though appreciate your input and agree that TMG was a great product for a purpose in on-premise.

  12. New SharePoint Certifications

    I work in the Real World with SharePoint 2013 daily. You could call me a "PowerUser" and "FrontEnd SharePoint Programmer" Can you PLEASE offer (Starting with SharePoint 2016) A "SharePoint Certification Path that will actually be worth something? In large corporations only a very, very few will be allowed to use PowerShell, and set up Site Collections, and design server farms... You need SharePoint Certifications for the person who uses it in the office daily a "power user cert", and you need some that certify you on programming SharePoint using (JavaScript, HTML5, CSS3, jQuery, BootStrap, etc...) for those of us…

    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  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, this would not be however the right channel to provide feedback around the available certifications. Would suggest to provide this input to MS Learning by using different channels available from https://borntolearn.mslearn.net/. That way your input will reach the right audience.

  13. SharePoint Hosted APP with Code behind

    Allow SharePoint hosted APP to use code behind, keeping the same separation as provider hosted app (separated pool or some docker-like experience)

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

  14. NAPA supporting ECMAScript 2015 or Typescript for both on- and off-premise programming of event receivers

    Present programming of Remote Event Receivers is complicated and limited so farm deployed server-side Event receivers are used. Support of ECMAScript 2015 or Typescript is needed in a simple freestanding tool (NAPA?) for both on- and off-premise installations.

    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  ·  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. NAPA service is no longer supported and the models are moving more towards scenarios with web hooks and Azure functions.

  15. Worklflow 2013 should have MORE functionality than WF 2010

    8pproval Workflow functionality is limited. A ItemModertorStusChanged event reciver is missing. WF 2010 has more functionality and hence used instead of WF2013. Even with WF2010 it is tricky to get appovers names and dates into library columns. SharePoint Designer 2013 is unstable and may corrupt the system!

    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  ·  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. In SharePoint Online we are gradually moving towards Flow from the classic workflow scenarios. In on-premises workflow is absolutely supported and there should not be any corrupt issues. If that would be the case, it would be rather a bug than a new feature. We do understand the importance of the business processes support and are looking to further invest in this area also in future, but not using the classic concepts.

  16. ItemModertorStatusChanged event receiver

    ItemUpdated event receiver is a very rough async process that blocks SharePoint functionality heavily. It can't be empty since workflows communicate with SharePoint using it. My Suggestion is to introduce a ItemModertorStatusChanged event receiver. To obtain backwards comptibility, it should be a tick box when creating a workflow in SharePoint Designer to use ItemUpdated or ItemModertorStatusChanged event receiver.

    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  ·  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. Your suggestion does make sense but would require changes across multiple areas, where we are not currently planning to invest.

  17. Make the name of the current Composed Look a property of the Web object

    Currently there is no simple way to pro grammatically get/set the current Composed Look for a site. The Composed Looks list available from the Site Settings page shows all the looks available, but the only way to determine which one of them is the current one is to tediously compare every item in the list to the one with the name "current", which is inefficient and error prone because if there is a background image as part of the Composed Look, the value in the background image field is changed when the look is chosen by the user so the…

    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  ·  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 would absolutely help on the programmatic handling of the site configuration, but we are not currently looking to invest in this area of the branding elements.

  18. Programmatic way to configure search with CSOM

    There's currently no better way to configure search indexed and managed properties than export/import configuration. It's a huge pain when building search related apps and a black box, we need something better

    99 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.

    We are potentially looking into having Microsoft Graph API operations for the search configuration in the future, but we cannot currently share any ETA for this and capability will not be provided through classic CSOM APIs.

  19. Fix the REST API to return the value and not the Id when getting single value Managed Metadata field

    REST API should be fixed when getting single value Managed Metadata since it returns the Id instead of the actual value, which then requires another call to get the value. Without this you cannot show a list of items/docs with the single Managed Metadata value. Note that "Allow Multiple" Managed Metadata works fine as it returns a collection of actual values.

    For details see: http://sharepointificate.blogspot.com/2014/05/taxonomy-columns-sharepoint-2013-list.html

    159 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. SharePoint 2016 certification

    Please organize more competitions like #KnowItProveIt and improve certifications learning material availability. Waiting for 2016 certification launch.

    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  ·  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 can act from this system. Your feedback is though noted and bypassed to marketing for possible future competitions.

  • Don't see your idea?

Feedback and Knowledge Base