Said It Here

How to manage software updates across multiple client accounts

Software updates and new features do not automatically roll out across multiple client tenants, forcing administrators to manually check blogs, reauthorize changes by hand, and track mismatched versions across different environments. This lack of centralized notifications and bulk management tools makes it impossible to efficiently verify what is fully updated without checking every account individually.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    Reading vendor blogs after every update and manually reauthorizing each tenant one by one by hand
  2. 2
    Looking for alternative vendor products
  3. 3
    Writing a custom script to automatically download, extract, and launch the correct version based on the launch string.

In their words

Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.

r/msp2 people · September 2026

“New features Avanan adds don't automatically get added to your tenants... you have to reauthorize them, manually, each time, by hand.”source ↗

“There's no way to do it faster, no way to check which ones are fully updated, and no way to know when you need to do it, except to read their blog every time they post an update then go check your tenants and see if the new feature is there?”source ↗

Vyper28 · r/msp · 11 upvotes

“I'm using NinjaOne over multiple environments, and I ran into a problem today where my main instance updated the viewer to version 15, but another one I use for a different client is still on viewer version 14.”source ↗

JediMasterSeamus · r/msp · 5 upvotes

Where this came up

r/mspit managementsoftware managementsoftware updatesvendor communication

People with this problem also raised