Outlook Admin Consent for Organizations

Some Microsoft organizations restrict which apps employees can connect to. If your team members see a "Need admin approval" message when trying to connect Outlook to meetergo, an IT administrator needs to grant consent first.

When is this needed?

This is required when your Microsoft Entra ID (Azure AD) tenant has "User consent to applications" set to "Do not allow user consent". In this case, only administrators can approve third-party apps like meetergo.

You'll know this is the issue if users see one of these:

A "Need admin approval" page from Microsoft during the connection flow
An "Admin approval required" error in meetergo after attempting to connect

Signing up before IT has approved meetergo

When Microsoft refuses a sign-up because of the calendar permissions, meetergo offers Continue with Microsoft without calendar access. You sign in with the same Microsoft account, asking only for the basic sign-in permissions (openid, profile, email, offline_access, User.Read). Once your IT admin has granted consent, connect your calendar in meetergo.

If your organization does not let users approve any app at all, ask IT for consent first, or sign up with email.

Open the following link as a Microsoft admin (Global Administrator or Application Administrator):

https://login.microsoftonline.com/common/adminconsent?client_id=ca903c3f-d495-4e82-9296-78fa315043b0&redirect_uri=https://my.meetergo.com/admin-consent-success

Sign in with your admin account
Review the permissions and click "Accept"
You'll be redirected to a confirmation page

After this, all users in your organization can connect their Outlook calendars to meetergo without further approval.

Option 2: Via Azure Portal

Go to Microsoft Entra ID (Azure AD) → Enterprise Applications
Search for meetergo
Go to Permissions
Click "Grant admin consent for [Your Organization]"
Review and accept the permissions

Required permissions

Every Outlook connection asks for four permissions. Everything else is only asked for when a user switches on the feature that needs it, and each user grants it for their own account.

Always requested

Permission	What meetergo does with it
`Calendars.ReadWrite`	Reads free and busy times and adds, changes or removes the events of meetergo bookings
`OnlineMeetings.ReadWrite`	Creates Microsoft Teams links for bookings (work or school accounts only)
`User.Read`	Reads the user's name and email address
`offline_access`	Keeps the connection working without signing in again

Only for the feature that needs it

Permission	Requested when	What meetergo does with it
`Mail.Read`	A user turns on CRM Email Sync or connects the mailbox to the email inbox	Reads the mailbox. Email Sync keeps only emails with the user's CRM contacts. Read only
`Mail.Send`	A user lets meetergo send replies and follow-ups from their mailbox	Sends emails the user sends in meetergo, and follow-ups they approve or let Mira send automatically. They appear in their Sent folder
`Mail.ReadWrite`	A user sends a large attachment from meetergo (needs both permissions above)	Uploads the attachment to a draft before it is sent
`Mail.Read.Shared`, `Mail.Send.Shared`	A user connects a shared mailbox they already have access to, for example `info@`	The same as above, for that shared mailbox
`Calendars.Read.Shared`	A user adds a meeting room	Reads the room's free and busy times. The room is booked by inviting it to the meeting

Separate connection: sending booking emails

Microsoft 365 email delivery is its own connection. It asks for SMTP.Send (plus openid, email and offline_access) so meetergo can send booking confirmations and reminders from your own address. It cannot read mail. It needs SMTP AUTH enabled for the mailbox.

Exchange on-premises

Exchange servers in your own data center connect through Exchange Web Services (EWS), not through Microsoft Graph, so no consent in Entra ID is involved. They work for the calendar and for CRM Email Sync. See Connecting Microsoft Exchange for the requirements.

meetergo does not access files, OneDrive, Teams chats or other Microsoft data.

Privacy: who can read emails

Only the user's own mailbox. Each user connects their own account. meetergo reads no other mailbox, except a shared mailbox the user connects and already has access to.
Email Sync stores no message body. It stores subject, sender, recipients, time and a short preview of emails to and from the user's contacts. The message body and attachments are not stored.
Visible to colleagues who can see the contact. Email history is scoped to your company. Colleagues who can open a contact see that contact's emails.
Processed in Germany. meetergo runs on servers of Hetzner Online GmbH in Germany. See the list of subprocessors.
No staff access in normal operation. Access by meetergo staff is limited and logged. We do not access customer data except for a support request or a legal requirement.
Revocable at any time. A user can turn Email Sync off or disconnect the account. An admin can remove the consent in Entra ID.

Troubleshooting

Make sure you granted consent as a Global Administrator or Application Administrator. Other admin roles may not have permission to grant tenant-wide consent.

The meetergo app registration may need to be updated. Please contact meetergo support and we'll resolve this quickly.

Yes. Go to Entra ID → Enterprise Applications → meetergo → Permissions and remove the granted permissions. Note that this will disconnect all existing Outlook connections for users in your organization.

Does this affect personal Microsoft accounts?

No. Admin consent only applies to organizational (work/school) accounts managed through Microsoft Entra ID. Personal Microsoft accounts (outlook.com, hotmail.com) handle consent individually.

Related articles