Skip to content

Commit a7df744

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

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,10 +40,10 @@ To deploy the DICOM service, you need a workspace created in the Azure portal. F
4040

4141

4242
4. Enter a name for the DICOM service.
43-
- Select Blob Storage (legacy) for the storage location.
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)
43+
- Select Blob Storage (legacy) for the storage location.
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

46-
- 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**
46+
- 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. Select **Review + create**.
4747

4848
![Screenshot showing the DICOM service name and storage location option.](media/deploy-dicom-services-in-azure/enter-dicom-service-name.png)
4949

0 commit comments

Comments
 (0)