Container Status Remaining "Waiting" While Deploying DICOMCast about dicom-server HOT 3 CLOSED

DefaultAzureCredential will go through different types of authentication until it finds one that works - https://learn.microsoft.com/en-us/dotnet/azure/sdk/authentication/?tabs=command-line#exploring-the-sequence-of-defaultazurecredential-authentication-methods
So its not failing on EnvironmentCredential or WorkloadIdentityCredential, but just moving on to the next credential. It looks like it finally uses ManagedIdentityCredential and stops there.

https://github.com/microsoft/dicom-server/blob/main/converter/dicom-cast/docs/authentication.md - see these docs for more options on how to set up authentication

from dicom-server.

Thank you for your reply,

As you describe here, DefaultAzureCredential uses ManagedIdentityCredential

As per the documentation, I've followed all the steps and still facing this issue.

from dicom-server.

Hello @jnlycklama

We are still facing issues with the sample application implementations.

Followed the documentation, I've followed all the steps and still facing this #3045.

Is there any other way or possibility that you can help ?

from dicom-server.