Hi @Sagar Jade,
Thank you for posting your question to Microsoft Q&A Forum.
The "Something went wrong 4oggx" error typically occurs on Samsung Galaxy devices when attempting to sign into Outlook or Teams due to a conflict during the secure authentication process.
On many Galaxy devices, the Link to Windows app (com.microsoft.appmanager) comes preinstalled and is capable of performing MAM (Mobile Application Management) broker functions.
In environments using App Protection Policies, authentication flows rely on a trusted broker (e.g., Intune Company Portal). However, with older versions of Link to Windows, it incorrectly assumes the broker role and intercepts the authentication process. During this interception, it fails to apply the required policies, which leads to the 4oggx login failure.
As a quick fix, some users found success by installing or updating Microsoft Authenticator before signing into Outlook/Teams.
- Go to Google Play Store > search for Microsoft Authenticator > update or install it
- Afterward, reopen Outlook/Teams and try logging in again
Another workaround for this error code is disabling Samsung’s "Link to Windows" services:
You can disable the Link to Windows Samsung app by going to Settings > Apps > App Info and Connected devices. You should also force-stopped both the Link to Windows app and the Link to Windows Service. 
Since "Link to Windows" app is updated on 19 Nov 2025, please update "Link to Windows" app using Google Play
It redirects you to Company Portal app correctly.
For factory reset devices or out of box devices, check if "Link to Windows" app is the latest version.
Enable developer mode and USB debugging for Android device.
Connect your device using USB cable, and run following command: (download adb from here: https://developer.android.com/tools/adb?hl=en):
adb shell pm disable-user com.microsoft.appmanager
It disables "Link to Windows" app, which app was unexpectedly taking over the broker role.
Then, restart Teams (or other Microsoft 365 application) and login again. Once disabled, running the dumpsys window command again confirmed that Company Portal was now correctly acting as the MAM broker.
If you ever need to re-enable the built-in Link to Windows app, use:
adb shell pm enable com.microsoft.appmanager
I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, feel free to share them in the comments on this post so I can continue to assist you.
I look forward to hearing your thoughts on this.
If the answer is helpful, click "Accept Answer" and vote positively.
Note: Follow the steps in our documentation to enable email notifications if you want to receive email notifications related to this topic.