Share via

Correlation id: cdd3d46c-6571-4ad3-9a26-938df4b90adb

Scott Matlou 0 Reputation points
2026-03-30T12:01:22.6033333+00:00

Hello Sridevi,

Thank you for responding.

The error occurs when attempting to log into Microsoft Partner Center at partner.microsoft.com — not the Azure Portal.

Full details:

Error code: AADSTS5000228

Error message: "The user account does not exist in the tenant"

Tenant attempting to access: [******@axltecptyltd.onmicrosoft.com] (Tenant ID: 7ac4df4e-a945-450a-935e-6e2b987b7c01)

Root cause (as I understand it): There is an older, incomplete tenant created during a previous registration attempt — axltec.onmicrosoft.com — that appears to be conflicting with the new tenant. The old tenant was never fully configured and has no active MPN registration, but it is blocking access to the new one.

What I am trying to do: Complete MPN (Microsoft AI Cloud Partner Program) registration under the new tenant [******@axltecptyltd.onmicrosoft.com] in order to obtain an MPN ID and activate a CSP reseller agreement through Tarsus Distribution.

What I have already tried:

Logging in via InPrivate/Incognito browser — same error

Clearing all browser cache and cookies — same error

Attempting login from a different device — same error

Request: I need the old incomplete tenant (axltec.onmicrosoft.com) either disassociated from my account or deleted, so that the new tenant can proceed through Partner Center registration without conflict.

Correlation IDs for reference:

019d2fd3-51cd-7123-86c7-d38988481559 (27 March 2026)

f8ac5216-74ca-40a1-91db-bd1d49942ac8 (29 March 2026)

Please advise on the correct escalation path to resolve the tenant conflict. I am happy to verify account ownership through any required process.

Thank you, Scott Elijah Matlou Director, AXLTEC (Pty) Ltd [******@axltec.co.za] | +27 83 626 2252

Keep your account secure

Error image This might be due to timeout or something else. Please try again or contact your admin and share your troubleshooting details.

Troubleshooting details Error code: BadRequest

Correlation id: cdd3d46c-6571-4ad3-9a26-938df4b90adb

Timestamp: 2026-03-30T11:59:20.8084844Z

Microsoft Partner Center | Other

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-03-30T12:01:36.31+00:00

    The error message shows a generic BadRequest during a Microsoft Entra sign-in/security prompt and provides a correlation ID and timestamp. The correlation ID itself cannot be used directly to fix the issue; it is used by an administrator to trace the failing request in logs.

    Steps to resolve:

    1. If this is an end user scenario:
      • Retry the operation once or twice in case it was a transient timeout.
      • If the problem persists, contact the organization’s helpdesk or IT administrator and provide:
        • Error code: BadRequest
        • Correlation ID: cdd3d46c-6571-4ad3-9a26-938df4b90adb
        • Timestamp: 2026-03-30T11:59:20.8084844Z
      • The admin can then investigate using Microsoft Entra sign-in logs and other diagnostics.
    2. If this is an admin/IT Pro scenario:
      • Use the correlation ID and timestamp to locate the relevant entry in the service logs:
        • For SharePoint/ULS-style scenarios, locate the ULS logs for the time of the event and search for the correlation ID across the web front ends until a match is found. The correlation ID will not directly fix the error but will show what happened immediately before and during the failure, including any detailed error messages.
      • Use a log viewing tool (for example, ULSViewer in SharePoint scenarios) to filter by correlation ID and event level to narrow down the cause.
      • For Microsoft Entra sign-in issues, review the sign-in logs around the provided timestamp to identify whether the BadRequest is due to misconfiguration (for example, MFA, conditional access, or application settings) or unusual activity.

    If repeated sign-in attempts are being made and MFA is involved, Microsoft Entra multifactor authentication may temporarily block additional attempts when unusual activity is detected. In that case:

    • Wait before trying again, or
    • Use a different MFA method if available, and
    • If suspicious activity is suspected, investigate via Microsoft Entra sign-in logs and adjust MFA/conditional access configuration as needed.

    If the issue continues after these steps, escalate through the organization’s normal support channels with the correlation ID, timestamp, and any sign-in log details collected.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.