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.

Please change how SharePoint generates links to uploaded documents and site pages, so that URLs with spaces will replace %20 with a dash instead. Most CMS tools including blogs do when generating SEO friendly URLs. Links with %20 throughout are too difficult to read.

This feedback site is a perfect example:

This:
https://sharepoint.uservoice.com/forums/282887-customer-feedback-for-sharepoint-server

is easier to read than this:
https://sharepoint.uservoice.com/forums/282887%20customer%20feedback%20for%20sharepoint%20server

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.

In case I get access SharePoint Online along with the URL which is not encoded through Internet Explorer, I am aware that the HTTP 500 internal error occurs when clicking the App launcher's［Email］［Calendar］in the sate that the URL includes the double-byte characters(such as Home). I hope the immediate improvement concerning this incident.

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.

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

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.

Make a tool that allows members of a site in SharePoint to sync the files from the SharePoint site to their desktop.

Working on a presentation, budget sheet or a regular word document is still easier from the desktop applications. And when you are on the go you will not always have internet access which is why you have to be able to access your files offline.

Please remove the restriction for 50 hub sites per tenant (or at least increase it to 500 sites) as there could be many scenarios where one would need more than 50 hub sites particularly the large / multinational enterprise/organisations. For example, Project Management Office (PMO) used to create subsites for a large projects to manage different streams within a single project and would now create Office 365 Groups and I can see PMO could easily use 10 - 20 hub sites.

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

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?

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.

Make it easier to delete sites.