Skip to content

Commit b7ec860

Browse files
authored
Update deploy-dicom-services-in-azure.md
1 parent 1898b69 commit b7ec860

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: mmitrik
99
ms.custom: mode-api
1010
---
1111

12-
# Deploy the DICOM service by using the Azure portal
12+
# Deploy the DICOM service with Blob storage by using the Azure portal
1313

1414
In this quickstart, you learn how to deploy the DICOM® service by using the Azure portal.
1515

@@ -41,7 +41,7 @@ To deploy the DICOM service, you need a workspace created in the Azure portal. F
4141

4242
4. Enter a name for the DICOM service.
4343
- Select Blob Storage (legacy) for the storage location.
44-
- Select **Enable data partitions** when you deploy a new DICOM service. After data partitioning is turned on, it can't be turned off. In addition, data partitions can't be turned on for any DICOM service that is already deployed.
44+
- (Optional) Select **Enable data partitions** when you deploy a new DICOM service. After data partitioning is turned on, it can't be turned off. In addition, data partitions can't be turned on for any DICOM service that is already deployed.For more information, see : [Enable data partitioning](data-partitions.md)
4545

4646
- After the data partitions setting is turned on, the capability modifies the API surface of the DICOM server and makes any previous data accessible under the `Microsoft.Default` partition and then select **Review + create**
4747

0 commit comments

Comments
 (0)