Last month I wrote that security at CMC is something we do together. This post is about the next step in that shared work — and the one you will actually notice, because it touches the thing you do several times a day: signing in.
Over the coming months, CMC will move multi-factor authentication from Duo to Microsoft Entra ID — the cloud identity platform that already sits underneath Microsoft 365 and much of what we use. In practical terms, that means the familiar “approve it in the app” moment shifts from the Duo Mobile app to Microsoft Authenticator, using a number-matching prompt instead of a blind push.
Why We Are Making the Change
Duo has served the Claremont colleges well as a shared consortium service. But the consortium’s identity direction has consolidated around Microsoft Entra ID, and CMC is moving with it for three plain reasons:
- One identity, not two. Entra ID already authenticates our Microsoft 365 accounts. Bringing MFA into the same platform removes a hand-off between systems — fewer moving parts, fewer gaps.
- A stronger prompt. Number matching — typing a two-digit code shown on your screen into your phone — resists the push-fatigue tricks that have made “approve the login” attacks successful elsewhere. This is exactly the kind of friction the Responsible Secure Computing Policy is built on: a small pause that protects everything behind your account.
- Consortium economics. As partner campuses depart the shared Duo service, remaining costs rise and integration gets harder. Aligning now, on a coordinated timeline, is cheaper and smoother than being the last campus holding a key to an empty room.
What Changes — and What Doesn’t
What changes, when your turn comes:
- You will enroll your CMC account in Microsoft Authenticator (one enrollment, covering sign-ins across campus systems).
- Sign-ins will use number matching instead of a Duo push.
- Duo Mobile will eventually no longer be needed for CMC sign-in.
What does not change: your CMC username and password stay exactly the same. Your email, Canvas, Google Workspace, Slack, Workday, printing, and Wi-Fi all keep working — they just ride on the new front door. And nothing about our promises changes either: ITS will never ask you for your password, in email, by phone, or in person. If someone does, that is phishing — use the Report Phishing button.
The Timeline
ITS is targeting the spring 2027 release cycle (2027.04) for the first enrollment wave, with a phased rollout that continues through the year — first a pilot group, then staff, then faculty, then students. For a stretch, the two systems will run side by side; nobody loses access in the handoff. Legacy campus applications that predate modern authentication get engineering work along the way, and our timing is coordinated across the Claremont campuses so that students on shared platforms like Canvas are not bouncing between two different sign-in experiences.
You will hear from us well before anything changes for you — through your CMC email, the Help Desk, and the release notes, not through a surprise at the login screen. You can follow the work on the 2027.04 roadmap page.
What You Need to Do Right Now
Nothing. Duo keeps working exactly as it does today until ITS tells you otherwise. When your group’s enrollment window opens, the setup takes about five minutes, and Help Desk and Student Tech Services will be available in person for anyone who wants a hand. If you would like a head start on the habits that matter — strong unique passwords, number matching, reporting phishing — the MFA setup guide and the Responsible Secure Computing Policy cover them in five readable minutes.
Change at the login screen is the most visible kind of IT change, so it deserves plain talk: this one is worth it. One identity platform, a phishing-resistant prompt, and a consortium moving together. More details as the rollout takes shape this academic year.
Questions about the Duo-to-Entra transition? As always, the Help Desk is the front door for any account question.
Contact the Help Desk See the 2027.04 Roadmap MFA Setup Guide Responsible Secure Computing Policy– Carlos De La Rosa, Chief Information Officer