Skip to content

Commit d8239b0

Browse files
authored
Merge pull request #32845 from adrianwells/patch-2
Add to Deployment requirements
2 parents 0c230d4 + 19553dd commit d8239b0

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/active-directory/authentication/howto-password-ban-bad-on-premises-deploy.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,7 @@ After the feature has been running in audit mode for a reasonable period, you ca
3333

3434
## Deployment requirements
3535

36+
* Azure Active Directory Premium P1 or P2 license. For more detailed information about Azure Active Directory licensing, see the [Azure Active Directory pricing page](https://azure.microsoft.com/pricing/details/active-directory/).
3637
* All domain controllers that get the DC Agent service for Azure AD password protection installed must run Windows Server 2012 or later. This requirement does not imply that the Active Directory domain or forest must also be at Windows Server 2012 domain or forest functional level. As mentioned in [Design Principles](concept-password-ban-bad-on-premises.md#design-principles), there is no minimum DFL or FFL required for either the DC agent or proxy software to run.
3738
* All machines that get the DC agent service installed must have .NET 4.5 installed.
3839
* All machines that get the proxy service for Azure AD password protection installed must run Windows Server 2012 R2 or later.

0 commit comments

Comments
 (0)