After my initial input I have more things to say. There is no techincal systems that will fix the issues on MSFT culture with documentation ticket handling. Let me show two examples for one particular issue:
https://github.com/MicrosoftDocs/azure-docs/issues/108679
- Closed in five days
- Did not get any comments if the issue is real
- No real feedback at all
https://github.com/MicrosoftDocs/azure-docs/issues/108023
- same issue by different author
- initial feeback from MSFT in 4 days
- then full silence except for one internal ping
- multiple users were telling that they have same issue. Some users even provided HTTP requests payloads and correlation ids
- after 11 months issue was just closed without any explanation if issue has been worked at all (re-opened after request)
- finally some third_party user told in the thread that limitation is fixed and the change is being deployed into Azure regions
I tried also get some escalation through @AzureSupport on Twitter. Result:
- They won't read or ping stakeholders about issues in https://github.com/MicrosoftDocs/azure-docs/
- They asked me to post my question into QA site and promised to ping relevant stakeholders
- After multiple requests they promised to escalate ticket internally => nobody from MSFT updated ticket or contacted otherwise for more information
On QA site: https://learn.microsoft.com/en-us/answers/questions/1485199/azure-container-instances-with-managed-identities
- Two responses from MSFT. Mostly telling that content author is AWOL is too busy
On other QA site related discussion @AzureSupport on Twitter told following
- QA site is community driven and stakeholders might notice the thread if it gets enough upvotes (= interpretation of mine: they won't do escalation)
-----
For me it looks like upcoming change is just to hide all missing interactions. If feedback platform is designed for one-way communications then users reporting issues will not see:
- The fact that nobody is working with tickets
- And the fact that ticket is being closed just because it is too old even nobdy has been worked with it or escalted issue to relevant stakeholder on PG
This is really sneaky way to increase average customer experience by hiding absence of feedback loops.