Software
The Lync Meeting Add-In for Microsoft Office 2013 download lets you schedule and join meetings without leaving your documents.
If you’ve ever struggled to connect Lync to Word or Outlook, this tool is the game-changer you need. Below, I’ll show you where to get the official 32-bit and 64-bit versions, plus how to avoid installation headaches that waste hours.
Where to download the Lync Meeting add-in for Office 2013 (32-Bit/64-Bit)
The Lync Meeting Add-In for Office 2013 lets you launch meetings directly from Outlook, Word, or PowerPoint. However, Microsoft no longer hosts direct downloads for older versions like Office 2013, forcing users to dig through archives or third-party sites—often risking malware.
I’ll show you the safest way to get the official add-in, including bit-version compatibility and verification steps to avoid fakes.
Microsoft’s official support for Office 2013 ended in 2023, but the Lync Meeting Add-In (now part of Skype for Business) remains functional if downloaded from trusted sources. The add-in is critical for users relying on Outlook integration or PowerPoint presenter mode during Lync/Skype meetings.
Below, I’ve compiled the most reliable download methods, including direct links and system checks.
Before downloading, confirm your Office 2013 bit-version (32-bit or 64-bit) by right-clicking the Office shortcut > Properties > Compatibility tab. Mixing bit-versions can cause the add-in to fail silently. The table below compares the two versions and their requirements.
| Spec | 32-Bit Version | 64-Bit Version |
|---|---|---|
| Office 2013 Compatibility | Office 2013 32-bit only | Office 2013 64-bit only |
| Lync/Skype for Business Version | 2013 or later | 2013 or later |
| Download Source | Microsoft Archive | Microsoft Archive |
| File Size | ~12 MB | ~15 MB |
| Key Features | Outlook meeting scheduling, Word/PPT integration | Same as 32-bit + 64-bit app support |
| Verification Step | Check digital signature via File > Properties | Same as 32-bit |
The Microsoft Archive links above are the safest sources for the Lync Meeting Add-In. If these links fail, try the Microsoft Update Catalog (catalog.update.microsoft.com) and search for "Lync Meeting Add-in for Office 2013".
Always verify the file’s digital signature by right-clicking the downloaded .exe > Properties > Digital Signatures tab. Look for a signature from "Microsoft Corporation"—anything else is a fake.
If you’re using Skype for Business (Lync’s successor), ensure it’s updated to the latest version via Control Panel > Programs > Programs and Features. Older versions of Skype for Business may block the add-in from loading.
Pro tip: Install the add-in before opening Outlook for the first time to avoid permission prompts later.
For users stuck with corporate-managed Office 2013, check with your IT admin first—the add-in might be deployed via Group Policy or Software Center. If not, the manual download steps above still apply.
Avoid third-party sites like Softonic or FileHorse, as they often bundle unwanted software or outdated versions.
Once downloaded, run the installer as Administrator (right-click > Run as Administrator). The setup will guide you through adding the add-in to your Office applications. If you encounter errors, ensure Lync/Skype for Business is installed and running.
For PowerPoint users, the add-in adds a "Lync Meeting" tab during presentations—critical for remote collaboration.
Still having issues? Try repairing your Office 2013 installation via **Control Panel > Programs > Programs and
How to install and configure the add-in in Office 2013 (with common errors fixed)
Before installing the Lync Meeting Add-In, verify your Office 2013 version (32-bit or 64-bit) matches the add-in’s architecture. Run the Office 2013 installer again to confirm—most 64-bit systems default to 32-bit Office, which can cause compatibility issues.
Also, ensure Lync/Skype for Business is installed, as the add-in relies on it for meeting functionality. I’ve seen users skip this step and waste hours troubleshooting later.
Download the add-in from Microsoft’s official site—never third-party sources. Extract the MSI installer to a folder (e.g., C:\LyncAddIn\) for easy access. Right-click the file and select Run as Administrator to bypass permission errors.
If prompted, accept the End User License Agreement and follow the default installation path. This step is critical for avoiding ‘Add-In failed to load’ errors later.
Installing a 64-bit add-in on 32-bit Office (or vice versa) will trigger the ‘Add-In failed to load’ error. Double-check your Office 2013 version in File > Account. If unsure, run the Office installer and select Change > Quick Repair to reset components.
Open Outlook 2013 first—this app often caches add-in configurations. Go to File > Options > Add-Ins and select COM Add-Ins from the dropdown. Click Go, then browse to the Lync Meeting Add-In location (e.g., C:\Program Files\Common Files\Microsoft Lync Add-in\).
Check the box and restart Outlook. For Word/PowerPoint, repeat in File > Options > Add-Ins > Manage > COM Add-Ins.
If you see the ‘Lync not detected’ error, launch Lync/Skype for Business manually and sign in. The add-in requires an active connection to sync meeting data. Test by creating a dummy meeting in Outlook—if the Join Meeting button appears in the ribbon, the add-in is working.
For stubborn issues, run Office Repair via Control Panel > Programs > Programs and Features.
To verify compatibility, check your Office 2013 update level (should be KB2817300 or later). Outdated versions may block add-ins. Use Windows Update to patch Office, then restart your PC.
Pro tip: Disable other COM add-ins temporarily—they can conflict with Lync’s integration. Go to File > Options > Add-Ins > Manage > COM Add-Ins and uncheck non-essential plugins.
After installation, test the add-in in all three apps: Outlook (meeting scheduling), Word (shared documents), and PowerPoint (live presentations). If errors persist, check the Event Viewer (Win + X > Event Viewer > Windows Logs > Application) for clues.
Most issues stem from permission conflicts or corrupted Office profiles. Creating a new Office profile often resolves this.
