Hi @Nishma Parvin
Thanks for letting us know your user experience. According to your case description, I do understand how frustrated you are now.
When I received this case, I looked up a lot of information and did a lot of research. I regret to inform you that the issue seems to be related to assertion audience mismatch between client application and server application.
This can happen when the client application requests a token for a different resource than the server application expected.
Following what I know so far, I provide a method:
One possible solution is to ensure that the client application and server application have the same Application ID URI in Azure AD.
You can check and update the Application ID URI in the Azure portal under Application Registration > Your Application > Public API. The Application ID URI should be a unique identifier for the application, such as https://contoso.com/myapp.
If you ensure consistency, but still have issues. Then I suggest that you report the problem in this platform, which can better help you solve the problem
Here is link for your reference:
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.