This means RICOCHET could not verify your PC's security settings with Microsoft, so you are limited to a restricted matchmaking pool. It is not a ban. Jump to your situation below or work through the methods in order.
Failed Attestation Status means RICOCHET Anti-Cheat's Remote Attestation could not verify your PC's security state through Microsoft Azure Attestation (MAA), so Call of Duty places you in a restricted matchmaking pool (Warzone Battle Royale Casual, Black Ops 7 Nuketown 24/7). It is not a ban and nothing is wrong with your account. The fix is to bring your PC to a known-good, verifiable state: enable TPM 2.0 and Secure Boot in BIOS, make sure Windows boots in UEFI mode on a GPT disk (disable CSM), and on many AMD boards update the BIOS because older AMD fTPM firmware in the 3.x.0.x range fails the check. Run the official Call of Duty Secure Attestation Wizard first, it names exactly what is wrong, then re-enable any settings a BIOS flash reset. Note that Activision has acknowledged some cases are a backend attestation bug with no user-side fix, where the only option is to wait for a game or anti-cheat update.
RICOCHET uses Remote Attestation to confirm your TPM 2.0 and Secure Boot settings with Microsoft's servers rather than trusting your PC's local report. If that Microsoft Azure Attestation check cannot verify a trusted state, you fail attestation and are pushed into a separate, restricted matchmaking pool.
Bringing your PC to a verifiable state clears it: enable TPM 2.0 and Secure Boot, boot in UEFI on a GPT disk, and update the BIOS on AMD systems with old fTPM firmware. The Secure Attestation Wizard tells you the exact failing item. A minority of cases are a backend bug you can only wait out.
“Failed Attestation trips people up because it is not really about cheating, it is RICOCHET asking Microsoft to vouch for your PC's security. So I get the machine into a state Microsoft will vouch for: TPM 2.0 on, Secure Boot on, booting UEFI on a GPT disk. On AMD, if it still fails with everything enabled, it is almost always old fTPM firmware, so update the BIOS and re-enable fTPM afterwards. Run the Secure Attestation Wizard first, it points at the exact problem. And be honest with people: some of these are a backend bug Activision is still fixing, and no amount of BIOS tweaking will help until they patch it.”
tpm.msc msinfo32
mbr2gpt before disabling CSM.Failed Attestation Status means RICOCHET could not verify your PC via Microsoft Azure Attestation, restricting matchmaking. Enable TPM 2.0 and Secure Boot, boot UEFI on a GPT disk (disable CSM), and update the BIOS on AMD systems with old fTPM firmware. Run the Secure Attestation Wizard to see the exact fault. Some cases are a backend bug with no user fix.
If your TPM, Secure Boot, UEFI and BIOS are all correct and attestation still fails, you are likely in the known backend-bug bucket Activision is investigating; keep everything updated and wait for an anti-cheat update rather than reflashing repeatedly. You can also submit your error to us for a tailored fix.