SharePoint
Feedback by UserVoice

SharePoint Administration

Welcome! This is your place to suggest ideas or vote for ideas for improving the SharePoint Administration experience.

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. Porting Sharepoint Online cmdlets to PowerShell Core and ensure they are cross platform, so that it's available on the PowerShell Linux port

    port SharePoint Online cmdlets to PowerShell Core and ensure they are cross platform, so that it can be made available on the PowerShell Linux port.

    I have been forwared to this sharepoint.uservoice.com from my initial question at https://github.com/PowerShell/PowerShell/issues/4526.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  2. Full-featured SharePoint Online Management Shell

    Full-featured SharePoint Online Management Shell
    If not a full suite of Cmdlets (currently SPO's ~35 plays On-Premises 730+), can we please at least have CSOM load all attributes of an object?
    On premises I can do:

    $Web = get-spweb <a rel="nofollow noreferrer" href="https://site/web">https://site/web</a>
    

    and get * properties with $web.AnyPropertyILike
    There isn't enough room here to paste script I need to do this in SPO

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. A feature to mass abort permission inheritance

    *English follows Japanese
    ■Title(件名):
    権限の継承を一括で実施する機能について
    A feature to mass abort permission inheritance


    ■Description(内容):
    親サイトの権限継承を中止するには GUI 上での操作が必要となるが、​サイトコレクション配下に多数のサブサイトが存在することを想定した場合、GUI 上からの操作は工数がかかるため、PowerShell コマンドレットなどで一括で権限の継承を中止できる機能の提供を要望します。
    GUI operations are necessary if user wants to abort the permission inheritance for parent sites, but as GUI operations will require lots of workload if there are lots of subsites under the site collections, we hope a feature will be provided to mass abort permission inheritance using PowerShell commandlets.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  4. Improve on a feature to mass change "SPS-HideFromAddressLists" for multiple users in SharePoint Online

    *English follows Japanese
    ■Title(件名):
    SharePoint Online にて複数のユーザーの "SPS-HideFromAddressLists" を一括で変更する機能の拡充
    Improve on a feature to mass change "SPS-HideFromAddressLists" for multiple users in SharePoint Online


    ■Description(内容):
    現在、ユーザーの "SPS-HideFromAddressLists" を変更するには PowerShell コマンドレットにて、1 ユーザーずつ変更しなければならないため、非常に大きい工数が発生するため、数のユーザーの "SPS-HideFromAddressLists" を一括で変更する機能の拡充を希望します。
    Currently PowerShell commandlets need to be used to change "SPS-HideFromAddressLists" for users and they need to be done one by one for each user which creates a massive workload. Thus we hope that this feature will be improved to enable mass changing of "SPS-HideFromAddressLists" for multiple users.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. Bulk List Imports via PnP

    Could you please add the ability to bulk import records via PnP powershell? Example use cases would be:

    1) New-PnPList - New switch option which points to a CSV file and performs a mass load of data.

    2) Add-PnPListItem - New bulk process operation to send say 100+ records at a time in bulk. Attempting to use this command to process 15,000 records 1 line at a time is very slow.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  6. About the behavior when running the commandlet: Set-SPOSite -Identity [Site Collection URL to be applied] - DisableSharingForNonOwners

    *English follows Japanese

    ■Title(件名):
    Set-SPOSite -Identity [本設定を適用したいサイト コレクションの URL] -DisableSharingForNonOwners のコマンドレット実行時の動作について
    About the behavior when running the commandlet: Set-SPOSite -Identity [Site Collection URL to be applied] - DisableSharingForNonOwners


    ■Description(内容):
    DisableSharingForNonOwners のコマンドレットを実行すると、[アクセス要求の設定] 内のすべてのチェックが外れる動作になるが、 現在は、[アクセス要求の許可] について、アクセス要求を受け取るユーザーをサイトの "管理者" を選択している場合には、該当のコマンドレット実行しても [アクセス要求の許可] のチェックが外れない動作となっている。アクセス要求を受け取るユーザーのメール アドレスを指定したうえで上記のコマンドレットを実行すると、 [アクセス要求の許可] のチェックが外れるため、"管理者" もしくは "所有者" を選択している場合にも該当のコマンドレットが有効となるように機能の拡充を希望します。
    When running the commandlet: DisableSharingForNonOwners on PowerShell, it should be that all the checkboxes in [configuring access requests] become unchecked. However currently, if the current user is designated as “administrator” and runs the commandlet above, [allow access requests] will remain checked. While [allow access requests] is checked, and an e-mail address is filled in, and then…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. Request for a command to extract only Office 365 group sites that connect with Teams teams

    *English follows Japanese
    ■Title(件名): Teams のチームと接続する Office 365 グループ サイトのみを抽出するコマンドの要望

    Request for a command to extract only Office 365 group sites that connect with Teams teams


    ■Description(内容):
    現在、PowerShell において、Teams のチームに接続する Office 365 グループ サイトのみを表示するようなコマンドが実装されていない。

    管理を容易にするため、Teams のチームに接続する Office 365 グループ サイトのみを表示するコマンドの実装を要望します。

    Currently, PowerShell does not implement a command to display only Office 365 group sites that connect to Teams teams.

    For ease of management, we would like to implement a command to show only the Office 365 group sites that connect to the Teams team.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. Install-pnpapp scope for web

    Allow Install-pnpapp to install custom apps at web(sub sites) level.
    Right now it only installs on site collections

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  9. MySite Cleanup Powershell commands

    The current MySite Cleanup process is a black-box and often fails for various reasons. If it doesn't find a manager or secondary contact, the job just stops.

    Option 1: Fix the black box so it sets the MySite deletion timer even when there is no manager or secondary contact.

    Option 2: Create commands enabling admin to assign a delegate and start the timer on site deletion, or just start the deletion timer

    Option 3: Expand the Site Closure policy to include the criteria option for 'MySite Owner no longer a valid user'

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  10. the picture automatic switching function is disabled

    Following the release of the Office 365 CDN, the picture automatic switching function is disabled by default on “Picture Library Slideshow Web Part”.
    If you want to use the picture automatic switching function, you need to register the “Picture Library” r in Office 365 CDN.
    But using PowerShell command is the only way to register in the library.
    It would be really helpful if there’s a way to register library in Office 365 CDN from UI.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  11. We hope a feature will be added to enable PowerShell commandlets to retrieve a list of site users by date

    *English follows Japanese
    ■Title(件名):
    PowerShell コマンドレットにてサイトを利用したユーザーを日付ごとにリストで取得する機能の追加を希望します。
    We hope a feature will be added to enable PowerShell commandlets to retrieve a list of site users by date


    ■Description(内容):
    Office 365 監査ログ以外に、PowerShell コマンドレットにてサイトを利用したユーザーを日付ごとにリストで取得する機能の追加を希望します。
    Office 365 監査ログを有効化した場合のテナント全体への影響を懸念しているため、Office 365 監査ログ以外の機能でサイトを利用したユーザーを取得したいと考えています。
    We hope that other than Office 365 audit logs, a feature will be added to enable PowerShell commandlets to retrieve a list of site users by date as well.
    We are concerned about the impact on the entire tenant when Office 365 audit logs are enabled, so we would like to retrieve site users with features other than Office 365 audit logs.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  12. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  13. Changing the Office 36 group site title using PowerShell commandlets

    *English follows Japanese
    ■Title(件名):
    PowerShell コマンドレットでの Office 365 グループ サイトのタイトルの変更について
    Changing the Office 365 group site title using PowerShell commandlets


    ■Description(内容):
    Office 365 グループ サイトでは "-Title" パラメーターの使用ができないため、PowerShell コマンドレットにてタイトルの変更ができない。
    また、"SPOSiteRename" コマンドでは URL も変更されるため、タイトルのみ変更することができない。
    そのため、Office 365 グループ サイトのタイトルのみ変更するための PowerShell コマンドレットの実装を要望します。​
    As the "-Title" parameter cannot be used for Office 365 group sites, PowerShell commandlets cannot be used to change the title.
    If the "SPOSiteRename" command is used the URL will be changed as well, so it cannot be used to change just the title.
    Thus we hope that a PowerShell commandlet to change just the Office 365 group site title will be…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  14. Improving the standard commandlet feature for SharePoint Online

    *English follows Japanese
    ■Title(件名):
    SharePoint Online の標準コマンドレッドの機能拡充について
    Improving the standard commandlet feature for SharePoint Online


    ■Description(内容):
    現在の SharePoint Online の標準コマンドレッドでは細かい設定が行えず、PnP などのオープン ソースを利用しなければならない。オープン ソースは自身でモジュールの更新など行わなければならなかったり、コミュニティやフォーラム以外のサポートがないため、不便である。
    PowerShell を利用して業務の仕組みを組み込むことが多いが、標準コマンドででくることが少なく、オープンソースの利用だと Online の魅力がなくなってしまうため、Microsoft がサポートする標準コマンドレッドの機能拡充を要望します。
    Currently the standard commandlets for SharePoint Online cannot be used to make settings in detail, so open source like PnP had to be used instead. However for open source we have to update the modules ourselves and there is no support other than the community and forums, so it is inconvenient.
    PowerShell is used frequently to incorporate operation mechanisms, but not much can be done using the standard commands, if open source…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  15. Please implement a PowerShell commandlet to invite multiple guest users to SharePoint Online and grant access rights to them

    *English follows Japanese
    ■Title(件名):
    SharePoint Online に複数のゲスト ユーザーを招待しアクセス権を付与する PowerShell コマンドレットの実装希望
    Please implement a PowerShell commandlet to invite multiple guest users to SharePoint Online and grant access rights to them


    ■Description(内容):
    現在は、PowerShell コマンドレットの "New-AzureADMSInvitation" にて、ゲスト ユーザーの招待が可能だが、SharePoint Online のサイトにゲスト ユーザーが 1 度アクセスを行わなければアクセス権付与が行えない。
    また、SharePoint Online 上の GUI より、ゲスト ユーザーを招待しアクセス権を付与するは可能だが、複数名を同時に登録が行えない。

    複数のゲスト ユーザーと共有を行う場合、ゲスト ユーザーが 1 度 SharePoint Online のサイトにアクセス権がないままアクセスを行うか、SharePoint Online 管理者が 1 名ずつ GUI 上より登録を行うため、人数が多くなるほど作業の負担が増える。
    上記作業の負担を軽減するため、SharePoint Online に複数のゲスト ユーザーを招待しアクセス権を付与する PowerShell コマンドレットの機能実装を希望します。
    Currently, guest users can be invited using the PowerShell commandlet "New-AzureADMSInvitation", but access rights cannot be granted unless the guest user accesses the SharePoint Online site once.
    Guest users can be invited and granted…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  16. Requesting improvements in the feature where PowerShell commandlets are used to export audit logs

    *English follows Japanese
    ■Title(件名):
    監査ログを PowerShell コマンドレッドを使って エクスポートする際の機能拡充要望
    Requesting improvements in the feature where PowerShell commandlets are used to export audit logs


    ■Description(内容):
    現時点では、PowerShell コマンドレッドで、監査ログの取得は可能であるも、監査ログの結果を "結果のエクスポート" の種類として 「読み込まれた結果を保存します」 で得られる CVS ファイルと同様の CSV ファイルではない。
    そのため、「読み込まれた結果を保存します」 で得られる CVS ファイルと同様の CSV ファイルを出力可能な PowerShell コマンドレッドの提供を希望します。
    Currently, even if audit logs can be retrieved using PowerShell commandlets, the audit log results can be classified as "Exporting results" and are not the same CSV as the CSV files obtained through "Loading and saving the results".
    Thus we hope that PowerShell commandlets to output CSV files that are the same as those that can be obtained through…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. Delete SharePoint Online profile pictures via PowerShell

    *English follows Japanese

    ■Title(件名):
    SharePoint Online PowerShell にてプロフィール写真を削除を可能とする機能の実装
    Delete SharePoint Online profile pictures via PowerShell


    ■Description(内容):
    Exchange Online PowerShell では、ユーザーのプロフィール画像を削除できるが、SharePoint Online 側で設定したプロフィール画像は、削除されない動作となっているため、SharePoint Online PowerShell でプロフィール画像を削除できるコマンドレットの実装を希望します。
    Currently it is possible to delete users’ profile pictures on Exchange Online PowerShell, but profile pictures set on SharePoint Online are not deleted. Therefore I would like for it to be made possible to delete these profile pictures using a commandlet in SharePoint Online PowerShell.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  18. Extracting which Site Collections are included in a given Security Group via PowerShell

    *English follows Japanese

    ■Title(件名):
    PowerShell にて対象のセキュリティグループが含まれるサイト コレクションの抽出
    Extracting which Site Collections are included in a given Security Group via PowerShell


    ■Description(内容):
    PowerShell にてサイト コレクションごとに割り当てされたセキュリティグループやユーザーの一覧を抽出するコマンドレットはあるが、対象のセキュリティグループが含まれるサイト コレクションを抽出するコマンドレットがないため、ひとつひとつのサイト コレクションを確認するのは、時間がかかってしまいます。
    そのため、セキュリティグループが含まれるサイト コレクション一覧を抽出するコマンドレットの実装を希望します。
    There exists a commandlet to extract the users and security groups assigned to Site Collections, but there is no commandlet to extract which site collections are included in a security group, and it takes a lot of time to check the site collections one-by-one. Therefore I would like a commandlet to show all the site collections being included in a given security group.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  19. Officially bless an automated installation of SP2016 / SP2019 on prem.

    It would be excellent if you would officially bless an automated installation of SP2016 / SP2019 on prem. I know that it is an unspoken thing but I have been at multiple clients that will not allow use of "non Microsoft" scripts/tools.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  20. throttl

    The SharePoint Online Management PowerShell commandlets are not throttle (throttling) aware. Microsoft recommends handling throttling via the following article. https://github.com/SharePoint/PnP/tree/dev/Samples/Core.Throttling Unfortunately, Microsoft's own PowerShell commandlets for SharePoint Online do not implement these recommendations. Customers are getting themselves and their scripts throttled due to the lack of this implementation (option parameter on commandlets?) and lack of notification of this potential issue. It's not realistic to direct everyone to write CSOM. Plenty of savvy administrators can write PowerShell, but not CSOM.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base