Why is login.microsoftonline.com/tenantId/v2.0 404 Not Found

Leonard, Jared 56 Reputation points
2023-04-13T15:56:36.9233333+00:00

I am trying to determine why https://login.microsoftonline.com/tenantId/v2.0 results in a 404 for my tenant, in both the browser and Postman. Both https://login.microsoftonline.com/tenantId/v2.0/.well-known/openid-configuration and https://login.microsoftonline.com/tenantId/oauth2/v2.0/token work. According to this article, https://login.microsoftonline.com/tenantId/v2.0 should act as the Open ID issuer, so what Azure settings could be preventing that page from working?

Microsoft Security | Microsoft Entra | Microsoft Entra ID
{count} votes

3 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Shweta Mathur 30,296 Reputation points Microsoft Employee Moderator
    2023-04-18T06:23:12.3166667+00:00

    Hi @Leonard, Jared ,

    Thanks for reaching out and apologies for the delay in response. https://login.microsoftonline.com/{tenant}/v2.0 is the OpenID issuer URL that identifies the issuer of the OpenID Connect ID token where {tenant} is the tenant ID or name. This URL is used by the relying party to verify the authenticity of the ID token.

    The OpenID issuer URL provides metadata about the OpenID Connect provider. Every app registration in Azure AD is provided with a publicly accessible endpoint that serves its OpenID configuration document. To determine the URI of the configuration document's endpoint for your app, append the well-known OpenID configuration path to issuer URL.

    • Well-known configuration document path: /.well-known/openid-configuration
    • OpenID Issuer URL: https://login.microsoftonline.com/{tenant}/v2.0

    In the case of OpenID Connect, the .well-known directory is used to store the OpenID Connect discovery document that provides metadata about the OpenID Connect provider, including the supported scopes, claims, and endpoints.

    Hope this will help.

    Thanks,

    Shweta


    Please remember to "Accept Answer" if answer helped you.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.