I was again quite busy at work so had not that time to blog, which will result that I will loose my MVP at the end of June.
Hopefully I will find the time to blog more from now on, again.
I got some comments also from a customer that starting at end of may my blog post about
“How to bulk invite B2B user” stops working.
Investigating this it seems Microsoft has done some updates to be compliant with GDPR.
However there was no notice before this change so one customer ran into issues while in a larger migration project.
What I can say for sure is, the described way I wrote about in my blog post will no longer work, Azure AD B2B bulk invite without redemption has gone.
But good news:
The new implementation in quite easier with some challenges as you can see in the
“Updated Azure AD B2B redemption documentation”
So here are the changes compared to the old solution:
- You don’t need an account in the tenant you are about to invite users from (source tenant)
- You just need at least guest inviter role in your tenant, like before
- You don’t need to send out the invitation mail with the redemption link, users can directly go to the resource and accept the new consent screen (GDPR)
- You can still invite MSA account and also now google accounts.
- If you invite a user who does not have an Azure AD (work/school account) the user is forced to create a MSA account
- This means NO viral/unmanaged tenant is created any more (great news)
So as a conclusion, just bulk invite (PowerShell or Graph API) as many guests as you need without sending the invitation mail and users can just accept the consent screen which does the redemption automatically.
However, I find that this current behavior has some not so nice side effects:
- If you invite a user without a tenant, the user need to create a MSA
- If the company of that user decide to use Azure AD in the future, those users will have an MSA with the same mail address at the work/school account.
Which in fact is not possible currently to create and also not recommended. In fact most of us created a mail alias to get the MSA away from the work account.
- If the user wants to use their new work/school account you currently need to delete and invite the user again with his work/school account.
Hope there will be an update that addresses this issue in the near future and that the above information cleared up some things for you guys.