I did not find any related issues that address this specific problem.
[REQUIRED] Version info
node: v18.20.3
firebase-functions: 5.0.1
firebase-tools: 13.11.2
firebase-admin: 12.2.0
[REQUIRED] Test case
I have a Firebase Cloud Function that triggers on user creation (functions.auth.user().onCreate()). When a user registers using the Microsoft authentication provider, the emailVerified field is returned as false in the user object, even though the Microsoft account has a verified email.
[REQUIRED] Steps to reproduce
Set up Firebase Authentication with Microsoft as a provider.
Create a Cloud Function that triggers on user creation (functions.auth.user().onCreate()).
Register a new user using the Microsoft provider.
Inspect the emailVerified field in the user object within the triggered Cloud Function.
[REQUIRED] Expected behavior
The emailVerified field should be true when the user registers using the Microsoft provider, as the email is verified by Microsoft during their authentication process.
[REQUIRED] Actual behavior
The emailVerified field is returned as false for users registering with the Microsoft provider, even though the email should be considered verified by Microsoft.
Related issues
I did not find any related issues that address this specific problem.
[REQUIRED] Version info
node: v18.20.3
firebase-functions: 5.0.1
firebase-tools: 13.11.2
firebase-admin: 12.2.0
[REQUIRED] Test case
I have a Firebase Cloud Function that triggers on user creation (functions.auth.user().onCreate()). When a user registers using the Microsoft authentication provider, the emailVerified field is returned as false in the user object, even though the Microsoft account has a verified email.
[REQUIRED] Steps to reproduce
[REQUIRED] Expected behavior
The emailVerified field should be true when the user registers using the Microsoft provider, as the email is verified by Microsoft during their authentication process.
[REQUIRED] Actual behavior
The emailVerified field is returned as false for users registering with the Microsoft provider, even though the email should be considered verified by Microsoft.
result User into hook
Note: Locally in the emulator, this works as expected, and the emailVerified field is set to true.
Were you able to successfully deploy your functions?
Yes, the functions deploy successfully without any errors.