Skip to content

Commit ea25390

Browse files
Update memo-22-09-multi-factor-authentication.md
found the items that were listed as blocking for memo-22-09-authorization. they were in the mfa article.
1 parent 06acb6b commit ea25390

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

articles/active-directory/standards/memo-22-09-multi-factor-authentication.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -92,18 +92,14 @@ For each of the five phishing-resistant MFA types previously mentioned, you use
9292

9393
### Enforcing phishing-resistant MFA
9494

95-
Today, Conditional Access enable you to enforce MFA for users in your tenant. With the addition of Cross Tenant Access Policies, you can enforce it on external users.
96-
97-
In the future, you will be able to assess the strength of authenticators in Conditional Access policies. This functionality will enable you to accept any authenticator with the specified strength.
95+
Conditional Access enables you to enforce MFA for users in your tenant. With the addition of Cross Tenant Access Policies, you can enforce it on external users.
9896

9997
#### Enforcement across agencies
10098

10199
[Azure AD B2B collaboration](../external-identities/what-is-b2b.md) (B2B) helps you to meet the requirement to facilitate integration among agencies. It does this by both limiting what other Microsoft tenants your users can access, and by enabling you to allow access to users that you do not have to manage in your own tenant, but whom you can subject to your MFA and other access requirements.
102100

103101
You must enforce MFA for partners and external users who access your organization’s resources. This is common in many inter-agency collaboration scenarios. Azure AD provides [Cross Tenant Access Policies (XTAP)](../external-identities/cross-tenant-access-overview.md) to help you configure MFA for external users accessing your applications and resources. XTAP uses trust settings that allow you to trust the MFA method used by the guest user’s tenant instead of having them register an MFA method directly with your tenant. These policies can be configured on a per organization basis. This requires you to understand the available MFA methods in the user’s home tenant and determine if they meet the requirement for phishing resistance.
104102

105-
In the future, Microsoft will enable signals from your tenant and guest users’ home tenants to help determine if the MFA used by the guest user was phishing resistant. These settings will allow you to incorporate MFA requirements directly into your Conditional Access policies for external users
106-
107103
## Password policies
108104

109105
The memo requires organizations to change password policies that have proven to be ineffective, such as complex passwords that are rotated often. This includes the removal of the requirement for special characters and numbers as well as time-based password rotation policies. Instead, consider doing the following:

0 commit comments

Comments
 (0)