u/dantofisial

MS health dashboard lags. By the time it acknowledges an issue, half the support tickets are already in. The signal is usually in r/microsoft365 and r/sysadmin first.

Built a thing that scrapes r/microsoft365, r/Office365, r/sysadmin, r/Intune, r/exchangeserver, MS health dashboard, bleeping computer, askwoody, borncity every 4–6h. It classifies posts as real regressions only when they cite a KB or specific service + concrete breakage. Groups duplicates so 15 reports of "Teams calendar not syncing" collapse to one entry.

Here you can try it out: https://www.patchscanner.com/

M365 service incidents don't always come with KBs. Do you need something tied harder to MC/IT change notifications in the admin center? Any feedback is welcome.

Every patch tuesday the same dance: did this CU break DHCP again? RDS? NTLM? Built a scraper that pulls r/sysadmin, r/WindowsServer adjacent subs, r/ActiveDirectory, MS health dashboard, bleeping computer, a handful of patch blogs every 4–6h. Tags real regressions (KB + component + concrete breakage), dedups across sources.

So instead of doomscrolling 4 subs and 3 blogs the morning after, you get one ranked list.

What other server related sources should I be pulling? Specific MVP blogs, mailing lists, MS tech community boards?

Can drop the link of the tracker in the comments if anyone wants to try it out

EDIT: Added json api and sources on all regressions, thanks for the feedback!

Built a tracker that aggregates r/sysadmin, r/sccm-adjacent subs, MS Health Dashboard, Bleeping Computer, AskWoody, and a few patch blogs. LLM filters to real regressions tied to KB + component, dedups across sources, ranks by how many people are reporting.

Idea: check it before approving a deployment ring, get a heads-up on KBs that are blowing up in the wild.

https://win-update-tracker.vercel.app free weekly email digest available.

For ConfigMgr-heavy shops: what's your current pre-deploy "is this KB safe" check? Mailing list? Specific blogger? Trying to make sure the feeds match where you'd already look.

Half my Azure incidents start with "is anyone else seeing..." in a chat instead of a known issues page.

Built a thing that scrapes r/sysadmin, r/AZURE, r/Intune, MS Health Dashboard, Bleeping Computer, AskWoody, BornCity, and a few WinITPro/Exchange blogs every 4–6 hours. Runs each post through an LLM that flags it as a real regression only if it cites a KB / specific component and a fix or workaround. Groups by KB so you see "12 people hit this, here's the workaround" instead of 12 separate posts.

https://win-update-tracker.vercel.app runs weekly digest if you want it pushed to inbox.

Mainly want to know: does this catch Azure-side stuff fast enough, or do I need more sources (status.azure.com RSS, Azure updates blog, etc)? What feed am I missing?

First post here! Every Exchange CU and SU release I'd find out something broke one of three ways: a user ticket, someone posting about it 48 hours later, or the Exchange team blog quietly editing a Known Issues section three weeks in.

So I built a thing that watches for it:

What it does:

- Scrapes r/exchangeserver, r/sysadmin, r/msp, r/Intune, r/ActiveDirectory, r/AZURE

- Pulls RSS from Bleeping Computer, AskWoody, BornCity, MS Security Blog, and the Exchange Team / Windows IT Pro / Intune TechCommunity boards

- Classifies each post by KB number, component, severity (LLM, every claim links back to its source thread)

- Optional Thursday digest email if you want it pushed before next CU window

Feedback wanted, especially Exchange-specific regressions from this month it missed, hybrid mailflow, OWA, AMSI, transport rules, that kind of thing.

 Free. Looking for feedback, especially regressions from this month it missed, or false positives.

https://win-update-tracker.vercel.app/

First post here! Every patch wave I was finding out an update broke something one of three ways: ring 1 user tickets the morning after, someone posting about it 48 hours later, or it showing up on the MS Health Dashboard three weeks late.

So I built a thing that watches for it:

What it does:
- Scrapes r/Intune, r/sysadmin, r/msp, r/ActiveDirectory, r/exchangeserver, r/AZURE
- Pulls RSS from Bleeping Computer, AskWoody, BornCity, MS Security Blog, and the Intune / Windows IT Pro / Exchange TechCommunity boards
- Classifies each post by KB number, component, severity (LLM, every claim links back to its source thread)
- Optional Thursday digest email if you want it pushed before you greenlight the next ring

Feedback wanted, especially Intune-specific regressions from this month it missed, co-management edge cases, autopilot, compliance policy weirdness, that kind of thing.

Disclosure: I built it, free to use. Happy to drop the link in the comments if anyone wants to poke at it.

First post here! Every patch tuesday I was finding out about broken KBs one of three ways: a user ticket the morning after, someone posting here 48 hours later, or MS adding it to their Known Issues page three weeks later.

So I built a thing that watches for it:

What it does:
- Scrapes r/sysadmin, r/msp, r/Intune, r/ActiveDirectory, r/exchangeserver, r/AZURE
- Pulls RSS from Bleeping Computer, AskWoody, BornCity, MS Security Blog, and the Windows IT Pro / Intune / Exchange TechCommunity boards
- Classifies each post by KB number, component, severity (LLM, every claim links back to its source thread)
- Optional Thursday digest email if you want it pushed

Feedback wanted, especially if it missed regressions from this month

you can use it here, it is free, would love to improve it for my personal use and help others if they find it helpful:
https://win-update-tracker.vercel.app/