The MSISDN is already registered to another IAM user account

TheBeerGenius wrote:

TheBeerGenius wrote:

Exact same problem as of 7/12/2022.  Almost the same case as those above -- returning customer from an experiment with a different carrier (trying to save a few bucks); well, their [the other carrier] service sucked and I am coming back to T-Mobile after about a 4 month break in service.  

But, I have been on the phone with 611 for the past 30 minutes and I have even given them the link to this Community post -- it seems that they *STILL* don’t have a use case in their playbook for how to remedy this.  

I will update this post if I ever get resolution. 

Ok, so without any help from T-Mobile (611)… sorry to say, but they are nice, chipper, and well-meaning, but some are ill-equipped to handle this (and the word "expert" is thrown around too liberally).  So, I finally got access to my account.  I ultimately kept clicking on different ways to login (with a user ID, my phone, and of course my old email address that was linked).  

Now, I apologize if this gets gray, but sadly I didn't write down all of these steps that got me access, but here's a rundown from what I can remember.  Through trying to login different ways, e.g., forgot password, or using my phone number, or using an older username I found, I ultimately got to an error page that told me that "the email account you just used is already in use, would you like to use this email address to manage multiple T-Mobile accounts?"  I clicked YES and within a few more two-factor checks (text to my phone number) and verifying an answer to a security question I had on file -- I was able to get to my account!  I was then able to set up a two-factor Authenticator app again (T-Mobile wants you to use Google Authenticator, but any app that can scan a QR code will work -- I am using the MS Authenticator app since all of my other accounts requiring two-factor are in there).  

So, lesson learned from an Identity Access Management (IAM) stance -- T-Mobile doesn't seem to understand that some people prefer to use only one email address and that their account binding process doesn't work when someone leaves and then comes back.  In the IAM world, this is the MLJ issue (MLJ stands for Move, Leave, Join).  Since this user ID isn't used anywhere else, it's not a Federation issue… it's just crappy IAM management.  

Well, good luck to you guys!  I am in and I was able to map to my NetFlix account and pick up the free year of Paramount+.  

¡Saludos!
Scott a.k.a TheBeerGenius

 

You are the man Scott!

This was frustrating me for a while.  I was finally on hold for technical support when I came across this post. 

For anyone that is still having problem with this issue:

Get to the screen where you can select sign up.  Sign up normally.  Then select yes when asked if you want to use your XXX email to manage all of your TMobile accounts.  Voila!