Skip to main content

Why MeetGeek Couldn’t Connect to Your Microsoft Account

If you're having trouble signing into MeetGeek via Microsoft, this guide will help you understand why it's happening and how to resolve it.

Carolline Miranda avatar
Written by Carolline Miranda
Updated over 2 weeks ago

MeetGeek tried to sign you in with Microsoft but was blocked by your company’s security settings.

For IT admins: Microsoft labels this behind‑the‑scenes as error 53003.

What’s Happening?

  • Geo‑blocking rule – Your organization’s Microsoft tenant only allows sign‑ins from certain countries or networks.

  • This issue isn't related to MeetGeek – The block is triggered by your company’s default security policy, not because MeetGeek is unsafe. All of our controls and certifications are documented in the MeetGeek Security Center.

What You Can Do:

  1. Share this page with your IT team

  2. Ask them to review the conditional‑access or location rules in Azure AD that may be stopping third‑party apps.

  3. What IT should check

    • Location‑based or “named location” rules

    • Trusted IP lists

    • Any policy that restricts cloud apps by geography

  4. Try again

  5. Once those settings are updated, sign in to MeetGeek one more time—the block should disappear.

Need More Help?

  • Quickest option: Open the in‑app chat in MeetGeek and send us a message.

  • Still blocked after IT changes? Let us know in chat, and our team will investigate with you.

  • For subscription questions, you can also request a call with our Customer Success team directly through the chat.

Additional Information: Microsoft Documentation on Conditional Access Policies https://learn.microsoft.com/en-us/entra/identity/conditional-access/overview

We’re here to make sure you get back to your meetings—smoothly and securely!

Did this answer your question?