Home › Knowledgebase › KB-1662

Why am I seeing 'There was a problem signing you in' when launching my medical practice software?

Summary

This guide helps you troubleshoot and resolve: Why am I seeing 'There was a problem signing you in' when launching my medical practice software?. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? đź’» Open a Ticket

Common Causes

This article helps allied health clinic staff resolve the “There was a problem signing you in” error when launching cloud-based medical practice management software using Microsoft Entra ID (formerly Azure AD) single sign-on (SSO). In a clinic environment, this error often prevents receptionists and clinicians from accessing patient booking and billing systems, disrupting daily workflows. The issue typically stems from one of three areas: browser cache and cookies on the local workstation, network DNS or firewall restrictions at the clinic, or a misconfiguration in the cloud identity provider such as Entra Conditional Access or Application Proxy settings.

Quick Fix Steps

  1. Close all browser windows and restart the web browser.
  2. Clear the browser cache and cookies for the practice software website.
  3. Try launching the software using a different browser or an InPrivate/Incognito window.
  4. Confirm the workstation has an active internet connection by visiting a public website.
  5. If the error persists, proceed to the detailed troubleshooting steps below.

Detailed Instructions

1. Clear Browser Cache and Cookies

Stored session data or outdated cookies can interfere with Microsoft Entra ID authentication. Clearing these removes corrupted session tokens that may be causing the sign-in failure.

Microsoft Edge

  1. Open Microsoft Edge.
  2. Press Ctrl + Shift + Delete to open the “Clear browsing data” dialog.
  3. Select the time range All time.
  4. Tick Cookies and other site data and Cached images and files.
  5. Click Clear now.
  6. Restart Microsoft Edge and attempt to sign in again.

Google Chrome

  1. Open Google Chrome.
  2. Press Ctrl + Shift + Delete to open the “Clear browsing data” dialog.
  3. Select the time range All time.
  4. Tick Cookies and other site data and Cached images and files.
  5. Click Clear data.
  6. Restart Google Chrome and attempt to sign in again.

2. Test Network Connectivity and DNS

Clinic firewalls or DNS settings may block the authentication endpoints required by Microsoft Entra ID. Allied health clinics often have strict network segmentation between patient Wi-Fi and staff workstations.

  1. Open a new browser tab and navigate to a public website such as https://www.microsoft.com to confirm general internet access.
  2. Attempt to reach the practice software login page directly.
  3. If the page fails to load while other websites work, check that the clinic router or firewall is not blocking required Microsoft authentication domains.
  4. Restart the clinic router if local network issues are suspected.
  5. If possible, connect the workstation to a mobile hotspot and test the login. If sign-in succeeds on the hotspot, the clinic network is likely blocking authentication traffic.

3. Check Microsoft Entra ID Sign-In Logs

If local and network checks do not resolve the issue, the fault may be in the cloud tenant configuration. Reviewing sign-in logs helps determine whether the authentication request even reached Microsoft’s identity service.

  1. Sign in to the Microsoft Entra admin centre with administrator credentials.
  2. Navigate to Monitoring > Sign-in logs.
  3. Filter by the affected user’s email address and the approximate time of the failed sign-in attempt.
  4. Review the error code and failure reason. Common causes include Conditional Access policies blocking the device or location, multi-factor authentication requirements not being met, or Application Proxy connector issues.
  5. Note the error details for escalation to your IT provider.

Troubleshooting Scenarios

Mobile app vs browser launch

Some practice management vendors offer a dedicated mobile app for iOS or Android that uses a different authentication flow than the browser-based version. If the browser login fails but the mobile app works, the issue is likely isolated to the workstation browser or its cached credentials. If both fail, the issue is more likely related to the user account, Conditional Access policy, or network connectivity.

Shared workstation scenarios

Allied health clinics commonly use shared workstations at reception desks or in consulting rooms. Multiple users signing in and out of the same browser can leave behind conflicting session cookies and cached tokens. To resolve this:

Entra sign-in logs show no sign-in attempt recorded

If you check the Microsoft Entra ID sign-in logs and find no record of the failed attempt, the authentication request never reached Microsoft’s cloud service. This usually indicates:

Error persists after clearing cache

Sign-in works on mobile hotspot but not clinic Wi-Fi

Entra sign-in logs show a Conditional Access block

Multi-factor authentication (MFA) considerations

Many health sector organisations enforce MFA for access to practice management software containing patient health information. If the user’s MFA device (such as a mobile phone running the Microsoft Authenticator app) is unavailable, lost, or not registered, sign-in will fail even with a correct password. Confirm the user can complete their MFA challenge before escalating.

Escalation

If none of the above steps resolve the issue, gather the following information and Open a Ticket:

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

đź’» Open a Ticket