Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Extra sign-in checks for remote application access without locking people out

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Stronger sign-in for hosted application access—often multifactor authentication at the gateway or identity layer—reduces credential theft risk. It also adds failure modes: lost phones, push fatigue, and users who cannot complete a challenge while travelling. Buyer planning should pair enforcement with break-glass accounts, registration campaigns, and clear ownership of identity versus hosting support.

Why it matters

Security-conscious owners want MFA on remote paths without inventing a lockout story that stops payroll on Friday. Microsoft’s integration guide for Remote Desktop Gateway and Entra multifactor authentication via the NPS extension describes a flow where username/password is verified, policies are evaluated, then secondary authentication is triggered before the gateway accepts the session.

How it works

RD Gateway terminates TLS from clients and applies Connection Authorization Policies and Resource Authorization Policies. Integrating cloud MFA places the NPS extension in the RADIUS path: after primary auth succeeds, Entra MFA performs the second step. Supported methods in that article include phone call and Authenticator Approve/Deny push; edge cases exist when users register TOTP in ways that conflict with gateway challenges—Microsoft documents registry override options when number matching blocks gateway sign-in.

Remote Desktop Gateway sign-in does not offer a field to type a verification code for Entra MFA. Microsoft states that if a user is not configured for phone verification or the Microsoft Authenticator app with Approve/Deny push notifications, the user cannot complete the MFA challenge and sign in through RD Gateway (SMS text is also called out as unsuitable for this path).

This is hosted buyer planning, not a how-to for repairing a broken Entra Conditional Access policy. Prerequisites include synced identities, NPS role placement, and MFA licensing—your design must name who operates each layer.

Identity-admin recovery vs staff gateway access

Microsoft emergency access accounts are cloud-only Entra administrator accounts for tenant emergencies—for example when Conditional Access, federation, or MFA blocks normal Global Administrator work. They are not a substitute for restoring everyday staff RD Gateway sign-in when on-premises Active Directory, NPS, or federation for workforce users is down. Plan identity-administrator recovery (Entra break-glass, validation drills, monitoring) separately from gateway access recovery (documented on-premises AD, NPS, RD Gateway, and workforce MFA contingencies your architecture team owns).

Labelled example — professional services firm: Enforces MFA on RD Gateway for all staff; maintains Entra emergency access accounts excluded from blocking Conditional Access policies, with validation drills at least every 90 days per Microsoft emergency access guidance, plus separate runbooks for AD/NPS gateway outages.

Labelled example — distributed sales team: Phased MFA by group after Authenticator registration pilots; helpdesk script aligned with Entra MFA deployment guidance.

What to choose and why

Step Purpose
Inventory who uses remote access Scope MFA registration
Register MFA before enforcement deadline Avoid mass lockout
Document break-glass and escalation Owner-approved exception path
Pilot gateway + MFA with native client Exercises the path most session-based LOB pilots use
Communicate that MFA is separate from app password Reduces “ERP is down” misreports

Create emergency (break-glass) access accounts before you widen enforcement, then pilot sign-in with a representative group. Microsoft’s emergency access guidance describes cloud-only accounts, phishing-resistant credentials, excluding those accounts from Conditional Access policies that would block the very scenario the accounts exist for, and validating account functionality at least every 90 days (including sign-in and administrative task drills).

Risks and limits

The NPS extension article explicitly warns against using it with legacy MFA Server deployments. Gateway CAP/RAP misconfiguration can deny access even when MFA succeeds. Lab validation: none.

Sources

Related reading

Learning notes

  1. MFA at the gateway is an additional gate after primary directory authentication.
  2. RD Gateway MFA expects phone call or Authenticator push—not arbitrary TOTP entry in the client.
  3. Break-glass accounts need monitoring, 90-day validation, and post-use review per Microsoft guidance—not a blanket “security off” switch.
  4. Native RDP clients are the practical MFA pilot channel for LOB staff.
  5. Identity and hosting providers split responsibility; document both support lines and separate Entra admin recovery from staff gateway recovery.