Yes, I am facing the same issue, but there is really nothing to do in that case.
The solution is to allow inline scripts and/or convert them to include the correct nonce I think.
At the moment the reports are collected apparently. I am seeing things like [1]. My guess is, that MS would like to enforce CSP. The only practical way is to do quite a bit of monitoring first...
[1]
csp-report: {,…}
blocked-uri: "inline"
disposition: "report"
document-uri: "<redacted>"
effective-directive: "script-src-elem"
line-number: 1
original-policy: "script-src 'strict-dynamic' 'self' 'nonce-5gt3vNyAiXk/dSs6Z4l3Gw==' 'report-sample'; report-uri /<redacted>cspreport?p=B2C_1_Auth"
referrer: "<redacted>
script-sample: "javascript:void(0);"
source-file: "<redacted>/B2C_1_Auth/api/CombinedSigninAndSignup/unified"
status-code: 0
violated-directive: "script-src-elem"