The request access process is inconsistent across the product. When a user requests access to a site he or she is not a member of, the site owner has an easy time granting the user the appropriate level of access by clicking the ... context menu and assigning the user to a group.

If a user requests access to a library with unique permissions from the parent, the site owner can only grant the user an explicit permission level even though there are groups in place that govern access. Giving a bunch of users direct access to an object just isn't maintainable. Go get around this, the site owner has to decline the request and go add the user to the appropriate group through a series of clicks and hops.

I would like to see the experience for any object request treated the same. Any groups that govern access to the object are presented in the access request to the site owner as well as explicit permission levels.

A bonus to this would be to set the default permission level to Contribute versus Edit.

*English follows Japanese

■Title(件名)：
ルート サイトへリダイレクトされる動作について
About behavior redirected to a root site

■Description(内容):
Internet Explorer のブラウザーを利用し、"RpsContextCookie" という Cookie が保持されていない場合、Office 365 ポータル サイト (https://portal.office.com) を経由せずに SharePoint Online サイトへの URL へ直接アクセスすると認証後にルート サイト コレクション (https://<テナント名>.sharepoint.com) へアクセスされる動作について、他ブラウザーでは発生しない事象のため、Internet Explorer においても発生しないよう、改善を希望します。
On Internet Explorer in which a cookie called “RpsContextCookie” is not stored, if you directly access a URL in a SharePoint Online site without going through an Office 365 portal site (https://portal.office.com), after accepting a cookie, a URL will direct you to a root site collection (https://<tenant name>.sharepoint.com).
However, this does not happen in other browsers, so please fix the problem.

*English follows Japanese

■Title(件名)：
クイック リンク Web パーツに SharePoint Online サイトのリンクを追加するとブラウザーの同一タブで画面が遷移される
Allow us to open SharePoint Online site links with different browser when the link is in the quick link web parts

■Description(内容):
クイック リンク Web パーツに SharePoint Online サイトのリンクを追加すると、ブラウザーの同一タブで画面が遷移され、新しいタブでリンク先に遷移することができない。
外部サイトのリンクの場合は、ブラウザーの別のタブで画面遷移することが可能なため、SharePoint Online サイトの場合も同様に別のタブで画面遷移ができる機能の実装を要望します。

When we click the link of SharePoint Online sites which are inserted in quick link webparts, we can not open the link with different browser, they open with new tab in the same browser.

If the link is outside of SharePoint Online, we are able to open it with different browser, so please let us to open the SharePoint Site links in the same way.

Thank you for your consideration.

*English follows Japanese

■Title(件名)：
既存のサイト名で新しいサイトを作成した際のエラー メッセージについて
Show the clear message when the users are not able to create new sites

■Description(内容):
従来の SharePoint 管理センターから新しいサイトを作成する場合、既に同じ URL が存在している場合は "サイト コレクションが既に存在します" というメッセージが表示されます。

しかしながら、既に存在しているサイトに権限がないユーザーが新しく同じ URL でサイトを作成しようとすると "アクセスの拒否" と表示されます。
アクセスの拒否のエラーでは "権限がないために サイトの作成ができない" と読み取れる為、既に作成済みのサイトに権限がない場合でも、同じ URL でサイトを作成しようとした場合には、"サイト コレクションが既に存在します"というエラーが表示されるようにしてほしい

At the SharePoint admin center, users see the error message as “the site collection already exists” if they try to create the new site with same URL as existing site.

However, if the user creating the new site do not have permission to the existing site, they just see “Access denied” and this message make users considered that they can not create the new site because of the permission issue.

We would like you to show “the site collection already exists” message even though the users who are creating sites do not have permission the existing site.

Thank you for your considerations.

*English follows Japanese
■Title(件名)：
ページやドキュメントごとのアクセス数を集計する機能について
A feature to aggregate the number of accesses for each page and document

■Description(内容):
以前は、[人気の傾向] 機能にてアクセス数の確認が可能でしたが、2020 年 2 月 29 日以降に機能の提供を終了したため、現在は監査ログ機能にてアクセス数を手動で計算することができます。

しかしながら、監査ログ機能の場合、管理者でしか操作ができないため、フル コントロール権限程度で、"ドキュメントごと" "ユーザーごと" "ダウンロード数" などのアクセス数が確認可能な機能の拡充を希望いたします。​
In the past the "Popularity Trends" feature could be used to check the number of accesses, but as this feature has been discontinued from 29th Feburary 2020, currently the number of accesses has to be calculated manually by using the audit log feature.

However since the audit log feature can only be operated by the administrator, we hope that it can be improved to allow users with full control permissions to check the number of accesses like "Per Document", "Per User", "Downloads" etc.

Currently in SharePoint Online we can configure the Global access control policy in the SPO Admin Center for full access, limited (web-only) access, or to block access. This setting applies to all SPO sites in the tenant.

There is also a site level conditional access policy parameter that can be set on each SPO site. For example:

-ConditionalAccessPolicy AllowFullAccess
-ConditionalAccessPolicy AllowLimitedAccess

The catch here is sites currently must be as restrictive as the Global Policy. This creates a problem if you want all your sites to have the Global limited access by default (no downloading of files) except for a few approved sites where you set/configure full access.

This uservoice request is to remove the dependency between these two settings to allow granular access control at the site level. Since all new SPO sites apply the Global policy by default, this will keep new SPO and Teams sites restricted when created by default. An Admin could then allow full access if needed at the site level without impacting the entire tenant.

We have discovered that users are able to use the full Teams client to access content stored in SPO that does not respect the Global access control policy configured in the SharePoint admin center. However the same content IS restricted in SPO by the Global policy.

Ideally the Site Level SPO conditional access policy will be able to override the Global policy and take effect both in the Teams client and SPO sites. This would provide the most control and best experience for managing a dynamic growing environment that needs to be kept secure but flexible for external guest access.

Thank you for considering the request and thank you for your vote! Each one counts.. :)