A security update broke our business app, but removing it breaks Office sign-in. What now?

One workaround reported for this kind of issue is to open Office or the document directly, rather than launching it from the affected third-party app. It is clunky, but it may let people keep working without removing the update and creating a separate sign-in problem.

If that does not help, contact your business support channel and the app vendor with the exact update, app version, and what happens when users try to open a document. That gives both sides something concrete to investigate.

I would avoid treating uninstalling the patch as a clean rollback if it also breaks Office authentication in your RDS setup. You are trading one outage for another, and the security change may have other consequences too.

If you have a small staging setup, reproduce the same app, update, and sign-in flow there before making another change in production. If you do not, even a limited pilot with a few representative users can help reveal whether a proposed workaround causes the same auth issue. Not every organization has spare test infrastructure, though, so the safe option depends on what you can actually support.

It is not always possible to tell from the symptoms alone whether the app depends on behavior that changed, or whether the update broke a previously working interaction. The app vendor and Microsoft may both have a part to play. I would keep the report focused on the observable failure rather than guessing which side is at fault.

Since the vendor is already raising the issue and a replacement patch has no clear timing, I would ask them for a status update and a supported temporary procedure. That is more useful than repeatedly removing and reinstalling updates with the same tradeoff.