Tips: How to find the Outlook Folder GUIDs to use?

1. Using the Spirion "Gather Data" Tool (Recommended for Support/Admins)

The most reliable way to get the exact GUID that the Spirion agent "sees" is to use Spirion's own diagnostic tools.

• The Process: Run a small "Discovery" scan or use the Gather Data utility on a machine where the mailbox is configured.
• Where to look: In the resulting diagnostic logs (specifically the IdentityFinder.log or the XML output of a discovery scan), Spirion lists the folders it encounters. Next to the folder name (for example, "Inbox"), you see a long string of alphanumeric characters in brackets—that is the GUID.
• Example: Inbox {00000000-0000-0000-0000-000000000000}

2. Using MFCMAPI (The "Pro" Method)

MFCMAPI is a free, open-source tool from Microsoft used by Exchange administrators to look "under the hood" of Outlook profiles.

1. Download and run MFCMAPI on the computer with the Outlook profile.
2. Go to Session > Logon and select the Outlook profile.
3. Double-click the mailbox store (e.g., Mailbox - User Name).
4. Expand Root Container and then Top of Information Store.
5. Right-click the folder you want (e.g., "Inbox") and select Display Property Book.
6. Look for the property PR_ENTRYID or PR_STORE_ENTRYID.
7. • Note: Spirion typically uses the EntryID as the unique identifier for targeting. You can copy the "Binary" or "Ansi" string value from here.

3. Using PowerShell (Best for Exchange/O365 Admins)

If you are an administrator and need to find GUIDs for many users at once, you can use the Exchange Management Shell or the ExchangeOnlineManagement module.

• Use the following PowerShell command:

Get-MailboxFolderStatistics -Identity "user@company.com" | Select Name, FolderId

• The Result: A list of all folders in that user's mailbox along with their FolderId (which is the GUID format Spirion requires) is returned.

Important Tips for Using GUIDs in Spirion:

• One per line: When you paste the GUIDs into the "Insert Outlook Folder GUIDs" box in the Spirion wizard, ensure you put each GUID on its own line.
• Format: Ensure you are copying the full string. It usually looks like a long series of random characters (e.g., AAMkAGU0MmY...).
• Permissions: Even if you have the correct GUID, the agent must still have the necessary permissions (either as the logged-in user or via a Service Account) to access that specific folder, or the scan will return an "Access Denied" error.

Summary: If you are troubleshooting a single machine, MFCMAPI is the fastest way to see the ID. If you are setting up a large-scale policy, use PowerShell to gather the IDs from the server side.