This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 90%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
I have a free trial version. I am trying to set up a dicom service and doing POC before we upgrade license. I have created workspace,VM. However, I am unable to create Dicom Service or set it up. I can only see view option.
I want to set this up so that admin can store and use Dicom service to store medical images from people and use this service. Could you help me to set up?
I have tried using https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/get-started-with-dicom but could not follow the steps apart from creating workspace.
Fast help will be helpful
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 10%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
JYOTIDIP BARMAN Thanks for posting your question in Microsoft Q&A. Based on my understanding, you were able to create Azure Health Data Services workspace (doc reference) but unable to create Dicom service. I assume you are seeing this issue in the portal.
Please follow instructions in Deploy DICOM service using the Azure portal doc and navigate to your Azure Health Data Services workspace. Then you should be able to see option to Deploy DICOM service with window shown below and on selecting it should display Add DICOM service and using that option you can create DICOM service as below:
Deploy DICOM service
Add DICOM service
If you don't see the option, please check if default limit: 10 has been exceeded for the workspace Azure Health Data Services limits. Please share screenshots or additional details where you see only view option or face any errors while creating it. That would help in assisting you better.
I cant find the Create Dicom Service so am stuck there
I cant see the new dicom service option
Can you share screenshot of your Azure Health Data Services workspace in the portal like I shared?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 64%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
I have not received any suggestion on this.
Can someone help on this?
Jyotidip Barman In my previous comment, I have requested you to share Azure Health Data Services workspace name since the screenshot you shared doesn't show the workspace (Azure Health Data Services workspace). Please follow instructions in Deploy DICOM service using the Azure portal doc and navigate to your Azure Health Data Services workspace to create DICOM service.
Please note, DICOM service is a managed service and can be deployed via Azure PowerShell, CLI and Rest API as well.
Hi,
I have created a Azure Health Data Services, screenshot given
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
The service link for Dicom service is not opening as well.
https://trinnect-trinnectdicomservice.dicom.azurehealthcareapis.com/
Could you help?
The trial period is getting over so need help urgently.
JYOTIDIP BARMAN Based on the screenshot/info shared, you were able to create Dicom service, but it doesn't open with the endpoint. As mentioned in doc, you would need to specify version as well as part of URL such as studies when making the requests since routes without version are no longer supported.
API versioning for DICOM service
The version of the REST API must be explicitly specified in the request URL like <service_url>/v<version>/studies. So, your question should look like https://trinnect-trinnectdicomservice.dicom.azurehealthcareapis.com/v1/studies.
When I tested with the endpoint, I got 401 unauthorized error since I didn't pass authentication token. Refer 401 error while accessing DICOM API and make sure to pass authentication token while testing it via Postman or any other tool.
I hope this helps with your question.
I have generated the auth token but I am unable to pass this along with the URL, could you help me on this?
Tried this format
authority/tenant id/outh2/token
Please help urgently as my trial period is getting over.
@MuthuKumaranMurugaachari-MSFT can you check on this?
JYOTIDIP BARMAN You mentioned you have generated the auth token, if so, you need to pass this token in authentication header to your endpoint API call like detailed here.
The URL <Authority>/<tenant-ID>/oauth2/token described in article: https://github.com/microsoft/dicom-server/blob/main/docs/how-to-guides/enable-authentication-with-tokens.md#get-access-token-using-postman is to generate auth token. If you see any issues in generating the token, share the additional details about authority, or faced any errors.
As I mentioned in comment, I did follow the same but it didnt work
JYOTIDIP BARMAN Sorry if I may ask, do you have issues in generating AUTH token from Identity Server? or pass the token to DICOM service?
If you have set up authentication with authority like https://login.microsoftonline.com/<tenant-name>.onmicrosoft.com and using Azure AD V2, then you have to use <Authority>/<tenant-ID>/oauth2/v2.0/token instead of Authority>/<tenant-ID>/oauth2/token.
Can you please elaborate what is not working? That additional details would really help in understanding the issue better.
Authority:https://login.microsoftonline.com/e016df82-b7eb-41f8-b1f3-37187b065a2c/
Tenant Id : e016df82-b7eb-41f8-b1f3-37187b065a2c
Auth Code: eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ii1LSTNROW5OUjdiUm9meG1lWm9YcWJIWkdldyIsImtpZCI6Ii1LSTNROW5OUjdiUm9meG1lWm9YcWJIWkdldyJ9.eyJhdWQiOiJodHRwczovL3RyaW5uZWN0LXRyaW5uZWN0Zmhpci5maGlyLmF6dXJlaGVhbHRoY2FyZWFwaXMuY29tLyIsImlzcyI6Imh0dHBzOi8vc3RzLndpbmRvd3MubmV0L2UwMTZkZjgyLWI3ZWItNDFmOC1iMWYzLTM3MTg3YjA2NWEyYy8iLCJpYXQiOjE2Nzc0MTIyMTAsIm5iZiI6MTY3NzQxMjIxMCwiZXhwIjoxNjc3NDE2MTEwLCJhaW8iOiJFMlpnWUhqcC8rQlV0dDYwaEpnUHkrN2xmUHRzQmdBPSIsImFwcGlkIjoiNWY5MzE1YmUtNTMxYi00NzRmLTkwYTQtNzFlMjc4NzkzMzUzIiwiYXBwaWRhY3IiOiIxIiwiaWRwIjoiaHR0cHM6Ly9zdHMud2luZG93cy5uZXQvZTAxNmRmODItYjdlYi00MWY4LWIxZjMtMzcxODdiMDY1YTJjLyIsIm9pZCI6IjUwZDkxOWRkLWViYjItNDhhYS05YTU1LTIwODNlZWMzNDI1MSIsInJoIjoiMC5BVllBZ3Q4VzRPdTMtRUd4OHpjWWV3WmFMTmg0WjBfdld0eERvZi13YzNKTGxKV2ZBQUEuIiwic3ViIjoiNTBkOTE5ZGQtZWJiMi00OGFhLTlhNTUtMjA4M2VlYzM0MjUxIiwidGlkIjoiZTAxNmRmODItYjdlYi00MWY4LWIxZjMtMzcxODdiMDY1YTJjIiwidXRpIjoiRXJPYWRXek5YRXUzTVFpOTFZTU5BQSIsInZlciI6IjEuMCJ9.VmOU5_LjBCkp91lNp2F64vCTR3uYSCJDn8JspKTVAVM_6dodWCjOoP-3Ey4bn5C0OGxRjY_YW1ul1Sl0GSn405MHhlqK_mwDwk6b1Bb9xJCZpIwYhJMKLIJO37S2Xd63KVXWBnO2_arq0RWJr21NH9yxfRCSj34St9bC7imZbHHQP5USi-pT5y_8C2oPUma-lsi8SjG3G3KCQGO2PZctHL9gsBv3EtS21vzGLdvl5Tt3tRfx18RAQ5ql28Xznp3Pfd3DI-JErVH8CEmFgVlqueOj_6yKuO-lZhZtumaxxKVH4KYifw0iGxYU_OJbkDRaCH3YhdG4O5rEcLVzoF4cgw
Finally the link is :
but this given an error :
Bad Request - Invalid URL
HTTP Error 400. The request URL is invalid.
JYOTIDIP BARMAN Based on the info shared, you are trying to call <Authority>/<tenant-ID>/oauth2/v2.0/token replacing token with auth code and that seems to be the problem. If you follow doc, this flow is used to generate AUTH token from Identity Server (maybe Azure AD if you set it up that way) and input to endpoints are authority URL, tenant-ID and other info passed in HTTP headers such as clientid, grantType, client_secret etc.
Since you already have AUTH token generated, then you would need to pass this token via Authorization header (not via URL or Query parameters) when calling DICOM endpoint.
Postman sample:
I hope this helps and let me know if any questions.
Note: User sensitive info in the comment will be deleted for security reasons.