Forum Discussion
File Share Connector users not mapping
Hi everyone,
In need of some help here. I've setup an on-prem file share connector following this guide:
https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/fileshare-connector
I can see the indexed items in my test folder, but, we can't crawl that data because the users are not mapping for some reason. I've been testing using the NTFS file permissions option. Has anyone had any success with using this option to sync/map users to the connector? If so, what were the requirements?
The users are AD to entra id connect synced and the group I created is also AD to entra id connect synced as well. I applied ntfs perms to the test folder directly using the synced identity and tried using the group and the full crawl still does not populate users. I am not using nested groups neither. I also tried removing built-in groups such as administrators, authenticated users, etc.
I've had a ticket open for weeks with Microsoft now with no answers.
4 Replies
The first real world deployment I'm doing has hit the above issue. Connector in the admin portal showing 0 users synced, 105 items synced.
Rollout audience is correct, the copilot user is able to login to the on-premise machine and get access to the same file share location.
I did this with a Hyper-V VM before the engagement and it worked flawlessly.
For us I found our problem, it was the folder permissions on our file server. The folder I was testing with just had Domain Users for permissions and that was it. Since Entra AD Connect does not sync the domain users group, I was getting access denied from the File Share connector in CoPilot. Had to either add my user manually to the folder or add a group that was part of an Entra AD Synced OU and it worked after that. For what it's worth as well, the user mappings on the main page of the File Share Connector still shows zero, but if you go to the index search and paste in a path to a file that is part of the index then click the permissions/access tab it will show you who actually has access
Beat me to it. This was also our issue. The OU being used to provide access was outside the Entra Sync so it would not be recognised.
After adding a group which was Entra sync’d it worked.
Hey were you able to find a solution to this? We are running into the exact same issue as well with the exact same setup as you have
