Can't delete bitlocker recovery keys from microsoft account

Question

Hi,

I have been using my microsoft account for several years to store my bitlocker keys everytime I encrypt my C: and D: drives.
As part of the process every time I do the new encryption I first go to my microsoft account and delete the old keys.

However, suddenly today, I was not able to delete them. When I click and check the checkbox that I already have a copy of the keys and
click continue the dialog just sits there with the waiting feedback loop and never comes back. I looked in the browser console, it seems that
I get a 403/forbidden response back.

I have tried different browsers, clearing cache, logging out and in even tried it from my mobile and I still have the same problem.

Any Ideas as to why this happens? I appreciate your thoughts.

Thank you.

EDIT: 17/Jul/2022 : As of today, the issue is fixed for me. I managed to delete the old keys. I also saved my current keys and deleted them again successfully and have no further problems with this. Thanks Microsoft.

Answer 1

Just contacted Microsoft Chat Support today. They told me they are still working on it. Jun 22nd.

Answer 2

Ok. So. I just got off of ANOTHER support call with Microsoft. FINALLY, all of my tickets are consolidated into one issue.
FINALLY, Engineering and Accounts are paying attention and Engineering has agreed to escalation and managing a joint project to fix this issue.
FINALLY, Microsoft has acknowledged this is GLOBAL.
It took so long because the escalation team finally took time to scour all cases and SURPRISE, they found a lot.
They asked me to pass along, there is no ETA when the issue will be fixed.
I was told there is a possibility they might try fixing my account and, once successful, they would roll the fix out globally.

They are humbled and quite apologetic for ignoring us for so long.

Answer 3

I know this is a year old thread but now, one year later, the same problem is happening again. Is there anyone else with the same problem?

Answer 4

Response to https://account.microsoft.com/devices/recoverykey/deleterecoverykey?keyId=1500B52BA59A441B!198366
Request method DELETE
Is {"statusCode":403,"message":""}

Perhaps Microsoft account is struggling with DDoS or other attacks?

Answer 5

For MS SWE: Full diags from the latest desktop Edge. "[REDACTED_STRING_N]" each represents the same string, "[REDACTED]" a unique string. Not redacting FVE ids as they are expired anyway.

### Backtrace ###  
DELETE https://account.microsoft.com/devices/recoverykey/deleterecoverykey?keyId=E8B2D54E79B180E6!3217&X-Requested-With=XMLHttpRequest 403 (Forbidden)  
send		@ jquery-1.11.1.min.js:4  
ajax		@ jquery-1.11.1.min.js:4  
m		@ bradbury?v=[REDACTED_STRING_1]:1  
makeRequest	@ bradbury?v=[REDACTED_STRING_1]:1  
delImpl		@ bradbury?v=[REDACTED_STRING_1]:1  
sendRequest	@ bradbury?v=[REDACTED_STRING_1]:1  
ajaxDelete	@ bradbury?v=[REDACTED_STRING_1]:1  
t.sendDeleteKeyCommand	@ get-recovery-key?v=[REDACTED_STRING_2]:1  
onclick		@ get-recovery-key?v=[REDACTED_STRING_2]:1  
dispatch	@ jquery-1.11.1.min.js:3  
r.handle	@ jquery-1.11.1.min.js:3  
  
### General ###  
Request URL: https://account.microsoft.com/devices/recoverykey/deleterecoverykey?keyId=E8B2D54E79B180E6!3217&X-Requested-With=XMLHttpRequest  
Request Method: DELETE  
Status Code: 403 Forbidden  
Remote Address: 23.205.201.81:443  
Referrer Policy: strict-origin-when-cross-origin  
  
### Request Headers ###  
Accept: text/plain, */*; q=0.01  
Accept-Encoding: gzip, deflate, br  
Accept-Language: en-US,en;q=0.9  
Connection: keep-alive  
Content-Length: 19  
Content-Type: application/x-www-form-urlencoded; charset=UTF-8  
Cookie: [REDACTED]  
Correlation-Context: v=1,ms.b.tel.market=en-US,ms.b.tel.scenario=ust.amc.devices.deleterecoverykey,ms.c.ust.scenarioStep=ClickedDeleteRecoveryKey  
DNT: 1  
Host: account.microsoft.com  
MS-CV: [REDACTED_STRING_3].3.36  
Origin: https://account.microsoft.com  
Referer: https://account.microsoft.com/devices/recoverykey?refd=onedrive.live.com  
sec-ch-ua: " Not;A Brand";v="99", "Microsoft Edge";v="103", "Chromium";v="103"  
sec-ch-ua-mobile: ?0  
sec-ch-ua-platform: "Windows"  
Sec-Fetch-Dest: empty  
Sec-Fetch-Mode: cors  
Sec-Fetch-Site: same-origin  
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.114 Safari/537.36 Edg/103.0.1264.49  
  
### Request Body ###  
undefined=undefined  
  
### Response Headers ###  
Cache-Control: no-cache, no-store  
Connection: keep-alive  
Content-Language: en-US  
Content-Length: 31  
Content-Type: application/json; charset=utf-8  
Date: Fri, 08 Jul 2022 21:43:25 GMT  
Expires: -1  
MS-CV: [REDACTED_STRING_3].3.36.11  
P3P: CAO DSP COR ADMa DEV CONo TELo CUR PSA PSD TAI IVDo OUR SAM BUS DEM NAV STA UNI COM INT PHY ONL FIN PRE PUR  
Pragma: no-cache  
Set-Cookie: market=US; domain=microsoft.com; path=/; secure; HttpOnly  
Set-Cookie: bm_sv=[REDACTED]~1; Domain=.microsoft.com; Path=/; Expires=Fri, 08 Jul 2022 22:05:38 GMT; Max-Age=1333; Secure  
Strict-Transport-Security: max-age=31536000  
X-Content-Type-Options: nosniff  
X-Frame-Options: SAMEORIGIN  
X-Served-By: [REDACTED]  
X-UA-Compatible: IE=Edge  
X-XSS-Protection: 1; mode=block  
  
### Response Body ###  
{"statusCode":403,"message":""}