https://portal.atp.azure.com/ can't be reached

%3CLINGO-SUB%20id%3D%22lingo-sub-3053357%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Fportal.atp.azure.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.atp.azure.com%2F%3C%2FA%3E%20can't%20be%20reached%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3053357%22%20slang%3D%22en-US%22%3E%3CP%3EFrom%20The%20Netherlands%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Super_Jay_0-1641469783252.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F337727iB777F41FD2B24C5D%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Super_Jay_0-1641469783252.png%22%20alt%3D%22Super_Jay_0-1641469783252.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

From The Netherlands:

Super_Jay_0-1641469783252.png

Anybody else got this experience?

3 Replies
This is a known issue with some specific accounts.
We have a fix on the way but it will take a few days to roll out.
I suggest to open a support case.
A possible workaround might be to use a different set of credentials to connect for onboarding until fixed.
Different set of credentials (fellow worker) same response, page can't be reached.
We are now 4 days further in time, any more info on the estimated time of the fix?
Fellow worker might have a similar issue.
I suggest to open a support case to get more details.