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

    180 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    We have now provided explicitly supportability statement for the IE 11 in the context of SharePoint Online at following location: https://support.office.com/en-us/article/which-browsers-work-with-office-for-the-web-ad1303e0-a318-47aa-b409-d3a5eb44e452?ui=en-US&rs=en-US&ad=US

    “Modern pages, lists and libraries on SharePoint Online are only supported in Internet Explorer 11 when Document mode is set to Internet Explorer 11”

    Other browser modes are unfortunately not using modern web technologies and are not supported as such.

    If you find any issues on the SharePoint Framework capabilities with IE 11 which is in the IE 11 mode, please open an issue at http://aka.ms/spdev-issues with sufficient details, so that we can provide support for your issue.

    Hopefully that provides the needed clarity on the situation.

  2. Ability to use App-Only calls to create modern sites

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

    382 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Microsoft 365 Learning Pathways: Add MFA Support

    Please add support for Multi Factor Authentication (MFA) with Microsoft 365 Learning Pathways (https://github.com/pnp/custom-learning-office-365). Specifically, update M365lpConfiguration.ps1 (https://github.com/pnp/custom-learning-office-365/blob/master/webpart/M365lpConfiguration.ps1) with a Switch parameter to use MFA (-UseMfa). When the switch is provided, use the -UseWebLogin parameter with Connect-PnPOnline instead the -Credentials parameter. Also, use Parameter Sets to only require the $Credentials object (and ask for them if not supplied) when the MFA switch is not used.

    Do the same with TelemetryOptOut.ps1 (https://github.com/pnp/custom-learning-office-365/blob/master/webpart/TelemetryOptOut.ps1)

    2 votes
    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 →
  4. Connect-PNPOnline using local certificate without PFX

    When deploying to azure, we are using the app-only pattern where we basically connect to Azure AD using an AppID and a local non-exportable certificate. When we initially created the certificate, we stored the private key of the certificate (pfx) in the AAD application key credentials and leaved the public key in the local certificates store.

    This pattern is perfect because you don't have to carry around a PFX file or hash, the only way you can connect to Azure AD is by being on the actual server which has the local certificate installed and you can't export the certificate,…

    3 votes
    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 →
  5. TypeScript is way out of date - bottomline - if your going to go open source... then go open source and keep up to date with the industry.

    TypeScript 2.4..... all of the major UI frameworks are in the Industry of UX are rocking 2.8 or higher, even 3. MS you have to stay ontop of this or SPFX will die on the vine.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  6. Remove pop-up requirement for Graph API SPFx web parts

    Graph API web parts have a huge amount of potential for SPFx web parts and extensions. The preview version requires pop-ups which are not user friendly. In some environments pop-ups will be blocked by group policy. This is a ADAL.JS dependency but moving forwards it would be a backwards step to require pop-ups and make SharePoint less user friendly again. Vote for this and lets make MS move this forwards in the right direction.

    94 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    We are happy to update you on significant changes with this capability as part of the SharePoint Framework 1.6 release, which technically removes the requirement of the popup.

    As this capability is using adal.js under the hood (only GA capability in JS for Azure AD), there are still some edge scenarios where the popup might happen, so solution is not quite perfect due to the limitations in the AAD side, but it’s the best possible implementation and in normal scenarios you will not see any popups when accessing Graph information.

  7. Harden PnP Provisioning Service for known pre-requisite failures

    There are a handful of PnP Provisioning service pre-requisites that are required (tenant level permissions, app catalog, access to app catalog, etc) to deploy the Custom Learning and Starter Kit template successfully. We also know that users miss our documentation. Hence this request is to harden the PnP Provisioning service deployment process to clearly call out provisioning failures specific to not following pre-reqs and to point users to that documentation.

    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 →
  8. Add support for library packages in the SharePoint Framework

    When building web parts I'd like to be able to extract common code to a separate library that can be shared amongst the different web parts.

    Related issue on GitHub: https://github.com/SharePoint/sp-dev-docs/issues/467#issuecomment-284631927

    451 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! We’re happy to report that your suggestion was delivered as preview as part of the SharePoint Framework 1.8 release. See more details from the release notes – https://github.com/SharePoint/sp-dev-docs/wiki/SharePoint-Framework-v1.8-release-notes and from the official SharePoint dev documentation at http://aka.ms/spdev-docs. This capability is currently in preview, but will be shipping close as is to production soon, so we are closing this already to ensure that the progress is noted.

  9. Support .NET Core with CSOM

    Support .NET Core with CSOM

    2,394 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! We’re happy to report that your suggestion is now part of the newly released SharePoint Online CSOM API NuGet package.

    See more details from following blog post where we reference additional documentation on the usage and have also a video on showing this in practice – https://developer.microsoft.com/en-us/microsoft-365/blogs/net-standard-version-of-sharepoint-online-csom-apis

  10. Add additional permissions to GraphHttpClient

    With the graph GQL gone, having this "easy" method to query Graph API directly from SharePoint when already authenticated is a huge must have.

    For example I'd ask priority on the permissions that let you fetch Recent Files, Trending Files, Trending People, and Planner tasks for the current user. Those make the most sense to be featured on intranet home pages. We do this currently (and it is quite messy with adal.js, particular when it comes to token refreshes), but has lots of end user value.

    I have 4 custom web parts today in a SEWP. One gets recent documents,…

    81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! We’re happy to report that your suggestion is now part of the SPFx v1.4.1 release with the introduction of AadHttpClient and MSGraphClient classes, which will replace the previously available GraphHttpClient. This new capability is now in preview, in similar ways as GraphHttpClient was, but is planned to move to General Availability within spring 2018. You can read more details on the possibility to use ANY Graph scope from https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-msgraph.

  11. Add support for Single Page Applications to the SharePoint Framework

    As an example - Angular2 provides an excellent user experience, especially when tied to Bootstrap (v3 or v4) suitable for creating immersive experiences where the whole of the SharePoint chrome is replaced (other than the top bar).

    However integrating it with the SharePoint REST API framework is cumbersome and unless extensive work is undertaken to mock SharePoint the unit testing and rapid deployment is very unpleasant if possible at all.

    The SharePoint framework provides a rapid deployment and unit testable mechanism for developing SharePoint functionality but is limited to single web parts and extensions.

    Please extend the model so that…

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

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

    Thanks for your feedback! We are happy to inform that the official documentation has been updated to include the note on using app@sharepoint identity for enabling write operations with app-only policy.

    This means that app-only model also for writing taxonomy data is now fully supported.

    Documentation updated at https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/elevated-privileges-in-sharepoint-add-ins.

  13. Support ComplianceTag on the CSOM list object

    Today CSOM expose ComplianceTag per item in a list/library. The library UI support setting a default ComplianceTag. Having this property in CSOM would be useful for provisioning scenarios.

    If you look at the SchemaXml for the list the property is visible.

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

    Thanks for your feedback! We’re happy to report that your suggestion is now part of SPO CSOM package. Please do submit an additional item for any other requests, like on having this on the content type level, as we cannot track additional requests simply on the UserVoice comments. Thx.

  14. Ability to add full width web parts to pages

    The full width section on communication pages only allows the hero and images web part. It would be great if we could deploy custom full width web parts that can be added to this section.

    12 votes
    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 →
  15. Enabled Javascript in Modern view

    I have implemented, JSlink for the Document library's default view, where JSLink associated at field level to get field properties and invoke Java script functions to get the properties and do some tweaks.

    We want to have same type of approach with the Modern view also. As per Microsoft still it not supported in Modern view of library. Any alternate way to achieve this?

    I have already tried with the custom Action at the document library Toolbar (associate custom action with Content type), but the issue is it not support JavaScript calling.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint Add-ins  ·  Flag idea as inappropriate…  ·  Admin →
  16. CSOM .NET async support

    CSOM for both Silverlight and JavaScript have an ExecuteQueryAsync method. This is not available for the .NET version.

    Currently, ExecuteQuery blocks the current thread and in the context of an ASP.Net application this is very resource intensive - the request thread cannot be used to service other threads whilst ExecuteQuery is waiting for a response.

    ASP.Net applications only have a small number of threads proportionate to the number of cores and the lack of async support makes it very difficult to write SharePoint provider-hosted add-ins capable of handling large numbers of concurrent requests.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Create a seperate yeoman generator for SPFx on-premesis SharePoint 2016

    Please preate a @microsoft/sharepoint-2016 SPFx generator, so that I don't have to keep uninstalling the supported on-premesis (@1.0.2) generator, then re-installing the @latest version for SPO. I should have access to both generators at the same time, one supporting the latest on-prem feature pack, and one for the latest SPO environment.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! We’re happy to report that your suggestion is now part of the SharePoint Framework 1.3 Yeoman flow. You do no longer need to install specific Yeoman versions for on-premises and online.

  18. Extend SharePoint REST API to retrieve list by staticname

    We have a solution which provisions lists to several site collections. There can be different language version, so list display names are localized. It would be nice have a REST endpoint to retrieve list by it's internal name.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Ability to run development and production versions of the SP Fx web parts in two different site collections

    Currently, the SharePoint Framework solutions are deployed as tenant wide app packages. Thereby, all instances of the web parts refer the JavaScript files from the CDN location specified in the packaged that is deployed in the app catalog. We need the ability to run Development, Staging and Production environments as different Site Collections in the same tenant.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  20. Use CSS Grids and Flexbox for Layout

    It's 2017, you really shouldn't be using <table> for layout!

    SharePoint should use Grid and Flexbox for layout of not just the Ribbon, sidebar, navbar etc but for List forms too. This would clean up the SharePoint HTML and CSS considerably as well as making it easier to customise the layout of forms.

    (Sure, there's an argument to be made that there's a semantic relationship between form input and tabular data, but I'm pretty sure the 'tables for form layout' is just something carried over from earlier versions of SharePoint needing to serve browsers with poor standards support.)

    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 →

    Hi – thanks for your input. Technically this has been already done at SharePoint Online where all the new experiences are natively responsive, including site pages, site contents, list or library experiences. We are also working on including these in the future feature packs for SharePoint 2016 on-premises. We are not using

    format for the layouts with the modern experiences.

    See following blog posts for additional details

    - https://blogs.office.com/2016/07/25/modern-sharepoint-lists-are-here-including-integration-with-microsoft-flow-and-powerapps/
    - https://blogs.office.com/2016/06/07/modern-document-libraries-in-sharepoint/
    - https://blogs.office.com/2016/08/31/new-capabilities-in-sharepoint-online-team-sites-including-integration-with-office-365-groups/

    ← Previous 1 3
    • Don't see your idea?

    Feedback and Knowledge Base