Merge pull request #192506 from Justinha/table

small edits

Author: jborsecnik

articles/active-directory/authentication/feature-availability.md

@@ -6,7 +6,7 @@ services: multi-factor-authentication
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: conceptual
-ms.date: 02/28/2022
+ms.date: 03/22/2022
 
 ms.author: justinha
 author: justinha
@@ -25,59 +25,51 @@ This following tables list Azure AD feature availability in Azure Government.
 
 |Service     | Feature | Availability |
 |:------|---------|:------------:|
-|**Authentication, single sign-on, and MFA**|||
-||Cloud authentication (Pass-through authentication, password hash synchronization) | ✅ |
+|**Authentication, single sign-on, and MFA**|Cloud authentication (Pass-through authentication, password hash synchronization) | ✅ |
 || Federated authentication (Active Directory Federation Services or federation with other identity providers) | ✅ |
 || Single sign-on (SSO) unlimited | ✅ | 
 || Multifactor authentication (MFA) | Hardware OATH tokens are not available. Instead, use Conditional Access policies with named locations to establish when multifactor authentication should and should not be required based off the user's current IP address. Microsoft Authenticator only shows GUID and not UPN for compliance reasons. | 
 || Passwordless (Windows Hello for Business, Microsoft Authenticator, FIDO2 security key integrations) | ✅ | 
 || Service-level agreement | ✅ | 
-|**Applications access**|||
-|| SaaS apps with modern authentication (Azure AD application gallery apps, SAML, and OAUTH 2.0) | ✅ | 
+|**Applications access**|SaaS apps with modern authentication (Azure AD application gallery apps, SAML, and OAUTH 2.0) | ✅ | 
 || Group assignment to applications | ✅ | 
 || Cloud app discovery (Microsoft Cloud App Security) | ✅ | 
 || Application Proxy for on-premises, header-based, and Integrated Windows Authentication | ✅ | 
 || Secure hybrid access partnerships (Kerberos, NTLM, LDAP, RDP, and SSH authentication) | ✅ | 
-|**Authorization and Conditional Access**|||
-|| Role-based access control (RBAC) | ✅ | 
+|**Authorization and Conditional Access**|Role-based access control (RBAC) | ✅ | 
 || Conditional Access  | ✅ | 
 || SharePoint limited access | ✅ | 
 || Session lifetime management | ✅ | 
 || Identity Protection (vulnerabilities and risky accounts) | See [Identity protection](#identity-protection) below. | 
 || Identity Protection (risk events investigation, SIEM connectivity) | See [Identity protection](#identity-protection) below. | 
-|**Administration and hybrid identity**|||
-|| User and group management | ✅ | 
+|**Administration and hybrid identity**|User and group management | ✅ | 
 || Advanced group management (Dynamic groups, naming policies, expiration, default classification) | ✅ | 
 || Directory synchronization—Azure AD Connect (sync and cloud sync) | ✅ | 
 || Azure AD Connect Health reporting | ✅ | 
 || Delegated administration—built-in roles  | ✅ | 
 || Global password protection and management – cloud-only users | ✅ | 
 || Global password protection and management – custom banned passwords, users synchronized from on-premises Active Directory | ✅ | 
 || Microsoft Identity Manager user client access license (CAL) | ✅ | 
-|**End-user self-service**|||
-|| Application launch portal (My Apps) | ✅ | 
+|**End-user self-service**|Application launch portal (My Apps) | ✅ | 
 || User application collections in My Apps | ✅ |
 || Self-service account management portal (My Account) | ✅ |
 || Self-service password change for cloud users | ✅ |
 || Self-service password reset/change/unlock with on-premises write-back | ✅ |
 || Self-service sign-in activity search and reporting | ✅ |
 || Self-service group management (My Groups) | ✅ |
 || Self-service entitlement management (My Access) | ✅ |
-|**Identity governance**|||
-|| Automated user provisioning to apps | ✅ |
+|**Identity governance**|Automated user provisioning to apps | ✅ |
 || Automated group provisioning to apps | ✅ |
 || HR-driven provisioning | Partial. See [HR-provisioning apps](#hr-provisioning-apps). |
 || Terms of use attestation | ✅ |
 || Access certifications and reviews | ✅ |
 || Entitlement management | ✅ |
 || Privileged Identity Management (PIM), just-in-time access |  ✅ |
-|**Event logging and reporting**|||
-|| Basic security and usage reports | ✅ |
+|**Event logging and reporting**|Basic security and usage reports | ✅ |
 || Advanced security and usage reports | ✅ |
 || Identity Protection: vulnerabilities and risky accounts | ✅ |
 || Identity Protection: risk events investigation, SIEM connectivity | ✅ |
-|**Frontline workers**|||
-|| SMS sign-in | Feature not available. |
+|**Frontline workers**|SMS sign-in | Feature not available. |
 || Shared device sign-out | Enterprise state roaming for Windows 10 devices is not available. |
 || Delegated user management portal (My Staff) | Feature not available. |
 

articles/active-directory/authentication/how-to-mfa-registration-campaign.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: conceptual
-ms.date: 02/28/2022
+ms.date: 03/22/2022
 
 ms.author: justinha
 author: mjsantani
@@ -101,7 +101,7 @@ The following table lists **authenticationMethodsRegistrationCampaign** properti
 | Name | Possible values | Description |
 |------|-----------------|-------------|
 | state | "enabled"<br>"disabled"<br>"default" | Allows you to enable or disable the feature.<br>Default value is used when the configuration hasn't been explicitly set and will use Azure AD default value for this setting. Currently maps to disabled.<br>Change states to either enabled or disabled as needed.  |
-| snoozeDurationInDays | Range: 0 – 14 | Defines after how many days the user will see the nudge again.<br>If the value is 0, the user is nudged during every MFA attempt.<br>Default: 1 day |
+| snoozeDurationInDays | Range: 0 – 14 | Defines the number of days before the user is nudged again.<br>If the value is 0, the user is nudged during every MFA attempt.<br>Default: 1 day |
 | includeTargets | N/A | Allows you to include different users and groups that you want the feature to target. |
 | excludeTargets | N/A | Allows you to exclude different users and groups that you want omitted from the feature. If a user is in a group that is excluded and a group that is included, the user will be excluded from the feature.|
 

articles/active-directory/authentication/howto-mfa-mfasettings.md

@@ -6,7 +6,7 @@ services: multi-factor-authentication
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: how-to
-ms.date: 01/11/2022
+ms.date: 03/22/2022
 
 ms.author: justinha
 author: justinha
@@ -24,7 +24,7 @@ The following Azure AD Multi-Factor Authentication settings are available in the
 
 | Feature | Description |
 | ------- | ----------- |
-| [Account lockout](#account-lockout) | Temporarily lock accounts from using Azure AD Multi-Factor Authentication if there are too many denied authentication attempts in a row. This feature applies only to users who enter a PIN to authenticate. (MFA Server) |
+| [Account lockout](#account-lockout) | Temporarily lock accounts from using Azure AD Multi-Factor Authentication if there are too many denied authentication attempts in a row. This feature applies only to users who enter a PIN to authenticate. (MFA Server only) |
 | [Block/unblock users](#block-and-unblock-users) | Block specific users from being able to receive Azure AD Multi-Factor Authentication requests. Any authentication attempts for blocked users are automatically denied. Users remain blocked for 90 days from the time that they're blocked or until they're manually unblocked. |
 | [Fraud alert](#fraud-alert) | Configure settings that allow users to report fraudulent verification requests. |
 | [Notifications](#notifications) | Enable notifications of events from MFA Server. |