Azure Health Data Services
An Azure offering that provides a suite of purpose-built technologies for protected health information in the cloud.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We're running into an issue where we see patient exports successfully coming back anonymized within one container, but not within another.
Any advice for troubleshooting this would be greatly appreciated!
Will Shirley Thanks for posting your question in Microsoft Q&A. Can you elaborate more about the endpoint for container exports via Postman (removing sensitive data), full exception details/stack trace for export operation etc.?
For sure! We are making a GET request to the following endpoint:
We successfully get a 202 regardless of which container we are pointing it to, but with the second container, no exported file appears in the directory. When we make a subsequent GET request to the Content-Location that is returned by the 202, we receive the error message(despite the file being in the same corresponding location within the second container):
@GeethaThatipatri-MSFT would it be possible to have your assistance with this? One of my team members recommended reaching out to you directly since you have previously worked with our teams.
Will Shirley We are really sorry for the delay on this. Based on the exception, it appears an issue with the file path, and I understand the file path is same in second container. This requires investigation from our backend logs to find exact cause and the best way is to open a ticket to our support team.
If you don't have support plan, please send an email to firstname.lastname@example.org referencing this thread with your subscription ID, details and subject as "Attn: Muthu". I will assist you with next steps.
Will Shirley Just a follow up to get your thoughts on how we can assist you with your issue.
Sign in to comment