Forum Discussion
Reset guest redemption status not possible after creating Multitenant Organization (MTO)
Hi all, we're on the path to creating a Multitenant Organization (MTO) for our global organization.
We already have a relationship with one partner tenant which has B2B Collaboration and B2B Direct Connect set-up and is working well.
We took the step of creating a Multitenant Organization in our 365 admin center and started testing with a sandbox tenant, which has since been removed.
The issue we are having now, is that guest users which are not part of B2B Collaboration or an MTO cannot have their redemption status reset.
I first found this wasn't possible from the error in a Power Automate workflow using Microsoft Graph, then confirmed I got the same error in Entra ID.
The documentation for MTO was updated a few days ago and includes this, saying that as part of a multitenant organization, reset redemption for an already redeemed B2B user is currently disabled.
But should this be the case for guest users not part of B2B Collaboration or Multitenant? Is this an error or expected behaviour, I wonder?
Thanks!
Same issue here.
Has anyone been able to reverse the Multi Tenant Configuration (MTO) so that the reset redemption status function works again?
It seems to only affect identities of the type ExternalAzureAD. Identities of the type MicrosoftAccount and mail still work.
However, most external users have an ExternalAzureAD identity, which is why the function is urgently needed. It must be possible to reverse the MTO configuration. Unfortunately, Microsoft Support has not been able to help so far.
Has anyone ever successfully reversed the MTO configuration? What happens if I delete the owner tenant from the MTO configuration? Does it have any impact or side effects on other tenant-wide functionality? Is the status then reset, so that the reset redemption status function works again for ExternalAzureAD guest accounts? The tenants with the member role have already been removed from the MTO configuration, but without any effect. The reset redemption status still indicates that it is not possible due to the MTO configuration, as Alasdair mentioned.Same here.
Has anyone been able to reverse the Multi Tenant Configuration so that the reset redemption status function works again?It seems to only affect identities of the type ExternalAzureAD. Identities of the type MicrosoftAccount and mail still work.
However, most external users have an ExternalAzureAD identity, which is why the function is urgently needed. It must be possible to reverse the MTO configuration. Unfortunately, Microsoft Support has not been able to help so far.
Has anyone ever successfully reversed the MTO configuration? What happens if I delete the owner tenant from the MTO configuration? Does it have any impact or side effects on other tenant-wide functionality? Is the status then reset, so that the reset redemption status function works again for ExternalAzureAD guest accounts? The tenants with the member role have already been removed from the MTO configuration, but without any effect. The reset redemption status still indicates that it is not possible due to the MTO configuration, as Alasdair mentioned.
The only workaround I currently know is to convert the external account to an internal account and then back to an external account again. This sets the external account back to invitation state: pending acceptance, and the user receives a new invitation message from the tenant. However, I'm not sure if this has any unknown side effects, so use it with caution.
Thanks.
Hi,
We have also started experiencing the same issue. Has a resolution been found yet?
