r/sysadmin • u/LookAtThatMonkey Technology Architect • 18h ago
Question Entra ID 404 on certain pages
Anyone else seeing this? I've been trying to get to the authentication methods > policies and the password reset pages, and I'm just getting 404 not found responses. Other parts of Entra are OK. The service health doesn't seem to report this as a detected issue? Our tenant is in the UK.
MgGraph is working fine.
1
u/bberg22 18h ago
I was getting similar on other Microsoft websites too like powershell gallery for example. few user reports of issues with Linkedin earlier this AM. US East coast. Cloudflare posted an outage as well, could be related? https://www.cloudflarestatus.com/incidents/dk2obcyw2aew
1
u/SpectreHaza 18h ago
Yep seeing it too. Both auth methods and password reset now you mention it
Have tried through azure blade with same issue (I just wanted to get to auth method policies)
1
u/iswearimnotanaibot 18h ago
Might be a cloudflare or isp issue. Was having the same thing switched to our backup isp and they are handling traffic without issue.
1
u/dontbethefatguy 16h ago
I’ve been getting this since yesterday. Started immediately after I tweaked some CA policies, so that was fun. Either that or I’ve managed to lock everyone out. My bad.
1
u/zAuspiciousApricot 16h ago
at least you didn’t change server registry settings for a voip issue like some poor soul did
1
u/Mehere_64 15h ago
I have noticed that Entra/Azure portal is slow to respond this morning. No 404 though for me.
1
u/mrussellblount 14h ago
i cant even access sign-in logs for tenants. all of them say no sign-ins found and ofc the status page for entra says all good.
1
1
1
u/zAuspiciousApricot 18h ago
AI will fix it
1
u/Pure-Tumbleweed1132 18h ago
i swear half the job now is just refreshing the service health page while it insists everything is fine
our tenant did this last month for conditional access, was down for like 4 hours and microsoft never acknowledged it. classic
1
1
u/Weekly-Offer-4172 18h ago
Service health is slow to light up for Entra, incidents regularly take an hour or more to get posted so no detected issue doesnt mean much yet. Try loading the same blades through the Azure portal instead of the Entra admin center, they are different front ends and one is often fine while the other 404s. A private window or a different admin account is worth a shot too, a stale token makes some blades 404 instead of erroring cleanly. If it is a backend thing in your region the auth methods and password reset policies can still be read and changed through the graph powershell module if it cant wait