Timeout issue getting Communication Identity access token in Azure Comms

Question

Timeout issue getting Communication Identity access token in Azure Comms

Dylan Olney 140

Hi,

I have built an a web app for my client, a clinical trials company, which incorporates the Azure Comms phone calling service. This aspect of the app had been working fine in production for many months. However, as of recently, there have been timeout issues getting Communication Identity access tokens for users.

I'm using the C# packages in my .net API application:

Azure.Communication.Common

Azure.Communication.Identity

Azure.Communication.CallAutomation

The issue is that lately, the C# GetTokenAsync function seems to be hanging, and the lack of a prompt response is causing my API application to return a timeout error. Like I said, it had been working fine in production for several months up until now.

It's weird in that users are reporting that they can still make calls. I'm wondering how this is possible if the the request to get the token required to set up their front-end call agent is timing out.

Any advice, information or help would be greatly appreciated,

Your truly,

Dylan Olney.

Software Developer, Nimbus Research Center, MTU, Ireland.

Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-04-14T13:46:32.5733333+00:00

Hi @Dylan Olney

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?
Dylan Olney 140 Reputation points

2026-04-14T14:48:58.5133333+00:00

Hi @Golla Venkata Pavani ,

Thanks for your support on this issue. The information you provided is very useful. The fact that the call agent never actually stopped working in my app means that the initial token fetch was never producing a timeout at least. I think that subsequent timeouts were due to a bug in my code whereby it was calling my agent initialization function twice in rapid succession. Although I have since corrected this flaw, it hadn't been causing any issue until lately, probably due to some recent changes on the Azure side under the hood. I know this because the app is set up to report any http errors via a pop-up, and they only started happening lately. I've also added some of the recommended optimizations such as fetching the token first, caching it locally, and providing it as the token option to the AzureCommunicationTokenCredential constructor, along with the other options such as the tokenRefresher function and whether to refreshProactively. Before, it was relying on the tokenRefresher to get the token initially, and there was no caching. All of these improvements combined have stopped the timeout issue, so thankfully it's now resolved. Thanks again for the detailed response.

Yours truly,

Dylan Olney.

2 answers

Your answer

Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-04-14T13:46:32.5733333+00:00

Hi @Dylan Olney

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?
Dylan Olney 140 Reputation points

2026-04-14T14:48:58.5133333+00:00

Hi @Golla Venkata Pavani ,

Thanks for your support on this issue. The information you provided is very useful. The fact that the call agent never actually stopped working in my app means that the initial token fetch was never producing a timeout at least. I think that subsequent timeouts were due to a bug in my code whereby it was calling my agent initialization function twice in rapid succession. Although I have since corrected this flaw, it hadn't been causing any issue until lately, probably due to some recent changes on the Azure side under the hood. I know this because the app is set up to report any http errors via a pop-up, and they only started happening lately. I've also added some of the recommended optimizations such as fetching the token first, caching it locally, and providing it as the token option to the AzureCommunicationTokenCredential constructor, along with the other options such as the tokenRefresher function and whether to refreshProactively. Before, it was relying on the tokenRefresher to get the token initially, and there was no caching. All of these improvements combined have stopped the timeout issue, so thankfully it's now resolved. Thanks again for the detailed response.

Yours truly,

Dylan Olney.

Answer 1

Dylan Olney 140

Issue is now resolved.

Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-04-14T14:54:52.3533333+00:00

Hi @Dylan Olney

we are glad to hear your positive response and appreciate you sharing the update.

Just checking in to see if the earlier answer helped resolve your query. If it did, please click “Accept the answer” and consider upvoting it—this can be helpful for other community members who might face a similar issue.

If you have any further questions or need additional assistance, please feel free to let us know. We’re here to help!

Answer 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