Microsoft Entra ID
Fundamentals

Prerequisites

In brief

Two registration URL table rows now include closing cell delimiters, and the 4 MB scoping-limit note has corrected punctuation.

What Entra admins need to know

No administrator action is required.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

  • We recommend hardening the Microsoft Entra provisioning agent server as a Control Plane (formerly Tier 0) asset by following the guidance provided in Secure Privileged Access and Active Directory administrative tier model.

  • Restrict administrative access to the Microsoft Entra provisioning agent server to only domain administrators or other tightly controlled security groups.

  • Create a dedicated account for all personnel with privileged access. Administrators shouldn't be browsing the web, checking their email, and doing day-to-day productivity tasks with highly privileged accounts.

  • Follow the guidance provided in Securing privileged access.

  • Deny use of NTLM authentication with the Microsoft Entra provisioning agent server. Here are some ways to do this: Restricting NTLM on the Microsoft Entra provisioning agent Server and Restricting NTLM on a domain

  • Ensure every machine has a unique local administrator password. For more information, see Local Administrator Password Solution (Windows LAPS) can configure unique random passwords on each workstation and server store them in Active Directory protected by an ACL. Only eligible authorized users can read or request the reset of these local administrator account passwords. Additional guidance for operating an environment with Windows LAPS and privileged access workstations (PAWs) can be found in Operational standards based on clean source principle.

  • Implement dedicated privileged access workstations for all personnel with privileged access to your organization's information systems.

  • Follow these additional guidelines to reduce the attack surface of your Active Directory environment.

  • Follow the Monitor changes to federation configuration to set up alerts to monitor changes to the trust established between your IdP and Microsoft Entra ID.

  • Enable multifactor authentication (MFA) for all users that have privileged access in Microsoft Entra ID or in AD. One security issue with using Microsoft Entra provisioning agent is that if an attacker can get control over the Microsoft Entra provisioning agent server they can manipulate users in Microsoft Entra ID. To prevent an attacker from using these capabilities to take over Microsoft Entra accounts, MFA offers protections. For example, even if an attacker manages to reset a user's password using the Microsoft Entra provisioning agent, they still can't bypass the second factor.

    |*.msappproxy.net
    *.servicebus.windows.net|The agent uses these URLs to communicate with the Microsoft Entra cloud service. | |*.microsoftonline.com
    *.microsoft.com
    *.msappproxy.com
    *.windowsazure.com|The agent uses these URLs to communicate with the Microsoft Entra cloud service. | |mscrl.microsoft.com:80
    crl.microsoft.com:80
    ocsp.msocsp.com:80
    www.microsoft.com:80| The agent uses these URLs to verify certificates.| |login.windows.net
    login.live.com|The agent uses these URLs during the registration process.| |aadcdn.msauth.net
    aadcdn.msftauth.net
    www.msftconnecttest.com|The agent uses these URLs during the registration process.|

|-----|-----| |*.msappproxy.us
*.servicebus.usgovcloudapi.net|The agent uses these URLs to communicate with the Microsoft Entra cloud service. | |mscrl.microsoft.us:80
crl.microsoft.us:80
ocsp.msocsp.us:80
www.microsoft.us:80| The agent uses these URLs to verify certificates.| |login.windows.us
secure.aadcdn.microsoftonline-p.com
*.microsoftonline.us
*.microsoftonline-p.us
*.msauth.net
*.msauthimages.net
*.msecnd.net
*.msftauth.net
*.msftauthimages.net
*.phonefactor.net
enterpriseregistration.windows.net
management.azure.com
policykeyservice.dc.ad.msft.net
ctldl.windowsupdate.us:80
aadcdn.msftauthimages.us
*.microsoft.us
msauthimages.us
msftauthimages.us| The agent uses these URLs during the registration process.|

  • Nested OUs are supported (that is, you can sync an OU that has 130 nested OUs, but you can't sync 60 separate OUs in the same configuration).

Password Hash Sync

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…