Page 1 of 1

Office 365 source is indexed incorrectly (shared folders)

PostPosted: Wed Apr 05, 2017 5:27 am
by Dan
Office 365 acccount daniel@domain.com, setup in Outlook 2016. X1 is indexing that account fine.

The account daniel@domain.com has also access to several shared folders defined in Office 365 (Ein@domain.com, Support@domain.com). Those folders are assigned to daniel@domain.com via automapping in Outlook.
As you see in the screenshot below, those additional shared folders are visible in Outlook, but are NOT selected in X1. I would expect that those shared folders are not indexed.

Image

Unfortunately, the shared folders ARE indexed. And I think I know why.

In Outlook 365 OWA (web access to Office 365), one does not see the shared folders initially (automapping only works with Outlook). However, I can manually "Add shared folder..." in the OWA frontend (right click the folder root). That way I can easily add the shared folders I am supposed to hace access to, also in the OWA GUI. This "add" only needs to be done once and the shared folders are visible after each subsequent login.

Now comes the problem.
As soon as I add such a shared folder in OWA, it is also indexed in X1 on my local PC. Even if I explicitely did not select those folders in the X1 configuration (see above screenshot).
If I remove this added folder in Office 365 OWA GUI again, it is not indexed anymore.

I consider this a bug.

Any comments?

Daniel

Re: Office 365 source is indexed incorrectly (shared folders

PostPosted: Wed Apr 05, 2017 7:16 am
by Dan
I must correct myself.
Shared folders are apparently indexed always.
I believe this is still a bug.
Daniel