Only one user fails to login to GSuite with SAML integration with AzureAD

Question

I am using AzureAD with a free license.
I believe there was no limit on the number of SAML integrations last year even for free.

I used the "Google Cloud / G Suite Connector by Microsoft" to set up SAML integration to GSuite.
Of the 6 people registered in AzureAD, 5 are able to login to GSuite via SSO using the user ID registered in AzureAD, but only 1 is getting an error.

Does anyone know the cause?

---

The error says
* After logging in with AzureAD, it redirects to the Google side, but the Google side shows "Invalid email" and the login fails.

Azure Plan:
* This is a free plan. (I haven't even registered my credit card).

Linkage Settings:
* Using "Google Cloud / G Suite Connector by Microsoft", set AzureAD as the parent and GSuite as the child.
Provisioning: Both provisioning and SAML integration have been configured.

What I found out
* A user was created on the GSuite side. When I unlinked them and tried to log in on the GSuite side, the user who had the login error was also able to log in to GSuite.
* It seems that both SAML integration and provisioning integration are configured correctly. The other 5 users can use it without any problem.
* I contacted Google. However, they said they could not find any problem on Google side.
* Google told me that the problem is similar to what happened in the past when there was not enough license on Microsoft side.

   `  
    I know the error can also happen sometimes if the user doesn't have a valid Exchange license. I am not too familiar with how the system looks in Azure but I know I am not too familiar with how the system looks in Azure but I know this has worked for others in the past.  

Are you able to check if the user has an Exchange license?

   `  

   ![65289-%E8%B2%BC%E3%82%8A%E4%BB%98%E3%81%91%E3%81%9F%E7%94%BB%E5%83%8F-2021-02-08-18-34.jpg][1]  


     [1]: /api/attachments/65289-貼り付けた画像-2021-02-08-18-34.jpg?platform=QnA

Answer 1

This sometimes happens if the user mapping is not correct. Please make sure that the value in the NameID in the SAML Response is matching with the user in Google apps.