Permit OTP for users who do have a corresponding Azure AD account
We sometimes encounter situations where a user may actually have an existing Azure AD account (in another tenant) or and MSA - but we want to invite them as an OTP user.
The reason for this - using the existing AAD account as an example - is that this may be an account that is the product of some abandoned POC that this other org did. And as a result, the user does not know the password and SSPR may not be enabled. The result is that the user is unable to redeem a non-OTP invite.
For best flexibility, maybe the b2b invite api should just permit forcing an OTP or non-OTP invite on a case by case basis. i.e. so that we can work around issues like the example above - or force MSA creation - whatever suits the case.
Daniel Askin commented
Need the ability to specify OTP as authentication method for Guests. Leaving this decision with Microsoft with no visibility means we do not know with certainty what method the user will be asked to use. We have seen several scenarios where guest users are already MS/O365 tenants but this is unknown to them and they do not then know how to reset passwords etc. as no policy/administrator is defined.