Deyaaeldeen Almahallawi

> I feel like we should move the loggingPolicy into afterPhase: "Sign" to account for this. That makes sense to me! > I'm less sure about moving the default auth...

Couldn't get approval for this PR because the new UX is not confirmed whether it actually solves the problem and is a bit awkward.

/cc @witemple-msft @joheredi @KarishmaGhiya. I am digging deeper into this and will share my findings.

Quick update: The scopes for TA are: AzCloud: cognitiveservices.azure.com UsGov: cognitiveservices.azure.us China: cognitiveservices.azure.cn ~Germany: TBD but most likely cognitiveservices.azure.de~ deprecated I looked at using the authority host to infer the...

@schaabs confirmed that it is not likely but it is valid for the authority host to be in one cloud while the resource being authenticated into is in another.

.NET TA client library added an audience option to support other clouds in https://github.com/Azure/azure-sdk-for-net/pull/26583. I am planning on doing the same and will try to finish it in this milestone.

remoterendering failures are not related to this PR: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1773877&view=logs&j=b800360f-d572-5e16-3e20-e4f204d3fbd3&t=3b97752f-f53c-5e36-3379-45368efa0b3c

The problem with the linter packages is that they could have breaking changes between minor versions, which could be annoying to fix in automatic rush update --full PRs. Perhaps we...

@qiaozha yeah it is more of a collaboration effort between both team. autorest needs to specify the minimal requirements needed for complete code generation and the swagger team should work...

@leni-msft yes I am familiar with the extension and it does not specify all the information needed (e.g., when to stop polling in dataplane services LROs). @qiaozha we actually need...