The email app may not be the account provider
Outlook can display a Microsoft, Google, Telstra or another provider’s mailbox; changing the app does not recover the underlying account. Use this guide only for your own account or one you are authorised to manage. A work or school mailbox needs its responsible administrator and incident process promptly.
Step 1 of 9
In this guide
Verify the alert and contact the right owner
Verify the alert and contact the right owner
Open the provider’s genuine app, a previously verified bookmark or its known address independently. Do not use a link, QR code or phone number in the alert. Look for the event in the real account’s security information. A new device, travel, VPN or approximate location can explain an unfamiliar-looking event, but do not dismiss activity you cannot account for.
Microsoft explains its unusual sign-in process; other providers use their own controls. Follow the genuine account’s event response. Approve only activity you actually recognise; do not approve a new multi-factor authentication (MFA) prompt simply to stop it appearing.
For business/school email, notify the responsible team through an established channel. Do not change tenant-wide access, delete logs or use a personal recovery process for a managed account. If the alert is not genuine and you did not interact with it, use the appropriate reporting process and stop. If there is unexplained account activity, lost access or information already shared, continue with the real event rather than assume the message’s appearance proves a takeover.
Keep the genuine provider’s event and your own recognised activity separate. An unverified alert or approximate location alone is not proof of an account takeover.
Record the scope and protect urgent exposures
Record the scope and protect urgent exposures
Keep a short private record of times, unexpected changes, affected accounts and actions already taken. Use the provider’s security activity and mail records where safely available. Messages in Sent that you did not write, changed recovery details or unexpected forwarding are useful observations. A recipient seeing your display name does not alone establish that your account sent the message; do not accuse someone or dismiss a report solely from that clue.
If bank/card details, payment changes or identity records may be exposed, contact the affected bank/service through an established route immediately. Tell a workplace team about business mail or customer information. Do not send money to a claimed safe account, pay for guaranteed recovery or wait for every technical check before protecting urgent access. Scamwatch’s response guidance covers immediate protection and follow-up recovery scams.
Preserve useful messages and event details through the responsible team’s private process. Do not forward live attachments widely, publish full headers/tokens or delete Sent, Trash or logs to tidy up. If the usual device may have malicious software or unauthorised remote access, stop sensitive activity there and use a trusted alternative for recovery. Keep device and account response as separate tasks.
Preserve the scope and take urgent protection first. A record, scam report or lack of suspicious Sent items does not establish that no information was accessed.
Regain access through the genuine provider
Regain access through the genuine provider
If you can still sign in, use the genuine provider’s security/recovery guidance to secure the affected account. Where its password was exposed, use a strong unique replacement and protect any other account that reused it. If locked out, follow its official recovery flow using your legitimate recovery methods and accurate information; avoid repeated guessed answers or links from an unsolicited helper.
Start with Microsoft personal-account recovery, Google account recovery/security guidance or Telstra’s compromised-email guidance as appropriate. Microsoft365 work/school ownership and recovery goes through its administrator. The mailbox address and responsible provider matter more than the app used to read it.
Use a trusted device if the original may be unsafe. Provider pages discuss device security too, but do not delay urgent bank/account contact on a trusted alternative while a suspect machine scans. If legitimate recovery methods are unavailable or changed, stop and use the provider’s supported escalation. IT support cannot promise to bypass ownership checks or recover every account. Preserve any remaining legitimate session and records until the provider or responsible team has a safe plan; do not sign out your only working access by guesswork.
Restored sign-in or a new password is not the whole recovery. Preserve legitimate access and continue with recovery methods, active access and mail changes.
More checks6 detailed checks
Review recovery methods and authentication
Review recovery methods and authentication
In the genuine account’s security settings, review recovery email addresses, phone numbers, authentication methods and security notifications. Check what belongs to you and what has changed. Record suspicious settings privately where appropriate before correcting them; a managed account needs its administrator’s process.
Remove unauthorised recovery/authentication access through the provider’s supported controls, while ensuring your own valid method works. Do not remove your last usable method, switch off MFA to make setup easier or publish backup codes. Follow any provider waiting period or ownership check rather than treating it as an error to bypass.
Use supported MFA or a passkey where available, with secure private recovery arrangements. The official account-compromise guidance explains why recovery and authentication methods matter as well as the password. If a method cannot be identified, a change was not yours or valid recovery cannot be retained, stop and get provider/administrator help before removing access indiscriminately.

