If your organization enforces restrictions on third-party app permissions, MeetGeek sign-in can fail until an admin approves access. This guide explains how MeetGeek authenticates with Microsoft, which permissions it requests, and how your IT admin can resolve the most common consent and Conditional Access errors in the Azure portal.
In this guide:
How MeetGeek authenticates (OAuth 2.0)
MeetGeek uses OAuth 2.0 to delegate authentication to Microsoft. For how Microsoft implements it, see the Microsoft OAuth 2.0 documentation, or the diagram below.
The OAuth 2.0 flow may look like SSO to users, but Single Sign-On (SSO) is not supported out of the box at this time.
Requested permissions
Signing in to MeetGeek with Azure requires permission to access basic user profile information.
Connecting your calendar requests one additional permission, which lets MeetGeek scan calendar meetings automatically and request to join as a participant.
Note: Connecting the calendar is optional, but it makes automating the join process easier.
Admin permissions troubleshooting
If you or your colleagues hit a login error like the one below, have your IT admin review the following settings in the Azure portal.
User consent permissions
Make sure your Azure settings let users request consent for new applications, subject to IT admin approval. See the Microsoft guide on configuring user consent and review your options as shown below.
When a user requests a delegated permission, your IT admin receives a request in the Azure portal. Approve it under Identity > Applications > Enterprise Applications > Admin consent requests. See the Microsoft guide on reviewing admin consent requests.
Admin consent flow permissions
If users can't request consent, your IT admin can also check the admin consent workflow under Identity > Applications > Enterprise applications > Consent and permissions > Admin consent settings. See the Microsoft guide on the admin consent workflow.
Grant MeetGeek tenant-wide admin consent
To grant tenant-wide admin consent to MeetGeek, ask your IT admin to:
Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
Browse to Identity > Applications > Enterprise applications > All applications.
Search for and select MeetGeek.
Important: For MeetGeek to appear in the application list, at least one user in your organization must have previously requested admin consent. See User consent permissions and Admin consent flow permissions above.
Select Permissions under Security.
Review the permissions the application requires. If you agree with them, select Grant admin consent.
Azure AD error 53003
Microsoft error code 53003 means "Access Denied" caused by Conditional Access policies — not ordinary app-permission issues. It surfaces during Azure Active Directory (Azure AD) authentication and is usually organization-wide, enforcing geo-location, MFA, or other risk policies.
To find the Conditional Access policies:
Go to the Microsoft Entra ID page.
In the left panel, open Protection > Conditional Access.
Go to the Policies page.
For more detail, see Why MeetGeek Couldn't Connect to Your Microsoft Account.
Need Help?
If you have any questions or need assistance, reach out at [email protected] or use the chat messenger in the MeetGeek app.
Related Articles