NOt able to access PII

Question

NOt able to access PII

Pellegrini, Laura 0

I'm not able to access this link ///Personal information

Siddhesh Desai 8,210 Reputation points Microsoft External Staff Moderator

2026-06-16T09:15:34.2033333+00:00
Hi @Pellegrini, Laura

Thank you for reaching out to Microsoft Q&A.

The issue with accessing the provided URL is most likely because tfs.azure.bakerhughes.com is a legacy Azure DevOps (TFS) endpoint which may no longer be valid, publicly accessible, or could be restricted to an internal corporate network. In many cases, organizations migrate from older tfs.azure... URLs to the newer dev.azure.com/{organization} format, and the old URL stops working. Additionally, access failures can occur due to browser cache/session issues, incorrect account login, missing permissions, or network restrictions such as VPN/firewall policies.

Refer below points to resolve this issue or this is the workaround

Verify if the URL is correct and still active

Old TFS URLs may be deprecated or replaced. Confirm the correct URL with the administrator. Try the new format:

https://dev.azure.com/{organizationName}

Check if VPN or corporate network access is required

The server may be internal-only. Connect to VPN or corporate network and retry access.

Clear browser cache and sign out completely

Visit: https://aka.ms/VsSignout

Clear cookies and cache (Ctrl + Shift + Delete)

Restart browser and try again in Incognito/InPrivate mode

Ensure correct account is used for login

Make sure you are using the correct Work (Entra ID) account and not a personal Microsoft account.

Verify permissions with administrator

Confirm your account is added to the Azure DevOps organization/project and has required access (Basic/Read).

Check server availability (if on-premises TFS)

If this is an on-prem TFS setup, the server might be down or inaccessible. Contact the internal IT team.

Test from a different network or device

Try accessing from another system or network to identify if the issue is environment-specific.

1 answer

Your answer

Siddhesh Desai 8,210 Reputation points Microsoft External Staff Moderator

2026-06-16T09:15:34.2033333+00:00

Hi @Pellegrini, Laura

Thank you for reaching out to Microsoft Q&A.

The issue with accessing the provided URL is most likely because tfs.azure.bakerhughes.com is a legacy Azure DevOps (TFS) endpoint which may no longer be valid, publicly accessible, or could be restricted to an internal corporate network. In many cases, organizations migrate from older tfs.azure... URLs to the newer dev.azure.com/{organization} format, and the old URL stops working. Additionally, access failures can occur due to browser cache/session issues, incorrect account login, missing permissions, or network restrictions such as VPN/firewall policies.

Refer below points to resolve this issue or this is the workaround

Verify if the URL is correct and still active

Old TFS URLs may be deprecated or replaced. Confirm the correct URL with the administrator. Try the new format:

https://dev.azure.com/{organizationName}

Check if VPN or corporate network access is required

The server may be internal-only. Connect to VPN or corporate network and retry access.

Clear browser cache and sign out completely

Visit: https://aka.ms/VsSignout

Clear cookies and cache (Ctrl + Shift + Delete)

Restart browser and try again in Incognito/InPrivate mode

Ensure correct account is used for login

Make sure you are using the correct Work (Entra ID) account and not a personal Microsoft account.

Verify permissions with administrator

Confirm your account is added to the Azure DevOps organization/project and has required access (Basic/Read).

Check server availability (if on-premises TFS)

If this is an on-prem TFS setup, the server might be down or inaccessible. Contact the internal IT team.

Test from a different network or device

Try accessing from another system or network to identify if the issue is environment-specific.

Answer 1

The URL tfs.azure.bakerhughes.com is a legacy-style Azure DevOps/TFS endpoint. When access to an Azure DevOps organization or project fails, the most common causes are:

Using the wrong URL or endpoint format.
Browser sign-in/cache issues.
Missing or insufficient permissions to the organization/project.

Try the following steps:

Clear sign-in state and browser cache
- Sign out using https://aka.ms/VsSignout.
- Then clear all browser cookies and site data (for example, press Ctrl+Shift+Delete and clear cookies/cache).
- Close the browser, reopen it, and try accessing the organization again.
Use a private/incognito browser session
- Open an InPrivate/Incognito window and try to access the Azure DevOps organization from there.
- This helps rule out cached credentials or conflicting sign-ins.
Verify the organization URL pattern
- Ensure the URL being used matches the expected Azure DevOps pattern:
  https://dev.azure.com/{organizationName}
- If the organization has been moved or renamed, the old tfs.azure... URL might no longer be valid, and the updated dev.azure.com URL must be used instead (contact the internal Azure DevOps admin if unsure of the correct organization name).
Check account type and permissions
- Confirm that the correct account type is being used to sign in (Microsoft Entra ID vs. personal Microsoft account), as mismatched accounts can block access.
- If the URL is correct but access is still denied or redirected, contact the Azure DevOps organization administrator to confirm that the account has been added as a project/organization member and has sufficient permissions.

If, after these steps, access is still not possible, the issue is likely related to tenant/organization configuration or permissions and must be checked by the Azure DevOps or Microsoft 365 administrator for the bakerhughes.com environment.

References: