A solution was found for us through MS ticket 2405200030001117 (May 2024)
Product team confirmed this was a BUG for SIP device. ETA for fix: 28th June 2024
We confirmed the broken accounts remain broken, but SIP handset forwarding was the cause, and it no longer breaks accounts when used.
Details: When user had a SIP device handset, and used the MS short-dial code to set their forwarding, it broke the call answering rules in Teams phone system. eg: on a Polycom VVX410 SIP device the user dialled: * 33 * <cellphone number> and heard two rings before the call hung up automatically.
This caused the issue. Confirmed in Teams Admin Center > user's account > Voice settings > "We can't load the call answering rules" popup warning appears.
Accounts that have experienced this issue ARE NOT FIXED by Microsoft's fix.
We opened new tickets to rectify accounts, but ultimately the accounts had to be recreated.
If your environment has no SIP devices (only Teams native handsets) this might not have been your issue.
https://learn.microsoft.com/en-us/answers/questions/921865/not-possible-to-change-call-answering-rules