By Caroline West, university IT service-desk lead with 10 years of experience supporting identity, email, and campus application access
Last reviewed: July 27, 2026
My JH Edu is a search phrase commonly used for myJH, the Johns Hopkins gateway to institutional applications and community information. The correct starting point is the Johns Hopkins myJH landing page, which describes itself as an access point to hundreds of Hopkins web applications.
This is an independent guide and is not affiliated with Johns Hopkins University or Johns Hopkins Medicine. Use Johns Hopkins-controlled support channels for account activation, password recovery, MFA changes, and application permissions.
What is My JH Edu?
The service is formally branded as myJH. It provides a central route to Johns Hopkins resources such as email, password-management tools, the enterprise directory, and applications used by students, faculty, staff, clinicians, and other authorized affiliates.
The login identity is called a JHED Login ID. JHED stands for Johns Hopkins Enterprise Directory, and Hopkins documentation may also refer to the username as a JHED ID or JHED LID.
These terms describe separate pieces of the experience:
| Term | What it does |
|---|---|
| myJH | Provides a gateway to Johns Hopkins applications |
| JHED Login ID | Identifies the user during institutional sign-in |
| JH Enterprise Directory | Stores searchable people and organizational information |
| Connected application | Applies its own role and access requirements |
This separation explains why a person may successfully enter myJH but remain unable to open one particular application. The central identity works, while the downstream service is still checking a separate permission or institutional record.
Start at the main myJH page
Open the main Johns Hopkins myJH landing page and use the sign-in control shown there. The public page currently identifies myJH as the access point to hundreds of Johns Hopkins web applications and key information about the Hopkins community.
Welch Medical Library’s login instructions describe the normal path as opening the myJH homepage, selecting Login, and entering the JHED Login ID and password on the Enterprise Authentication screen.
Use the main page first. Skip an old authentication bookmark.
A long address copied after single sign-on may contain a temporary request from an earlier session. When that request expires, the page can fail even though the JHED account remains valid.
The username format also deserves attention. Johns Hopkins’ myProfile instructions say the Enterprise Authentication screen asks users to enter the JHED ID followed by @jh.edu, then continue to the password step.
A public-facing Hopkins email address may use a different form. Follow the example displayed by the active authentication screen rather than assuming every Johns Hopkins email alias functions as the sign-in identity.
Who receives a JHED account?
MyJH is not an unrestricted public account service. Johns Hopkins must first create or assign an identity through an eligible student, employment, faculty, clinical, or affiliate relationship.
Incoming students without a previous Johns Hopkins affiliation generally receive a system-generated message containing their JHED ID before matriculation. MyJH Support directs students who never received that communication to Student Enrollment and Account Management rather than telling them to create an unrelated account.
New faculty and staff may receive their identity through a manager, supervisor, departmental human-resources representative, or another onboarding contact. The sequence can vary by school, division, hospital, appointment, and program.
New students in Johns Hopkins Advanced Academic Programs receive another concrete timeline: the program says the JHED ID is emailed 48 to 72 hours after the decision letter. That timing applies to that program and should not be treated as a university-wide promise.
Check the instructions for your exact affiliation. Skip a setup page intended for another Hopkins population when it conflicts with the onboarding message sent directly to you.
First-time JHED activation
The first login process is different from an ordinary return visit. MyJH Support describes first-time login as unique and routes new users to its account-creation instructions.
A typical first-time path includes:
- Confirm that Johns Hopkins assigned a JHED Login ID.
- Open the first-time-user route from myJH.
- Enter the assigned identity.
- Complete the current account-establishment screens.
- Create a password under the policy shown by Johns Hopkins.
Activation configures an identity that already exists. It does not establish admission, employment, or eligibility for every connected application.
Processing can continue after the first password is created. The Johns Hopkins registrar notes that the JHED directory synchronization process for incoming transfer students takes at least one hour before later account steps are completed.
That timing is specific. Another school, employee group, or application may use a different process.
Do not repeat first-time activation because one application is missing. Determine whether the JHED identity itself fails or whether only the downstream service is unavailable.
Finding the right application after login
The updated myJH portal includes a single search bar, the ability to switch among search types, favorites for commonly used applications, and profile features such as preferred names and pronouns.
The search type matters.
Use the application or resources search when looking for email, registration, payroll, VPN, or another service. Use the enterprise-directory search when looking for a person, department, or directory listing.
Wrong mode. No result.
Before reporting a missing application, enter its complete name and verify that the search is set to tools or resources. Review the full result list rather than only the first visible suggestions.
Once the application is found, save it as a favorite when that control is available. This creates a dependable route through myJH and avoids bookmarking an authentication address that may later expire.
Why the portal opens but an app does not
MyJH authentication and application authorization are different checks.
A connected service may require:
- Current enrollment
- Active employment or appointment status
- Membership in a school or department
- An assigned application role
- Completed onboarding
- A campus or profile setting
- Time for account synchronization
Use the scope of the failure to choose the next step.
When myJH and several unrelated tools work, investigate the one missing application. When myJH, email, and several services all reject the account, investigate the central identity, password, browser session, or MFA method.
Do not reset a working password first. A password change cannot add a missing departmental role.
Some services also require specific navigation after the portal login. Johns Hopkins graduate-registration instructions, for example, direct students to enter SIS with their JHED ID and password, open Registration, and choose Search for Classes/Registration.
That work is completed inside SIS, not on the general myJH homepage.
Browser loops and expired requests
An expired authentication request may produce repeated redirects, return the user to the same login page, or fail after opening an old bookmark.
Close every window in the affected browser. Reopen it and begin from the main myJH landing page.
Do not restore the failed tabs.
A private browsing window can help distinguish an account problem from stored cookies or extensions. If the portal works privately, the JHED identity may be fine and the regular browser profile may contain the stale session.
Check the device date and time as well. Institutional authentication requests are time-sensitive, and a substantially incorrect system clock can interrupt the process.
Change one thing at a time. Simultaneously resetting the password, switching browsers, altering MFA methods, and clearing all settings makes the original cause difficult to isolate.
What Action Required means
MyJH Support documents an account state called Action Required and describes it as a locked-down myJH state. Its page directs users who need assistance to the IT Help Desk.
Follow the instructions shown on the screen. If no available action restores normal access, record the exact wording and contact institutional support.
Do not keep opening new sign-in windows. Repeated authentication attempts may return to the same restricted state because the condition belongs to the account or required profile action rather than the current browser tab.
MFA and blocked sign-ins
Johns Hopkins lists Azure multifactor authentication among its institutional account and authentication services.
When the password is accepted but the second step fails, use another authentication method already registered to the account, if the screen offers one. A phone replacement, changed number, or inaccessible authenticator is an MFA-recovery problem rather than proof that the password is wrong.
No backup method available? Contact Johns Hopkins IT.
Reject an MFA prompt you did not initiate. The official IT Help Desk warns that no Johns Hopkins representative will call or email asking for a password or MFA code; such a request is a scam.
Protect the account first. Skip anyone asking you to read back a verification code.
Password changes and myProfile
Users who can sign in may change a known password from myJH. Johns Hopkins instructs users to open the portal, select the photo icon near the upper-right corner, and choose Change Password.
Use that route for a planned password change. It is not the correct fix for a missing application role, inaccessible MFA device, or restricted account state.
MyProfile is reached from the user avatar after authentication. Johns Hopkins’ instructions place that control near the upper-right corner of myJH.
Review profile and recovery information while access works. An outdated phone number or personal email becomes more difficult to correct after every authentication route has failed.
Remote access and VPN
MyJH can also be used to locate Johns Hopkins remote-access resources. Current IT guidance says the VPN resource is available through the portal under the Technology category and requires Azure MFA and the listed VPN client.
That does not mean every myJH application requires VPN.
Check the instructions for the particular application. Skip VPN troubleshooting when the service is intended to work through a normal web connection.
A portal that opens remotely can still lead to an application with additional network, device, or role requirements.
Frequently asked questions
Is My JH Edu the portal’s real name?
The portal is called myJH.
What username does myJH use?
Use the JHED Login ID assigned by Johns Hopkins.
Should I add @jh.edu?
The myProfile authentication instructions say to enter the JHED ID followed by @jh.edu. Follow the format displayed on the current sign-in screen.
Can anyone create a myJH account?
No public registration route is described. Johns Hopkins must first assign an eligible JHED identity.
Why can I sign in but not see an application?
The wrong search type may be active, or the application may require separate enrollment, employment, departmental, or role-based authorization.
How long does new access take?
It varies by population and service. One registrar workflow says JHED synchronization takes at least one hour, while AAP says its new students receive a JHED ID 48 to 72 hours after the decision letter. Neither timeframe should be generalized to every Hopkins account.
What does Action Required mean?
It is a documented restricted myJH state. Follow the screen instructions or contact the IT Help Desk.
Will Johns Hopkins support ask for my MFA code?
No. Johns Hopkins states that its representatives will not request a password or MFA code by phone or email.
Start from the current myJH landing page, confirm the JHED identity format requested by the screen, and determine whether the problem affects the central account or only one connected application.