Shirley's edits

Author: yelevin

articles/sentinel/whats-new.md

@@ -34,17 +34,17 @@ If you're looking for items older than six months, you'll find them in the [Arch
 
 ### Heads up: Account enrichment fields removed from Azure AD Identity Protection connector
 
-As of **September 30 2022**, alerts coming from the Azure Activity Directory Information Protection connector will no longer contain the following fields:
+As of **September 30 2022**, alerts coming from the Azure Activity Directory Information Protection connector no longer contain the following fields:
 
 - CompromisedEntity
 - ExtendedProperties["User Account"]
 - ExtendedProperties["User Name”]
 
-The corresponding ID field remains part of the table, and any built-in queries and other operations will execute the appropriate name lookups in other ways (using the IdentityInfo table), so you shouldn’t be affected by this change in nearly all circumstances.
+We are working to adapt Microsoft Sentinel's built-in queries and other operations affected by this change to look up these values in other ways (using the *IdentityInfo* table).
 
-If you've built any custom queries or rules directly referencing these fields, you'll need another way to get this information. Use the following two-step process to look up these values in the *IdentityInfo* table:
+In the meantime, or if you've built any custom queries or rules directly referencing these fields, you'll need another way to get this information. Use the following two-step process to look up these values in the *IdentityInfo* table:
 
-1. Enable the UEBA solution to sync the *IdentityInfo* table with your Azure AD logs. Follow the instructions in [this document](enable-entity-behavior-analytics.md).  
+1. If you haven't already, **enable the UEBA solution** to sync the *IdentityInfo* table with your Azure AD logs. Follow the instructions in [this document](enable-entity-behavior-analytics.md).  
 (If you don't intend to use UEBA in general, you can ignore the last instruction  about selecting data sources on which to enable entity behavior analytics.)
 1. Incorporate the query below in your existing custom queries or rules to look up this data by joining the *SecurityAlert* table with the *IdentityInfo* table.