[axsharma]

This, as others have pointed out via tweets and Tutanota themselves acknowledging the technicality on Reddit, is why I couldn't report on it (we received the blog from them too) and am inclined to believe this is sensationalized.

https://www.reddit.com/r/tutanota/comments/wfu0vk/comment/ij...

Microsoft support can do better, no denying, but to use words like "blocked" and "anti-competitive practice" when a technical issue like this may apply to other domains, not just Tutanota, seems hyperbole.

[judge2020]

They say this

> We asked them to change the domain to a public one, which Microsoft support denied. It must be technically possible, I guess, but here we are.

So I suppose the issue is: when example.com is a verified domain for some AAD organization, users with a live.com account ending @example.com cannot accept invites to become a guest of an external AAD directory (example2.com) due to this error message.

But i'm skeptical if this is MS's problem where they can't downgrade a domain to only allow registrations via `live.com`, or if Tutanota just wants to have the best of both worlds where some email accounts (maybe even employees' personal email accounts) can be manually AAD-registered to allow data governance within their Microsoft 365 organization, while everyone that's not an employee can still create a live.com account and won't have issues joining external AAD directories.