{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/", "slug": "dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows", "url": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/" }, "title": "Pair each Elastic SAN IQN with its target portal before configuring Windows connections", "summary": "DSE recommends a connection worksheet with one row for each volume, its IQN, target portal, and requested session count.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-17T16:33:47+00:00", "modified_at": "2026-09-17T16:38:45+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 215, "potentially_affected": "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.", "primary_source": { "name": "Connect to an Azure Elastic SAN volume - Windows | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-connect-windows", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n", "content_text": "Source facts\nMicrosoft 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\nApplicability\nUse this review when connecting a Windows VM to Azure Elastic SAN through the VM extension, especially when the request includes more than one volume.\nDSE recommendation\nDSE 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.\nVerification\nInspect 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.\nOfficial references\n\nMicrosoft: Connect to an Azure Elastic SAN volume – Windows | Microsoft Learn", "content_markdown": "## Source facts\n\nMicrosoft 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](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-connect-windows)\n\n## Applicability\n\nUse this review when connecting a Windows VM to Azure Elastic SAN through the VM extension, especially when the request includes more than one volume.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nInspect 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.\n\n## Official references\n\n- [Microsoft: Connect to an Azure Elastic SAN volume – Windows | Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-connect-windows)" }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/", "url": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Pair each Elastic SAN IQN with its target portal before configuring Windows connections", "item": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/", "url": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/", "headline": "Pair each Elastic SAN IQN with its target portal before configuring Windows connections", "description": "DSE recommends a connection worksheet with one row for each volume, its IQN, target portal, and requested session count.", "abstract": "DSE recommends a connection worksheet with one row for each volume, its IQN, target portal, and requested session count.", "articleBody": "Source facts\nMicrosoft 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\nApplicability\nUse this review when connecting a Windows VM to Azure Elastic SAN through the VM extension, especially when the request includes more than one volume.\nDSE recommendation\nDSE 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.\nVerification\nInspect 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.\nOfficial references\n\nMicrosoft: Connect to an Azure Elastic SAN volume – Windows | Microsoft Learn", "datePublished": "2026-09-17T16:33:47+00:00", "dateModified": "2026-09-17T16:38:45+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260917-073-pair-each-elastic-san-iqn-with-its-target-portal-before-configuring-windows/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Pair each Elastic SAN IQN with its target portal before configuring Windows connections" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 215, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Connect to an Azure Elastic SAN volume - Windows | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-connect-windows" } } ] } }