SOLVED

Teams for Free - "we cannot create a self-service azure ad account for you"

%3CLINGO-SUB%20id%3D%22lingo-sub-2363745%22%20slang%3D%22de-DE%22%3ETeams%20for%20Free%20-%20%22we%20cannot%20create%20a%20self-service%20azure%20ad%20account%20for%20you%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2363745%22%20slang%3D%22de-DE%22%3E%3CP%3EWe're%20using%20Teams%20for%20Free.%20One%20of%20our%20colleagues%20has%20meetings%20with%20external%20contacts%20on%20a%20regular%20basis.%20When%20one%20of%20the%20external%20contacts%20sends%20us%20an%20invitation%20to%20their%20team%20to%20collaborate%20on%20their%20files%2C%20we%20get%20the%20folling%20error%3A%20%22We%20cannot%20create%20a%20self-service%20Azure%20AD%20account%20for%20you%20because%20%22r******.com%22%20%3CEM%3E%20%3CSTRONG%3E%5Bour%20domain%5D%3C%2FSTRONG%3E%20%3C%2FEM%3Ehas%20disabled%20self-service%20account%20sign-up%20by%20email%20validation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20understand%20this%20error%20since%20the%20colleague%20who%20tries%20to%20accept%20the%20invitation%20already%20got%20a%20working%20teams%20account.%20I%20should%20mention%20that%20we%20created%20an%20Office%20365%20tenant%20for%20our%20domain%20a%20couple%20of%20months%20ago%20which%20was%20never%20used.%20A%20couple%20of%20days%20ago%20I%20removed%20our%20domain%20from%20that%20specific%20tenant%2C%20thinking%20that%20would%20solve%20this%20issue.%20Unfortunately%2C%20it%20didn't.%20How%20to%20fix%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2363745%22%20slang%3D%22de-DE%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2367504%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20for%20Free%20-%20%22we%20cannot%20create%20a%20self-service%20azure%20ad%20account%20for%20you%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2367504%22%20slang%3D%22en-US%22%3ESelf%20Service%20sign-up%20is%20most%20likely%20disabled%20in%20the%20previous%20tenant%20that%20owned%20the%20domain%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fenterprise-users%2Fdirectory-self-service-signup%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fenterprise-users%2Fdirectory-self-service-signup%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20may%20need%20to%20readd%20the%20domain%20and%20enable%20it%20or%20ask%20the%20sender%20to%20use%20enable%20OTP%20as%20self-service%20sign%20up%20is%20being%20depreciated%20soon.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fseanmcavinue.net%2F2020%2F12%2F01%2Fmicrosoft-are-removing-support-for-redemption-of-invitations-by-creating-unmanaged-azure-ad-accounts-and-tenants-for-b2b-collaboration-scenario%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fseanmcavinue.net%2F2020%2F12%2F01%2Fmicrosoft-are-removing-support-for-redemption-of-invitations-by-creating-unmanaged-azure-ad-accounts-and-tenants-for-b2b-collaboration-scenario%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E
New Contributor

We're using Teams for Free. One of our colleagues has meetings with external contacts on a regular basis. When one of the external contacts sends us an invitation to their Team to collaborate on their files, we get the folling error: "We cannot create a self-service Azure AD account for you because "r******.com" [our domain] has disabled self-service account sign-up by email validation.

 

I don't understand this error since the colleague who tries to accept the invitation already got a working Teams account. I should mention, that we created an Office 365 tenant for our domain a couple of months ago which was never used. A couple of days ago I removed our domain from that specific tenant, thinking that would solve this issue. Unfortunately, it didn't. How to fix this?

 

Thanks in advance

3 Replies
Self Service sign-up is most likely disabled in the previous tenant that owned the domain:
https://docs.microsoft.com/en-us/azure/active-directory/enterprise-users/directory-self-service-sign...

You may need to readd the domain and enable it or ask the sender to use enable OTP as self-service sign up is being depreciated soon.

https://seanmcavinue.net/2020/12/01/microsoft-are-removing-support-for-redemption-of-invitations-by-...

@SeanMcAvinue 

 

Thank you. I opened a support ticket asked to delete the tenant entirely since it's not in use anyway. Do you think that would solve my problem?

best response confirmed by ThereseSolimeno (Microsoft)
Solution
A support ticket should be able to resolve the issue. I suspect the setting was set at a domain level originally and when the domain was removed this flag was not cleared.