BitLocker is the disk encryption built into Windows, and for a small business it is one of the cheapest ways to make a lost or stolen laptop a hardware problem instead of a data breach. Turning it on is the easy part. What protects you is where the recovery keys live, who can read them, and whether you can prove every machine is encrypted. That is a management job, and it is the part most small offices skip.
This guide covers what BitLocker does, how it differs from Windows device encryption, how to manage keys, and how to roll it out without locking your staff out of their own computers. It is written for owners and office managers at Wisconsin manufacturers, law offices, dental practices and financial firms, not for IT specialists.
TL;DR
- BitLocker encrypts the whole drive, so a lost or stolen laptop or an offline disk shows only unreadable data without the key.
- Device encryption is the simplified version that switches on automatically. Full BitLocker adds policy control, removable-drive protection and key management for a business.
- The recovery key is the real risk. Store it centrally in your Microsoft 365 or Active Directory directory before you encrypt, and limit who can read it.
- Roll out in stages: audit devices, escrow keys, test a recovery, then enforce. Report on status before you block anyone.
- Regulated firms (health, finance, legal) should document the encryption decision, because auditors ask for evidence, not intentions.
Table of Contents
- What BitLocker does for a small business
- Device encryption vs full BitLocker
- Is BitLocker already on?
- BitLocker key management: the part that decides whether it works
- How to roll out BitLocker without locking people out
- A policy checklist for regulated small businesses
- Where small businesses go wrong
- Our perspective
- How Collett Systems fits in
- FAQ
- Sources
What BitLocker does for a small business
BitLocker encrypts a drive so that anyone reading it offline needs the decryption key. Without it, the data looks like gibberish, and Microsoft calls it particularly valuable when a device is lost or stolen.
Think about what leaves your building every week: a project manager's laptop in a truck, a lawyer's laptop in a court bag, a dental office PC that gets replaced and discarded. Encryption means the person who finds or buys that device cannot pull client files, CAD drawings or patient records off the disk by plugging it into another machine.
Technically, Microsoft documents that BitLocker uses AES in XTS or CBC mode with 128-bit or 256-bit keys. It covers the operating system drive, fixed data drives and, through BitLocker To Go, USB flash drives, SD cards and external hard drives. You do not need to understand the math. You need to know that it is a recognized, standard cipher and that the weak points are the keys and the settings around it.
One limit is worth knowing: encryption protects data at rest. It does not stop a phishing email from handing your password to an attacker while the laptop is unlocked. That is why encryption works best next to multifactor authentication for Microsoft 365 and identity controls, not instead of them.
Device encryption vs full BitLocker
This is the question behind most searches, and the answer is about control. Microsoft describes Device Encryption as a simplified form of BitLocker that turns on automatically after Windows setup. It encrypts the operating system drive and fixed drives, but not external USB drives. Organizations can disable it in favor of full BitLocker for more granular policy control.
| Device encryption | Full BitLocker | |
|---|---|---|
| How it starts | Automatically after setup | Configured by policy or an administrator |
| Drives covered | OS and fixed drives | OS, fixed and removable drives (BitLocker To Go) |
| Who sets the rules | Largely the device defaults | Your administrator, through Group Policy or Microsoft Intune |
| Startup protection | TPM-only by default | Can add a startup PIN or USB key |
| Cipher choice | Defaults | AES-128 or AES-256, XTS or CBC |
| Fits a business that... | Has a handful of PCs and no policy needs | Needs to prove and enforce encryption |
Two details matter for a small business. First, Windows Home gets the simplified device encryption, while full BitLocker functionality needs Pro, Enterprise or Education. If your office still runs Home licenses on business PCs, that is a licensing and management gap worth closing. Second, a recovery key saved automatically to someone's personal Microsoft account is a key your company does not control. If that employee leaves, so does your access to the key.
The practical rule: automatic device encryption is a good safety net, and full BitLocker managed centrally is the business standard.
Is BitLocker already on?
On many modern PCs, yes. Windows Latest reports that BitLocker is enabled by default on modern PCs, particularly after Windows 11 24H2, and that a clean Windows 11 install turns it on automatically. That sounds like good news, and it is, until you ask where the keys went.
For automatically enabled device encryption, Windows saves the recovery key to the Microsoft or work or school account before protection is activated. For a business-owned PC, you want that to be your company's Microsoft Entra ID (the directory behind Microsoft 365), not a staff member's personal account. If you have never checked, you probably have a mix: some keys in company accounts, some in personal ones, and some old machines with no stored key at all.
Also note that BitLocker integrates with Microsoft Entra ID and Active Directory for centralized key management, but recovery information is not backed up there by default. Backup is something a policy has to be set to do.
BitLocker key management: the part that decides whether it works
A BitLocker recovery key is a 48-digit number. It is what unlocks a drive when Windows cannot confirm the machine is in a trusted state. If you lose it, the encrypted data is gone, and the same strength that keeps thieves out keeps you out.
What gets stored
When the backup policy is configured, the saved information can include the 48-digit recovery password and a key package used to recover data from a damaged disk. Store these in your directory, tied to the device record, so a help desk can look up the right key in seconds.
Who can read the keys
Keys should be readable by administrators and not by every user. The CIS Microsoft 365 Foundations benchmark includes a control titled "Ensure users are restricted from recovering BitLocker keys", which points to limiting key retrieval to authorized administrators. A key that any employee can self-serve is a key an attacker with a stolen password can self-serve too. This ties directly to identity-first security: the account that can read a recovery key is as sensitive as the data it unlocks.
What triggers a recovery prompt
Staff will meet the blue recovery screen at some point. Microsoft lists common triggers including too many wrong PIN entries, changes to boot order on devices with TPM 1.2, docking or undocking, TPM changes or self-test failure, motherboard replacement, firmware upgrades, and moving a protected drive to a new computer.
In plain terms, Windows asks for the key when something changed that it cannot tell apart from an attack. Planned hardware or firmware work is the usual cause. For those, Microsoft's guidance is that temporarily suspending BitLocker keeps the drive fully encrypted and reseals the key without needing the recovery password. Microsoft also recommends finding the root cause after any recovery event, rather than just typing the key and moving on.
Some prompts come from settings. On Surface devices, recovery after a firmware update can happen when BitLocker uses non-default PCR values, for example with Secure Boot off. The lesson applies broadly: custom boot-integrity settings should be chosen on purpose and tested, not inherited.
Keep a break-glass procedure
Write down, in one page, who can retrieve a key, how they verify the caller is really the employee (a phone call from an unknown voice is a classic social engineering route), and where the retrieval is logged. Verification matters because recovery is a high-value request.
How to roll out BitLocker without locking people out
Microsoft's own planning guide starts with an informal audit of current policies, procedures, hardware and any existing disk-encryption software. That audit is the first step for any size of company. The sequence below follows that guidance and Microsoft's Zero Trust recommendations for BitLocker in Intune.
- Inventory every device. List each PC, its Windows edition, whether it has a TPM (the security chip that holds the key), and whether it is already encrypted. Include the old workstation in the shop-floor office and the spare laptop in the closet. On devices without a TPM, BitLocker can still encrypt the OS drive but without pre-startup system integrity checks, so note which machines fall into that group.
- Pick your standard. Decide the cipher and startup protection. Microsoft recommends XTS-AES for all drives, with 256-bit keys for faster hardware and 128-bit for slower devices, and the default is XTS-AES 128-bit. Some regulators or contracts require a specific key size, so check yours first. For laptops that travel, consider a startup PIN. BitLocker can require a PIN or USB startup key as multifactor authentication.
- Escrow keys before you encrypt. Microsoft advises requiring recovery-key escrow to Microsoft Entra ID before broad rollout. Set the policy so a drive does not finish encrypting until its key is safely stored.
- Pilot on a few machines and test recovery. Microsoft recommends testing recovery from both the administrator's and the end user's side. Time how long it takes to find a key and walk a user through it.
- Report first, enforce second. Use a compliance policy to check encryption status, but do not block access until reporting confirms deployment is healthy. Otherwise one misconfigured group puts a whole department in the recovery screen.
- Document exceptions. Some equipment cannot run encryption, such as legacy machines tied to a CNC controller. Record each exception, why it exists and what compensates for it. Our note on digital signage security and organization-wide encryption standards shows the same principle for special-purpose devices that sit outside the normal fleet.
- Handle removable media. Encrypt USB drives that must leave the building and restrict the rest. See USB device control for how to block or manage USB storage.
Plan for time as well. A 500 GB SSD typically takes 30 to 60 minutes for the first encryption, and new installs default to Used Space Only encryption. Staff can keep working during that period, but schedule the pilot off-peak.
A policy checklist for regulated small businesses
Many Wisconsin firms in this audience answer to someone: a patient-privacy rule, a lender, a customer's security questionnaire or a defense supplier's contract. Encryption is rarely the whole requirement, but it appears in nearly all of them.
- Dental and medical offices. HIPAA treats encryption of electronic protected health information as an addressable safeguard. Addressable does not mean optional: you assess it, implement it or document an equivalent alternative and why.
- Financial firms. The FTC's Safeguards Rule calls for encrypting customer information on your system and in transit, or using alternative controls approved by the Qualified Individual who supervises the security program.
- Law offices. Client files on laptops and phones are the exposure. Encryption plus controlled key access gives you a clear answer when a client's general counsel asks how you protect their documents.
- Manufacturers. Customer drawings, bills of materials and quality records live on engineering laptops and shared drives. Contracts often flow security requirements down to suppliers.
For a detailed technical baseline, the CIS Intune benchmark for Windows 11 lists OS-drive settings such as requiring a 48-digit recovery password, storing recovery information in AD DS and blocking enablement until it is stored. It also lists requiring a TPM startup PIN and denying write access to removable drives not protected by BitLocker. You do not have to adopt every line, but each one you skip should be a decision you can explain.
For contractors aligned to NIST SP 800-171, one compliance firm's guidance for small organizations pairs BitLocker with TPM, recovery-key escrow and restricted removable storage, with logs retained for the contractually required period. The point across all of these is evidence: a screenshot of a compliance report showing every device encrypted is worth more than a policy that says every device should be.
Where small businesses go wrong
- Keys in personal accounts. The automatic save described above can leave recovery keys with an individual, not the company.
- Encrypting first, escrowing later. A drive encrypted before its key is stored is a drive one failure away from loss.
- No tested recovery. The first time you try to retrieve a key should not be when the owner is locked out on a Monday morning.
- Forgetting firmware updates. Planned BIOS or TPM updates are a classic recovery trigger. Suspend protection first where the update guidance calls for it.
- Ignoring everything else on the device. Encryption does nothing for an unpatched remote access service. Our guide to remote desktop security covers one of the most common ransomware entry points, and conditional access policies can require a compliant, encrypted device before a user reaches company data.
Our perspective
We treat encryption as infrastructure, not a checkbox. A laptop with BitLocker on and keys nobody can find is no safer than one with BitLocker off, because the first time something changes on that machine, you are locked out of your own data.
That is why we run managed IT as one standardized, fully loaded stack at a fixed cost per user. Security management, 24/7 monitoring, proactive support and compliance documentation are part of the service, not add-ons you negotiate for after an incident. Encryption status, key custody and exceptions belong in that same documented picture of your environment.
Small manufacturers, law offices, dental practices and financial firms do not need more tools. They need someone who owns the outcome, shows up when something breaks and can hand an auditor a clean record. Over 150 local organizations trust us with that job.
Dustin Collett
How Collett Systems fits in
If you would rather not run encryption, key escrow and compliance evidence on top of your day job, our Managed IT Services cover full infrastructure management, security management, 24/7 monitoring, backup and disaster recovery, compliance documentation and an unlimited help desk, at a fixed cost per user. Teams that already have an in-house person can look at Co-Managed IT Services.
Not sure where your devices stand today? Start with our IT & Security Assessment, which gives you a documented view of your environment, or take the Free IT Risk Score first. If your team is a solo operator or a very small group, Total Secure is our managed security option.
FAQ
Is BitLocker enabled by default?
Often, yes. On many modern PCs, and on clean Windows 11 installs, encryption turns on automatically as device encryption. The catch is where the recovery key was saved, so confirm that it sits in your company directory and not a personal account.
Do I need Windows Pro for BitLocker?
Full BitLocker management requires Windows Pro, Enterprise or Education. Windows Home receives the simplified device encryption, which has no administrator policy control. Business PCs are better placed on Pro or higher so they can be managed centrally.
What happens if I lose the recovery key?
You lose access to the encrypted drive, and in practice the data on it. That is why keys should be stored in Microsoft Entra ID or Active Directory before encryption completes, with access limited to administrators and a documented retrieval process.
Can I turn BitLocker off?
An administrator can turn it off or suspend it. Suspending is the right move for planned firmware or hardware changes because the drive stays encrypted and the key reseals afterward. Turning it off entirely decrypts the drive and removes theft protection, so do it only for a documented reason.
Does BitLocker satisfy HIPAA or the FTC Safeguards Rule?
It is a widely used control for the encryption requirement in both, but neither rule is met by one setting. Each expects a risk assessment, documented decisions and evidence. Your compliance documentation should show which devices are encrypted and how keys are controlled.
Sources
- BitLocker overview, Microsoft Support
- Windows 11 security book: Encryption and data protection, Microsoft Learn
- BitLocker recovery overview, Microsoft Learn
- Surface BitLocker recovery troubleshooting, Microsoft Learn
- BitLocker planning guide, Microsoft Learn
- Configure BitLocker, Microsoft Learn
- MDM based policies for BitLocker, Microsoft Zero Trust
- Windows Latest on BitLocker defaults and recovery, May 2026
- Full disk encryption comparison, May 2026
- CIS Microsoft 365 Foundations v6.0.1 audit
- CIS Microsoft Intune for Windows 11 v4.0.0 audit
- Removable media policy for NIST SP 800-171, March 2026
- FTC Safeguards Rule: What Your Business Needs to Know
- Does the HIPAA Security Rule require encryption?
- Digital signage security guide
