Since the advent of Office 2013, I've been increasingly frustrated with the new Outlook contact cards, and the round-about way needed to access the legacy GAL properties dialog as shown below:

Outlook contact properties

After a ton of research, I discovered it's possible to add custom context menus within the Lync 2013 / Skype for Business client, as per this page from Microsoft. From here, I needed to discover the API necessary to actually launch the legacy GAL properties dialog box. Doing a bit of research, I simply could not find an easy way to do this, the only thing I was coming across was the following registry key, which just launched the GAL properties box from within Outlook:

DWORD: TurnOnLegacyGALDialog
Value: 1 (enable)

Nearly giving up after hours of digging through the API and searching, I was provided some help via Dmitry Streblechenko on StackOverflow (thank you, Dmitry!).

In the end, I ended up with a simple VBS and registry key:


If WScript.Arguments.Count = 2 Then
Dim objOutlook : Set objOutlook = CreateObject("Outlook.Application")
Dim objNamespace : Set objNamespace = objOutlook.GetNamespace("MAPI")
Set objOutlook = Nothing
Set objNamespace = Nothing
End If


Windows Registry Editor Version 5.00
"Name"="Outlook Properties"
"Path"="C:\\\\windows\\\\System32\\\\wscript.exe C:\\\\temp\\\\LaunchGALProp\\\\LaunchGALProperties.vbs \"%user-id%\" \"%contact-id%\""

Boom! After restarting Skype for Business, I was treated with the following view:

Outlook Properties context menu

It's quite unfortunate that Microsoft removed this functionality within the newer versions of the Lync/Skype clients, but at least with a little bit of elbow grease I was able to recover it...for now.

UPDATE 04/29/2019:

It appears that the wscript command is no longer working (for some reason). I was able to workaround this by creating a C# project with the following source code:


using System;
namespace LaunchGALProps {
class Program
static void Main(string[] args) {
if(args.Length == 2)
dynamic objApp;
dynamic objNamespace;
objApp = Activator.CreateInstance(Type.GetTypeFromProgID("Outlook.Application"));
objNamespace = objApp.GetNamespace("MAPI");

If you do not have Visual Studio installed, but you DO have .NET v4+ installed, you can compile the application like so:

C:\Windows\Microsoft.Net\v4.0.30319\csc.exe /out:LaunchGALProps.exe Program.cs

After my program was compiled, I was able to update my registry key values for ApplicationInstallPath and Path -- once this was done everything was working again.