Skip to content

Commit 0ac6ffa

Browse files
committed
updates
1 parent d5a5b27 commit 0ac6ffa

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/active-directory/fundamentals/whats-new.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -42,13 +42,13 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
4242
**Service category:** Provisioning
4343
**Product capability:** AAD Connect Cloud Sync
4444

45-
Microsoft will stop support for Azure AD provisioning agent with versions 1.1.818.0 and below starting Feb 1,2023. If you are using Azure AD cloud sync, please make sure you have the latest version of the agent. You can info about the agent release history [here](../app-provisioning/provisioning-agent-release-version-history.md). You can download the latest version [here](https://download.msappproxy.net/Subscription/d3c8b69d-6bf7-42be-a529-3fe9c2e70c90/Connector/provisioningAgentInstaller)
45+
Microsoft will stop support for Azure AD provisioning agent with versions 1.1.818.0 and below starting Feb 1,2023. If you're using Azure AD cloud sync, please make sure you have the latest version of the agent. You can info about the agent release history [here](../app-provisioning/provisioning-agent-release-version-history.md). You can download the latest version [here](https://download.msappproxy.net/Subscription/d3c8b69d-6bf7-42be-a529-3fe9c2e70c90/Connector/provisioningAgentInstaller)
4646

47-
You can find out which version of the agent you are using as follows:
47+
You can find out which version of the agent you're using as follows:
4848

49-
1. Going to the domain server which you have the agent installed
49+
1. Going to the domain server that you have the agent installed
5050
1. Right-click on the Microsoft Azure AD Connect Provisioning Agent app
51-
1. Click on “Details” tab and you can find the version number there
51+
1. Select on “Details” tab and you can find the version number there
5252

5353
> [!NOTE]
5454
> Azure Active Directory (AD) Connect follows the [Modern Lifecycle Policy](/lifecycle/policies/modern). Changes for products and services under the Modern Lifecycle Policy may be more frequent and require customers to be alert for forthcoming modifications to their product or service.
@@ -192,7 +192,7 @@ For more information, see: [What are Lifecycle Workflows? (Public Preview)](../g
192192
**Service category:** Access Reviews
193193
**Product capability:** Identity Governance
194194

195-
This feature provides Machine Learning based recommendations to the reviewers of Azure AD Access Reviews to make the review experience easier and more accurate. The recommendation detects user affiliation with other users within the group, and leverages the scoring mechanism we built by computing the user’s average distance with other users in the group. For more information, see: [Review recommendations for Access reviews](../governance/review-recommendations-access-reviews.md).
195+
This feature provides Machine Learning based recommendations to the reviewers of Azure AD Access Reviews to make the review experience easier and more accurate. The recommendation detects user affiliation with other users within the group, and applies the scoring mechanism we built by computing the user’s average distance with other users in the group. For more information, see: [Review recommendations for Access reviews](../governance/review-recommendations-access-reviews.md).
196196

197197
---
198198

@@ -218,7 +218,7 @@ When configuring writeback of attributes from Azure AD to SAP SuccessFactors Emp
218218

219219
To prevent accidental notification approvals, admins can now require users to enter the number displayed on the sign-in screen when approving an MFA notification in the Microsoft Authenticator app. We've also refreshed the Azure portal admin UX and Microsoft Graph APIs to make it easier for customers to manage Authenticator app feature roll-outs. As part of this update we have also added the highly requested ability for admins to exclude user groups from each feature.
220220

221-
The number matching feature greatly up-levels the security posture of the Microsoft Authenticator app and protects organizations from MFA fatigue attacks. We highly encourage our customers to adopt this feature leveraging the rollout controls we have built. Number Matching will begin to be enabled for all users of the Microsoft Authenticator app starting 27th of February 2023.
221+
The number matching feature greatly up-levels the security posture of the Microsoft Authenticator app and protects organizations from MFA fatigue attacks. We highly encourage our customers to adopt this feature applying the rollout controls we have built. Number Matching will begin to be enabled for all users of the Microsoft Authenticator app starting 27th of February 2023.
222222

223223

224224
For more information, see: [How to use number matching in multifactor authentication (MFA) notifications - Authentication methods policy](../authentication/how-to-mfa-number-match.md).

0 commit comments

Comments
 (0)