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. I would like to embed an unsecure site page in my Sharepoint page

    I would like to embed an unsecure site page in my Sharepoint page

    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 →

    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 is actually a security feature in the browsers which are blocking mixing https and http requests on the same page and we cannot solve that for you in SharePoint side.

  2. Scrap "client side web parts". You can do all this with normal javascript so why complicate it?

    Scrap client side web parts are just HTML and JavaScript but require the developer to install configure and use a whole suite of old hat wannabe command line software. This is a step back to the ancient art of command line cryptic development. Really, even notepad more advance then this.

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

    We do acknowledge that moving from classic JavaScript development to more structural industry standard patterns require some changes in your development process, but we absolutely want to standardize and move SharePoint development models aligned with what other platforms do. This changes might feel huge and even step backward, but it’s highly beneficial for the larger customizations. With the SPFx and client-side web parts you also get centralized control and governance, which is not there with random embedded JavaScript models like with Script Editor web part. We absolutely understand your feedback, but looking into adoption numbers (metrics of usage) of the SPFx, there’s really no reasons for us to turn back from this journey which we started a few years back.

  3. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  4. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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

  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  6. It should be possible to "save teamsite as a template"

    To save a site as a template used to be so easy! But now you need to be a developer to do this for modern teamsites or communication sites! Why??

    1 vote
    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 →

    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.

    Classic save site as a template capability was designed in away which is no longer valid implementation style in the cloud.

    We are in a journey with the Site Designs and Site Scripts potentially provide end user driven export capabilities, which could be used to achieve similar outcome, but we are not planning to provide classic “Save site as a template” capability in the modern SharePoint sites.

  7. SharePoint 2016 certification

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

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  8. List-Library Settings Access via CSOM

    Provide extra capabilities to deal with SharePoint List settings using CSOM.

    Currently some of the properties of List are not accessible using CSOM.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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 need to have more specific requests around what’s needed. We would appreciate more specific properties which you need so that we can evaluate exposure of them one-by-one. Thx.

  9. Use Vue.js instead of standard rendering

    It would be great to be able to (easily) use something like Vue.js instead of hacking around with XSL or rearranging forms with jquery on PreRender() etc. This would be great for Views too.

    Something like Vue.js would also be relatively comprehensible for power business users, not just developers. It could be abstracted too, to make it even easier.

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

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not precisely something we’re planning to do right now. That refers more specifically on the vue.js usage. You can though use any JavaScript framework in SharePoint Framework implementation. We are looking to enable more flexibility on the list and library templating in future though.

  10. Not intuitive AT ALL. WHy so many steps to publish!?!!!

    Scrap the whole program and think through how to set up the functionality of Sharepoint. All I'm trying to do us publish my site and it is unnecessarily complicated. Nothing is intuitive, would take a month to tell you everything. Scrap all the code and rebuild the entire program from scratch...so it makes sense. Remove all of the "Overthinkers" from program engineering staff (have them work on something else). To many redundant, over thought out processes that make simple processes too complicated. I feel like I am forced to look through 10 drawers of beautifully detailed knives and I desperately…

    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 →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, there was no concrete or actionable input on this one.

  11. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  12. Foooooooopoooooooooole bot

    Project bizines teknolezhi and abar clencher and abar news
    a ND وقطب بزرگ اطلاعات از تمام شاخه ها و رشته ها

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Get-PnpTenantSite Enhancements

    Get-PnPTenantSite -Detailed -IncludeOneDriveSites
    We would like to have the following:
    • we would like to be able to target only onedrive sites and/or group sites
    • we would like the report to run quickly as per the GUI report in the admin console - that seems to run a similar query in about 2 min.
    • we would like a report to show all onedrives / groups / sites created after date

    1 vote
    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 →

    Thank you for your input around the SharePoint PnP PowerShell. PnP CommandSets are however not part of the official product, so we support and have a discussion around them in the GitHub. In this case, would suggest creating a new entry to the issue list in the PnP-PowerShell repository at https://github.com/SharePoint/pnp-powershell/issues with these details. Asks are understandable and absolutely reasonable. Do also remember that PnP effort is dependent on the community contributions, so we cannot guarantee on the timelines for addressing any requests.

    Thx for your suggestion and time taken for providing us your input.

  14. alan

    edfg

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

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not detailed enough for us to perform any action actions.

  15. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  16. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Reverting to modern theme

    Hi,

    I changed a team site them to classic in SharePoint Online. I cannot find a way to revert back to modern look, I'm currently stuck with the classic look.

    1 vote
    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 →
  18. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  19. Cannot resolve schema file path in manifest.json using SPFx.

    When I create a new SPFx webpart, "$schema" path is wrong in WebPart.manifest.json. It must be "client-side-component-manifest.schema.json", but current is "clientSideComponentManifestSchema.json".

    1 vote
    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 →

    Thx for submitting this. This is clearly a bug and should have been already addressed with the v1.2 release. In future, if you have seen any specific bugs or random issues, we would recommend using https://github.com/SharePoint/sp-dev-docs/issues issue list to start a discussion with SharePoint engineering. Uservoice is mainly for the new feature requests and possible issues can, unfortunately, get hidden here. Thx anyway for the submission and please let us know in the issue list if you still have any questions.

  20. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  • Don't see your idea?

Feedback and Knowledge Base