{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/", "slug": "dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout", "url": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/" }, "title": "Check existing Windows update offers before postponing a gradual rollout", "summary": "Does moving a gradual feature rollout's start date retract offers that devices already received?", "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": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "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-10T00:22:57+00:00", "modified_at": "2026-09-10T02:11:18+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 1, "word_count": 215, "potentially_affected": "Use this check when pausing expansion or revising a gradual feature-update rollout. Separate devices with an existing offer from those still waiting, and distinguish offer availability from installation progress.", "dse_recommendation": "Base the intervention on current device states rather than a calendar edit alone.", "primary_source": { "name": "Configure Rollout Options for Feature Update Policies - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-rollout-options", "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

For a gradual Windows feature rollout, moving the first-group date into the future leaves existing offers in place; newly added devices wait for the revised start. Changing rollout dates can reassign devices that have not yet received an offer. Removing a device from targeting triggers an attempted offer retraction, except when the device has already begun processing the update. Microsoft Learn.

\n

Applicability

\n

Use this check when pausing expansion or revising a gradual feature-update rollout. Separate devices with an existing offer from those still waiting, and distinguish offer availability from installation progress.

\n

DSE recommendation

\n

Base the intervention on current device states rather than a calendar edit alone. Have the update owner identify the intended treatment for offered, processing, and not-yet-offered devices. Do not present a later start date as a universal stop command or promise that removing assignments can recall every update.

\n

Verification

\n

In an approved pilot, inspect offer state before and after changing the schedule. Compare a device already offered the update with one awaiting a future group. Where targeting is removed, verify the actual resulting state and account for devices already processing the update. Preserve the original schedule, revised dates, and observations so support teams know which devices remain in progress.

\n

Official references

\n

Microsoft Learn: Configure Rollout Options for Feature Update Policies.

", "content_text": "Source facts\nFor a gradual Windows feature rollout, moving the first-group date into the future leaves existing offers in place; newly added devices wait for the revised start. Changing rollout dates can reassign devices that have not yet received an offer. Removing a device from targeting triggers an attempted offer retraction, except when the device has already begun processing the update. Microsoft Learn.\nApplicability\nUse this check when pausing expansion or revising a gradual feature-update rollout. Separate devices with an existing offer from those still waiting, and distinguish offer availability from installation progress.\nDSE recommendation\nBase the intervention on current device states rather than a calendar edit alone. Have the update owner identify the intended treatment for offered, processing, and not-yet-offered devices. Do not present a later start date as a universal stop command or promise that removing assignments can recall every update.\nVerification\nIn an approved pilot, inspect offer state before and after changing the schedule. Compare a device already offered the update with one awaiting a future group. Where targeting is removed, verify the actual resulting state and account for devices already processing the update. Preserve the original schedule, revised dates, and observations so support teams know which devices remain in progress.\nOfficial references\nMicrosoft Learn: Configure Rollout Options for Feature Update Policies.", "content_markdown": "## Source facts\n\nFor a gradual Windows feature rollout, moving the first-group date into the future leaves existing offers in place; newly added devices wait for the revised start. Changing rollout dates can reassign devices that have not yet received an offer. Removing a device from targeting triggers an attempted offer retraction, except when the device has already begun processing the update. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-rollout-options).\n\n## Applicability\n\nUse this check when pausing expansion or revising a gradual feature-update rollout. Separate devices with an existing offer from those still waiting, and distinguish offer availability from installation progress.\n\n## DSE recommendation\n\nBase the intervention on current device states rather than a calendar edit alone. Have the update owner identify the intended treatment for offered, processing, and not-yet-offered devices. Do not present a later start date as a universal stop command or promise that removing assignments can recall every update.\n\n## Verification\n\nIn an approved pilot, inspect offer state before and after changing the schedule. Compare a device already offered the update with one awaiting a future group. Where targeting is removed, verify the actual resulting state and account for devices already processing the update. Preserve the original schedule, revised dates, and observations so support teams know which devices remain in progress.\n\n## Official references\n\n[Microsoft Learn: Configure Rollout Options for Feature Update Policies](https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-rollout-options)." }, "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-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/", "url": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Check existing Windows update offers before postponing a gradual rollout", "item": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/", "url": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/", "headline": "Check existing Windows update offers before postponing a gradual rollout", "description": "Does moving a gradual feature rollout's start date retract offers that devices already received?", "abstract": "Does moving a gradual feature rollout's start date retract offers that devices already received?", "articleBody": "Source facts\nFor a gradual Windows feature rollout, moving the first-group date into the future leaves existing offers in place; newly added devices wait for the revised start. Changing rollout dates can reassign devices that have not yet received an offer. Removing a device from targeting triggers an attempted offer retraction, except when the device has already begun processing the update. Microsoft Learn.\nApplicability\nUse this check when pausing expansion or revising a gradual feature-update rollout. Separate devices with an existing offer from those still waiting, and distinguish offer availability from installation progress.\nDSE recommendation\nBase the intervention on current device states rather than a calendar edit alone. Have the update owner identify the intended treatment for offered, processing, and not-yet-offered devices. Do not present a later start date as a universal stop command or promise that removing assignments can recall every update.\nVerification\nIn an approved pilot, inspect offer state before and after changing the schedule. Compare a device already offered the update with one awaiting a future group. Where targeting is removed, verify the actual resulting state and account for devices already processing the update. Preserve the original schedule, revised dates, and observations so support teams know which devices remain in progress.\nOfficial references\nMicrosoft Learn: Configure Rollout Options for Feature Update Policies.", "datePublished": "2026-09-10T00:22:57+00:00", "dateModified": "2026-09-10T02:11:18+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/" }, "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-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/#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": "Check existing Windows update offers before postponing a gradual rollout" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@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": "Configure Rollout Options for Feature Update Policies - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-rollout-options" } } ] } }