I'm curious about how Managed Security Service Providers (MSSPs) are dealing with the challenge of the 100 tenant limitation in the multi-tenant management portal at mto.security.microsoft.com. I currently manage 150 Azure tenants, each with their own subscription and Sentinel. With Sentinel moving to Defender, I'm looking into how support will work since Defender's multi-tenant platform also only allows for 100 tenants. I'm hopeful that Microsoft will increase this limit before Sentinel's UI gets retired next July. What strategies do you all recommend for managing the extra tenants?
3 Answers
We’ve got a tidy solution that doesn't require any duct tape and actually supports real multi-tenancy accounts. It's built specifically for MSSPs. If you're interested, just let me know!
One approach you could take is to create multiple MTO admin accounts for different sectors or regions. This way, you can segment your tenants without hitting the limit. Definitely raise your concerns through your partner channel—Microsoft might have to address this limit by the time they retire the Sentinel UI in July!
Could you clarify what you mean by 'multiple MTO accounts'? I'm not sure I fully understand. Any extra details would help!
I realize my wording was a bit unclear! Basically, you create several tenants for different sectors or regions and manage the customers under these hubs. Instead of using B2B guest accounts, you can copy policies and manage things using a local admin in that tenant. It shouldn't really add extra costs. You could have one self-owned tenant and then create more, dividing your client base however you like. Honestly, the 100 tenant limit is pretty ridiculous! A bit of a hacky solution could be to just use different browsers for each tenant—like Chrome for one and Firefox for another—so you don’t have to switch accounts all the time! Good luck!
That sounds awesome!!