{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/",
        "slug": "dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/"
        },
        "title": "Distinguish creating an NPS template from applying it",
        "summary": "When does an NPS template actually change server behavior?",
        "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:13:26+00:00",
        "modified_at": "2026-09-08T18:29:34+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 2,
        "word_count": 234,
        "potentially_affected": "Administrators managing reusable Network Policy Server templates.",
        "dse_recommendation": "Name the template owner and record its intended consumers before application.",
        "primary_source": {
            "name": "Manage NPS Templates",
            "url": "https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-templates",
            "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 describes NPS templates as reusable configuration elements, including RADIUS clients and shared secrets, that can be exported to other NPS servers. Creating a template alone does not change NPS operation; the template takes effect when it is selected and applied in the relevant console location. Templates Management provides functions to inspect template use as well as create, modify, duplicate, or remove templates. <a href=\"https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-templates\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Identify the configuration element being reused and the server objects intended to consume it. Separate a newly saved template from an applied configuration. Review any sensitive values through the approved secret-handling process rather than copying them into ordinary change notes.</p>\n<h2>DSE recommendation</h2>\n<p>Name the template owner and record its intended consumers before application. Have the NPS administrator review the template content and select a representative client or configuration object for the pilot. Preserve the original consumer settings. When distributing templates to another server, include the intended use and approval scope so a receiving operator does not assume import automatically applies every setting.</p>\n<h2>Verification</h2>\n<p>Inspect the actual consumer object after application and compare its effective configuration with the template decision. Test the associated RADIUS transaction, then verify that an unrelated object was not changed. Record where the template is in use and who will review later revisions. Keep template creation, transfer, and application as separate completed actions.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-templates\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Manage NPS Templates</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nMicrosoft describes NPS templates as reusable configuration elements, including RADIUS clients and shared secrets, that can be exported to other NPS servers. Creating a template alone does not change NPS operation; the template takes effect when it is selected and applied in the relevant console location. Templates Management provides functions to inspect template use as well as create, modify, duplicate, or remove templates. Microsoft Learn.\nApplicability\nIdentify the configuration element being reused and the server objects intended to consume it. Separate a newly saved template from an applied configuration. Review any sensitive values through the approved secret-handling process rather than copying them into ordinary change notes.\nDSE recommendation\nName the template owner and record its intended consumers before application. Have the NPS administrator review the template content and select a representative client or configuration object for the pilot. Preserve the original consumer settings. When distributing templates to another server, include the intended use and approval scope so a receiving operator does not assume import automatically applies every setting.\nVerification\nInspect the actual consumer object after application and compare its effective configuration with the template decision. Test the associated RADIUS transaction, then verify that an unrelated object was not changed. Record where the template is in use and who will review later revisions. Keep template creation, transfer, and application as separate completed actions.\nOfficial references\nMicrosoft Learn: Manage NPS Templates. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft describes NPS templates as reusable configuration elements, including RADIUS clients and shared secrets, that can be exported to other NPS servers. Creating a template alone does not change NPS operation; the template takes effect when it is selected and applied in the relevant console location. Templates Management provides functions to inspect template use as well as create, modify, duplicate, or remove templates. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-templates).\n\n## Applicability\n\nIdentify the configuration element being reused and the server objects intended to consume it. Separate a newly saved template from an applied configuration. Review any sensitive values through the approved secret-handling process rather than copying them into ordinary change notes.\n\n## DSE recommendation\n\nName the template owner and record its intended consumers before application. Have the NPS administrator review the template content and select a representative client or configuration object for the pilot. Preserve the original consumer settings. When distributing templates to another server, include the intended use and approval scope so a receiving operator does not assume import automatically applies every setting.\n\n## Verification\n\nInspect the actual consumer object after application and compare its effective configuration with the template decision. Test the associated RADIUS transaction, then verify that an unrelated object was not changed. Record where the template is in use and who will review later revisions. Keep template creation, transfer, and application as separate completed actions.\n\n## Official references\n\n[Microsoft Learn: Manage NPS Templates](https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-templates). 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-225-distinguish-creating-an-nps-template-from-applying-it/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Distinguish creating an NPS template from applying it",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/",
                "headline": "Distinguish creating an NPS template from applying it",
                "description": "When does an NPS template actually change server behavior?",
                "abstract": "When does an NPS template actually change server behavior?",
                "articleBody": "Source facts\nMicrosoft describes NPS templates as reusable configuration elements, including RADIUS clients and shared secrets, that can be exported to other NPS servers. Creating a template alone does not change NPS operation; the template takes effect when it is selected and applied in the relevant console location. Templates Management provides functions to inspect template use as well as create, modify, duplicate, or remove templates. Microsoft Learn.\nApplicability\nIdentify the configuration element being reused and the server objects intended to consume it. Separate a newly saved template from an applied configuration. Review any sensitive values through the approved secret-handling process rather than copying them into ordinary change notes.\nDSE recommendation\nName the template owner and record its intended consumers before application. Have the NPS administrator review the template content and select a representative client or configuration object for the pilot. Preserve the original consumer settings. When distributing templates to another server, include the intended use and approval scope so a receiving operator does not assume import automatically applies every setting.\nVerification\nInspect the actual consumer object after application and compare its effective configuration with the template decision. Test the associated RADIUS transaction, then verify that an unrelated object was not changed. Record where the template is in use and who will review later revisions. Keep template creation, transfer, and application as separate completed actions.\nOfficial references\nMicrosoft Learn: Manage NPS Templates. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:13:26+00:00",
                "dateModified": "2026-09-08T18:29:34+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-225-distinguish-creating-an-nps-template-from-applying-it/"
                },
                "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-225-distinguish-creating-an-nps-template-from-applying-it/#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": "Distinguish creating an NPS template from applying it"
                },
                "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": 234,
                "timeRequired": "PT2M",
                "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": "Manage NPS Templates",
                    "url": "https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-templates"
                }
            }
        ]
    }
}