Pair each Elastic SAN IQN with its target portal before configuring Windows connections

Source facts

Microsoft says the Elastic SAN extension connects volumes using the supplied IQNs, portal addresses, and session counts, with a one-to-one volume-to-portal mapping. The extension acts on the provided parameters and does not infer or retain a history of previous connections. Reconfiguration does not automatically change existing connections unless a disconnect is explicitly requested. Microsoft Learn

Applicability

Use this review when connecting a Windows VM to Azure Elastic SAN through the VM extension, especially when the request includes more than one volume.

DSE recommendation

DSE recommends a connection worksheet with one row for each volume, its IQN, target portal, and requested session count. Review the ordering of values before submitting a multi-volume configuration. Keep the current connection inventory beside the new request so an intended addition is not confused with an explicit disconnect. Require the workload owner to approve any removal and specify how the affected data will be checked afterward.

Verification

Inspect the extension result and the Windows connection inventory after the operation. Match each observed volume and portal to the worksheet and compare session counts with the request. Investigate unexpected existing connections separately rather than assuming reconfiguration removed them. Retain any failure message with the exact submitted mapping.

Official references

• Microsoft: Connect to an Azure Elastic SAN volume – Windows | Microsoft Learn