Google Meet add in for Microsoft Outlook: links inside the invite

The setup is common enough to be unremarkable. The company runs on Microsoft 365, so invitations go out of Outlook. Video calls happen on Google Meet, because that is where the customers and the partners already are. Every meeting therefore involves creating an Outlook event, opening Meet in a browser, generating a link, and pasting it into the invitation before sending.

The add in removes that middle step. It is published by Google on the Microsoft Marketplace, it is free to install, and it inserts the joining details into the Outlook item directly. What it does not do is reconcile the two calendars, which is the part worth understanding before deciding whether it solves the actual problem.

What the add in inserts, and what it leaves alone

The publisher's description of the function is narrow and accurate. The add in creates a new Meet video conference in Outlook, and adds the meeting access information to an appointment or an email. The listing puts it plainly: it inserts joining information for a Meet video meeting into the Outlook event or email.

That is the whole of it. The event remains an Outlook event, stored in the Microsoft mailbox, sent through Exchange, and tracked by Outlook's own responses. The Meet conference is a separate object on the Google side that the link points to. The two are connected by nothing except that string of text in the body of the invitation.

Several consequences follow from that, and all of them are the source of a common complaint.

Changing the time of the Outlook event does not change anything about the Meet conference, because there is nothing time bound on the Meet side to change. This is usually harmless. A Meet link created for a meeting works when the meeting happens, whenever that turns out to be.

Deleting the Outlook event does not clean up anything on the Google side either. Again, mostly harmless, but it means the link keeps working, which is a consideration for a series that has been cancelled.

Attendance data lives in two places. Outlook records who accepted the invitation. Meet records who joined the call. Nothing joins those two lists together, so for a meeting where turnout matters, the attendance question has to be answered from the Meet side.

The add in is a link generator, not a bridge between two calendars. Every expectation that survives that sentence is reasonable, and every expectation that does not will be disappointed.

What has to be true before it will install

The requirements published on the listing are short and every one of them blocks installation when unmet.

A Google account is needed, which is obvious. Less obvious is the second condition: Meet has to be turned on for the whole organization, and the listing directs anyone in doubt to ask an administrator. In a company that runs Microsoft 365 as its primary platform, a Google Workspace tenant may exist for a subset of people, or not at all, and that decision is not usually visible to the person trying to schedule a call.

The third requirement is the one that dates the listing. It names a desktop computer with Outlook 2013 or 2016 for Windows, or 2016 for Mac, or Outlook online. The version numbers predate the current releases by some distance. Treat them as a floor rather than a ceiling, and treat Outlook on the web as the route most likely to behave, since web add ins run in a browser either way.

The fourth is a hard limit rather than a version note. The listing states that mobile devices do not support the Meet add in for Outlook. Anyone whose actual working pattern is to schedule from a phone between meetings needs to know this before installing. For comparison, the Zoom add in on the same marketplace lists support for Outlook on Windows, Mac, web and mobile, with mobile requiring administrator deployment, so the absence on the Meet side is a specific choice rather than a platform limitation.

There is a fifth condition that is not written down anywhere on the listing. In many organizations, installing add ins from the store is disabled, and add ins arrive only when an administrator deploys them. When the option to add an app is missing from the ribbon entirely, that is the reason, and no amount of retrying will change it.

Installing it and finding it afterwards

Microsoft's own instructions split by version, and the wording of the menu differs enough to waste ten minutes.

In the new Outlook, the route is the ribbon or the navigation bar, then More apps, then Add apps. Search for the add in by name, review what it asks for, and select Add. Classic Outlook and Outlook on the web have their own paths, documented on the same Microsoft support page, and the concepts are identical even where the labels are not.

Finding it after installation is where most of the confusion happens, because the location depends on what is open. While composing a message, the add in appears on the Message tab of the ribbon, or behind Apps when the ribbon is crowded. While looking at a message, it is behind More apps on the ribbon or Apps on the message action bar.

The appointment case has a quirk worth memorising. Microsoft's guidance states that to use an add in on an existing meeting or appointment, the item has to be opened in a pop up window in order to see the ribbon at all. Anyone clicking an event in the calendar grid, seeing no add in, and concluding the installation failed has run into exactly this.

