Error 80048163 when Federated user signs in to Microsoft 365

This put up options options to repair error 80048163 when a federated user tries to signal in to Microsoft 365. The error happens if the authentication for the federated user is unsuccessful. The error message reads:

Sorry, however we’re having bother signing you in
Please strive once more in a couple of minutes. If this doesn’t work, you may want to contact your admin and report the next error: 80048163

Happily, you possibly can comply with these solutions to repair it.

Repair Error 80048163 when a federated user tries to signal in to Microsoft 365

To repair the error 80048163 when signing into Microsoft 365, confirm federation configuration and disable LSA. Apart from that, comply with these solutions:

1. Confirm Federation Configuration
2. Disable Native Safety Authority (LSA) credential caching
3. Replace the relying social gathering belief with Azure AD
4. Disable VPN/Proxy

Now let’s see these in element.

1] Confirm Federation Configuration

Begin by checking in case your group’s federated area settings are configured accurately. Double-check if the settings align with the necessities specified by Microsoft 365 and see if the error 80048163 will get fastened.

2] Disable Native Safety Authority (LSA) credential caching

Disabling Energetic Listing credential data caching will replace the LSA cache time-out setting. It might assist repair the error 80048163 however add further load on the server and Energetic Listing. Right here’s how:

1. Click on on Begin, sort regedit and hit Enter.
2. As soon as the Registry Editor opens, navigate to the next path:

   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa

3. Proper-click on Lsa, choose New after which click on on DWORD Worth.
4. Kind LsaLookupCacheMaxSize, and hit Enter to identify the brand new worth.
5. Now, right-click on LsaLookupCacheMaxSize, and choose Modify.
6. Set the Worth Knowledge as 0 and click on on Okay to save the adjustments.
7. As soon as carried out, Restart your system and see if the Microsoft 365 sign-in error will get fastened.

3] Replace the relying social gathering belief with Azure AD

Subsequent, strive updating the social gathering belief with Azure AD. Doing so may help repair the error 80048163 when a federated user tries signing in to Microsoft 365. Right here’s how one can replace the configuration of the federated area on a domain-joined system with Azure Energetic Listing Module:

1. Click on on Begin, search Home windows Azure Energetic Listing, and click on on Home windows Azure Energetic Listing Module for Home windows PowerShell.
2. Kind the next instructions one after the other and hit Enter:

   $cred = get-credential
   Join-MSOLService –credential:$cred
   Set-MSOLADFSContext –Laptop: 
   Replace-MSOLFederatedDomain –DomainName: 
   Replace-MSOLFederatedDomain –DomainName:  –supportmultipledomain

3. As soon as carried out, strive logging into Microsoft 365 once more.

4] Disable VPN/Proxy

Lastly, disable VPN or Proxy should you’re utilizing one to repair the error. It’s because error 80048163 can happen if you’re linked to a VPN/Proxy server. These conceal the IP handle by rerouting Web visitors through a distant server. However, right here is how one can disable it:

1. Press the Home windows key + I to open Settings.
2. Navigate to Community & Web > Proxy.
3. Right here, toggle off the Routinely detect settings possibility.
4. Click on on the Arrange possibility subsequent to Use a proxy server and toggle off the Use a proxy server possibility.

Learn: Repair 30015-4 (5), 0x4004f00d, 30175-11, Entry denied to set up supply, Workplace error

We hope this helped you.

What’s federated identification in Workplace 365?

Federated Identification in Workplace 365 is an authentication technique that enables customers to use the Workplace servers utilizing organizational credentials. It will assist customers leverage their present credentials from their group’s identification supplier (IdP) to entry the companies.

What’s error code 30183 2016 403 when putting in Workplace 365?

To repair the error code 30183 2016 403 when putting in Workplace 365, verify Workplace servers and your account credentials. If that doesn’t assist, strive putting in Workplace in Clear boot mode.