Skip to main content
The sign-in, sign-up and invitation pages of the console offer Continue with Google and Continue with Microsoft next to the password form (Sign up with Google and Sign up with Microsoft on the sign-up page). Every console user can use them, whatever their role, and nothing has to be set up by your administrator. They are a different thing from SAML single sign-on, which connects your organization’s own identity provider.

What happens when you sign in

ProofAge looks for your ProofAge account in this order:
  1. A Google or Microsoft account you linked before signs you in to that ProofAge account. It is matched by the provider’s own account identifier, so changing the email address at Google or Microsoft later does not move it to another ProofAge account.
  2. No link yet, and a ProofAge account has the same email address. ProofAge links the provider to that account and signs you in, but only when both of these hold:
    • the provider vouches for the address (see below);
    • the ProofAge account’s own email address has been verified, for example by accepting an invitation, resetting the password or verifying it in Profile → Security.
    You receive an email saying that Google or Microsoft sign-in was added to your account.
  3. No ProofAge account with that address. You can create one when the provider vouches for the address, or with a personal Microsoft account (see below): ProofAge asks for your company name and your name, and the account starts without a password.
If your account has an authenticator app, ProofAge asks for its code after Google or Microsoft has signed you in. The provider never replaces your second factor.

When an email address counts as confirmed

A provider’s email address links to an existing account, or accepts an invitation, only when ProofAge trusts it: A Google account on any other address, for example a Google account opened with a company address that is not a Workspace account, cannot link to an account by email or create one.

When ProofAge refuses

The sign-in page shows the reason. The most common ones:

Microsoft work accounts need their Email field

Microsoft puts the email address in what it sends ProofAge only when the user’s Email attribute (mail) is filled in. Microsoft 365 tenants with Exchange Online fill it; tenants without Exchange mail often leave it empty.
If a work account’s Email field is empty, that person can neither sign in nor sign up with Microsoft: the sign-in fails with the reason email_missing (“Microsoft did not share an email address for this account”). ProofAge does not fall back to the user principal name, because Microsoft documents it as changeable and not meant for authorization. A Microsoft administrator fixes it by filling in the user’s Email field in the Microsoft Entra admin center (Users → the user → Properties → Contact information), with an address on a domain the tenant has verified.
Linking Microsoft from Profile → Security still works for such an account, because there the person is already signed in to ProofAge. If Microsoft asks for an administrator’s approval the first time, your organization does not let people consent to apps themselves; a Microsoft administrator has to approve ProofAge.

Personal Microsoft accounts

A personal Microsoft account does not carry Microsoft’s “verified by the domain owner” mark. So:
  • it can create a new ProofAge account of its own. The sign-up page then says that Microsoft signed you in as the address, not that it confirmed it, and the account’s email stays unverified;
  • it never links to an existing ProofAge account by email, and never accepts an invitation;
  • to add an authenticator app or a passkey to that account, verify its email first (Profile → Security);
  • while the email is unverified, a password reset (the link goes to the mailbox) removes the Microsoft link, signs out every session and verifies the address: whoever holds the mailbox keeps the account.

Accepting an invitation

On the invitation page, Continue with Google or Continue with Microsoft accepts the invitation instead of setting a password. It works only when the provider’s address is trusted (table above) and is the exact address the invitation was sent to. Otherwise the page says why (with a shortened form of the invited address when the addresses differ), and you can accept with a password instead. If you already have a ProofAge account, sign in and accept from the banner in the console; an unverified email address must be verified first (Profile → Security). If your organization limits invitations to some domains, acceptance is checked against that list too.

Accounts without a password

An account created with Google, Microsoft or SAML has no password. Where the console asks you to confirm it is you (before changing sign-in methods or sessions, for example), it offers what your account has: your password, a passkey, or Microsoft, which is asked to make you sign in again. Google is offered only to an account with neither a password nor a passkey, because Google cannot be made to ask for the password again; a personal Microsoft account confirms only such an account too, and otherwise asks you to use your password or passkey. You can set a password in Profile → Security, and Forgot password? works for an account without one.

Unlinking

Profile → Security → Sign-in methods lists the linked accounts. Unlink asks you to confirm it is you, and is refused when it would leave the account with no way in: add a password or a passkey first.