Microsoft-Decision-1 scores changed on the same deployment / version 1 – anyone else?

The reversals across your 10,000 stored requests deserve investigation separately from the smaller variation between repeated calls. A fixed threshold that worked before should not be assumed valid for the changed score distribution.

Microsoft's launch announcement discusses future rebasing, but it does not confirm that your deployment changed behind version 1 on October 23–24. I cannot establish that cause from the public information. Azure's activity log records resource-management operations, so an unchanged log does not by itself explain inference behavior.

Preserve representative before-and-after examples with byte-identical state, instructions and criteria, the API version, returned model name, UTC timestamps and request identifiers. Submit those through Azure Support with the Sweden Central deployment details. Keep the unchanged examples distinct from tests where you removed a qualifying word. Microsoft's Decision-1 guidance recommends explicit true/false criteria and validating thresholds against labeled workload examples; it does not establish that NoAutoUpgrade restores your previous calibration.