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

  2. 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 →
  3. 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 →
  4. 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.

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

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

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

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

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

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

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

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

  13. Simplify CSOM for using w/Angular/Backbone/Sencha - for Real World Scenarios, use CSS than JS, overcome OData constraints (oriented to CRUD)

    All the things are related to SharePoint Online development:


    1. SharePoint CSOM model is too complex for using with leading technologies, such as AngularJS, Backbone, Sencha ExtJS and so on. And there is a lack of documentation for "built-in" CSOM/SharePoint JS API function, for example user name extraction from user field). You have to google a lot to find if anyone has found any solution how to solve it.


    2. There are lots of useless JavaScript that does a lot of functionality/processing that is available using pure CSS or native browser functionality (I'm not talking about HTML5 and CSS3 right now). For…

    89 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, we can’t really create unfortunately actionable items from this large list of requests. There are extremely valuable items in the text which we would love to get submitted as individual items, so that we can truly triage and address the challenges.

    What we are looking is specific actionable items in UserVoice for specific gaps. We can’t unfortunately address collection of items in single efficiently, since improvements will be also released gradually and not as a big bang.

    Your input has been absolutely acknowledged, but we’ll have to close this one and would rather request seeing if the specific items or topics have been already submitted as a one-by-one submissions or submit new items.

  14. Provide the ability to identify features that are deactivated using CSOM

    It's currently possible to identify the features that are activated at the Site and Web level using CSOM, it isn't however possible to determine which features are present but not activated using CSOM. It would be great if this feature could be added!

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

  15. SharePoint App/Add-In Development for On Premises - include Workflows as Integrated within the App like you allow in Office 365

    Today, when I create a new SharePoint Add-In (App), I cannot include the SharePoint 2013 workflow within my app (On Premises only). I see there is a workaround for Office 365 Add-Ins, but we are not in the cloud yet. I also see Visual Studio 2015 has a setting for Integrated App (true/false), but not sure if this will work on premises yet (will try this out soon). I need the ability to include my custom SharePoint 2013 Declarative workflow as part of my custom add-in (app) for on premises. Bill Baer stated that my app will work the same…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Fix CSOM SiteCollection Creation providing Lcid

    When creating Site Collections through CSOM and providing an LCID. (For example 2067) an exception is thrown.

    [Quote]
    SiteCreationProperties.Template\r\nParameter name: Specified value is not supported for the SiteCreationProperties.Template parameter." is thrown at ExecuteQuery();
    [/Quote]

    The Exception is also not pointing in the right direction.
    1) It should be possible to create Site Collections providing the LCID
    2) When an Invalid Lcid is passed, the exception should point in the right direction.

    93 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Add support for sandbox solutions upload and activation in CSOM

    You have now announced that no-code sandbox solutions are supported after all. Then you should logically (and quickly) add support for uploading and activating sandbox solutions in the CSOM.

    If you at MS are planning to NOT add that support in the CSOM, you should reconsider because:


    1. Customers want to use Save Site As Template. For example, they want to save an OOB team site with some extra lists into a .wsp (=sandbox solution). Then we need to be able to programmatically upload and activate that in a new site collection. Now not possible in the CSOM (except with HTTP…

    165 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, it’s not something we’re planning to do right now.

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

  19. Provide the JSOM API to create SharePoint Site Collections (Tenant Object as CSOM C# has)

    In the CSOM C# object model we have the Tenant object that allow us to create Site Collections and do other operations over the Tenant. There is a lack of this piece of the API in the JSOM JavaScript object model. Please extend the JavaScript API with this functionality.

    BTW - I would suggest to add a new category as "JSOM Gaps"

    106 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 looking into possibly opening up admin REST APIs in the future, but do not have exact timeline for this right now.

  20. Expose search managed properties and result sources through REST and CSOM.

    This will enable developers to build richer property searching applications.

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

    As search is also moving away from the SharePoint to be a service cross Office 365, these APIs are no longer relevant through the SharePoint platform.

  • Don't see your idea?

Feedback and Knowledge Base