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

Hi ChrisOezbek

One thing you can check yourself before the support case: the response has a model field that names the underlying model, separate from your deployment name. If you stored full responses, compare that field for calls before Oct 23 and after Oct 24. A difference is solid evidence to attach for support. I don't know whether it carries a build or version detail, so treat a match as inconclusive. If you only kept the scores, start logging that field with a UTC timestamp now.

Since one removed word moved a clear positive from 0.92 to 0.996, the question is leaning hard on its wording. If you haven't yet, add a criteria block with explicit true and false conditions to the noul question. Then rebuild the threshold from a labeled sample instead of the old calibration. The docs say to validate thresholds on labeled examples, and a middle band that goes to review instead of one hard cut-off would be my own suggestion for a gate like yours.