Unable to delete search service due to InvalidAuthenticationTokenTenant

Yifan Lin 0 Reputation points
2024-10-07T16:13:16.5966667+00:00

Hello community,

I recently provisioned both a search service and an OpenAI service within the same resource group. However, when attempting to delete the entire resource group, I encountered an issue: the search service failed to be deleted and displayed the following error.

Before this issue occurred, we didn’t make any changes to our tenant or subscription, and everything else seems to be working fine except for the search service. I’m unsure why this is happening and why two different IDs are shown in the error message. Any insights or guidance would be appreciated!

{"error":{"code":"InvalidAuthenticationTokenTenant","message":"The access token is from the wrong issuer 'https://sts.windows.net/{wrong tenant id }'. It must match the tenant 'https://sts.windows.net/{our tenant id }/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/{our tenant id}' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later."}}

Azure AI Search
Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
1,067 questions
Azure OpenAI Service
Azure OpenAI Service
An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
3,246 questions
{count} votes

3 answers

Sort by: Most helpful
  1. SnehaAgrawal-MSFT 21,771 Reputation points
    2024-10-09T07:14:55.7066667+00:00

    @Yifan Lin Thanks for asking question!

    The issue seems to be that you're attempting to access resources in a different tenant, or the resources have been transferred to another tenant. Ensure that the account you're using is properly registered.

    Refer to this solution for further assistance.

    Additionally, consider using ClientSecretCredential rather than setting the AZURE_TENANT_ID, AZURE_CLIENT_ID, and AZURE_CLIENT_SECRET as environment variables.

    0 comments No comments

  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. 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

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.