Keep working recovery and authentication private. Enabling MFA does not by itself remove an attacker’s existing sessions, app access or mail rules.
Review sessions, devices and connected-app access
Review sessions, devices and connected-app access
Use the provider’s security information to review signed-in devices, recent events and connected apps or delegated access. Identify entries with help from the provider/administrator when names, locations or times are unclear. Keep a private record of suspicious access rather than assume every unfamiliar device label is an attacker.
Follow the provider’s supported sign-out/revocation process for unauthorised sessions and app permissions, with your legitimate recovery/access confirmed first. On a managed account, the responsible team may need to revoke access and investigate service logs. Do not rely on uninstalling Outlook or removing one phone from a list to invalidate every token or permission.
Effects and timing differ. Microsoft’s personal-account sign-out-everywhere guidance currently allows up to 24 hours and names an Xbox-console exception; do not assume an immediate universal sign-out or apply that timing to other providers. If unauthorised activity continues or revocation cannot be confirmed, get provider/incident help promptly rather than wait through repeated password changes.
Keep timing, scope and remaining access clear. A sign-out request is not proof every token, app permission or service has already lost access.
Review mail rules, forwarding and delegation
Review mail rules, forwarding and delegation
Through genuine webmail/account settings, check forwarding addresses, inbox filters/rules, delegated mailbox access, automatic replies, signatures and outgoing identity settings where the service supports them. Check for changes that hide, redirect or impersonate mail. Some legitimate apps or work processes also use these features, so identify the setting before removing it.
Keep a private record for the provider or incident team, then correct confirmed unauthorised settings through the supported process. Google’s compromised-account guidance includes Gmail filters, forwarding and delegation. Other services expose different controls. Do not delete all rules, all messages or local archives as a blanket fix, or disable a required business workflow without its responsible team.
Look for missing or unexpected mail in the relevant folders without clearing evidence. Tell the provider promptly if messages appear deleted or redirected; recovery options and retention can be limited. A corrected rule stops that configured behaviour going forward but does not recall information already copied, read or forwarded.
Preserve legitimate mail and useful evidence. Corrected settings do not prove that previously exposed messages or identity information have been recovered or contained.
Protect connected accounts and inform affected people
Protect connected accounts and inform affected people
With the provider or responsible team, identify important accounts that use this email for password resets, sign-in or recovery. Prioritise financial, work, government and other sensitive access relevant to you. Review affected security/activity through those services’ genuine routes, including any single-sign-on relationships. Do not share passwords with a helper or assume changing the mailbox password also changes every linked service.
Tell the responsible organisation about exposed business/customer records. If someone has impersonated you or sent harmful requests, warn affected contacts through a known safe channel, explaining what to ignore without circulating the live attachment or private evidence. Check changed payment instructions independently with the relevant parties. A warning does not replace the bank’s or provider’s action.
Keep suspected device exposure separate. Use the malware-response checks and trusted support when a file, extension or remote-control tool may be involved; do not assume a clean scan reverses stolen credentials or information. Keep follow-up identity, payment and incident references private and monitor as the responsible services recommend.
Keep connected-account, device, identity and payment response scope separate. Regaining email access does not itself secure every linked service or undo disclosure.
Verify restored use and monitor for returning changes
Verify restored use and monitor for returning changes
Through the genuine provider, confirm your own sign-in and recovery methods, reviewed active access and intended mail settings. When appropriate, test ordinary sending and receipt with a trusted contact using harmless content. Check that mail is not unexpectedly redirected and that essential legitimate apps still work.
Reconnect authorised mail apps only through their supported sign-in. A Telstra/BigPond password change can require an existing mail app to authenticate again; do not weaken account security, enable legacy access or delete its only local mail store to fix a prompt. Keep records/archives intact and use provider/app guidance if the supported connection fails.
If legitimate use and the required response actions are verified, stop repeated setting changes and continue the agreed monitoring/follow-up. Unexpected rules, sign-ins or messages returning need provider/incident escalation. No short quiet period, working inbox or scan can certify that information was never accessed. Keep remaining financial, identity and workplace actions open until their responsible parties resolve them.
Stop repetitive changes once intended access and mail use are verified, while keeping required monitoring and unresolved incident actions open. A working mailbox is not a guarantee of complete recovery.
Back to the symptom checkerWhen should you get account-recovery help?
When should you get account-recovery help?
Contact the genuine provider if recovery access is unavailable, settings cannot be secured, messages are missing or unauthorised activity returns. A work/school account needs its administrator and incident process. Keep the account identity, dates, observations and actions available privately; do not provide passwords or codes to an unsolicited caller or public help post.
Bank/card and identity exposure need their relevant services promptly, even if email recovery is incomplete. Preserve device evidence and legitimate access while a supported plan is agreed. Be cautious of paid recovery guarantees or someone asking to install remote software before explaining who they are and what access is needed.
Our remote IT support can help assess the mail/device problem and coordinate appropriate next steps when access is authorised. It does not bypass provider ownership checks, guarantee recovery or certify that no information was taken.
Keep genuine provider contact, private evidence and remaining response actions clear. Escalation or a recovery request is not a completed restoration.
Book IT support



