Decision: Don’t assume your alumni mailbox is shutting down today. Microsoft says free Exchange Online for Alumni will exit when an eligible school reaches a relevant agreement renewal or expiry; ask your school about your account, then migrate personal accounts in stages.
This is for graduates who still receive account alerts, subscriptions, or website messages at a school address. It also helps freelancers and side-business owners who use that address for client contact or project accounts.
Last updated November 13, 2026. The policy details below were checked against Microsoft’s licensing announcement and Microsoft Learn’s education portfolio information. Your individual account schedule must come from your school.
The policy boundary
Microsoft has confirmed that free Exchange Online for Alumni will exit for applicable schools when they first renew, extend, or enter a new agreement on or after January 1, 2028. Existing licenses and benefits remain in place through the current agreement term, according to Microsoft’s announcement.
That statement describes a licensing change between Microsoft and an education institution. It does not give every graduate a personal mailbox shutdown date. Your school’s agreement, account configuration, and local communication determine what happens to your specific address.
Does Microsoft 365 Education’s free alumni email stop on the announcement date? No. The announcement is not a universal instruction to close every former student’s mailbox on that day. Microsoft Learn’s education FAQ describes the program, but your school must confirm how its agreement and account arrangements apply to you.
“Alumni email” can also conceal several different things. A school may provide an email address, mailbox access, or other Microsoft 365 Education benefits under its tenant and licensing arrangements. Your personal accounts at banks, social networks, shopping services, or work platforms are separate services. Changing a school license does not automatically update those third-party account records.
Ask the school’s IT or alumni office for written answers to these points:
- Is your mailbox currently active, and is it covered by the school’s existing agreement?
- What event or date could affect your account?
- Will the school provide an individual notice or a migration window?
- Does the school plan to offer forwarding, export, or another transition option?
- How long, if at all, will you be able to sign in after the mailbox changes?
Microsoft’s graduating-student license guidance is useful background, but it is not a substitute for the school’s account-specific instructions. Do not plan around a rumored deadline or a date reported without checking whether it applies to your institution.
Before changing anything: map the responsibilities
Treat the school address as a dependency to remove, not as a mailbox to abandon without review. It may appear in different fields on the same service: username or login address, contact email, and recovery address. Those fields can have separate settings and separate confirmation steps.
Search your inbox for account-related messages, receipts, security notices, password resets, and subscription renewals. Review your browser’s saved logins and password manager, plus any account list you already maintain. Search for the school domain in your records, but don’t rely on inbox search alone: a service may never have sent a recent message.
For each account, record the service, the address currently on file, what the address does, the next action, and the date you verified the change. Don’t place passwords or recovery codes in this inventory. Keep it in a secure location you can still reach if the school mailbox becomes unavailable.
How do you find personal accounts still tied to a school email? Start with the sources you control: saved logins, password-manager entries, recurring payment records, project tools, newsletters, and old account-confirmation messages. Then check important services directly. An empty search result does not prove that no account uses the address.
Rank each account by the consequence of losing access. Accounts that control money, identity, work, or access to other accounts need attention first. Routine newsletters can wait. A client contact address also deserves priority if a missed message could interrupt an active project.
| Account or address option | Best role during migration | Main benefit | Main limitation |
|---|---|---|---|
| School alumni mailbox | Temporary bridge, only while the school confirms it remains available | You can keep receiving messages already sent there while access continues | The school controls the account and its schedule |
| Personal mailbox you control | Primary login, contact, and recovery route for important services | You can sign in directly and manage the account yourself | You must keep its access and recovery details current |
| Long-term email alias or forwarding address | Separate incoming mail by project or service | Can help organize addresses and limit exposure of your main address | Does not update third-party records or automatically provide a separate login |
| Temporary inbox | Low-stakes, short-term signups where future access is unnecessary | Keeps a one-time registration separate from your main inbox | Unsuitable for important accounts, ongoing correspondence, or recovery |
An alias and a forwarding route solve different parts of the problem from a primary mailbox. They can help sort incoming mail or keep your main address private, but they do not automatically change the email stored in a service’s profile. They also do not guarantee that a service will accept an address or send every type of message to it.
For an account you need to access for the long term, choose an address you can open directly and recover independently. If you want to route subscriptions or project messages through an alias, confirm that the arrangement remains available and that you know how to manage it. The guide to email aliases for an ongoing learning account illustrates why an alias should not be confused with a reliable account-recovery path.
Set up the destination before moving accounts
Choose your personal mailbox first. It should be one you control outside the school’s tenant, can access directly, and can recover using methods that do not depend on the school address. Test its sign-in and recovery options before making it the destination for important accounts.
Then decide whether you need an address layer between that mailbox and routine incoming mail. A long-term alias can be useful for project enquiries or subscriptions if you can maintain it. A temporary inbox is a different choice: reserve it for a low-stakes interaction when you do not expect to need future sign-in, correspondence, or password recovery.
| Destination setup | Suitable use | Verify before relying on it |
|---|---|---|
| Direct personal mailbox | Important logins, account recovery, client correspondence | Sign-in works; recovery methods do not rely on the school address |
| Personal mailbox plus managed alias | Project or subscription messages you want to distinguish | The alias remains under your control; forwarded messages reach the destination |
| Temporary inbox for a one-off interaction | A short-lived registration with no expected future access | The account is genuinely low-stakes and does not require continuing recovery |
This is a choice about responsibility, not just inbox tidiness. A message routed to the right folder is useful only if you can still access the address and act on it. If the school account is the only recovery route for the personal mailbox itself, fix that dependency before changing a large set of third-party accounts.
Update accounts by consequence
Make changes in batches that reflect the risk of losing access. Avoid changing every account in one sitting. If you encounter an unexpected confirmation requirement or a login problem, a smaller batch makes it easier to identify which change caused it.
Start with accounts that must remain accessible: financial and identity services, password managers, primary cloud or device accounts, and tools that control your work. For each one, check the login address, contact address, and recovery address separately. A profile may display one email while its security settings retain another.
Next, update services that send work or customer messages. If a client uses the school address, replace it in the relevant profile, invoices, proposals, contact pages, and project systems. Keep the address consistent across the places where clients are told to reach you.
After that, update recurring subscriptions, websites, and general notifications. These often have lower immediate consequences, but they still need an owner. If you want to sort them by source, assign a distinct address only where you can maintain that address and receive messages for as long as the account matters.
For each change:
- Sign in using the existing method before editing the email field.
- Read the service’s own instructions for changing a login or recovery address.
- Enter the destination address and complete the service’s confirmation process.
- Check whether the service requires a separate change to contact or recovery details.
- Record the result and the address now listed.
- Return to the account later if the service has not confirmed the change or the displayed details remain unclear.
Can you assume every website accepts a new address in the same way? No. The change flow is controlled by each service. If its rules are unclear, check that service’s account settings or official help before acting. Don’t assume an alias, forwarding route, or temporary address will be accepted just because another service accepted it.
Verify receipt and account access
A confirmation email reaching the new mailbox is only one part of the test. You also need to know whether you can still sign in, whether recovery points to the intended address, and whether important notifications go where you expect.
For each account you update, check the service’s confirmation status and its profile or security page. Sign out and test the normal login path only when you know how to restore access if the test fails. If a service offers a separate recovery check, review it directly rather than inferring it from the contact address.
Before relying on a new address, how do you verify that it receives mail? Use the service’s own allowed confirmation process, then open the destination mailbox and confirm the message arrived. Return to the account settings and verify the saved address. For critical accounts, also confirm that the login and recovery methods are what you intended. Receiving one confirmation message does not establish that every future notification or recovery message will follow the same path.
A migration log helps prevent false confidence. Mark an account as complete only after you have checked the relevant fields and can access the account. If a message is delayed or absent, check the service’s instructions and the destination mailbox settings before repeating changes. Avoid removing the school address from a critical account until its replacement is confirmed and usable.
Keep the school address as a bridge only if the institution says it will remain available and its policy permits continued use. Do not treat forwarding as proof that every message, login challenge, or recovery process has moved. A forwarding route can deliver some mail while the account’s sign-in identity still points to the old address.
Maintain the new arrangement
Once the urgent accounts are stable, review the remaining inventory against the school’s confirmed schedule. If the school has not given you an individual date, ask again rather than inventing one. Microsoft’s policy boundary concerns eligible school agreements; it does not tell you when your own sign-in will change.
Each time you update an account, revise your address record. When you create a new project, subscription, or personal account, decide at that point whether it needs your primary mailbox or a managed alias. That small decision prevents the school address from silently becoming the default again.
The pros of this approach are control and traceability: you know which accounts depend on which address, and you can see which changes still need confirmation. The cost is maintenance. You must keep your inventory current, protect access to the personal mailbox, and confirm any alias or forwarding arrangement against its actual terms. A routing layer is not a permanent address unless you can verify its continued availability and manage it over time.
For a limited signup that does not need future access, a temporary address can keep your primary inbox out of a one-off registration. Tmpkey offers a temporary email option for that narrower use; it is not an official replacement for a school mailbox and should not be used as the sole login or recovery route for an important account. If you are weighing that option, review the Tmpkey service information and its data notice before deciding. For long-term accounts, move directly to a personal mailbox you control, then verify every login, contact, and recovery path.
Return to your inbox and check your address
Once you have a working connection, continue on your original device and browser. For ongoing email access, choose a forwarding alias.