By looking at the screenshot you have provided, the error message appears to be related to a recent policy change updated by the
Microsoft. It also seems like a widely spread issue, affecting Windows Server instances regardless of their location or hosting platform. I have a seen a
discussion thread in the Microsoft community where root cause analysis and workaround for this issue have been provided.