[Metrics Advisor] test failing in nightly runs

[v-jiaodi]

Metrics Advisor nightly test runs are failing with:

Error message:
body.metricAlertingConfigurations.anomalyDetectionConfigurationId cannot be null or undefined.

Stack trace:
Error: body.metricAlertingConfigurations.anomalyDetectionConfigurationId cannot be null or undefined.
at Serializer.serialize (D:\a_work\1\s\sdk\core\core-http\src\serializer.ts:131:13)
at serializeCompositeType (D:\a_work\1\s\sdk\core\core-http\src\serializer.ts:744:44)
at Serializer.serialize (D:\a_work\1\s\sdk\core\core-http\src\serializer.ts:176:19)
at serializeSequenceType (D:\a_work\1\s\sdk\core\core-http\src\serializer.ts:540:40)
at Serializer.serialize (D:\a_work\1\s\sdk\core\core-http\src\serializer.ts:158:19)
at serializeCompositeType (D:\a_work\1\s\sdk\core\core-http\src\serializer.ts:744:44)
at Serializer.serialize (D:\a_work\1\s\sdk\core\core-http\src\serializer.ts:176:19)
at getOperationArgumentValueFromParameterPath (D:\a_work\1\s\sdk\core\core-http\src\serviceClient.ts:914:18)
at getOperationArgumentValueFromParameter (D:\a_work\1\s\sdk\core\core-http\src\serviceClient.ts:866:10)
at serializeRequestBody (D:\a_work\1\s\sdk\core\core-http\src\serviceClient.ts:566:24)
at GeneratedClient.sendOperationRequest (D:\a_work\1\s\sdk\core\core-http\src\serviceClient.ts:509:7)
at GeneratedClient.createAnomalyAlertingConfiguration (D:\a_work\1\s\sdk\metricsadvisor\ai-metrics-advisor\src\generated\generatedClient.ts:148:4)
at MetricsAdvisorAdministrationClient.createAlertConfig (D:\a_work\1\s\sdk\metricsadvisor\ai-metrics-advisor\dist-esm\src\metricsAdvisorAdministrationClient.js:122:491)
at Context. (D:\a_work\1\s\sdk\metricsadvisor\ai-metrics-advisor\test\public\adminclient.spec.ts:282:39)
at callFn (D:\a_work\1\s\common\temp\node_modules.pnpm\mocha@7.2.0\node_modules\mocha\lib\runnable.js:374:21)
at Test.Runnable.run (D:\a_work\1\s\common\temp\node_modules.pnpm\mocha@7.2.0\node_modules\mocha\lib\runnable.js:361:7)
at Runner.runTest (D:\a_work\1\s\common\temp\node_modules.pnpm\mocha@7.2.0\node_modules\mocha\lib\runner.js:619:10)
at D:\a_work\1\s\common\temp\node_modules.pnpm\mocha@7.2.0\node_modules\mocha\lib\runner.js:745:12
at next (D:\a_work\1\s\common\temp\node_modules.pnpm\mocha@7.2.0\node_modules\mocha\lib\runner.js:536:14)
at D:\a_work\1\s\common\temp\node_modules.pnpm\mocha@7.2.0\node_modules\mocha\lib\runner.js:546:7
at next (D:\a_work\1\s\common\temp\node_modules.pnpm\mocha@7.2.0\node_modules\mocha\lib\runner.js:448:14)
at Immediate. (D:\a_work\1\s\common\temp\node_modules.pnpm\mocha@7.2.0\node_modules\mocha\lib\runner.js:514:5)
at processImmediate (internal/timers.js:461:21)

For more details check here:

• https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1030575&view=results

[KarishmaGhiya]

These issues are caused by service side permission issues. We were expecting a fix by the end of last week, but the tests are still failing. So will close all these issues and let only one of them be to track.