Windows Updates for Businesses Using InTune

Akins IT • April 11, 2018
Connect with us

Keeping Windows current is going to be more important than ever for organizations, but fear not administrators, modern management is here to help. With Microsoft’s mobile device management, Intune, it’s easier than ever keeping Windows 10 devices up-to-date by leveraging their new update model, Windows as a Service.  Here are some key terms that need to be outlined before jumping into implementation. 


Types of Updates 


There are two types of updates that are rolled out by Microsoft: Feature updates and Quality updates 

Feature Updates: Microsoft plans to release two feature updates a year, in spring and fall. New features like Bitlocker, Windows Defender ATP, Device Guard and Windows Hello to name a few, were released last year in version 1709. This version was coined the Fall Creator’s Update. 


Trivia Time: The version number 1709 isn’t arbitrary, it stands for the general release date of the update which was on September 2017 in this case. The next update, 1803, is a little overdue but rumor has it the release will be in early April. 


Quality Updates: Microsoft releases quality updates on Patch Tuesday, the first Tuesday of every month for workstations. As the name entails, quality updates provide either security, critical or driver updates to the system. 


Service Channels 


Service Channels provide a way for organizations to separate users into deployment groups for feature updates. The Insider Program, Semi-Annual Channel(Targeted) and Semi-Annual Channel are the most common. 


Insider Program:  The Insider Service Channel is for IT members eager to get their hands on the newest Windows features and provide feedback to Microsoft for improvements. Two flavors are available: Insider Slow and Insider Fast. The slow flavor will provide a more stable environment, whereas the fast flavor will include more features and components. 


Semi-Annual Channel(Targeted): The Semi-Annual Channel(Targeted) will make the semi-annual feature updates available as soon as it is released by Microsoft. The channel is intended for a pilot audience within the organization. 



Semi-Annual Channel: The Semi-Annual Channel is reserved for broad deployments of semi-annual feature updates. 

Deferral Period 


Deferral periods can be set on either feature updates or quality updates. This allows the IT department to test accordingly with their patching schedule and can be deferred up to 30 days from their initial release. 


Windows Ring (Deployment) 


Being a feature for Intune, Global Admin rights will be needed to create a Windows Ring. A Windows Ring is simply a group of settings that configure when and how the Windows 10 device will be updated. 

Log in to your Azure Tenant and head over to Intune – hopefully it’s saved to your favorites. Head to Software updates > Windows 10 Update Rings > Create. 


Here is an example of being able to preview new features before they’re generally released, while still on a stable Windows 10 environment – the Service channel is set to Insider Slow. The computer will check for Microsoft updates and Windows driver updates, and notify the user a download for an update was issued. Restart checks are enabled by default. By leaving it turned on, you have the ability to make sure your users’ computers are adequately charged. No deferral periods are being set for either feature or quality updates.   

Once the Window Ring policy is created, then it’s ready for group assignment. The Ring policy can be edited by clicking on Properties, above assignments. 

Learn More About Akins IT
By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts