Azure DICOMWeb service url always returns 404 service not found

Question

Azure DICOMWeb service url always returns 404 service not found

Shawn 20

Provisioned a DICOMWeb Service but it is not accessible the url https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com just returns 404 not found so does any sort of upload or query performed eg: https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com/Studies?api-version=2022-06-01

{

        "id": "/subscriptions/XXXXXXXX-f00d-XXXX-aba2-6fb7c3c81565/resourceGroups/AzureHealthDataServiceWorkspace/providers/Microsoft.HealthcareApis/workspaces/

        "name": "workspacename/dicomweb",

        "type": "Microsoft.HealthcareApis/workspaces/dicomservices",

        "etag": "\"a6016959-0000-0400-0000-68c53a7d0000\"",

        "location": "westus2",

        "tags": {},

        "properties": {

            "authenticationConfiguration": {

                "authority": "https://login.microsoftonline.com/9a44152e-XXXX-481a-8039-e0a3090a0cad/",

                "audiences": [

                    "https://dicom.healthcareapis.azure.com/",

                    "https://dicom.healthcareapis.azure.com"

                ]

            },

            "serviceUrl": "https://workspacename.dicom.azurehealthcareapis.com",

            "corsConfiguration": {

                "origins": [],

                "headers": [],

                "methods": [],

                "allowCredentials": false

            },

            "privateEndpointConnections": [],

            "publicNetworkAccess": "Enabled",

            "provisioningState": "Succeeded"

        },

        "identity": {

            "type": "None"

        },

        "systemData": {

            "createdAt": "2025-09-13T09:09:33.4495979Z",

            "lastModifiedAt": "2025-09-13T09:33:49.8012442Z"

        }

    }

Shawn 20 Reputation points

2025-09-17T07:28:26.29+00:00
I have been through the AI assistant and already confirmed the following items
Service URL Format: Make sure you're using the right format for your DICOM service URL, which should be https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com . Replace with the actual names you used during deployment.

API Versioning: Include the API version in the URL when you make requests. This helps the service recognize and process your requests properly.

Application Registration: After you’ve registered your app in Microsoft Entra ID, check that you’ve given it the necessary permissions to access the DICOM service. Look at the roles assigned to the app in the Azure portal.

Access Token: Ensure you're getting a Microsoft Entra access token correctly using PowerShell, Azure CLI, or other supported methods before trying to upload DICOM files.

Deployment Verification: Make sure your DICOM service has been deployed successfully and is running. You can see the details in the Azure portal.

If you’re still having issues, go through the deployment logs for any errors or warnings.

Answer accepted by question author

0 additional answers

Your answer

Shawn 20 Reputation points

2025-09-17T07:28:26.29+00:00

I have been through the AI assistant and already confirmed the following items
Service URL Format: Make sure you're using the right format for your DICOM service URL, which should be https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com . Replace with the actual names you used during deployment.

API Versioning: Include the API version in the URL when you make requests. This helps the service recognize and process your requests properly.

Application Registration: After you’ve registered your app in Microsoft Entra ID, check that you’ve given it the necessary permissions to access the DICOM service. Look at the roles assigned to the app in the Azure portal.

Access Token: Ensure you're getting a Microsoft Entra access token correctly using PowerShell, Azure CLI, or other supported methods before trying to upload DICOM files.

Deployment Verification: Make sure your DICOM service has been deployed successfully and is running. You can see the details in the Azure portal.

If you’re still having issues, go through the deployment logs for any errors or warnings.

Answer 1

Rakesh Mishra 4,030 Microsoft External Staff Moderator

Hi Shawn,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

APIs expect the API version as part of the URL path, not the ?api-version query parameter.
Currently the supported versions are:

v1.0-prerelease
v1
v2

Please try with below URL.

https://<workspaceName>-<dicomServiceName>.dicom.azurehealthcareapis.com/v2/studies

Reference: API versioning for DICOM service

I hope the provided answer is helpful, do let me know if you have any further questions on this. Please accept as Yes if the answer is helpful so that it can help others in the community. Thanks

Shawn 20 Reputation points

2025-09-17T16:19:35.72+00:00

Thank you this helped a lot!! It got me to at least getting a error 400 Bad Request. Which turned out to be related to partition names. For anyone else in the same situation from there

https://<workspaceName>-<dicomServiceName>.dicom.azurehealthcareapis.com/v2/partitions

gets you the list of partition names in my case it was just the "Microsoft.Default" so the full url became

https://<workspaceName>-<dicomServiceName>.dicom.azurehealthcareapis.com/v2/partitions/Microsoft.Default/studies
I now have some problems with missing dicom tags in the dcm file but this got me back on the road to success. Thanks Rakesh Mishra!!
Shawn 20 Reputation points

2025-09-18T18:07:56.3766667+00:00

deleted

Share via

Azure DICOMWeb service url always returns 404 service not found

0 additional answers

Your answer