# Create a cluster volume from an approved specification

> Which provisioning inputs should be checked when creating a new cluster volume in Windows Admin Center?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-028-create-a-cluster-volume-from-an-approved-specification/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:43+00:00
- Modified: 2026-09-08T18:17:14+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Which provisioning inputs should be checked when creating a new cluster volume in Windows Admin Center?

## Potentially affected

Use this Windows Admin Center review for an eligible multi-node cluster after its new volume design is approved.

## DSE recommendation

Have a second administrator compare the proposed creation inputs with the design record before execution.

## Article

## Source facts

Microsoft documents cluster-volume creation through Windows Admin Center and PowerShell. A single-node cluster requires the PowerShell creation path. For a mirrored volume in Windows Admin Center, the administrator supplies a name, chooses two-way or three-way resiliency according to server count, and sets the capacity. Optional selections include deduplication, integrity checksums, and encryption. The resulting volume can be opened from the cluster’s volume inventory. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/create-volumes).

## Applicability

Use this Windows Admin Center review for an eligible multi-node cluster after its new volume design is approved. Identify the cluster, name, usable size, selected resiliency, and optional features. Keep those approved values separate from examples in the interface walkthrough.

## DSE recommendation

Have a second administrator compare the proposed creation inputs with the design record before execution. Assign an owner to each optional feature and confirm that its prerequisites have been reviewed. Record the intended workload and access path. Avoid selecting extra options simply because they appear in the creation pane, and preserve the completed provisioning record for later capacity work.

## Verification

Inspect the new volume in inventory and compare its name, size, resiliency, and feature state with the approved specification. Perform a controlled file-access test through the intended path. Record any difference before placing application data on it. Keep future resizing and geometry changes in separate approved records tied to this original volume identity.

## Official references

[Microsoft Learn: Create volumes on Azure Local and Windows Server clusters](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/create-volumes). Source reviewed September 8, 2026.

## Primary reference

- Name: Create volumes on Azure Local and Windows Server clusters
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/create-volumes
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Create a cluster volume from an approved specification,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-028-create-a-cluster-volume-from-an-approved-specification/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.