Hi,
There has been another topic on that subject (Read here) It appears that the issue was coming from few geographical regions on Azure, we were not able to reproduce it on our side, and it seems to be mitigated at the moment.
Please let us know with more details if you still encounter the issue.
Thank you.
Mickaël