Typical at large, highly-corporate places I'm afraid.
I recall during one of my first internships (at Siemens, not Microsoft) my first task was to go over test results of electric motors being developed. I drafted an email with my results and fired it off to a number of people.
A short while later I was ushered off by one of the senior project managers. "Why'd you write that email?" "Um...?" "You don't call these things PROBLEMS, you call them ISSUES. Do you understand? You call them problems, people are going to think there are problems!"
And that was the moment I decided I wanted nothing to do with traditional engineering and the automative industry... unfortunately I had another 3.99 months to go on that internship at that point. The rest of the internship didn't go any better, and is still a massive source of antipatterns I still draw from today.
Funny note, those "issues" ended up costing the company millions in a product recall. Maybe they should've been called "problems" instead ;)
The neutering of language into corporate-speak is still one of the biggest red flags I look for when interviewing...