Who is this article for?

Users who can't access auto discovered SharePoint locations.

SharePoint Admin access required for some of these steps

This article covers a number of reasons why auto discovered SharePoint locations may not be appearing and how to address them.

1. Stale login

One possible cause could be that the login we have stored for accessing SharePoint has somehow become stale.

To check if this is the cause:

1. Close Outlook.
2. Open File Explorer.
3. Navigate to: %localappdata%\28Hands\Mail Manager\ 
4. Delete the mmAuthStore.db file.

5. Start Outlook.
6. Re-enter SharePoint login details when prompted.
7. Leave the application open for up to 2 hours.

The locations should appear if stale login was the cause of them not displaying.

Alternatively:

1. Open Task Manager.
2. Switch to the "Details" tab.
3. Look for MailManager.AutoDiscoveryLocations.exe.
   This needs to have started after you entered your SharePoint credentials. When it disappears, you can check if the locations have appeared.

If the process isn't already running, you can start it manually by right-clicking the Mail Manager icon in your tray and selecting Run discover filing locations.

2. Unable to access

Another reason could be that your Mail Manager cannot access the organisation's Shared Configuration Folder.

To check access:

1. Go to Mail Manager.
2. Select Status.
3. Switch to Session log.
4. Scroll to the top.
   It should list your Mail Manager Shared Configuration Folder path on the second line. You should also see "Mirror updating" and "Mirror updated" lines to confirm you have access.

If you don't see this line or see an error in your Session log, follow the steps to troubleshooting Shared Configuration Folder access issues.

3. Folder permissions changed

Another reason could be a change in folder permissions.

This can be checked by going to the folders along the path and making sure the correct users or groups have permission. You may also need to check the users are still members of the groups and if the groups are the owners of the site, you need to check site permissions too. 

To check permissions:

1. Open a library or folder.
2. Click the Information icon in the top-right of the screen.
   This will open a panel with additional page details.
3. Select the Manage access option.

To check site group permissions:

1. Click the Cog icon in the top-right of the page.
2. Select Site permissions.
3. Expand each group listed.

To resolve this, ensure the right users have permissions to view the folders.

Note that being an owner alone may not work and ensuring the user is also a member, even if as part of a group of users, would ensure this and has resolved it where a location in a site cannot be found.

3. Server permissions changed

Sever permissions are permissions that need to be granted for Mail Manager to access all required parts of SharePoint. This is done through the Admin App Consent Page.

There, you would enter the first part of your SharePoint address in the first box and click Submit to complete some of the links.

You need to follow, at the very least, the Mail Manager Desktop (SharePoint) link. You may need to follow other links depending on what you are using or what advice you receive from our Support Team.

To resolve this, try reapplying the permissions in case they have been disabled.

SharePoint Admin and/or Azure Admin access are required to apply some of these permissions.

4. SharePoint settings changed

Similar to the folder permissions, your sharing settings for the entire site could have changed.

To check sharing settings:

1. Click the Cog icon in the top-right of the page.
2. Select Shared with....
3. Ensure each setting is correct.
   This is particularly important for the Search settings, as they are required for Auto Discovery.

These settings can be changed at various levels, including the site and the SharePoint tenant as a whole.

5. Folders moved

Folders may have been relocated so the path doesn't match up with the pattern we are searching.

To resolve this, ensure the folders are still present in the default file path.

6. Non-existent filing folder

The folder may exist for the structure but the actual folder where the emails are to be filed may not exist.

To resolve this, create the folder manually for the location to be picked up by auto-discovery.

7. SharePoint tenant changed

It may be that you have moved to a different SharePoint Tenant. That means changing the address from https;//companyA.sharepoint.com to https://companyB.sharepoint.com, perhaps through company changes.

To resolve this, change your storage location.

8. Not discovering private channels

Using SharePoint auto discovery patterns with private channels is not supported.