Why has there been a 50% increasing the price of Microsoft 365 Personal? This is an extraordinary increase and unaffordable for most people .

I am a disability pensioner and student. A large increase of 50% affects me. Especially when we are forced to take on Ai, it should be optional.

It is not about my ability to afford. It is the fact that the price has risen 50%! Nothing to do with price rises since 2013? What are you chatting about! A simple charge was all we had as a one off! You have taken the liberty of the everyday user for extra software most do not require? Why should people have to pay the hike for your additional stuff?

I am going to speak to a body that can investigate this from Microsoft as it is not right.

Go into your account and then follow the instructions from elsewhere on this thread.

I can't find my way around the site to find help, the answers are pre scripted and do not answer my query. I can't find a phone number to call.

I don't think it's most of us complaining because of financial constraints. I'd be hard pressed to find anyone who pays the subscription that would suddenly find themselves without food or housing because of a 30 dollar a year increase.

I think it's more the fact that suddenly what was 66 is now going to be 99 because of the unwanted addition of the copilot feature. I know of nobody who wants this in Office - and I have over a thousand clients on various flavors of 365. Most are complaining about the intrusion of the Copilot **** in their daily work.

And the people who are using THESE cheaper versions are even less likely to want to pay the increase for something that's more of a pain than a feature.

People aren't complaining about it because if they pay they can't afford to eat anymore. They're complaining because it was Microsoft suddenly demanding everyone pay for something they didn't ask for in the first place.

Everyone is tired of the way MS forces THEIR changes on people without ever considering if that's what the population even wants... This was just more of the same. Fortunately, there ended up being a solution for this particular bit of Microsoft shortsighted stupidity...