Identify the failure boundary
| What staff see | Possible fault domain | Safe next question |
|---|---|---|
| Microsoft 365 sign-in rejected | Microsoft Entra identity, MFA, device or Conditional Access policy | Which app, error code, time and correlation ID? |
| Windows workstation login rejected | Local account or on-premises domain, connectivity or cached credentials | Is this one workstation, one identity or multiple devices? |
| Clinical app login rejected while email works | Clinical-vendor account, role, licence, session limit or application availability | Does the vendor report an account lock or a service fault? |
| Remote connection fails but on-site login works | VPN, remote desktop gateway, certificate, connectivity or remote-access policy | At which approved connection step does it fail? |
These are possible causes, not a diagnosis. A generic “access denied” may be a permission issue rather than a lockout. A server outage may affect everyone without locking any account. Hybrid environments can connect identity systems, so the administrator should check synchronisation and dependencies rather than assume passwords are independent.
Collect evidence safely
Ask staff to stop repeated attempts and record the exact failure time/time zone, application name, device identifier, location (on-site or remote), displayed error code and whether others are affected. Capture a redacted screenshot only if it contains no patient records, password, MFA code or recovery secret.
Use an approved restricted support channel for staff account identifiers or logs. Never ask someone to disclose their password, approve an MFA request they did not initiate, or email patient data to prove that an application is failing. Verify support contacts through a known route, not a phone number in an unexpected message.
An authorised administrator can correlate the event with Microsoft Entra sign-in logs, including the failure reason, application, error code and correlation ID. Log availability and retention depend on configuration and licensing. Practice managers should request the conclusion and corrective action, not seek broad administrator access to investigate themselves.
Routine causes to investigate, not bypass
An old phone, mail client, mapped resource or scheduled process may still retry an outdated password after a change. In a hypothetical clinic, a returning locum can sign in on one approved device but an old session keeps failing elsewhere. The provider should correlate logs and identify the source before changing credentials again; this is not a documented client incident.
Other possibilities include an expired or disabled account, wrong username, incorrect keyboard layout, lost MFA device, incomplete enrolment, device-compliance failure or a policy denying the location. Local/domain failures may involve reaching the domain controller, while a clinical platform may have its own session or role controls. A network outage is not solved by changing a password.
Have the responsible administrator or clinical vendor apply the supported recovery process after verifying the user’s identity. Do not remove MFA, weaken lockout policies, enable unrestricted remote access or share a colleague’s account to get a consultation started. Use the practice’s authorised continuity procedure if patient care is disrupted.
Suspicious activity is a separate escalation
Password spraying means attempts against multiple accounts using a small set of common passwords; repeated failures alone do not prove spraying. Unfamiliar successful sign-ins, unexpected MFA requests, suspicious email rules or failures across many users warrant prompt security triage through the agreed incident contact.
Preserve timestamps and logs and follow the incident plan. Authorised responders decide proportionate containment, session revocation and recovery; a routine helpdesk unlock must not overwrite that assessment. Do not investigate by trying passwords across staff accounts or asking staff to approve prompts for a technician.
The practice retains responsibility for assessing any affected personal information with appropriate advice. Not every lockout or suspicious event is an eligible data breach. Use the RACGP/APP 11 incident responsibilities guidance to separate technical response from legal decisions.
Prevention and escalation checklist
- Maintain named accounts and an approved role register; align locum start/end dates across Microsoft, clinical and remote-access systems.
- Document supported password-change and MFA-device replacement processes, including an independently verified help contact.
- Ask the provider to remove obsolete credential sources safely, rather than repeatedly unlocking an account without a cause.
- Agree ownership across the IT provider, clinical vendor and phone/remote-access suppliers so faults do not circulate indefinitely.
- Review recurring patterns, device health and identity-policy changes after incidents. Record a cause, action, owner and verification result.
- Keep approved emergency-access and downtime procedures available when email or remote access is unavailable; do not turn emergency access into everyday shared credentials.
- Escalate urgently when multiple staff cannot work, safe care is affected, or compromise is suspected. Confirm actual support coverage and charges in the agreement.
Questions for your provider
Can you distinguish authentication failure from missing permissions and application outage? What evidence identifies the failing system? Who can recover the clinical account if you cannot? How will you verify the person requesting recovery without requesting secrets? How will you check the fault has stopped recurring while keeping MFA enabled?
Use the clinic Microsoft 365 permissions matrix for access planning and existing Microsoft 365, managed IT and cybersecurity pages to discuss scope. Official Microsoft guidance above, RACGP access guidance and OAIC breach guidance checked 26 October 2026.
Responsibilities and next steps
Use these steps with the practice’s authorised decision-maker and relevant vendors. They are evaluation advice, not confirmed Netluma IT inclusions, prices, testing schedules or response commitments. See healthcare IT support and the RACGP F8 and APP 11 responsibilities guide to agree owners, approvals and evidence.
Netluma IT does not certify compliance or confer accreditation. Buying IT support does not guarantee accreditation or legal compliance. Practice governance and legal duties are not transferred to the provider. This is general information, not legal advice or an exhaustive compliance checklist.
Need IT Built for Healthcare?
Discuss practical IT support for your clinic, including agreed access, backup, connectivity and vendor responsibilities. IT support does not guarantee legal compliance or accreditation; practice governance and legal duties remain with the practice.
Related Services
IT SupportManaged ITCybersecurityPriority-based remote responseLocal Gold Coast team



