Azure DevOps error when restoring Microsoft.Health.Dicom.Client about dicom-server HOT 5 CLOSED

Yes, confirming the same issue happened to us. I posted my comment in above mentioned SO link: https://stackoverflow.com/a/76662452

Note:
if you use their CI feed, seems it works fine: https://microsofthealthoss.visualstudio.com/FhirServer/_artifacts/feed/CI/connect/nuget.exe

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="CI" value="https://microsofthealthoss.pkgs.visualstudio.com/FhirServer/_packaging/CI/nuget/v3/index.json" />
  </packageSources>
</configuration>

from dicom-server.

Thanks for the heads up. We'll check to see if anything changed with the feed configuration.

from dicom-server.

@brandonpollett Any update on this? Running into this issue as well and the package, "Microsoft.Health.Dicom.Client," is no longer is in the CI feed? @koswedo @EugeneBogushevich: what are ya'll currently doing?

Btw, it's in the official docs if that at all pumps up the priority.

from dicom-server.

@haywoodIII - Are you still encountering this problem? I was able to successfully perform a dotnet restore after referencing the package Microsoft.Health.Dicom.Client via the Public feed in a new dev environment. But perhaps I unintentionally included some additional authentication.

from dicom-server.

I'm going to close the issue for now pending other users that may report issues

from dicom-server.