Can’t add my Microsoft 365 (from GoDaddy) account to the Outlook desktop app. Outlook says it can’t connect to sso.godaddy.com and shows HTTP 403.

David Tucker 0 Reputation points
2026-11-06T14:19:39.4733333+00:00

Issue: Can’t add my Microsoft 365 (from GoDaddy) account to the Outlook desktop app. Outlook says it can’t connect to sso.godaddy.com and shows HTTP 403.

What works: Signing in at outlook.office.com in a browser works fine.

Already tried: clearing Windows Credential Manager entries, clearing Edge cookies for GoDaddy and Microsoft, resetting Internet Options with TLS 1.2 and 1.3 enabled, the DisableAADWAM registry fix, and a restart after each change.

I contacted GoDaddy and they said that the issue is with Microsoft and I need to contact them as they have disabled the GoDaddy login page and are working on a fix but that there is nothing that they can do. Is this correct or is there something I can do to fix this issue??? HELP!

Microsoft 365 and Office | Install, redeem, activate | For business | Windows
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-11-06T14:20:50.29+00:00

    Test the GoDaddy Microsoft 365 sign-in endpoint directly; if it returns HTTP 403 outside Outlook, GoDaddy must investigate the hosted account’s SSO configuration rather than repeating local Outlook credential or registry resets.

    1. Isolate the failing authentication boundary

    Open a private browser window and sign in through the GoDaddy Microsoft 365 login page.

    • If this page also returns 403: capture the page, exact time including time zone, affected email domain, and any correlation/request ID shown. Escalate to GoDaddy as “Microsoft 365 SSO HTTP 403 at sso.godaddy.com.” This endpoint is GoDaddy’s login service ^1^, and Microsoft 365 federation redirects authentication to the configured third-party identity provider ^2^.
    • If GoDaddy’s page works but Outlook still gets 403: apply the Windows remediation below.

    Successful access to outlook.office.com confirms that the mailbox is available, but it does not establish that every desktop redirect through GoDaddy SSO is functioning.

    2. Apply GoDaddy’s current Windows remediation

    GoDaddy documents this Outlook for Windows problem as potentially involving an older sign-in experience and directs affected users to update Windows and use the newer sign-in experience. Its current remediation path requires Windows 11 version 24H2 or later ^3^.

    1. Press Windows key + R, enter winver, and note the version.
    2. If it is Windows 11 24H2 or later, go to: Settings → Windows Update → Check for updates.
    3. Install all available cumulative updates and restart Windows.
    4. Open Outlook and add the account again, completing the newer browser-based GoDaddy sign-in when redirected.

    If the PC is on Windows 10 or Windows 11 earlier than 24H2, the applicability requirement for GoDaddy’s documented fix is not met. Do not assume the same remediation is available; ask GoDaddy whether that Windows release remains supported for its current Outlook authentication flow.

    3. Escalate with evidence if the updated client still fails

    Because Credential Manager, browser cookies, Internet Options, DisableAADWAM, and restarts have already been exhausted, do not repeat them. Send GoDaddy:

    • Screenshot of the 403 page with its full hostname.
    • Date, time, and time zone.
    • Result of the direct GoDaddy SSO test.
    • Windows version from winver.
    • Outlook version/build from Outlook → File → Office Account → About Outlook.
    • Confirmation that Outlook on the web works.
    • Confirmation that the failure remains after installing Windows updates.
    • Any request, correlation, or trace ID displayed.

    Ask GoDaddy to escalate specifically to its Microsoft 365 federation/SSO team and verify the account/domain’s redirect and authorization at sso.godaddy.com. The available public information does not confirm GoDaddy’s statement that Microsoft globally disabled its login page; GoDaddy’s SSO endpoint remains the provider-managed redirect involved in this error.

    Continue using Outlook on the web while the SSO case is investigated. Avoid the unrelated Autodiscover registry workaround: Microsoft documents that only when a custom domain’s web server returns an unexpected Autodiscover response, which has not been established by this sso.godaddy.com 403 ^4^.

    References

    1. Microsoft 365 Login - GoDaddy
    2. Integrate Microsoft Entra Agent ID with third-party identity providers
    3. Fix Microsoft 365 sign-in issues with Outlook for Windows - GoDaddy
    4. Something went wrong and Outlook couldn't set up your account | Microsoft Support
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Kristen Tran 2,785 Reputation points Independent Advisor
    2026-11-06T15:00:39.07+00:00

    Hi David,

    I’m sorry you’re still experiencing this issue, especially after you’ve already gone through several troubleshooting steps.

    The AI answer is generally aligned with the appropriate troubleshooting approach. However, I’d like to clarify one important point. GoDaddy currently provides specific guidance for Microsoft 365 sign-in issues in Outlook for Windows. According to their documentation, the recommended fix requires Windows 11 version 24H2 or later and enables the newer WebView2-based sign-in experience.

    You can follow the steps in GoDaddy's official guidance here: Fix Microsoft 365 sign-in issues with Outlook for Windows

    In summary:

    1. Close Outlook and all other Office applications.
    2. Open Registry Editor as administrator.
    3. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AAD
    4. Create a DWORD (32-bit) Value named: WebView2Integration
    5. Set its value to 1.
    6. Restart your computer and try adding the account to Outlook again.

    You should also check Settings > Apps > Installed apps and confirm that Microsoft Edge WebView2 Runtime is installed. If it is missing, GoDaddy's guidance provides a link to Microsoft's WebView2 installer.

    Since you mentioned that you already tried the DisableAADWAM registry setting, there is another important detail to check. GoDaddy advises removing DisableAADWAM, DisableADALatopWAMOverride, and EnableADAL if any of these values exist under:

    HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity

    These settings can cause Outlook to bypass the newer sign-in experience. I recommend backing up the relevant registry key before making any changes.

    If you're running Windows 10 or Windows 11 23H2 or earlier, GoDaddy states that this particular remediation does not apply. In that case, Outlook on the web can be used as a workaround while you check with GoDaddy Support about the authentication options available for your environment.

    If you are already on Windows 11 24H2 or later and the problem continues after completing the steps above, you can also test the GoDaddy Microsoft 365 sign-in page in an InPrivate/Incognito browser window: GoDaddy Microsoft 365 sign-in

    I would not recommend applying the additional Autodiscover registry workaround at this point. That workaround addresses a different scenario where Outlook receives an unexpected Autodiscover response from the domain's web server, which has not been established by the sso.godaddy.com HTTP 403 error you're seeing.

    If the issue still persists after completing GoDaddy's documented remediation, you can also ask your IT administrator to open a support request with Microsoft 365 Support through the Microsoft 365 admin center for further investigation. The steps are available here: Get support - Microsoft 365 admin

    I hope these steps help you restore access to your account in Outlook. If you have any further questions, please feel free to let me know.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.