Skip to content

Commit c061e30

Browse files
esmadaummitrik
andauthored
Apply suggestions from code review
mmitrik suggestions Co-authored-by: Matthew Mitrik <[email protected]>
1 parent 399729c commit c061e30

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/healthcare-apis/dicom/deploy-dicom-services-in-azure-data-lake.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -212,20 +212,20 @@ Use the Azure portal to **Deploy a custom template** and then use the sample ARM
212212

213213
### Connectivity
214214

215-
To be alerted to store health and connectivity failures, please sign up for [Resource Health alerts](https://learn.microsoft.com/en-us/azure/service-health/resource-health-alert-monitor-guide).
215+
To be alerted to store health and connectivity failures, please sign up for [Resource Health alerts](/azure/service-health/resource-health-alert-monitor-guide).
216216

217217
### 424 Failed Dependency
218218

219219
When the response status code is `424 Failed Dependency`, the issue lies with a dependency configured with DICOM and it may be the data lake store.
220-
The response body indicates which dependency failed and provides more context on the failure. For data lake storage account failures, an error code is provided which was received when attempting to interact with the store. For more information, see [Azure Blob Storage error codes](https://learn.microsoft.com/rest/api/storageservices/blob-service-error-codes).
220+
The response body indicates which dependency failed and provides more context on the failure. For data lake storage account failures, an error code is provided which was received when attempting to interact with the store. For more information, see [Azure Blob Storage error codes](/rest/api/storageservices/blob-service-error-codes).
221221
Note that a code of `ConditionNotMet` typically indicates the blob file has been moved, deleted or modified without using DICOM APIs. The best way to mitigate such a situation is to use the DICOM API to DELETE the instance to remove the index and then reupload the modified file. This will enable you to continue to reference and interact with the file through DICOM APIs.
222222

223223
## Next steps
224-
[Receive resource health alerts](https://learn.microsoft.com/azure/service-health/resource-health-alert-monitor-guide)
224+
[Receive resource health alerts](/azure/service-health/resource-health-alert-monitor-guide)
225225

226226
[Assign roles for the DICOM service](../configure-azure-rbac.md#assign-roles-for-the-dicom-service)
227227

228-
[Review DICOM service conformance statement](https://learn.microsoft.com/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2)
228+
[Review DICOM service conformance statement](/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2)
229229

230230
[Use DICOMweb Standard APIs with DICOM services](dicomweb-standard-apis-with-dicom-services.md)
231231

0 commit comments

Comments
 (0)