MeetGeek tried to sign you in with Microsoft but was blocked by your company's security settings. This is a configuration issue on your organization's side, not a problem with MeetGeek — here's what's happening and how to fix it.
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 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
Share this page with your IT team and ask them to review the conditional-access or location rules in Azure AD that may be blocking third-party apps.
Have IT check the following:
Location-based or "named location" rules
Trusted IP lists
Any policy that restricts cloud apps by geography
Try again. Once those settings are updated, sign in to MeetGeek one more time — the block should disappear.
Reference: Microsoft's documentation on Conditional Access policies.
Need Help?
The quickest way to reach us is the chat messenger in the MeetGeek app, or email [email protected]. If you're still blocked after IT makes these changes, let us know and our team will investigate with you. For subscription questions, you can also request a call with our Customer Success team through the chat.
Related Articles