If the user has already accepted the invitation and is unable to login to PartnerCenter, the account may be linked to a personal account:
To resolve the issue, the user will need to rename the personal account (if there are no concerns). There is also a need to clean the up the accounts in the backend. The user will need to be removed from Partner Center and the Azure portal and re-invited to the engagements.
See below for the steps shared with user x@y.com:
1) Admin user to login to PC account->Users
a. https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpartner.microsoft.com%2Fen-us%2Fdashboard%2Faccount%2Fusermanagement&data=01%7C01%7Cv-aifarh%40microsoft.com%7C910df23da99544a2a82508d6d26195ef%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=jfULPC29%2FSmtjJmXbStrS1domQWLGfLnrAMsTHdwSww%3D&reserved=0
2) Remove user (x@y.com) by clicking on the remove link
3) Invite user to PartnerCenter
a. Admin user to login to PC account->Users->Add new user
b. Select invite users and enter x@y.com
c. Grant additional permissions(Collaborate->Manager)
d. Submit
4) If they see the error “User already exists”
a. Global admin user to login to http://portal.azure.com-%3eaad-%3eusers/
b. Remove user (x@y.com) from the AAD tenant
c. The Global admin needs to delete this user completely.
d. Invite user from Partner Center (go to step #3).
When the user accepts the invitation sent to x@y.com. The user will be added to PartnerCenter and also will be added to the AAD tenant (z.onmicrosoft.com).
Note, the above instructions will need to be updated for specific users.