Traffic Manager Profile API should support ETAGs to resolve update conflicts between different clients
We have automation that have different clients that modify the same ATM profiles so race conditions are possible when creating or updating resources.
It looks like ATM API does not support ETAGs to resolve such conflicts. We have to resort to using Azure blobs for resource locking which is very inconventient.
Please support ETAGs in ATM API