Two smaller behaviours are worth knowing. Add ins can be pinned, by opening More apps, right clicking the add in, and selecting Pin, which puts it on the ribbon permanently instead of two menus deep. And add ins are unavailable offline: Microsoft documents that with no internet connection at launch, installed add ins do not appear on the ribbon or action bar, because Outlook cannot determine what is installed. A link that cannot be generated on a train is a genuine planning constraint, not a fault.

Where the meeting actually ends up

The choice of which system creates the invitation decides more than which video service gets used. It decides which calendar holds the appointment, and on a Mac that has practical consequences every day.

	Meet add in inside Outlook	Invite from Google Calendar	Subscribe Outlook to a Google calendar
Where the event is stored	The Microsoft mailbox	The Google account	Outlook holds a copy, Google holds the event
Who tracks responses	Outlook	Google Calendar	Nobody, the copy is read only
Guests see it as	An Outlook invitation	A Google Calendar invitation	Not applicable
Editable after sending	Yes, in Outlook	Yes, in Google Calendar	No
Delay before changes appear	None, it is the original	None, it is the original	Set by the refresh schedule
Meet link present	Inserted by the add in	Created with the event	Carried as text in the body

The first column is right when Outlook is the system of record and the calendar everyone reads. The second is right when the schedule lives in Google and Outlook is mostly email. The third is a reference view and never a working surface, since a subscribed calendar cannot be edited and cannot accept an invitation.

What tends to happen in practice is a mixture of the first two, and that mixture is the real complaint behind most searches on this subject. Some meetings are in Outlook, some are in Google Calendar, and neither view shows the whole day. The add in does not address that at all. It makes one of the two routes less tedious.

Guests outside the organization

Access behaviour differs by who is invited, and the listing is specific about it.

Participants inside the organization join by clicking the video meeting link in the Outlook event. Participants outside the organization can request to join the meeting, which means somebody already in the call has to admit them. After the meeting starts, additional participants can be invited.

For an external meeting that matters, the operational detail is that the host needs to be in the call early enough to let people in, and needs to be watching for the request. A client waiting in a lobby while the host is still in a previous meeting is a bad first minute, and it is a predictable one.

Meeting room hardware is handled separately. Participants joining from Google Meet hardware enter the provided meeting code using the touchscreen or the remote control rather than clicking anything, so the code has to survive into the invitation text and not be trimmed out of it.

Capacity is set by the Google Workspace plan rather than by the add in. Google's published plan comparison puts video meetings at 100 participants on Starter, 150 on Standard, 500 on Plus and 1,000 on Enterprise. Meeting recording arrives at the Standard tier. The listing notes the same principle in one line: Meet is available at no cost, and some features are only available with a paid Workspace licence.

Permissions worth reading before installing

The marketplace page states what the add in can do inside the mailbox, and the wording deserves a slow read rather than a click through.

It can send data over the internet. It can access and modify personal information in the active message, including the body, the subject, the sender, the recipients and attachment information. Other items in the mailbox cannot be read or modified.

That scope is proportionate to the job, since inserting a link into an invitation requires writing to the body of the item being composed. It is also the kind of statement a security review will want to have seen in writing, particularly the part about the active message being readable, because that includes the invitations of meetings that have nothing to do with video calls.

What this looks like on a Mac

Most of the friction reported on Mac setups is not about the add in. It is about the number of calendars in play. An Outlook event created by the add in is in Exchange. A meeting a colleague scheduled in Google Calendar is in Google. Personal appointments are likely in iCloud. Three systems, and no single screen that shows the day.

Outlook and Google Calendar can each be told to show the other, and in both directions the result is a read only copy that refreshes on a schedule rather than on a change. That is adequate for judging whether a day is busy and unsafe as the only view of today.

The alternative arrangement is to connect all of the accounts to one desktop calendar and let each event stay where it was created. The Meet add in still does its job inside Outlook when Outlook is where the invitation has to originate, and the day is readable in one place regardless of which system holds each item. A comparison of the Mac applications that can do this, with three year costs, is on Compared with other calendars, and the account connection side is covered in the Guide.

What to change first

Before installing anything, confirm with an administrator that Meet is enabled for the organization and that store add ins are permitted, since those two facts decide whether the rest is possible. Then pin the add in to the ribbon so it is one click rather than two menus, and remember to open existing appointments in a pop up window. If the underlying problem is that the day is split across Outlook, Google and iCloud, a single Mac calendar connected to all three, such as Caltimate, addresses that rather than the link generation.