
Account Security
Part of Small business IT continuity
Keeping emergency access to critical business accounts
Identify critical accounts, arrange secure provider-supported recovery and control how emergency access is used and checked.
Emergency access lets an authorised person regain a critical business account when the usual administrator, device or sign-in method is unavailable. Identify accounts that control essential work. Establish each provider's supported recovery route while access still works, and check that the route survives the failure it is meant to cover. Protect emergency credentials and record their use.
Identify the accounts and dependencies
Start with business email, identity administration, domain registration, backup administration and applications holding essential work. For each, record the business owner, current administrators, sign-in methods, recovery contacts, supplier procedure, support contact and the date the route was last tested. Ask what would happen if the usual administrator's phone and laptop were both unavailable.
For a .au domain, record the registrar of record. Every .au domain name licence has one, even if you registered through a reseller, and auDA's WHOIS tool shows its name and contact details. A transfer to another registrar needs the transfer authorisation code (EPP authInfo), which differs from the username and password for your provider account.
Keep this register separate from passwords, recovery codes and security keys. The register should tell authorised staff where to find the procedure and who holds protected material without exposing the material itself.
Critical accounts and dependencies to record
- Business email
- Identity administration
- Domain registration
- Backup administration
- Applications holding essential work
- Business owner for each account
- Current administrators
- Sign-in methods and recovery contacts
- Supplier procedure and support contact
- Date the recovery route was last tested
Prepare the supported route
A lost authentication device, an absent administrator and a provider outage can require different responses. Add an approved second sign-in or recovery method where the service permits it. Check whether a recovery email or phone will remain available if the primary account is locked.
Where a service offers one-time backup codes, store them as credentials and follow that service's rules for use and replacement. Do not assume the same option exists in a business tenant or another service.
For administrator access, follow the provider's specific design. Microsoft Entra ID guidance is to create two or more emergency access accounts in your organisation. These accounts carry the Global Administrator role and are for emergency or "break glass" scenarios when normal administrative accounts can't be used.
Microsoft says their credentials should be known only to individuals authorised to use them, for example FIDO2 security keys kept in secure, fireproof safes in separate locations. Change the safe combinations regularly and after anyone with access leaves.
Do not disable multi-factor authentication for everyday users to simplify recovery. Keep emergency access limited to authorised people and visibly exceptional.
Prepare the supported recovery route
- Add an approved second sign-in or recovery method where the service permits it.
- Check that a recovery email or phone remains available if the primary account is locked.
- Store one-time backup codes as credentials and follow the service's rules for use and replacement.
- In Microsoft Entra ID, create two or more emergency access accounts.
- Assign the Global Administrator role for emergency or break-glass scenarios.
- Keep credentials known only to authorised individuals, for example FIDO2 security keys in secure, fireproof safes in separate locations.
- Change safe combinations regularly and after anyone with access leaves.
- Do not disable multi-factor authentication for everyday users to simplify recovery.
Control use and return
State who may authorise emergency access, how that person's identity is checked, who retrieves the credential or device and what they may do. Include a reachable supplier support route if the organisation cannot recover access itself. Record the reason, time, person, account and changes made.
After use, review the activity, replace any exposed secret under the provider's procedure, return protected material and confirm that normal named access works. Microsoft recommends validation drills at least every 90 days, covering the authorised-user list, sign-in and administrative tasks.
An authorised person can confirm access to the instructions and perform a permitted sign-in or supplier-supported check without making unnecessary live security changes. Record what was checked and what still depends on provider support. Review the route when an administrator leaves, an authentication device changes or a supplier changes its recovery process.
Control use and return of emergency access
- State who may authorise emergency access
- Define how the authoriser's identity is checked
- Nominate who retrieves the credential or device
- Set out what the authorised person may do
- Include a reachable supplier support route
- Record the reason, time, person, account and changes made
- After use, review the activity
- Replace any exposed secret under the provider's procedure
- Return protected material
- Confirm normal named access works
- Run validation drills at least every 90 days
- Review the route when an administrator leaves, an authentication device changes or a supplier changes its recovery process



