Setting up NearAuth with Microsoft Entra ID
There are two ways to use NearAuth with Entra ID. Most companies should start with
Part A.
- Part A, by group (recommended): people in one Entra group sign in to Microsoft as
usual (password or passkey), then Microsoft asks NearAuth to confirm their phone is with them. Everyone
else is unaffected, so you can start with a few people.
- Part B, whole company: NearAuth sits in front of Entra for everyone, and apps
such as Slack use NearAuth as their sign-in. Use this if you want NearAuth to be the identity provider
for your apps.
Below,
YOUR_COMPANY_ID stands for your Company ID, which is shown in the admin console.
Sign in to see your company's own values filled in.
You'll need: a Global Administrator of your Entra tenant (to approve NearAuth once),
Microsoft Entra ID P1 or higher for Conditional Access (included in Microsoft 365 Business Premium, E3 and E5),
a NearAuth administrator account whose email is in one of the tenant's verified domains, and about 30 minutes.
1. Add your people and set up their phones
- Add people on the Users page, or have NearAuth invite a whole Entra group
automatically on the Onboarding page (after step 2).
- Each person gets an email invitation and installs NearAuth on their phone and computer
(instructions).
- Set yourself up first, so you can test before anyone else is switched over.
Part A: require NearAuth for an Entra group
2. Connect your tenant
On the
Microsoft Entra ID page, click
Grant consent and
connect and sign in as a Global Administrator. Microsoft asks you to approve NearAuth's app, which lets
NearAuth read your groups, add and remove members of the NearAuth group, and end people's Microsoft sessions
when their devices are reset.
3. Create the NearAuth group
4. Add NearAuth as an external MFA method
In the Microsoft Entra admin center, go to
Entra ID > Authentication methods >
Policies and click
Add external method:
- Name:
NearAuth
- Client ID:
(shown here when you're signed in to the admin console)
- Discovery endpoint:
(shown here when you're signed in to the admin console)
- App ID:
(shown here when you're signed in to the admin console)
Turn it on (
Enable), and under
Target include only your NearAuth
group.
5. Make Microsoft ask for it
Go to
Entra ID > Conditional Access > Policies and create a new policy:
- Users: include your NearAuth group. Exclude your emergency (break-glass) admin accounts.
- Target resources: All resources (or the apps you want to protect).
- Grant: Require multifactor authentication. Don't use an authentication strength:
external methods like NearAuth don't count toward strengths.
- Optional, Session: sign-in frequency 1 hour, so Microsoft asks NearAuth again every hour.
- If you also use Part B, exclude NearAuth's own enterprise app from this policy, or Microsoft and NearAuth
will keep sending people to each other.
Start the policy in
Report-only mode, check the sign-in logs, then turn it
On.
6. Switch people over
- Add yourself on the Microsoft Entra ID page and test: in a private browser
window, sign in to myapps.microsoft.com.
After your password, Microsoft should send you to NearAuth and back, with and without your phone nearby.
- Then click Add everyone who's set up. Only people whose phone is set up are added,
and people are removed when their devices are reset.
Only add people who have NearAuth on their phone: once they're in the group, Microsoft won't let them in
without it.
Part B: NearAuth in front of Entra for the whole company (optional)
- In the Microsoft Entra admin center, go to Entra ID > Enterprise apps > New
application > Create your own application, name it NearAuth, and choose "Integrate any other
application you don't find in the gallery".
- Open Single sign-on > SAML and enter:
Identifier (Entity ID): https://secure.nearauth.ai/SAML2/SSO/YOUR_COMPANY_ID/EntityId
Reply URL (Assertion Consumer Service URL): https://secure.nearauth.ai/SAML2/SSO/YOUR_COMPANY_ID/fromIdp
Sign on URL: https://secure.nearauth.ai/SAML2/SSO/YOUR_COMPANY_ID/SignIn
Logout URL: https://secure.nearauth.ai/logout
(or upload NearAuth's metadata from https://secure.nearauth.ai/SAML2/SSO/YOUR_COMPANY_ID/nearAuthSpMetadata).
- Download the Federation Metadata XML from the same page.
- On NearAuth's Settings page, set Current Identity Provider
Connection to SAML / EntraID and click Upload SAML
to paste in that metadata.
- Under Users and groups in the enterprise app, assign the people who should sign in
through NearAuth.
- Point your other apps (Slack and so on) at NearAuth: register each one on the
Service Providers page and give the app NearAuth's metadata from
https://secure.nearauth.ai/SAML2/SSO/YOUR_COMPANY_ID/nearAuthIdpMetadata. People who aren't set up with
NearAuth are sent on to Entra and back to the app, if your Settings let in
people who aren't in the console.
Optional
- Invite automatically: on the Onboarding page, pick an
Entra group whose members NearAuth invites, reminds, and enforces once they're set up.
- Off-site rules: on the Off-site sign-ins page, set what
happens when people sign in away from your offices.
If someone can't sign in: remove them from the NearAuth group (on the
Microsoft Entra ID page or in Entra) and Microsoft stops asking NearAuth.
Questions: help@NearAuth.ai or 607-238-3533.