Log the length, age, and reset access path figures for your forecast backup password before you encrypt anything, so a second person can open the file after a password change or a rep departure.
- Length: Record the character count you chose for the backup password, or your organization's enforced minimum if stricter.
- Age: Record the actual expiration day count for the owning account from your tenant's settings, confirmed with your IT administrator; tenants created before 2021 default to 90 days.
- Reset path: Record the account name, whether 2-Step Verification is on, where the backup codes are stored, and a second person who can reach them.
- Repository location: Record where the backup file is written, since knowledge of the password is required to access the repository.
- Test restore: Open the backup once with the logged password and confirm the forecast file reads correctly.
Why a forecast backup dies quietly
Your forecast file is only as safe as the password wrapped around it. If you lose that password, the file is sealed. A rep leaves, takes the only known password with them, and your recovery plan fails.
Password rules are not arbitrary. They live in policy. Microsoft Entra ID's own documentation says: "In Microsoft Entra ID, there's a password policy that defines settings like the password complexity, length, or age." Read that at Microsoft's self-service password reset policy page. Complexity, length, and age.
A forecast backup password touches three numbers: how long it must be, how long it lives, and how a person proves it is theirs when it changes. Log all three. Do it before the backup, not after an incident.
The three figures to log before the file
Here is the short list. Keep it next to the backup job description.
Figure one: minimum length. Microsoft documents that tenant passwords allow "A minimum of 8 characters and a maximum of 256 characters." That range comes from the same Microsoft Entra ID policy page. Choose where your password sits inside that range. Write the chosen length down.
Figure two: expiration age. Microsoft states that "If the tenant was created before 2021, it has a 90 day expiration value by default." That default sits on the same Microsoft Entra ID policy page. Check your tenant's age. If it predates 2021, your password ages out on that schedule unless someone changed it. Log the actual age setting for the account that owns the backup.
Figure three: reset access path. Someone must be able to recover the account when the password expires or the rep leaves. Google documents that "To use backup codes, make sure 2-Step Verification is on." That requirement is on Google's sign in with backup codes help page. Record which account holds 2-Step Verification and where its codes are stored.
Three numbers: length, age, reset path. Repository location and a test restore matter too.
What to write down and where
Log the length figure as a number with a unit, like the character count. Log the age figure with the exact day count from your tenant settings. Log the reset path as account name, recovery method, storage location of recovery material, and a second person who can reach it. Keep the log in a place a second person can reach without you.
Do not store the log inside the same encrypted container as the backup. A locked box cannot open itself. Put the log in your team's password manager, or in a sealed envelope with your operations lead. If a rep leaves and only they knew the container password, the log records the reset path and figures, but it does not contain the container password, so the password must be stored separately and reachable by a second person.
The table: compare the figures side by side
This table pulls only the figures the sources state. Use it as a quick check.
| Figure | Source statement | What you log |
|---|---|---|
| Password length | Minimum 8 characters, maximum 256 characters | Your chosen character count |
| Password age (older tenants) | 90 day default expiration for tenants created before 2021 | Your tenant's actual expiration day count |
| Backup code access | 2-Step Verification must be on | The account with 2-Step Verification and where codes live |
Now keep reading for what each figure means in practice.
Figure one: minimum length, logged as a real number
Length is the first figure. The Microsoft policy page gives the range: minimum 8, maximum 256. That range is the boundary for the Entra ID account password. Inside that range, you choose. Your log should record the number you chose, not the range.
Why the exact number matters: the log should record the character count as a plain number so a second person knows what to set. If the log says "at least 8" and your actual password used a longer rule, a colleague guessing at 8 will fail. Write the number.
If your organization enforces a minimum above the tenant floor, log that enforced minimum instead. Ask your IT administrator for any enforced value above that range, then log it. Check with your IT administrator for the enforced value, then log it.
Length is one of the three settings the Microsoft Entra ID policy names: complexity, length, age. This post's three figures are length, age, and reset access path, so complexity is not among them. Length is the easiest to record, so record it first.
Figure two: password age, logged with your tenant's real expiration
Age is the figure teams forget. A password has a life. When it expires, the old password stops working.
The Microsoft Entra ID policy page says tenants created before 2021 carry a 90-day default expiration. That is a default, not a universal rule. Newer tenants may differ. Your tenant may have been changed by an administrator. Log the actual expiration day count from your tenant's settings, not the default.
Ask your IT administrator for the current password expiration setting on the service account that runs your backup. Write the day count into the log. If the answer is that passwords never expire, write that too. The log should describe reality, not a guess.
Age also touches the backup schedule. Refresh the credential in the backup tool before the account password ages out. Align the two. A password that expires on a known day count tells you when to refresh the credential in the backup tool.
Log the age figure with a date: the last day the password was set. From that date plus the day count, anyone can compute the next expiration. That computation is plain arithmetic; no source needs to state it. The two inputs, set date and day count, come from your own settings.
Figure three: reset access path, logged so a second person can act
The third figure is not a number in the same sense. It is a path: how a person proves ownership when the password changes or the rep leaves. Log which recovery method is live and where its material sits.
Google's backup codes page states that 2-Step Verification must be on to use backup codes. If the owning account is a Google account, log whether it has 2-Step Verification enabled and where its codes are stored; if the owning account sits in your Microsoft Entra ID tenant, log that tenant's recovery method and where its recovery material sits. If codes are printed, log the drawer. If codes are in a password manager, log the vault name.
Google also explains that if codes are lost, run out, or suspected stolen, a new set can be created, and that creating new codes makes the old set inactive. Read that on the Google backup codes help page. Log the rule your team follows: who may generate a new set, and who is told when the old set dies.
This figure protects you when a rep leaves. The rep may hold the only session that knows the password. If the recovery path is logged and reachable, a remaining colleague can reset access without waiting on the departed person.
Log the reset path as: account name, recovery method, storage location of recovery material, and the name of a second person who can reach that material. Four fields. Keep them together.
Where the backup file actually lives matters too
A password protects a container. The restic documentation calls that container a repository: "The place where your backups will be saved is called a 'repository'." See restic's repository preparation page.
The same page states plainly: "Please note that knowledge of your password is required to access the repository." That single sentence is why your three logged figures matter. Without the password, the repository is a locked box.
Log the repository location alongside the three figures. A forecast backup that lives on a departed rep's laptop is not a backup. Write down the host, the path or bucket, and the account that can read it. Then write down the password figures that open it.
If you use restic, the repository location and the password are two separate things. Both belong in the log. The repository location tells a colleague where to look. The password figures tell them how to open it.
If your backup tool is something else, the same principle applies. Find the equivalent of the repository: the place the file is written. Log its location next to the password figures.
The worked scenario, in plain words
Picture a revenue operations team with a forecast file that lives in a shared drive. A rep owns the encryption password. The rep leaves on a Friday. On Monday, the team needs to rotate the password because policy requires it. The new operator opens the log and reads three things: the chosen character count, the expiration day count from the tenant's actual settings, and the recovery account with 2-Step Verification plus the location of its backup codes. The operator resets the owning account using the logged codes, sets a new password that meets the logged length, updates the expiration date in the log, and re-runs the backup against the repository path also written in the log. Resetting the owning account does not supply the repository password. The operator must still obtain that password from a separate, reachable store before the repository opens.
Without the log, that Monday looks different. The operator does not know the length rule, does not know when the old password expired, and does not know which account can reset access. Each unknown becomes a ticket, and each ticket waits on someone. The file stays sealed until all three answers arrive.
The scenario uses no invented figures. Length and age figures for the Entra ID account password come from the Microsoft range and tenant default statement. Reset access depends on the owning account's provider; the Google 2-Step Verification requirement is one documented example. Repository meaning and the password requirement come from restic. The human steps are ordinary operations work.
Checklist before you hit backup
Run this list once, before the first encrypted forecast backup of a period.
- Length logged. Record the character count your password uses, inside the documented minimum and maximum.
- Age logged. Record the actual expiration day count for the owning account, confirmed with your IT administrator.
- Reset path logged. Record the account, the 2-Step Verification status, and the storage location of backup codes.
- Repository logged. Record the location where the backup file is written.
- Second reader named. Record one colleague who can reach all of the above without you.
- Test restore. Open the backup once with the logged password and confirm the forecast file reads correctly.
The test restore, the repository logging, and the second-reader step are steps no source here mandates. It is plain prudence. A backup you have never opened is a guess. Open it once. If it fails, fix the log or the password before you rely on the file.
Keep the checklist short enough that a manager can complete it in one sitting. A long checklist gets skipped. Six lines get done.
What to do when a rep leaves
Leaving day is when your log earns its keep. Walk these steps with whoever takes over the account.
- Reset the owning account's password using the logged recovery path.
- Set a new password that matches the logged length rule.
- Update the expiration date and day count in the log.
- Regenerate backup codes if the departed rep may still hold them; the old set becomes inactive when a new set is created.
- Re-run one backup against the logged repository and confirm it writes.
- Open one restore and confirm the forecast file reads.
Step four deserves care. Google's guidance makes the trade-off clear: new codes deactivate the old set. That is the safe direction after a departure. Log the regeneration date so the next person knows the codes' vintage.
Do not skip step five. A password change that nobody tested can leave the backup tool pointing at a credential the repository no longer accepts. One successful run proves the credential reaches the file.
Related guides
Frequently asked questions
What if our tenant was created after 2021? The 90-day default applies to tenants created before 2021. A newer tenant may carry a different expiration. Ask your IT administrator for the actual setting, then log that day count instead of assuming the default.
Can we just store the password in the same file as the backup? No. The restic documentation states that knowledge of the password is required to access the repository. If the password sits inside the repository, you cannot read it to open the repository. Keep the log outside the container.
What if we do not use Google for the owning account? The reset-path figure still applies. Log whichever recovery method your provider supports, plus where the recovery material is stored. The Google 2-Step Verification rule is one documented path; your provider's equivalent belongs in the same log slot.
How often should we re-check the log? Re-check when any of the three figures changes: a password rotation, a tenant policy change, or a staff departure. Also re-check before any planned restore drill. A log older than the last change is stale.
Who should hold the second copy of the log? Name one colleague who is not the account owner. Their job is to reach the repository and open it if the owner is unavailable. If you cannot name that person, you do not yet have a backup plan.
Closing note
Three figures. Length, age, reset path. Log them before the first encrypted forecast backup. Add the repository location and a named second reader. Test one restore. Then the file stays open to your team, even after a password change or a departure.