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
- Check if it's already been suggested. If it has, vote for it.
- If it's new, submit it in 50 words or less.
- Gather support!
- 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.
-
Admins running Connect-SPOService should be given broader options to connect
Currently, you have to type the whole fqdn of the admin portal for SPO to connect-SPOService.
However, the technology to do lookups is there; we should be able to do
Connect-SPOService -domain fabrikam.com
or
Connect-SPOService -user admin.user.upn@fabrikam.com
or
Connect-SPOService -tenantprefix fabrikam
1 vote -
Onedive Sync Auto-Connect
If One-Drive has to be unlinked from a PC at any point for any reason, it loses its synced connections with document libraries in sharepoint. The curious thing about this is that Windows is smart enough to realize that those syncs have been previously made on the machine. If you re-sync one of the previously sycned libraries, the rest of them will show up but do not automatically begin to sync. A powershell to easily reconnect these previous connections would be extremely helpful when users are needing to connect upwards of 25 libraries.
1 vote -
ForceOAuth option for Connect-SPOService
Currently it is not possible to run an Azure Function that loads the SharePoint module and use a user account to connect using Connect-SPOService. This is because the ForceOAuth parameter must be set in registry, and the registry is read only in Azure Functions.
There is no workaround other than patching the Microsoft.Online.SharePoint.PowerShell.dll, changing an if in InstantiateSPOService.
A very simple patch to Microsoft.Online.SharePoint.PowerShell.dll, adding a new parameter to Connect-SPOService called "ForceOAuth", that adds the ForceOAuth parameter to InstantiateSPOService, would solve this issue.
Also, even though functions are dotnetcore, the module runs just fine using Import-Module $moduleFile -DisableNameChecking -UseWindowsPowerShell
1 vote -
Powershell QuickLinks Audiences targeting
Hi
It will be great to be able to consume the Audiences parameter from PnP or CSOM for Sharepoint Online
Something like
Add-PnPNavigationNode -Title "Contoso" -Url "http://contoso.sharepoint.com/sites/contoso/" -Location "QuickLaunch" -Audience "Contoso Members"
Thanks1 vote -
get-sposite StorageQuotaType blank for bulk queries
StorageQuotaType is blank when using get-SPOSite to retrieve sites in bulk (querying individual sites works OK).
Please make this attribute available for bulk operations.1 vote -
get tenant space using ps
Be able to get current used and max tenant space via ps, not only in admin console ui
1 vote -
Add a PowerShell cmdlet to get a list of all Microsoft 365 permissions assigned to specified user(s)
*English follows Japanese
■Title(件名):
特定のアクティブなユーザーに付与されている Microsoft 365 に関連する権限のすべてを一括で取得する Windows PowerShell のコマンドレットを提供してほしい。
Add a PowerShell cmdlet to get a list of all Microsoft 365 permissions assigned to specified user(s)
■Description(内容):
特定のアクティブなユーザーに付与されている Microsoft 365 に関連する権限のすべて確認したいが、SharePoint Online や Exchange Online など、権限を取得するコマンドレットが分かれており、一括ですべての権限を取得できるコマンドレットが存在しないので、すべての権限を一括で取得できる Windows PowerShell のコマンドレットを提供してほしい。We want to check all the Microsoft 365 permissions assigned to specific users, but the cmdlets used to get the permissions for SharePoint Online, Exchange Online etc. are all separate from each other, and there is no cmdlet to get all permissions at once, so please add a PowerShell cmdlet to get these.
7 votes -
Fix differences in the display of Microsoft Search ProvisioningStatus in PowerShell between tenants and users
*English follows Japanese
■Title(件名):
PowerShell で表示される Microsoft Search の ProvisioningStatus がテナントとユーザーで表示に差異がでる動作について改善を希望します
Fix differences in the display of Microsoft Search ProvisioningStatus in PowerShell between tenants and users
■Description(内容):
ライセンス、サービスの付与を PowerShell でアカウントごとに設定しているため、テナントの Microsoft Search のProvisioningStatus が Success で表示されているにも拘らず、ユーザーで ProvisioningStatus を確認すると PendingProvisioning で表示されているため、Office 365 管理センターで確認作業が必要になり手間がかかる。
また、Office 365 管理センターの確認についてはアカウントに当該ライセンスを付与する必要がありさらに作業工程が増えてしまいます。
"このアプリは組織レベルで割り当てられています。ユーザーごとに割り当てることはできません" に該当するサービスについてはテナントで確認する ProvisioningStatus をユーザーで表示されている PendingProvisioning に統一して表示することを希望します。We use PowerShell to check license and service assignments for each account, and regardless of whether the tenant’s Microsoft Search ProvisioningStatus is shown as “Success”, checking it from the user’s side shows it as PendingProvisioning, thus requiring extra work to check it via the Office 365 Admin Center.
Also,…14 votes -
Better, faster recycle bin restore capability
Users accidentally delete stuff...no getting around it. This morning I had someone accidentally delete 35,000 files from a OneDrive-synced SharePoint doc library, and now I'm in the process of restoring them. get-pnprecyclebinitem is painfully, unacceptably slow. This is literally going to take DAYS at this rate. Restoring via the GUI is no good because you can't easily select thousands of files at once. There has to be a better way to bulk-undo user errors like this.
7 votes -
Enable Setting ConditionalAccessPolicy without Interactive PowerShell Session
Currently, when running 'Set-SPOTenant -ConditionalAccessPolicy BlockAccess', the command prompts for user confirmation, which cannot be bypassed either using -Force or -Confirm:$false. This means that the command cannot be run non-interactively in a PowerShell script.
Request that the cmdlet parameter be fixed so that it allows running in a non-interactive PowerShell session.
Confirmed in the latest Microsoft.Online.SharePoint.PowerShell module, version 16.0.20212.12000.
4 votes -
Method to configure detailed settings for each site collection in cases where domains are restricted in the organization
*English follows Japanese
■Title(件名):
組織でドメイン制限している場合のサイト コレクションごとの詳細設定方法
Method to configure detailed settings for each site collection in cases where domains are restricted in the organization
■Description(内容):
組織単位でドメインを制限している場合に、サイト コレクションごとの詳細なドメイン許可設定については GUI 上からサイト コレクションごとに設定が必要で不便であるため、PowerShell にてまとめて設定できるよう希望します。In cases where domains are individually restricted for the organization, you need to apply detailed domain permission settings for every site collection separately using the GUI. This is inconvenient so please add a way to do this all at once using PowerShell.
7 votes -
Set "show this view in folders of content type" with PowerShell | Modern experience
Please add the ability to set "show this view in folders of content type" with PowerShell. This field is no editable right now.
The missing possibility of editing leads to a lot of work in our IT department.
Furthermore, please activate this view feature in the modern experience. This great feature deserves to be available in the modern experience...
15 votes -
PowerShell "Site owners and members, and people with Edit permissions can share files and folders, but only site owners can share the site"
The ability to set the SharePoint Online site sharing permissions setting to "Site owners and members, and people with Edit permissions can share files and folders, but only site owners can share the site" using PowerShell, this way it can be set for a large number of sites via scripting. Currently Microsoft tells me this is not possible via PowerShell and can only be done manually per site.
14 votes -
Extract only the URL for a team using the team name in PowerShell
*English follows Japanese
■Title(件名):
Microsoft Teams のチーム名から、PowerShell にて URL のみを取得したい
Extract only the URL for a team using the team name in PowerShell
■Description(内容):
"Get-UnifiedGroup -Identity "チーム名" | select SharePointSiteUrl" を実行すると、URL だけではなく、"SharePointSiteUrl" という項目も取得ができる。取得した値を変数に代入するため、"SharePointSiteUrl" という項目は取得せず、URL のみを取得できるようにしたいIf you run "Get-UnifiedGroup -Identity "Team name" | select SharePointSiteUrl", not only is the URL extracted, but so is the “SharePointSiteUrl” item. We wish to assign the value we obtain from this command to a variable, and therefore would like to be able to pull only the URL, without also getting the “SharePointSiteUrl” item.
11 votes -
In Sharepoint, create a feature to search relate files based on author & fileType then delete & purge these files.
In Sharepoint, create a feature to search relate files based on author & fileType then delete & purge these files.
1 vote -
Way to check how much storage volume is currently in use for a tenant using PowerShell
*English follows Japanese
■Title(件名):
PowerShellでテナントの現在の使用量を確認する方法を希望します
Way to check how much storage volume is currently in use for a tenant using PowerShell
■Description(内容):
PowerShell にてテナント全体の上限値やサイトコレクション単位の上限値と現在の使用量を確認できるが、テナント全体の現在の使用量は確認できない。
テナント全体の現在の使用量をPowerShellのコマンドで確認できるように機能の追加を希望しますWhile it is possible to use PowerShell to check the upper storage limit for the whole tenant, as well as the storage limit and currently used storage for individual site collections, it is currently not possible to check the currently used storage for the tenant as a whole.
Please make it possible to check this using a PowerShell command.12 votes -
Use a PowerShell cmdlet to find the size of an object in a site collection
*English follows Japanese
■Title(件名):
サイト コレクション内のオブジェクトの容量を確認する PowerShell コマンドレットの提供について
Use a PowerShell cmdlet to find the size of an object in a site collection
■Description(内容):
現在提供されている PowerShell コマンドレットでは、サイト コレクション全体の容量しか出力できず、各サブサイトやサイトコンテンツ、ファイル、ファイル バージョンの容量を確認することができない。
管理者が容量を確認する際に、サイト ページへアクセスすることなくサイト コレクション内のオブジェクトをコマンドレットで確認できるよう、機能を提供してほしい。Currently existing PowerShell cmdlets can be used to output the total size of a site collection but cannot be used to find the sizes of individual subsites, contents, files or file versions.
Please make it possible for administrators to find the sizes of objects in a site collection using a cmdlet instead of by having to access the site page.6 votes -
Option to edit item names within a document library en masse
*English follows Japanese
■Title(件名):
ドキュメント ライブラリ内のアイテム名を一括で変更する機能の拡充
Option to edit item names within a document library en masse
■Description(内容):
ドキュメント ライブラリ内のアイテム名を変更するには、クイック編集機能でもアイテムごとに変更が必要なため工数が発生する。
そのため、PowerShell コマンドレットなどで CSV ファイルに保存した内容を取り込み一括でアイテム名を変更可能な機能の拡充を要望します。In order to change item names within a document library, one needs to use the quick edit function on each item, one-by-one, which takes a lot of work.
Therefore we would like to be able to make changes to item names in bulk using information read from a CSV file, applied via PowerShell cmdlets or such.5 votes -
Expand PowerShell cmdlet functionality in syncing many users with SharePoint Online document libraries
*English follows Japanese
■Title(件名):
PowerShell コマンドレットによる SharePoint Online ドキュメントライブラリ を複数ユーザーに同期させる機能拡充について
Expand PowerShell cmdlet functionality in syncing many users with SharePoint Online document libraries
■Description(内容):
PowerShell コマンドレットにて SharePoint Online のドキュメント ライブラリを全ユーザーの同期クライアントに同期させたいため、上記動作を実現する機能拡充を要望します。I want to be able to use a PowerShell cmdlet to have all users’ sync clients sync a document library on SharePoint Online, so please add such a feature.
0 votes -
Add PowerShell cmdlet for administrators of team sites linked to Office 365 groups to restrict use of “Create Team” function
*English follows Japanese
■Title(件名):
Office 365 グループに紐づくチーム サイトの管理者による "チームを作成する" 動作を抑制する Windows PowerShell のコマンドレットを提供してほしい。
Add PowerShell cmdlet for administrators of team sites linked to Office 365 groups to restrict use of “Create Team” function
■Description(内容):
Office 365 グループに紐づくチーム サイトを作成した際に、サイト コレクションの管理者がチーム サイトを開くと、"チームを作成する" の表示より Microsoft Teams 上にチームの作成を行うことができる。Microsoft Teams のチーム作成を一元管理するために、チーム サイト上の "チームを作成する" 動作を抑制する Windows PowerShell のコマンドレットを提供してほしい。
When a team site linked to an Office 365 group has been made, the administrator of the site collection is able to use the “Create Team” function to create a team on Teams when they open the site. Please add a Windows PowerShell cmdlet to restrict the use…9 votes
- Don't see your idea?