Unable to Connect to Lab Environment – “Please wait while connecting” stuck during Microsoft Applied Skills Assessment

Phyo Thiri Aung 5 Reputation points
2026-03-25T07:23:51.1566667+00:00

I am currently taking the Microsoft Applied Skills assessment for Power Automate on Microsoft Learn. During the lab session, the environment fails to load and remains stuck on the message “Please wait while connecting…”. A popup appears with a “Retry Connection” option, but retrying does not resolve the issue.

The issue persists even after waiting for several minutes. I am unable to access the lab environment, which is preventing me from continuing or completing the assessment.

Details:

  • Assessment Name: Microsoft Applied Skills – Create and manage automated processes by using Power Automate
  • Issue: Lab environment not loading / connection failure
  • Error Message: “Please wait while connecting…” + “Retry Connection”
  • Impact: Unable to proceed with assessment just 3 times

Requesting assistance to resolve the lab connection issue or reset the assessment session.

Microsoft Edge | Browser crashes or stops working | Windows 11
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-03-25T07:24:10.96+00:00

    The behavior described matches a lab connectivity problem rather than an issue with the assessment itself.

    Use the following steps to troubleshoot and, if needed, escalate:

    1. Verify basic connectivity and latency
      • Run the Lab Orientation & Connectivity Check to confirm the machine can connect and function within the lab environment: Lab Orientation & Connectivity Check.
      • Check the latency indicator in the lab interface:
        • 100–250 ms = Good
        • 250–500 ms = OK
        • 500 ms or higher = Poor
      • If latency is high or the lab feels sluggish/blank/black, it is likely a connectivity issue.
    2. Rule out local network and device issues
      • Avoid VPN or proxy while using the lab; VPNs are not recommended and can block or degrade remote sessions.
      • Use a wired connection instead of Wi‑Fi/hotspot/cellular/satellite, which often have higher latency and packet loss.
      • Ensure port 443 is open for inbound and outbound traffic on the local network and firewall.
      • Temporarily disable third‑party antivirus, pop‑up blockers, and ad blockers that might interfere with the remote session.
      • Power‑cycle modem and router to reset the local network.
      • Confirm bandwidth: at least 200 kbps up/down consistent / 1 Mbps burst per user.
      • Try a different browser (for example, if using Edge, test with another supported browser) and, if possible, a different computer (especially a non–work‑issued device, since corporate policies can block remote sessions).
    3. Run a deep connection assessment
      • Use the connection assessment speed test to measure throughput, capacity, and packet quality: speed test.
      • If the test shows significant data loss, high latency, or other quality issues, work with the local IT/network provider to improve the connection before reattempting the lab.
    4. Check for signs of lab host or path issues
      • Even if the in‑lab latency indicator shows good or excellent, there can still be routing or firewall issues on intermediate “hops” between the device and the lab host.
      • If repeated attempts from a clean network and different browser/device still hang on “Please wait while connecting…”, the problem may be beyond the local environment.
    5. If the issue persists across attempts
      • Capture details: time of occurrence, browser used, whether other sites/services work normally, and any screenshots of the stuck “Please wait while connecting…” and “Retry Connection” dialog.
      • Use Microsoft Learn/Certification support channels (for Applied Skills and labs) to request assistance. Provide the assessment name, description of the connectivity troubleshooting already performed, and ask for the lab session to be reset or for alternative arrangements.

    These steps address the common causes of lab sessions failing to connect (latency, blocked ports, VPN/proxy, device/network restrictions). If the environment still does not load after these checks, support intervention is required to review lab host status and reset the session.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.