{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/",
        "slug": "dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/"
        },
        "title": "Close Azure VM file-recovery access after copying the required files",
        "summary": "How should an Azure VM file-recovery session be ended without leaving recovery access open?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "continuity-recovery",
            "label": "Continuity & recovery",
            "alt": "Paired infrastructure paths converging on a stable recovered service.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "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-10T00:22:21+00:00",
        "modified_at": "2026-09-10T02:14:31+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 1,
        "word_count": 219,
        "potentially_affected": "This file-recovery path is for Resource Manager Azure VMs protected to a Recovery Services vault; encrypted VM backups are excluded. Check the recovery machine's documented operating-system, storage, and network compatibility before starting.",
        "dse_recommendation": "Give each file-recovery session an owner and an explicit closeout step.",
        "primary_source": {
            "name": "Recover files and folders from Azure VM backup - Azure Backup | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm",
            "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": "<h2>Source facts</h2>\n<p>The Azure VM file-recovery script provides read-only recovery-point access and is valid for 12 hours. Unmounting that recovery point invalidates the script immediately, rather than waiting for its validity period to end. Microsoft warns that leaving the connection open can disrupt a subsequent backup of the recovery machine. On Linux, disconnected mount paths can remain visible as orphan volumes until explicitly cleaned. <a href=\"https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>This file-recovery path is for Resource Manager Azure VMs protected to a Recovery Services vault; encrypted VM backups are excluded. Check the recovery machine&#8217;s documented operating-system, storage, and network compatibility before starting.</p>\n<h2>DSE recommendation</h2>\n<p>Give each file-recovery session an owner and an explicit closeout step. Track the chosen recovery point, approved destination, and files to recover without distributing the access script or password broadly. After the copy is accepted, close the connection through the documented unmount action. Keep Linux mount cleanup distinct from revoking access; use the documented cleanup procedure only for the recovery session&#8217;s mounts.</p>\n<h2>Verification</h2>\n<p>Confirm the requested files are readable at the approved destination, then verify unmount completion and any required local cleanup. If the recovery machine is itself backed up, check its next backup result. Preserve evidence of completion without retaining recovery credentials in the general ticket.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Recover files and folders from Azure VM backup</a>.</p>",
        "content_text": "Source facts\nThe Azure VM file-recovery script provides read-only recovery-point access and is valid for 12 hours. Unmounting that recovery point invalidates the script immediately, rather than waiting for its validity period to end. Microsoft warns that leaving the connection open can disrupt a subsequent backup of the recovery machine. On Linux, disconnected mount paths can remain visible as orphan volumes until explicitly cleaned. Microsoft Learn.\nApplicability\nThis file-recovery path is for Resource Manager Azure VMs protected to a Recovery Services vault; encrypted VM backups are excluded. Check the recovery machine’s documented operating-system, storage, and network compatibility before starting.\nDSE recommendation\nGive each file-recovery session an owner and an explicit closeout step. Track the chosen recovery point, approved destination, and files to recover without distributing the access script or password broadly. After the copy is accepted, close the connection through the documented unmount action. Keep Linux mount cleanup distinct from revoking access; use the documented cleanup procedure only for the recovery session’s mounts.\nVerification\nConfirm the requested files are readable at the approved destination, then verify unmount completion and any required local cleanup. If the recovery machine is itself backed up, check its next backup result. Preserve evidence of completion without retaining recovery credentials in the general ticket.\nOfficial references\nMicrosoft Learn: Recover files and folders from Azure VM backup.",
        "content_markdown": "## Source facts\n\nThe Azure VM file-recovery script provides read-only recovery-point access and is valid for 12 hours. Unmounting that recovery point invalidates the script immediately, rather than waiting for its validity period to end. Microsoft warns that leaving the connection open can disrupt a subsequent backup of the recovery machine. On Linux, disconnected mount paths can remain visible as orphan volumes until explicitly cleaned. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm).\n\n## Applicability\n\nThis file-recovery path is for Resource Manager Azure VMs protected to a Recovery Services vault; encrypted VM backups are excluded. Check the recovery machine’s documented operating-system, storage, and network compatibility before starting.\n\n## DSE recommendation\n\nGive each file-recovery session an owner and an explicit closeout step. Track the chosen recovery point, approved destination, and files to recover without distributing the access script or password broadly. After the copy is accepted, close the connection through the documented unmount action. Keep Linux mount cleanup distinct from revoking access; use the documented cleanup procedure only for the recovery session’s mounts.\n\n## Verification\n\nConfirm the requested files are readable at the approved destination, then verify unmount completion and any required local cleanup. If the recovery machine is itself backed up, check its next backup result. Preserve evidence of completion without retaining recovery credentials in the general ticket.\n\n## Official references\n\n[Microsoft Learn: Recover files and folders from Azure VM backup](https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm)."
    },
    "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-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Close Azure VM file-recovery access after copying the required files",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/",
                "headline": "Close Azure VM file-recovery access after copying the required files",
                "description": "How should an Azure VM file-recovery session be ended without leaving recovery access open?",
                "abstract": "How should an Azure VM file-recovery session be ended without leaving recovery access open?",
                "articleBody": "Source facts\nThe Azure VM file-recovery script provides read-only recovery-point access and is valid for 12 hours. Unmounting that recovery point invalidates the script immediately, rather than waiting for its validity period to end. Microsoft warns that leaving the connection open can disrupt a subsequent backup of the recovery machine. On Linux, disconnected mount paths can remain visible as orphan volumes until explicitly cleaned. Microsoft Learn.\nApplicability\nThis file-recovery path is for Resource Manager Azure VMs protected to a Recovery Services vault; encrypted VM backups are excluded. Check the recovery machine’s documented operating-system, storage, and network compatibility before starting.\nDSE recommendation\nGive each file-recovery session an owner and an explicit closeout step. Track the chosen recovery point, approved destination, and files to recover without distributing the access script or password broadly. After the copy is accepted, close the connection through the documented unmount action. Keep Linux mount cleanup distinct from revoking access; use the documented cleanup procedure only for the recovery session’s mounts.\nVerification\nConfirm the requested files are readable at the approved destination, then verify unmount completion and any required local cleanup. If the recovery machine is itself backed up, check its next backup result. Preserve evidence of completion without retaining recovery credentials in the general ticket.\nOfficial references\nMicrosoft Learn: Recover files and folders from Azure VM backup.",
                "datePublished": "2026-09-10T00:22:21+00:00",
                "dateModified": "2026-09-10T02:14:31+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/"
                },
                "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-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Close Azure VM file-recovery access after copying the required files"
                },
                "articleSection": [
                    "Business Continuity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Business Continuity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 219,
                "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": "Recover files and folders from Azure VM backup - Azure Backup | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm"
                }
            }
        ]
    }
}