Microsoft Learn help and reporting
Training/documentation feedback is separate from a customer's Azure runtime problem.
Live Domain Check
Run a live reachability check for learn.microsoft.com. Compare the regional responses with the problem you see in Microsoft Learn.
Find Microsoft Learn help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Microsoft Learn documentation, training progress and lab environments have different support needs.
The checker above requests learn.microsoft.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Microsoft Learn action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Training/documentation feedback is separate from a customer's Azure runtime problem.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
No separate incident dashboard is linked here. Use the official product help and any current announcements it links to; this does not mean that no outage is possible.
Training/documentation feedback is separate from a customer's Azure runtime problem.
Open Microsoft Learn help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Learn URL, module/unit, language, signed-in state and sandbox/error details.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Microsoft Learn.
These are troubleshooting comparisons, not claims that Microsoft Learn is currently experiencing a particular incident.
Compare the article/module URL with its parent section and note whether reading, sign-in or a learning sandbox fails.
For a documentation problem use the page's feedback path; for an Azure runtime failure investigate the actual subscription/resource.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Microsoft Learn seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open learn.microsoft.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Microsoft Learn issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft Learn support.
Run the learn.microsoft.com check and compare its original timestamps and responses with your actual error. Microsoft Learn documentation, training progress and lab environments have different support needs.
Use the official help/reporting resource linked above. Training/documentation feedback is separate from a customer's Azure runtime problem.
Compare the article/module URL with its parent section and note whether reading, sign-in or a learning sandbox fails. For a documentation problem use the page's feedback path; for an Azure runtime failure investigate the actual subscription/resource.
Learn URL, module/unit, language, signed-in state and sandbox/error details.