Accessing Microsoft Teams using organizational or personal credentials
Hello @Jacek Robakiewicz,
Thank you for sharing the screenshots and details.
I’d like to first confirm: are you encountering this error after signing in to Microsoft Teams, or does it happen during the sign‑in process before you can fully access Teams? From the error message shown, it indicates that the account cannot be found in the "CBSG..." tenant. This type of behavior commonly occurs when there is cached information from a previous tenant stored on the device.
To better understand the scenario, could you please clarify whether "CBSG..." is a newly created tenant, or an existing tenant that you’ve used before? If it is an used tenant, I recommend clearing local Teams cache and old credentials to remove any leftover tenant information.
Please try the following steps on your Windows device:
First, sign out of Microsoft Teams and any other Office apps you are currently signed in to. Make sure Teams is completely closed and not running in the background (right‑click the Teams icon in the taskbar and select "Quit").
Next, clear the Microsoft Teams cache by following the steps in this article: Clear the Teams client cache - Microsoft Teams | Microsoft Learn
After that, please clear old credentials stored on the device:
- Press Windows key + S, type Credential Manager, and open it.
- Go to Windows Credentials.
- Remove any entries related to Microsoft 365, Office, or Teams. This will delete cached authentication tokens from the previous tenant.
Additionally, regarding the third login screen shown in your screenshots, could you please confirm which site or application you’re accessing at that moment? Based on experience, it appears you might be signing in via a personal Microsoft account portal, whereas your account is actually a business account.
Instead, please try signing in directly at https://www.office.com using your business credentials, and then access Teams from there.
Once you’ve tried the steps above, please let me know the results and confirm whether the issue persists. This will help narrow down whether the problem is related to cached tenant data or an incorrect sign‑in path.
Kind regards,
If the answer is helpful, please click "Accepted" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.