In version 3.1.15 CAE Enablement is default - this is a breaking change!

Describe the bug

We upgraded from a version 2.x to version 3.2.1 and in version 3.1.15 you have enabled CAE by default.
This has caused an outage for two of our customers when we upgraded to 3.2.1 (from 2.0.15) becasue we are getting a 401 CAE challenge due to what we see as a breaking chnage in 3.1.15

Please can you provide instructions how we would disable the default enablement of CAE ?

Expected behavior

If its not a breaking chnage then upgradeing from version 2.x to a version 3.1.15 or higher should continue to work as before this is 100% not the case!

How to reproduce

Upgrade from a version prior to 3.1.15 to version 3.1.15 or greater and CAE is enabled tenants will return a 401 challenge...
How can we disable this default enablement

SDK Version

3.2.1

Latest version known to work for scenario above?

2.0.15

Known Workarounds

rolling back to previous version

Debug output

</details>


### Configuration

_No response_

### Other information

_No response_

Start by reproducing the upgrade from SDK 2.0.15 to 3.2.1, focusing on the CAE behavior introduced in version 3.1.15 and the resulting 401 challenge. Identify how CAE is enabled and whether the SDK exposes a way to disable it by default. Done means the upgrade path is documented or the breaking behavior is corrected, with the reported scenario verified.