{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/", "slug": "dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy", "url": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/" }, "title": "Distinguish DSCP marking from outbound throttling in Windows QoS policy", "summary": "Should a Windows QoS policy mark traffic, throttle it, or apply both controls?", "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/" }, { "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:00+00:00", "modified_at": "2026-09-08T18:23:27+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 191, "potentially_affected": "Administrators creating application-scoped Windows QoS policies through Group Policy.", "dse_recommendation": "Have the application and network owners agree on the selected executable or path and the intended traffic behavior.", "primary_source": { "name": "Manage QoS Policy", "url": "https://learn.microsoft.com/en-us/windows-server/networking/technologies/qos/qos-policy-manage", "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

Windows QoS policies combine traffic controls with Group Policy management. A DSCP setting specifies the marking used for outbound traffic. A throttle setting limits the rate of outgoing traffic, and Microsoft permits marking and throttling together. The policy can target all applications, a named executable, a path and executable, or HTTP-server applications handling a specified URL. Microsoft documentation.

\n

Applicability

\n

Identify the application, traffic direction, endpoints, and the actual network treatment expected for its marking. Review whether the requirement is classification, a rate cap, or both before setting policy.

\n

DSE recommendation

\n

Have the application and network owners agree on the selected executable or path and the intended traffic behavior. Record the DSCP value and any throttle separately, including the chosen rate units. Scope the GPO to a representative pilot group and retain the former policy configuration.

\n

Verification

\n

Run the intended application and inspect its outbound marking and measured rate. Include another application that should remain outside the policy. Compare observed traffic with the approved settings and investigate unexpected matches or restrictions before assigning the policy to a larger device group.

\n

Official references

\n

Microsoft Learn: Manage QoS Policy. Source reviewed September 8, 2026.

", "content_text": "Source facts\nWindows QoS policies combine traffic controls with Group Policy management. A DSCP setting specifies the marking used for outbound traffic. A throttle setting limits the rate of outgoing traffic, and Microsoft permits marking and throttling together. The policy can target all applications, a named executable, a path and executable, or HTTP-server applications handling a specified URL. Microsoft documentation.\nApplicability\nIdentify the application, traffic direction, endpoints, and the actual network treatment expected for its marking. Review whether the requirement is classification, a rate cap, or both before setting policy.\nDSE recommendation\nHave the application and network owners agree on the selected executable or path and the intended traffic behavior. Record the DSCP value and any throttle separately, including the chosen rate units. Scope the GPO to a representative pilot group and retain the former policy configuration.\nVerification\nRun the intended application and inspect its outbound marking and measured rate. Include another application that should remain outside the policy. Compare observed traffic with the approved settings and investigate unexpected matches or restrictions before assigning the policy to a larger device group.\nOfficial references\nMicrosoft Learn: Manage QoS Policy. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nWindows QoS policies combine traffic controls with Group Policy management. A DSCP setting specifies the marking used for outbound traffic. A throttle setting limits the rate of outgoing traffic, and Microsoft permits marking and throttling together. The policy can target all applications, a named executable, a path and executable, or HTTP-server applications handling a specified URL. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/networking/technologies/qos/qos-policy-manage).\n\n## Applicability\n\nIdentify the application, traffic direction, endpoints, and the actual network treatment expected for its marking. Review whether the requirement is classification, a rate cap, or both before setting policy.\n\n## DSE recommendation\n\nHave the application and network owners agree on the selected executable or path and the intended traffic behavior. Record the DSCP value and any throttle separately, including the chosen rate units. Scope the GPO to a representative pilot group and retain the former policy configuration.\n\n## Verification\n\nRun the intended application and inspect its outbound marking and measured rate. Include another application that should remain outside the policy. Compare observed traffic with the approved settings and investigate unexpected matches or restrictions before assigning the policy to a larger device group.\n\n## Official references\n\n[Microsoft Learn: Manage QoS Policy](https://learn.microsoft.com/en-us/windows-server/networking/technologies/qos/qos-policy-manage). 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-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/", "url": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Distinguish DSCP marking from outbound throttling in Windows QoS policy", "item": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/", "url": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/", "headline": "Distinguish DSCP marking from outbound throttling in Windows QoS policy", "description": "Should a Windows QoS policy mark traffic, throttle it, or apply both controls?", "abstract": "Should a Windows QoS policy mark traffic, throttle it, or apply both controls?", "articleBody": "Source facts\nWindows QoS policies combine traffic controls with Group Policy management. A DSCP setting specifies the marking used for outbound traffic. A throttle setting limits the rate of outgoing traffic, and Microsoft permits marking and throttling together. The policy can target all applications, a named executable, a path and executable, or HTTP-server applications handling a specified URL. Microsoft documentation.\nApplicability\nIdentify the application, traffic direction, endpoints, and the actual network treatment expected for its marking. Review whether the requirement is classification, a rate cap, or both before setting policy.\nDSE recommendation\nHave the application and network owners agree on the selected executable or path and the intended traffic behavior. Record the DSCP value and any throttle separately, including the chosen rate units. Scope the GPO to a representative pilot group and retain the former policy configuration.\nVerification\nRun the intended application and inspect its outbound marking and measured rate. Include another application that should remain outside the policy. Compare observed traffic with the approved settings and investigate unexpected matches or restrictions before assigning the policy to a larger device group.\nOfficial references\nMicrosoft Learn: Manage QoS Policy. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:15:00+00:00", "dateModified": "2026-09-08T18:23:27+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/" }, "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-131-distinguish-dscp-marking-from-outbound-throttling-in-windows-qos-policy/#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": "Distinguish DSCP marking from outbound throttling in Windows QoS policy" }, "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": 191, "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": "Manage QoS Policy", "url": "https://learn.microsoft.com/en-us/windows-server/networking/technologies/qos/qos-policy-manage" } } ] } }