Azure devops opening issue

Hi @Dabhi R Thank you for reaching out to Microsoft Q&A.

When accessing an Azure DevOps organization (for example, https://dev.azure.com/rysun), the error “500 – Something went wrong! We’ve encountered an error and cannot fulfill this request” typically occurs after successful authentication, not before. This issue is most commonly caused by identity conflicts or corrupted authentication state. In real-world scenarios, this happens when the same email address is associated with both a personal Microsoft account and a work (Microsoft Entra ID) account, or when an Azure DevOps organization is recently linked or re-linked to Entra ID. As a result, Azure DevOps is unable to correctly resolve the user identity and fails with a server-side 500 error instead of a standard access-denied message. In some cases, stale or broken sign-in cookies and tokens can also trigger this behavior. If none of the standard sign-out or browser-based steps resolve the issue, the organization is usually left in a broken identity state, which requires Microsoft Azure DevOps backend intervention.

-

Refer below points to resolve this issue or as a workaround

1. Force a complete Azure DevOps sign-out (recommended first step)
Azure DevOps maintains separate authentication cookies, and a normal browser sign-out is often insufficient.

• Open the following URL to sign out globally: https://app.vssps.visualstudio.com/_signout
• Then open this cleanup URL and wait for the green checkmark to appear:
  https://app.vssps.visualstudio.com/_signout?wa=wsignoutcleanup1.0
• Close all browser windows completely.
• Open a new InPrivate / Incognito browser session.
• Access the organization again using:
  https://aex.dev.azure.com/ and select your organization.
• When prompted, explicitly choose “Work or School account”.

2. Verify the correct account type is being used

• Ensure you are not accidentally signing in with a personal Microsoft account when the organization is connected to Microsoft Entra ID.
• Avoid browser auto-login or cached account selection and manually select the correct work account during sign-in.

3. Check for identity conflicts at the organization level

• If you are an org admin (or can contact one), verify there are no duplicate or stale user invitations for the same email address.
• If possible, remove and re-invite the affected user using the correct Entra ID identity.
• In some cases, changing or adding an alternate email alias to avoid personal/work account overlap can help break the conflict.

4. Escalate to the Azure DevOps product team if the issue persists

• If the error continues even after cleanup and correct account selection, this indicates an orphaned or corrupted Azure DevOps organization identity state. Raise a issue here: https://developercommunity.visualstudio.com/AzureDevOps

Use the following steps to troubleshoot access to https://dev.azure.com/rysun when seeing errors during sign-in:

1. Perform a complete sign-out and browser cleanup
   • Go to https://aka.ms/VsSignout to sign out of all Azure DevOps sessions.
   • Clear browser data (cookies, cached images/files, and autofill data) using Ctrl+Shift+Delete.
   • Close all browser windows and any Visual Studio instances.
   • Open a new InPrivate/incognito window and try accessing https://dev.azure.com/rysun again.
2. Verify the correct organization URL and account
   • Ensure the URL format is exactly https://dev.azure.com/rysun.
   • If there are multiple Microsoft accounts (work/school and personal) with the same email, explicitly choose the correct one when prompted.
   • If still blocked, open an InPrivate window, go again to https://aka.ms/VsSignout, then sign in with the intended identity only.
3. Check authentication and permissions
   • Ask the Azure DevOps organization administrator to confirm that the user identity is added to the rysun organization Users list and has at least Read permissions on the organization/project.
   • If the account is a B2B guest, ensure the Microsoft Entra invitation email has been accepted; if not, the tenant admin should resend the invitation and the user must accept it before trying again.
4. Validate network/firewall settings
   • Ensure the corporate firewall or proxy allows outbound HTTPS (port 443) to dev.azure.com and *.dev.azure.com, and to the other Azure DevOps endpoints as required.
   • If on a corporate network, test access from a different network (for example, a personal connection) to rule out network restrictions.
5. If the issue persists
   • Capture a browser trace of the failed sign-in attempt as described in the documentation.
   • Contact Microsoft Support and provide the error timestamp, correlation ID (if shown on the 500 page), the browser trace, and a description of the steps already taken.

References:

• Troubleshoot connecting to a project
• Allowed IP addresses and domain URLs
• Troubleshoot access and permission issues