*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(件名)：
クイック リンク 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(件名)：カスタム リストに添付した Office ファイルを開く際の動作について

Make the Office files attached to the Custom list open/editing by Office Client.

■Description(内容):
サイト コレクションのサイトの設定にて、 "既定でクライアント アプリケーションでドキュメントを開く" をアクティブにしているにも関わらず、現在カスタム リストに添付したOffice ファイルをモダン UI にて開く際に、Office Online 以外で開くことができません。
サイト コレクション全体の設定と矛盾した動きになっていますので、カスタム リストに添付した Office ファイルについても、Office クライアントで開けるように動作の改善を希望します。

We are aware of that the files can only be opened with Office Online when opening the Office file attached to the Custom list via the modern UI although "Open Documents in Client Applications by Default " is enabled in the settings of the Site collection.

It seems the settings of the Site collection is not properly applied, hence, we hope this behavior will be corrected that the Office file attached to the Custom list can be opened by the Office Client appropriately.

Thank you for your consideration.

*English follows Japanese

■Title(件名)：
一般ユーザーに対し Microsoft Stream の [グループの作成] をさせないよう [グループの作成] を非表示にしたい。

Disable the [New Group] function for the general users arbitrarily in Microsoft Stream.

■Description(内容):
Microsoft Stream でグループを作成を管理者のみが実施する運用を検討しているため、一般ユーザーに対し Microsoft Stream の [グループの作成] をさせないよう [グループの作成] を非表示にしたい。現時点では、Microsoft Stream で [グループの作成] を非表示に​する機能は実装されていないため、 [グループの作成] を非表示にできるよう機能拡充を要望します。​​

Now we are considering the internal operation that allows the group creation only the administrators for in Microsoft Stream. In order to achieve this expected operation, we would like to suggest you make the hide option for [New Group] to disable the Microsoft Stream groups creation for the general users.

For ease of management, we hope the feature will be added that disables the [New Group] function for non-administrators as soon as possible.

Thank you for your consideration.

Access control is extremely important to my company and our customers. Currently, unless you're an Owner of a team site, you have a very limited view of who has access to what. Members can see who content has been shared with via the Share->Shared With dialog view, but this doesn't show the level of access those individuals have (read vs. write). This causes angst among our users who sometimes won't add content because they are not sure who has the ability to modify the content they add. To get around this, we have created a custom page for our team sites called "Access Control" that displays the membership of those groups associated with the team site. This at least provides the default access controls by name. It would be brilliant if users could easily be able to see who has what level of access to containers and objects in a team site.

The Share feature apparently creates a new security principal that overrides the classic SharePoint permission model. These security principals neither can be seen, nor broken on lower levels in the hierarchy. This makes the tracking of who has permission to what at any given time impossible. (Technically it is possible, but the logic would be throttled by the SPO service.) The issue appears for internal, guest and anonymous links as well.

We need a way to be able to keep track of what is shared on what level. (The announced feature of sharing report is not providing the necessary information.) Please make sure the links created through the Share feature:
- Appear on every level of the hierarchy
- Are reportable through the APIs
- Respect existing broken permission inheritance
- Can be broken at any time

For example: You have a document library with a folder structure of 3 levels. You break the permission on the second level. You create a Link through the Share function on the first level to a user (User1) that should not have access to the second (and third) level folders. You check the sharing status on the second an third level and see that the folders are not shared, and User1 does not have access to the folder. When using the Check Permission function you also see User1 showing up with the proper permission, but you do not see from where this permission is inherited. User1 will have access to any existing and new items created under the second and third level.