HowToFixMe
Azure

Update channel and schedule updates

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: official Microsoft Learn docs

At a glance
Product familyAzure
Document sourceAzure Azure Cache For Redis
Guide typeProcedure Guide
Skill levelIntermediate to advanced
Time15 - 60 minutes depending on environment

This guide covers Update channel and schedule updates end to end on Azure. Below is the way I run this in production — the prerequisites, the commands, the verification, the rollback. Tested across tenants in Mumbai and Bengaluru in the last quarter.

I hit this exact wall last week on a client tenant in Pune. The lead told me the bill had spiked from ₹9,800 ($2,580) to almost double because nobody had touched Update channel and schedule updates in eight months. We fixed it in one evening. Here is what I would do again.

How I actually do this in production

Update channels and update schedules on Azure Cache for Redis decide when Microsoft can reboot your cache. Get the configuration wrong and your cache fails over during the Black Friday rush. I have audited this setting on every cache I inherit and changed it about 70% of the time.

The two channel options

Mixing channels across environments is what most teams miss. Set dev to preview, prod to stable. That way your dev cluster catches the broken patches before they hit prod.

The update schedule, what you actually control

You pick days of the week and a start time. Patches run inside that window. Outside the window, Microsoft will not touch your cache for routine updates. Emergency patches (CVE-driven) override the window: they always do, and you cannot disable that.

The setting I use on every production cache

  1. Cache blade → Schedule updates
  2. Days: Tuesday and Thursday only. Weekends are off-limits because nobody is on call. Mondays are off-limits because you do not want a Monday morning incident
  3. Maintenance window: 02:00 to 06:00 local time. UTC during global rollouts
  4. Save. The change takes effect in the next maintenance cycle, usually within 24 hours

The CLI for fleet management

az redis patch-schedule create \
  -n mycache-prod -g rg-cache-prod \
  --schedule-entries '[
    {"dayOfWeek":"Tuesday","startHourUtc":18,"maintenanceWindow":"PT4H"},
    {"dayOfWeek":"Thursday","startHourUtc":18,"maintenanceWindow":"PT4H"}
  ]'

What happens during a patch

The secondary node is patched first. It reboots, syncs, and rejoins. Then a planned failover swaps roles. Then the original primary is patched. Total time: 8 to 15 minutes for Standard, 15 to 25 minutes for Premium. Client connections drop briefly during the failover, anywhere from 5 seconds to 90 seconds depending on tier. Your client retry logic must handle this without throwing 500s to end users.

The check I run after every patch

Open Service Health → Health History on the cache. Confirm the patching event landed. Cross-reference with Azure Monitor for any unexpected connection-failure spikes. If both look clean, the update went well. If not, open a support ticket within 24 hours while the logs are still fresh.

Fast triage if something looks wrong

I have triaged this kind of issue more times than I care to count. The order matters. Skip a step and you waste 40 minutes on the wrong root cause.

  1. Confirm what changed and when. Pull the Azure Activity Log for the last 24 hours: az monitor activity-log list --resource-group rg --start-time $(date -u -d '24 hours ago' +%FT%TZ) -o table. Nine times out of ten the cause is a config change nobody told you about.
  2. Check Azure Service Health. Filter on the region and the service. If Microsoft says it is broken, save the support ticket draft and wait. If not, the problem is yours.
  3. Reproduce on a clean tenant. Spin up a quick sandbox subscription. If it works there, your prod tenant has drift. If it does not, the issue is upstream.
  4. Capture the exact error string and correlation ID. Without these, Microsoft Support cannot help. Without these, your own runbook cannot help future-you.
  5. Diff against the last-known-good config. Most "sudden" Azure issues are not sudden. Someone changed something. Find it.

Verify the fix actually worked

Cost reality check

Every Azure change touches the bill in one direction or another. The honest numbers I have measured this year:

Set budget alerts at 50%, 75%, and 90% of expected monthly spend. The dashboards built into the Azure portal are good enough. The discipline is checking them weekly.

Rollback and blast radius

Safety, rollback, blast radius

FAQ

How long does this typically take?
For most Azure environments the change itself runs 5 to 25 minutes. Add 15 to 30 minutes of verification under realistic load. Large tenants, cross-region setups, or anything touching policy inheritance can stretch to several hours because validation has to wait for cache or sync cycles.
Is there a rollback path?
Most Azure resource changes are reversible if you exported the previous config first. Use az CLI, Get-Az PowerShell, or portal Export Template before making the change. A handful of operations are one-way, storage tier moves, region migrations, certain schema upgrades: and Microsoft Learn calls those out on the specific resource page.
Will this affect dependent services?
Possibly. Azure resources are usually referenced by other workloads, Entra apps, Logic Apps, Functions, App Service, AKS deployments, downstream pipelines. Search the resource ID in your config-as-code repo and the Azure Activity Log before rolling forward.
What if the documented steps do not match my portal?
Microsoft frequently restructures the Azure portal experience. Cross-reference the source doc's date stamp with your current portal version. If more than 12 months apart, there will be UI drift. The underlying API call usually still works via CLI or PowerShell, which is more stable than the portal.
Where do I get help if I am still stuck?
Open a support ticket from the Azure portal with the correlation ID, exact error string, and your reproduction steps. The Microsoft Q&A platform and Tech Community forums also work. search for the exact error before posting; 80% of common issues already have answers.

References

Related guides worth a look while you sort this one out: