New Outlook: Users Say It's Broken—Microsoft response.

Sadly, we may have to turn off the new Outlook client in our tenant due to the inability to manage signatures for 13k users. There is a major operational gap between classic Outlook and new Outlook.

In classic Outlook, we can automate signature updates using PowerShell and SCCM, ensuring consistent branding and compliance across business units. With the new Outlook storing signatures in the cloud and removing local file access, we’ve lost the ability to:

• Deploy HTML signatures with dynamic AD attributes
• Enforce branding and legal disclaimers
• Manage signatures without relying on costly third-party tools

This issue affects not just branding, but legal compliance and user experience. In order to continue down the path of new Outlook in our tenant, at minimum we need either the ability to manage it or a no-cost add-in that covers this gap.

Never heard an actual answer as to why Outlook "new" is being forced upon users. Why the insecurity around your products that you feel you have to force people to use your products?

It used to be Microsoft products were well received with tech articles touting features and users would adopt because they wanted to. But now it feels like you know how inadequate and poorly implemented they are now that you have to force them upon users. Outlook "new" isn't the only product Microsoft is forcing upon their users, but it really shows how the developers at Microsoft are out of touch with their user base. Of course maybe these decisions are made by MBA types at Microsoft who have no clue at the history of Microsoft or their user base.

And it's laughable to say you have 10s of millions of users who've switched, when you FORCE the switch. Do you take that in account with your numbers? I was FORCED on my home machines to switch, and switched back. Do you consider those scenarios with your numbers?