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. Support SharePoint 2016/2019 with .NET Standard APIs

    While the SharePoint online version is supported, we would like to see the SharePoint on-prem versions (SharePoint 2016/2019) supported with .NET standard CSOM APIs.

    https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/16585795-support-net-core-with-csom
    ^ this only allows for SharePoint Online .NET Standard CSOM support.

    Many customers have significant investments and longer term roadmaps to get to SharePoint Online, but in the interim would like to start developing solutions that can be more easily converted to work in SharePoint Online along with being able to leverage the latest version of the Microsoft technology stack - that is growing the skillsets / toolset familiarity without waiting for longer term plans…

    429 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Improved API feedback around throttling

    Currently working with the API's for drive, graph, sharepoint are very difficult due to the throttling that can be encountered.

    Each api offers different guidance to avoid throttling. Example are:
    1) use a special user-agent header
    2) respect the retry-after header

    Speaking with microsoft representatives they instruct us to perform major api processing in off peak hours. Additionally tenant's can have hard locks placed on them.

    This request is to get better information around tenant usage returned in the API's.

    1) If a tenant is hard locked, tell us in a distinct message so that don't just hammer the requests…

    182 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Enable ListItem SystemUpdate via REST

    Allow REST clients to update list items a la SystemUpdate. That is, REST clients should be able to update list item metadata without creating a new version and without affecting system columns like authors and timestamps. The same idea for CSOM was recently implemented and I'm puzzled why the REST API is always left behind.
    The CSOM idea:
    https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/15147093-enable-listitem-systemupdate-via-csom

    128 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Provide the AddToCurrentScopeOnly in the RoleAssignment class for JSOM and CSOM

    The SharePoint "fine grain permissions" best practices document recommends using this method as a way to help prevent performance penalties when unique permissions are applied. However, we need this capability in JSOM and CSOM since AddToCurrentScopeOnly is currently only available for use on-premises using the server-side object model.

    46 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. In Place Records Management: Provide a property that would expose manual record declaration availability in CSOM / REST

    1) Hopefully the feature InPlaceRecords (da2e115b-07e4-49d9-bb2c-35e93bb9fca9) shows up in the list of web features when it is activated.

    2) Expose a property that would specify the setting selected by the user in the Library Record Declaration Settings.
    a. Manual Record Declaration Availability
    b. Automatic Declaration

    3) Or - It would be great to have another property called "CanDeclareAsRecord" on this class:

    public class Microsoft.SharePoint.Client.RecordsRepository.Records
    Currently, it only provides a check if item is already an existing record. However, there is no method that says if a currently undeclared item can be declared.

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. incrase CSOM support for ExportDocumentSet to more than 50MB

    It will be great to increase the size limit of DocumentSet using the CSOM method "ExportDocumentSet".

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Provide ListItem.SystemUpdate also for SharePoint on-premises

    Please provide the SystemUpdate function via CSOM not only for SPO but also for on-premises at minimum for SharePoint 2016 (2013 would also be nice ;-))

    39 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Create UserProfile Properties programmatically in SPO

    Currently there is no API available to create custom UserProfile properties (and/or sections) in SharePoint Online. Are there any plans (to make this part of the Tenant administration namespace so) this can also be set via code/script as opposed to GUI only?

    37 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. AAD app-only access site permission control

    As described in this doc: https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread
    When granted All Site Full Control permission, the application would be able to access all sites in my organization. But can we grant permissions to specific sites? In other words, can we restrict the sites the application can access? If we can, how to do this?

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Expose NavigationNode.TitleResource in CSOM & JSOM

    You can already localize using SetValueForUICulture() for TitleResource or NameResource and DescriptionResource properties of Web, List, ContentType, and Field. What is missing is the ability to do this for NavigationNode and maybe CommandUIExtension to make localization complete.

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. 30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Make Localization accessible for QuickLaunch NavigationNode and WebPart titles

    Hi all,

    It would be really nice to add more support for localization in CSOM for SharePoint on-prem and online.

    In server side object model, it possible to localize NavigationNode (SPNavigationNode) using the TitleResource property like this:

            using (var site = new SPSite(&quot;<a rel="nofollow noreferrer" href="https://UrlToMySharePointSite&quot;)">https://UrlToMySharePointSite&quot;)</a>)
    
    {
    using (var web = site.OpenWeb())
    {
    var nodes = web.Navigation.QuickLaunch;
    foreach (SPNavigationNode node in nodes)
    {
    node.TitleResource.SetValueForUICulture(new CultureInfo(1036), &quot;My French Title&quot;);
    }
    }
    }

    Same for WebPart Title. I've found a way to do this but don't have tested it (I tested it for NavigationNode but doesn't work) : http://sadomovalex.blogspot.ch/2015/09/localize-web-part-titles-via-client.html

    As we have…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Add MFA Support for .Net Standard CSOM

    With the new support of CSOM with .Net Standard we should be able to acquire tokens with accounts that have MFA enabled and not just regular accounts that don't have added security.

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. SharePoint CSOM/Rest EnsureUser multiple users per query

    It'd be nice to have the ability to ensure multiple users at once working properly.
    More context https://github.com/SharePoint/sp-dev-docs/issues/3191

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Listing SharePoint Site Collection URLs in a Web App should have a special permission to avoid giving too much admin access

    Listing site collection URLs in a web app should be a special permission by itself. Many times you end up giving full admin rights to a user just because you need that ability. And this forces you to violate the principal of Least Permissions.

    Make the ability to give access to list site collections without being a full admin.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Support Compliance Tag on list level using REST API

    Today we can apply retention labels to documents using REST and CSOM. Last year CSOM was updated to support list labels.

    I would like for the REST API to support the following:
    1: Listing available labels
    2: Applying a retention label to a list.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Add support in CSOM to modify the CustomScriptSafeDomains settings for a site

    Support was added in March 2018 to read the CustomScriptSafeDomains settings for a site - we'd like the possibility to modify this setting through the CSOM API - not methods are currently available to modify this settings through code.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Parameter for passing specific Site Design in Modern Team site Creation

    While creating the Modern communication site programmatically through Rest API/ Graph API there is a parameter available to choose the site design.

    Title = "title
    Description = "description
    AllowFileSharingForGuestUsers = false
    Classification = "classification"
    SiteDesign = CommunicationSiteDesign.Topic

    But while creating the modern team site programmatically there is no option to choose the Site Design, by default it is picking up the default Site Design. Even though we can create multiple site script and site design for Teams site, we are not able to specify a site design at the time of provisioning the Group.
    Is there any possibility to choose…

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Add UseAccessRequestDefault Rest API or CSOM when receiver is the team site owner in Access Request Settings.

    Environment: SPO

    There is a new option to allow the team site owners to receive the access requests email, but there is no Rest API/CSOM to support this, Please have add this into CSOM API, Thank you.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3 4 5 6 7
  • Don't see your idea?

Feedback and Knowledge Base