Currently the site collection URLs are fixed as https://tenant.sharepoint.com and cannot be changed. This does not fit with flexible cloud-based solutions - business needs will inevitably result in an organisation changing it's name during its lifetime (mergers, acquisitions, rebranding etc). While it may not be possible to change it so that entirely custom domains are used (eg contoso.com, instead of sharepoint.com), it must be possible to allow the sub-domain to be changed (eg. newtenant.sharepoint.com)? Please?

Migrating an entire organisation (likely to include Exchange, Skype, Sharepoint and Onedrive data!!) to a new Tenancy is absolutely not a viable option.

This is essential and needs to be easy to find instead of hacking the URL every time you need to sign in as a different user.

Content types are an essential part of SharePoint. One issue that has been around since SharePoint 2007 is the absence of an overview of all applied content types. Why is this important? Try to delete a content type and you get the message it's still in use. Good luck finding out where. This is very frustrating and time consuming. That's why I vote for an overview where you can see where the content types are applied.

I would like a option to see all sharepoint sites that i have access to.

Allow the owners of the sites to view a report of the security of their site. Start by adding a chart of the inheritance breaks of the whole site in one glance. This will become more and more important since you can use the 'Share' button on a file and break inheritance without understanding what you're doing.

The new layout looks better, but there does not seem to be any way of re-ordering these - not even alphabetically. When you follow a lot of sites as I do, they can be hard to find in an unordered jumble of large tiles.
Please either sort automatically or provide a means for us to sort them!

give options / settings to modify basic look and feel on https://annu28.sharepoint.com/_layouts/15/sharepoint.aspx. user should be able to choose which Team sites tiles should display on this page.

Please remove deleted sharepoint sites from Frequent Sites and Suggested Sites if they no longer exist. It confuses staff.

Currently the two managed paths (/sites and /teams) are fairly limited and I suggest that you add two more managed paths.

/groups
/projects

Having these two additional managed paths would allow for more flexibility and a much better information architecture in SharePoint Online

It should be possible to exclude / hide the external or guests accounts form the people picker in the share forms.

We want to invite customers to some of our sites but we do not want their account to show up when we use the share dialog.

We want to avoid confusion when both an internal resource and a customer have the same name.

Whenever 'Copy Link' option is hit in SharePoint, it automatically breaks the inheritance for that document/folder. This makes it very hard to manage the site permissions and result in tons of items where inheritance is broken.

It would be great, if it doesn't break inheritance unless someone who doesn't have permissions to the site tries to access the item.

*English follows Japanese

■件名 ： “電子メール招待状を送信する”を無効にする設定について
■内容:　 SharePoint Online のサイトへの権限設定時の [電子メール招待状を送信する] のチェックが入ったままであると、チェックを外し忘れてしまった際に招待されたユーザーにメールが送信させたく無い場合にもされてしまうかと存じます。
該当のチェックを既定で外れる設定があると、作業の手間が少しでも省けるため、該当のチェックを外すことが出来る設定を希望いたします。
-----
In case the checkbox of ”Send an email invitation” is checked at the time of setting the right to SharePoint Online site, there is a possibility that e-mails might be sent to users if unchecking would be neglected. I would say that it is helpful in avoiding some troubles if there could be a setting by default to uncheck the box. Therefore, I hope the setting to be available that could enable for me to uncheck the box.

On prem, we use web apps and managed path to define our sites structure. I understand that we cannot have webapps online but why can't we create managed path?

I would use it to group sites by type
http://tenant/teams/TeamA
http://tenant/groups/GroupA
http://tenant/services/IT
http://tenant/clients/000000

It would help for search and administration.

Thanks.

Make it easier to delete sites.

We typically discourage site owners from sharing at the document level due to the increase in administrative work that it causes. We also discourage owners from inviting individuals - we suggest that inviting groups makes the work simpler. However, the interface when sharing a document doesn't encourage sharing with groups - doesn't even make it obvious that sharing with groups is possible there. Are we wrong in how we are encouraging our site owners to manage their sites? If not, can it be made more obvious that sharing with groups is the best practice?