Forum Discussion
Feedback about MS-102 retirement
Just adding my thoughts here because I’m completely on the same page.
I honestly don’t get the logic behind retiring an expert‑level exam like MS‑102 and replacing it with an associate‑level one. Microsoft 365 is massive, and MS‑102 has been one of the few certifications that actually reflects the depth of what we do day‑to‑day. Losing it feels like we’re removing a key part of the certification path. I am the guy that did both your 100/101 and the beta of 102 and to have this AI chucked at us after removing SPO and EXO exams.
AB‑650 might cover some of the MS‑102 content, sure, but it also brings in a lot of AI‑heavy material that doesn’t replace the core admin and engineering skills the expert exam validated and we actually use daya to day. With MS‑900 already gone, and the Exchange and SharePoint exams retired years ago (which im still peeeeeeeeed about), we’re left without any proper certification that covers those workloads — even though they’re still critical in real environments. Want proof, check how many 3rd party content sites the MCTs are using for SPO and EXO, check and your see.
It really feels like the Microsoft 365 exams aren’t being treated with the seriousness they deserve. We need solid, role‑based exams that actually map to the responsibilities we have, not more AI‑focused content replacing foundational and expert‑level material. And we also need actual content deigners and writer and not AI slop or 3rd parties who put slop together, much like the refreshed md-102.
Could you or someone from the team please give some clear communication around the retirement of MS‑102 on the actual pages, why the change at a fundamental/curriculum planning structure and what the roadmap looks like for Microsoft 365 certifications going forward? A lot of us rely on these exams for professional development, for training work (IE contract work) and planning, so knowing the direction at this point will forge my participation going forward
There was an opportunity for MCTs to discuss with the content leads exactly on this change to the curriculum but only a handful of us bothered to attend.
Monthly MCT Content Community - Copilot Curriculums | Microsoft Community Hub
- Timrae79578Jul 01, 2026MCT
Hi Julian
This mentions copilot and nothing to do with ms-102. If it said copilot integration changes to 102 104 yadda yadda list the courses sure. But one looks and goes oh ok, its changing the current ab streams, not my remit and scroll on. Context and clarity in communication needed to be redefined on events also
- Timrae79578Jul 01, 2026MCT
You mean a shielded post to hide the copilot agenda and 0 contibutions from the community leads prior. I would have spoken up and im asking those responsible present . Yet again poor communication. Courseware marketplace has responded now with its own course now.
- Jul 01, 2026
We are MCT Community Leads, not Microsoft Credential Community Leads. Stuff from other product groups is communicated to us, we don't have a say unless they specifically want our feedback.
And also, no offense but we have known about the change since March and it has been publicly available for like 2 months now, not once have I seen you bringing this up on the call or in the MCT CL Teams. You posting this stuff now seems very performative.
- Timrae79578Jul 02, 2026MCT
I'd like to see in out meeting note if this was flagged but as I have been to every one for 2026, I believe this is a no. Yes I subscribe to alot of alerts. But seriously MS should engage by participation of the ms learn material and exam to gauge how much more notice and widespread. Sure march but again I challenge whether anything was communicated in LI before the partner call. My gut (and computer) says no.
- Jul 01, 2026
Yhea right, the name of that session don’t say anything useful… The MCT lounge is a mess so if this whas a important session than the communication fails again…
- Julian_SharpJul 01, 2026Learn Expert
All sessions with the content dev teams are important. If you didn't understand what was to be covered, you could have asked