On this page

This guide is for SharePoint and Microsoft 365 tenant administrators. It lets the DYNO Mapper crawl account sign in to SharePoint Online without an MFA prompt, without turning off or weakening MFA anywhere else in your tenant.

Optional

DYNO Mapper can also answer MFA prompts during a crawl, including Microsoft Authenticator number matching and one-time passcodes. Set up this exemption when you want the crawl account to sign in without a prompt.

Prerequisites

  • Microsoft Entra ID P1 or P2 license. Conditional Access requires one of these. If your tenant uses Security Defaults only, skip to the note at the end.
  • Global Administrator or Conditional Access Administrator role.
  • A dedicated, read-only service account already created for the DYNO Mapper crawl. Never use a real employee's account.

DYNO Mapper's static IP addresses

Static IP 135.86.4.170
Static IP 252.37.219.87

Step 1. Create a named location for DYNO Mapper's IPs

  1. Sign in to the Microsoft Entra admin center.
  2. Go to Protection > Conditional Access > Named locations.
  3. Select + IP ranges location (labeled "+ Add location" on some tenants).
  4. Give it a name you will recognize, for example DYNO Mapper Crawler - Trusted.
  5. Add both IPs in CIDR notation. A single address needs a /32 suffix:
    • 35.86.4.170/32
    • 52.37.219.87/32
  6. Check Mark as trusted location.
  7. Save.

Step 2. Create a Conditional Access policy for the crawl account only

Keep it narrow

Do not add this exclusion to your existing "require MFA for everyone" policy. That would exempt the IPs for every user, not just the crawl account. Build a separate policy instead.

  1. Go to Protection > Conditional Access > Policies > + New policy.
  2. Give it a name, for example DYNO Mapper Crawl Account - Trusted IP Exemption.
  3. Under Assignments > Users, include only the DYNO Mapper service account. Not "All users."
  4. Under Target resources, scope it to SharePoint Online, or to the specific apps DYNO Mapper needs to reach.
  5. Under Conditions > Network (labeled Locations on some tenants), set Configure to Yes, include Any network or location, then exclude the named location from Step 1.
  6. Under Grant, select Require multi-factor authentication.
  7. Set Enable policy to Report-only for now. Do not turn it on yet.

Step 3. Check for conflicts with your existing MFA policy

If you already have a tenant-wide "require MFA for all users" policy, it may still catch the crawl account after Step 2. Either:

  • Exclude the crawl account from that policy's user assignment, or
  • Add the same named location as an exclusion there too.

Skipping this step is the most common reason MFA is "still" prompted from a location that should be trusted. The account passes the new policy but still hits the old one.

Step 4. Test, then turn it on

  1. Run a test crawl, or a manual sign-in, from DYNO Mapper.
  2. In the Entra admin center, go to Identity > Monitoring & health > Sign-in logs, find the sign-in event and open the Conditional Access tab.
  3. Confirm the new policy shows Applied, the location condition shows Matched, and no MFA challenge appears.
  4. Once confirmed, switch the policy from Report-only to On.

If you use Security Defaults (no Conditional Access)

Conditional Access requires Entra ID P1 or P2. Without that license, this exemption path is not available. The only way to remove the prompt is a dedicated service account with MFA turned off entirely. For an added layer of control, you can restrict that account to DYNO Mapper's IP addresses at the network or firewall level, which does not require Conditional Access.

Need help with the setup?

Email support@dynomapper.com or call 1-866-389-4643.

Contact us