Share via

Microsoft 365 Developer E5 sandbox active but all sign-ins redirect to login

Matthew Helm 0 Reputation points
2026-05-04T21:19:45.8633333+00:00

My Microsoft 365 Developer Program E5 sandbox shows Active with remaining days, but all sign-ins fail across admin.microsoft.com, portal.office.com, and myaccount.microsoft.com. Authentication succeeds, then immediately redirects back to the login page with no error. The Microsoft 365 Developer Program support URLs return 404 and cannot be used. Tenant: [Moderator note: personal info removed] Admin: [Moderator note: personal info removed] Request escalation to the Microsoft 365 Developer Program team to verify tenant identity status.

Microsoft 365 and Office | Development | Microsoft 365 Developer Program
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Hani-Ng 11,825 Reputation points Microsoft External Staff Moderator
    2026-05-05T00:53:15.7733333+00:00

    Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

    Hi Matthew Helm

    Since this is a user‑to‑user support forum, so while members can share advice and experiences only, we do not have access to Microsoft 365 Developer Program backend systems. As such, we’re unable to escalate cases on behalf of users.  

    Based on your description, the first steps you could try are:

    • Use a Private Window: Try logging in with an InPrivate (Edge) or Incognito (Chrome) window.
    • Clear Cache: If it still persists, clear your browser's cache and cookies for "All time."
    • Switch Browsers: Try logging in with a different browser entirely (ex: use Edge if you normally use Chrome).

    Can you log in normally to Entra or the Azure portal? If yes, you can try creating a support ticket through these portals to reach out to the Microsoft support team.

    If you still cannot log in to Entra or the Azure portal, as a workaround you may consider creating a temporary Microsoft 365 tenant using a trial license.

    undefined

    • Once the new business account is created, sign in to the Microsoft 365 Admin Center and submit a support ticket directly. 

    More details on how to get help from Microsoft 365 support can be found here: Get support - Microsoft 365 admin | Microsoft Learn 

    Just a quick note: If you go with the trial account option, please be sure to cancel the subscription after resolving your issue to prevent unexpected charges.

    I hope this information helps.

    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.

    Was this answer helpful?

  2. AI answer

    2026-05-04T21:19:57.3033333+00:00

    The behavior described matches a sign-in loop where authentication succeeds but redirects back to the login page without error. The context provides two relevant angles: general sign-in loop troubleshooting and Developer Program/tenant status.

    1. Verify browser security and cookie settings
      • Ensure the following sites are not in the browser’s Trusted Sites list (for Internet Explorer or Microsoft Edge using IE-mode security zones), or if one must be trusted, ensure all are trusted together so cookies can be shared correctly:
        • microsoft.com
        • support.microsoft.com and any subdomains
        • login.live.com
        • login.microsoftonline.com
      • This aligns with the documented workaround for sign-in loops where the page appears to redirect but reloads the same authentication page.
    2. Confirm account and program compliance
      • The Microsoft 365 Developer Program requires adherence to its Terms and conditions. Accounts that violate these terms may be blocked from signing in to the Developer Program dashboard.
      • If the Developer E5 subscription is still shown as active with remaining days in the Developer Program dashboard, the tenant itself is likely still provisioned, but there may be an account or policy issue affecting sign-in.
    3. Check for Developer Program-specific issues
      • If the tenant was created as an instant sandbox between May 31, 2023 and June 5, 2023, there is a known issue where the tenant cannot be accessed. In that case, the documented resolution is:
        • Go to the Microsoft 365 Developer Program dashboard and sign in with the Developer Program account.
        • Choose Set up subscription to get a new instant sandbox.
        • Sign in with the new admin account within 14 days.
    4. Escalation path
      • For issues where the subscription appears active but sign-in fails or eligibility/status is inconsistent, the documented pattern is to open a support ticket and have it escalated to the backend/Developer Program infrastructure team. In similar cases, resolution was achieved only after backend validation/sync by internal teams.
      • Because direct escalation to the Microsoft 365 Developer Program team cannot be performed here, the practical next step is:
        • Use any available Microsoft support channel (for example, via another working tenant or general Microsoft support entry point) to open a support case.
        • Clearly state that this is a Microsoft 365 Developer Program E5 sandbox, that the dashboard shows the subscription as active, but all sign-ins to admin.microsoft.com, portal.office.com, and myaccount.microsoft.com result in a login loop with no error.
        • Request that the case be routed to the Microsoft 365 Developer Program / M365 Dev Portals and Infrastructure team or equivalent backend team to verify the tenant’s identity and status.
    5. If Developer Program dashboard itself is inaccessible
      • If sign-in to the Developer Program dashboard is also blocked, and standard sign-in loop troubleshooting (cookie/trusted sites adjustments) does not resolve it, this aligns with scenarios where only Microsoft support and backend teams can correct the tenant or account state.

    Given the constraints of the context, direct identity/tenant verification or manual escalation cannot be performed here. Resolution requires a Microsoft support case so backend teams can validate and, if necessary, repair the Developer Program tenant status.

    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.