Johns Hopkins users can reach email through myJH, but myJH itself is not the email system. Hopkins uses Microsoft Exchange for faculty, staff and student email accounts, while Microsoft Outlook provides the familiar mailbox interface. The myJH portal acts as one route for finding and launching that service.
That distinction matters when troubleshooting. If myJH opens but Outlook does not, the problem has already moved beyond the portal itself. Likewise, changing the arrangement of applications on the myJH homepage will not change the underlying mailbox.
[PUBLICATION NAME] is independent from Johns Hopkins and does not provide email authentication or request JHED credentials.
Where Outlook Appears in myJH
Johns Hopkins’ current remote-access documentation directs users to the Messaging category in myJH and then to the Outlook resource for web-based email access. Depending on the account and authentication context, MFA may also be required.
This gives the workflow three distinct layers:
myJH helps you locate Outlook.
JHED/enterprise authentication establishes who you are.
Outlook/Exchange handles the actual mailbox.
The same person may experience a problem at any one of those layers.
Johns Hopkins Uses Microsoft Exchange
The current myJH support documentation identifies Microsoft Exchange as the email platform for Johns Hopkins faculty, staff and students. The service is managed by the Enterprise Email Services Team within IT@JH.
Johns Hopkins IT also identifies Microsoft Outlook as the institution’s enterprise email system and places it alongside Microsoft 365 collaboration services such as OneDrive and SharePoint.
That means searches for:
- myJH email;
- Hopkins Outlook;
- JHU Outlook;
- Johns Hopkins Exchange;
- Hopkins Office 365 email
can all involve related parts of the same Microsoft-based environment without those names being interchangeable.
Does Outlook Require VPN?
Not necessarily.
Johns Hopkins remote-access guidance identifies Outlook’s web client as accessible through myJH. It separately states that Microsoft Office 365 tools can be accessed remotely through a web interface and do not require VPN access.
This is important because users sometimes assume that being off campus automatically means they need VPN.
For many cloud-hosted services, that is not the case.
VPN becomes more relevant when a resource is restricted to the Johns Hopkins network rather than simply being an authenticated cloud service.
Our separate guide to myJH remote access, VPN and MyCloud explains this distinction.
JHED ID and Email Address Are Related but Different
A JHED ID is the enterprise login identifier associated with a Johns Hopkins user.
Johns Hopkins explains that many institutional resources rely on the JHED Login ID, with email specifically listed as one example.
An email address is the address to which messages are delivered.
These may look similar because Hopkins email addresses can incorporate the user’s JHED identity, but a username used for authentication and an email address used for communication perform different functions.
That becomes particularly important when the user has an email alias.
What Is a Johns Hopkins Email Alias?
Johns Hopkins describes an email alias as an alternate email address that can forward messages to another Hopkins mail address.
Its current myJH documentation notes that Hopkins email accounts can use domains such as:
@jh.edu;@jhu.edu;@jhmi.edu.
Faculty and staff at Johns Hopkins University or Johns Hopkins Medical Institutions may be able to create a customized email alias.
An alias does not mean a second independent mailbox has necessarily been created.
That is a key distinction.
If original-address and preferred-address ultimately deliver into the same mailbox, losing access to Outlook is still an account-access issue rather than an alias-selection problem.
The Email Alias Tool Is a Separate myJH Resource
Current Hopkins instructions direct users to search myJH for the Email Alias application.
The service displays the Hopkins default email address and existing alias information. Depending on the user’s affiliation, it can provide options for aliases and forwarding addresses. Johns Hopkins notes that external forwarding is not available to every user.
This is another example of why myJH functions more like an application directory than a single monolithic system.
You may authenticate through one portal but interact with specialized tools for:
- email;
- aliases;
- payroll;
- student records;
- VPN;
- profile information.
Students and Employees Do Not Have Identical Alias Options
Current Hopkins documentation distinguishes student options from faculty/staff options.
Students can have options involving default and forwarding addresses, while eligible faculty and staff can have additional custom-alias functionality.
So comparing the Email Alias screen of two users from different Hopkins populations can be misleading.
A missing option may reflect the account’s affiliation rather than an application malfunction.
Group Email Accounts Are Something Else Again
A custom personal alias should also not be confused with a group email account.
Johns Hopkins describes Office 365 group accounts as accounts associated with department-sponsored projects, groups or organizational functions. Current guidance directs users to the IT Help Desk when requesting one.
That gives three different concepts:
Personal mailbox — your institutional email account.
Email alias — another address associated with email delivery.
Group account — an organizational account created for a recognized project, department or function.
Using the correct terminology makes support requests much easier to route.
Mailing Lists Are Also Separate
Johns Hopkins additionally provides mailing-list services for the Hopkins community.
The current myJH support site directs users who need to create a mailing list to the applicable ServiceNow resource rather than treating it as an ordinary email alias.
A list distributes mail among subscribers.
A group account represents an organizational mailbox or function.
An alias provides another address for email routing.
Those are three genuinely different email-management tasks.
When myJH Works but Outlook Does Not
If you successfully authenticate into myJH but Outlook fails afterward, diagnose the later stage.
Useful questions include:
Can you find Outlook in the Messaging category or through search?
If not, this may be portal discovery or application-availability trouble.
Does Outlook launch but reject authentication?
That moves the issue toward credentials, MFA or Microsoft authentication.
Does Outlook open but your mailbox behaves incorrectly?
That is likely an email-service issue rather than a myJH navigation issue.
Are you only trying to change the visible email address?
The Email Alias application may be the relevant destination instead.
The phrase “myJH email isn’t working” can therefore describe several completely different failures.
Email and the MFA Transition
Hopkins authentication is also undergoing an important change.
Johns Hopkins IT announced in July 2026 that SMS and voice-call MFA methods will be disabled by Hopkins in mid-December 2026, ahead of Microsoft’s January 28, 2027 retirement of those methods. Users relying on them are being directed toward alternatives such as Microsoft Authenticator and passkeys.
Because Outlook and other Microsoft services can require enterprise authentication, an MFA problem can look like an email problem even though the mailbox itself is functioning normally.
Our myJH password and MFA guide owns that authentication topic.
A Better Mental Model for Johns Hopkins Email
The system becomes easier to understand when each component has one job:
JHED ID identifies the institutional user.
Authentication and MFA verify the user.
myJH helps the user discover and reach resources.
Microsoft Exchange provides the enterprise email service.
Outlook provides an email interface.
Email Alias manages applicable alternate addresses.
That model is far more useful than describing everything as “myJH mail.”