Carol_R:
Thank you for your reply.
I must admit that this has been a most painful experience.
Basically, it has taken Microsoft OVER FIVE MONTHS to finally tell me that they acknowledge the problem I have reported, they have reproduced it, but they have
no current plans to fix the problem.
I may not like the final response (i.e., that Microsoft has no plans on fixing the issue), but what I find to be totally unacceptable and unprofessional is the fact that it took Microsoft
OVER FIVE MONTHS to provide a response that should have been provided within a month or less!!!!
Part of the delay was due to Forum Moderators not understanding the issue I was describing, which required significant persistence on my part to convince Forum Mods to reproduce the problem themselves. This (getting Forum Mods to reproduce the issue) should
not have been so difficult to accomplish. Forum Mods need better training in troubleshooting customer's issues.
Another part of the delay (once the problem I described was reproduced by Forum Mods) was the lack of a timely response from Microsoft's Engineers. They need better training in the importance of providing feedback to customers who have taken the trouble of
documenting a bug for them.
I realize that this is not personally your fault ... so please just pass my dissatisfaction back to your management (including Jennifer) and their contacts at Microsoft. Microsoft's unprofessional behavior (FIVE MONTHS to respond) truly discourages people from
reporting bugs ... but perhaps that is their intention!
Finally, I have unmarked your response as an "answer". I would like to leave this thread unanswered until such time that a fix for this issue becomes available in a future release of Outlook.com. When such a fix is available, just post a response in this thread.
I will gladly test the fix, and if the problem is resolved, I will mark this thread as answered.