Accessing Microsoft Teams using organizational or personal credentials
Based on the information provided, I understand that you want to use your company account, Email A, only within Microsoft Teams on your privately owned laptop, while keeping Windows and all other Microsoft apps associated exclusively with your personal account, Email B.
The repeated “We need you to sign in again” message began after you declined the Windows Hello prompt. Error 2148073526, which corresponds to 0x80090036, appears to be occurring during the Windows authentication stage. In other words, Teams is not completing the work-account authentication and therefore does not receive a valid sign-in token. Repairing Teams may not resolve this because the interrupted authentication state can be stored by Windows rather than solely within the Teams application.
Please try to clean up the partial state first
1.Settings > Accounts > Access work or school. If Email A is listed, select it and Disconnect.
2.Settings > Accounts > Email & accounts. Remove Email A if present.
3.Quit Teams completely (right-click the tray icon > Quit).
4.Open Credential Manager >Windows Credentials. Delete entries referencing MicrosoftOffice16_Data, msteams, MicrosoftAccount:target=SSO_POP_Device, or your work domain.
5.Delete the Teams cache: %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache
6.Reboot > Sign in correctly
Open Teams, enter Email A, complete your password and MFA. Then choose “Stay signed in to all your apps” > click No, sign in to this app only > “Use Windows Hello with your account” or a PIN setup screen > choose Skip for now, or Other ways to sign in / Use my password. Don’t press the X or Cancel; use the skip option, or you’ll land back on 0x80090036.
Teams will hold its own token. Windows stays on Email B, and Email A won’t appear in Access work or school, Windows Hello, Outlook, or OneDrive.
If your organization’s Conditional Access policy requires a compliant or registered device, none of the above will work and you’ll see an error saying your device must be managed. That’s a tenant-side setting no local change can bypass, and you’d need to raise it with your IT team.
Let me know which prompt you land on and I can narrow it down further.