Forum Discussion

Sian_AE's avatar
Sian_AE
Copper Contributor
Apr 26, 2022

That didn't work - user cannot be found in the directory

Hi all,

 

I am completely new to SharePoint and not fluent in tech speak so please be patient! 🙂

 

For months I have been sharing a folder with external clients successfully. Yesterday morning, I started to receive emails from everyone saying that they are all receiving the message 'User X@X.com can't be found in the XXX directory (see above).

 

I have looked at help articles and searched the forums but I cannot see why all external users would lose access overnight. I have checked their access (on the Manage access menu) and it all seems correct. I have tried removing and adding people again but they still get the same message.

 

Any ideas what could have changed overnight to mean that all external users no longer have access?

 

Thanks

Sian 

  • mr_w1nst0n's avatar
    mr_w1nst0n
    Iron Contributor

    Hi Sian_AE ,

     

    If I understood properly the issue you are facing is only with external people.

    I would follow the checklist below:

    • Check that affected external users are still present and valid in your Azure Active Directory corporate
    • Check if any SharePoint Admins modified recently the sharing policy settings globally or at specific site
    • Sian_AE's avatar
      Sian_AE
      Copper Contributor
      Hi mr_w1nston

      Thanks so much for your response.

      It turns out that the issue was a wider one with SharePoint affecting a certain number of people. It was resolved about 48 hours later.

      Apologies - I thought I had closed this thread but really appreciate your response.

      I was just relieved that it wasn't something that I had got wrong!
      • GerhardPeter's avatar
        GerhardPeter
        Copper Contributor

        Sian_AE Can you elaborate on how you resolved the issue? We are currently facing the same problem, that is, a certain number of people all of a sudden do not have access to SharePoint anymore and who receive the error message you just quoted.

Resources