Follow these steps to troubleshoot the issue where the Azure project page loads but shows nothing:
- Complete sign-out and browser cleanup
- Go to
https://aka.ms/VsSignoutto sign out of all Microsoft identities used with Azure DevOps/Azure. - After sign-out, clear browser data (Ctrl+Shift+Delete):
- Cookies and site data
- Cached images and files
- Autofill form data
- Close all browser windows completely.
- Go to
- Test with a private/incognito session
- Open a new InPrivate/Incognito window in the browser.
- Navigate to the Azure DevOps or Azure portal URL for the project.
- Sign in with the account that should have access to the project.
- Verify correct account and identity
- If there are multiple Microsoft accounts (work/school and personal), ensure sign-in with the account that actually has access to the project.
- If a 401 or access denied–type behavior appears, repeat sign-out using
https://aka.ms/vssignoutand choose a different identity when signing back in.
- Check access and permissions to the project
- Confirm that the account is a member of the correct Azure DevOps organization/project and has at least Project access.
- If the project still appears blank, an administrator should verify:
- Access level supports the service/feature being opened.
- The user is not in a restricted security group (for example, project-scoped or limited-scope group) that blocks access.
- No explicit deny permissions are set for that user or group.
- The relevant service (Boards/Repos/Pipelines, etc.) is not disabled at project or collection level.
- After any permission changes, refresh the browser so the new permissions are recognized.
- Network and environment checks
- If using a corporate network, test from a different network (for example, home or mobile hotspot) to rule out proxy/firewall issues.
- Ensure the corporate proxy or firewall allows access to Azure DevOps endpoints (for example,
*.visualstudio.com,*.azure.com).
- If the project is opened via Visual Studio
- In Visual Studio, remove existing Azure DevOps connections from Team Explorer.
- Clear cached credentials from Windows Credential Manager.
- Restart Visual Studio and add the Azure DevOps connection again using the correct account.
- Collect diagnostics and contact support if still failing
- Capture a browser trace of the failed load following the guidance in the connection troubleshooting article.
- Create a support request and include:
- Exact organization/project URL.
- Date/time and time zone of the failed attempts.
- Steps already tried (browsers, private mode, sign-out, cache clear, account used).
- Browser trace files and screenshots of the blank/failed page.
These steps address the most common causes: cached/incorrect identities, browser issues, missing permissions, and network restrictions.
References: