Change the sharepoint.aspx page

Almost a year ago I asked :

"Where is the data pulled from and why does Msft think anyone would want to see this?"

I still don't have an answer. I don't know what the problem is with answering that, but pretty clearly we are dealing with a dysfunctional company that has been unable to deal with the way the world has changed, as evidenced by the sharepoint.aspx page which it seems obvious to everyone but Msft is screwed up. Failing to acknowledge mistakes and continuing to repeat them is sure sign of corporate madness.

This really is astonishing disregard for product pride and customer satisfaction by Microsoft.

There must be some horrific politics or arrogance in Msft for the senior management not to see or react to this sort of thing.

It makes you understand why Satya Nadella asked the competition how they were dealing with the Intel firmware power management bugs that were screwing his Surface products, only to be told by the competition that it was not Intel's fault but his own Msft driver developers.

There is something very deeply flawed with authority and power that ruins collaborative effort.  Why can't someone just bang on the top man's door with the 100 or so excruciating issues like this one, and just nail them?  Why does power always have to find out by accident?  Or when defeated by the competition, like:  Windows Mobile, IE / Edge, Zune, etc., etc., etc.

Just imagine what the consumer, user, admin, pro, developer experience would be like if the top 100 "excruciations" were nailed?  The effected products would not just survive in the market, but thrive.

Office 365 / Azure is Msft's last bastion.  The competition has over-run you everywhere else.  If you screw this one up you're dead in the water.

I have shared my URLs and trace logs on another thread and still nothing..  Microsoft has to know where the aspx page gets its data from and should be able to fix this!.

There's no need to provide a url  - an individual tenant will not reveal anything because this is a system wide problem now almost a year old.  Msft refuses to acknowledge it's a design flaw and seems to be in denial. I'm going to have all the users that complain to me start posting here and maybe when there are several 1000 threads, Msft will notice them, though that's also doubtful.