{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/",
        "slug": "dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/"
        },
        "title": "Include rarely connected clients in each DirectAccess migration ring",
        "summary": "How should DirectAccess-to-Always-On-VPN migration rings account for remote clients?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            },
            {
                "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-08T18:15:25+00:00",
        "modified_at": "2026-09-08T18:23:26+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 1,
        "word_count": 201,
        "potentially_affected": "Administrators planning a phased DirectAccess migration to Always On VPN.",
        "dse_recommendation": "Build each ring from both regularly connected and infrequently connected devices.",
        "primary_source": {
            "name": "Remote Access Always On VPN migration planning",
            "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-access/da-always-on-vpn-migration/da-always-on-migration-planning",
            "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>Microsoft recommends running DirectAccess and Always On VPN alongside one another during a planned migration. An incorrect task order can leave remote users without access to organizational resources. Migration rings divide the work into successive phases. Microsoft recommends including users who visit the office frequently and those who do not in each phase. Remote clients can take longer to receive the migration update. <a href=\"https://learn.microsoft.com/en-us/windows-server/remote/remote-access/da-always-on-vpn-migration/da-always-on-migration-planning\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft documentation</a>.</p>\n<h2>Applicability</h2>\n<p>Identify the remote-user groups, device update paths, application access requirements, and support contacts. Review the complete migration sequence before changing the existing remote-access configuration.</p>\n<h2>DSE recommendation</h2>\n<p>Build each ring from both regularly connected and infrequently connected devices. Define how completion will be observed for each group and who can assist a user who cannot reconnect. Ask the service owner to approve the criteria for progressing to the next ring and for pausing the migration.</p>\n<h2>Verification</h2>\n<p>Track actual update receipt and test the required remote applications from each participating group. Include a device that has been away from the office for a representative period. Reconcile missing devices and user feedback before expanding a ring or withdrawing their former access route.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/remote/remote-access/da-always-on-vpn-migration/da-always-on-migration-planning\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Remote Access Always On VPN migration planning</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nMicrosoft recommends running DirectAccess and Always On VPN alongside one another during a planned migration. An incorrect task order can leave remote users without access to organizational resources. Migration rings divide the work into successive phases. Microsoft recommends including users who visit the office frequently and those who do not in each phase. Remote clients can take longer to receive the migration update. Microsoft documentation.\nApplicability\nIdentify the remote-user groups, device update paths, application access requirements, and support contacts. Review the complete migration sequence before changing the existing remote-access configuration.\nDSE recommendation\nBuild each ring from both regularly connected and infrequently connected devices. Define how completion will be observed for each group and who can assist a user who cannot reconnect. Ask the service owner to approve the criteria for progressing to the next ring and for pausing the migration.\nVerification\nTrack actual update receipt and test the required remote applications from each participating group. Include a device that has been away from the office for a representative period. Reconcile missing devices and user feedback before expanding a ring or withdrawing their former access route.\nOfficial references\nMicrosoft Learn: Remote Access Always On VPN migration planning. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft recommends running DirectAccess and Always On VPN alongside one another during a planned migration. An incorrect task order can leave remote users without access to organizational resources. Migration rings divide the work into successive phases. Microsoft recommends including users who visit the office frequently and those who do not in each phase. Remote clients can take longer to receive the migration update. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/remote/remote-access/da-always-on-vpn-migration/da-always-on-migration-planning).\n\n## Applicability\n\nIdentify the remote-user groups, device update paths, application access requirements, and support contacts. Review the complete migration sequence before changing the existing remote-access configuration.\n\n## DSE recommendation\n\nBuild each ring from both regularly connected and infrequently connected devices. Define how completion will be observed for each group and who can assist a user who cannot reconnect. Ask the service owner to approve the criteria for progressing to the next ring and for pausing the migration.\n\n## Verification\n\nTrack actual update receipt and test the required remote applications from each participating group. Include a device that has been away from the office for a representative period. Reconcile missing devices and user feedback before expanding a ring or withdrawing their former access route.\n\n## Official references\n\n[Microsoft Learn: Remote Access Always On VPN migration planning](https://learn.microsoft.com/en-us/windows-server/remote/remote-access/da-always-on-vpn-migration/da-always-on-migration-planning). Source reviewed September 8, 2026."
    },
    "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-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Include rarely connected clients in each DirectAccess migration ring",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/",
                "headline": "Include rarely connected clients in each DirectAccess migration ring",
                "description": "How should DirectAccess-to-Always-On-VPN migration rings account for remote clients?",
                "abstract": "How should DirectAccess-to-Always-On-VPN migration rings account for remote clients?",
                "articleBody": "Source facts\nMicrosoft recommends running DirectAccess and Always On VPN alongside one another during a planned migration. An incorrect task order can leave remote users without access to organizational resources. Migration rings divide the work into successive phases. Microsoft recommends including users who visit the office frequently and those who do not in each phase. Remote clients can take longer to receive the migration update. Microsoft documentation.\nApplicability\nIdentify the remote-user groups, device update paths, application access requirements, and support contacts. Review the complete migration sequence before changing the existing remote-access configuration.\nDSE recommendation\nBuild each ring from both regularly connected and infrequently connected devices. Define how completion will be observed for each group and who can assist a user who cannot reconnect. Ask the service owner to approve the criteria for progressing to the next ring and for pausing the migration.\nVerification\nTrack actual update receipt and test the required remote applications from each participating group. Include a device that has been away from the office for a representative period. Reconcile missing devices and user feedback before expanding a ring or withdrawing their former access route.\nOfficial references\nMicrosoft Learn: Remote Access Always On VPN migration planning. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:15:25+00:00",
                "dateModified": "2026-09-08T18:23:26+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/"
                },
                "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-20260908-106-include-rarely-connected-clients-in-each-directaccess-migration-ring/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Include rarely connected clients in each DirectAccess migration ring"
                },
                "articleSection": [
                    "IT",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "IT",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 201,
                "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": "Remote Access Always On VPN migration planning",
                    "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-access/da-always-on-vpn-migration/da-always-on-migration-planning"
                }
            }
        ]
    }
}