Merge pull request #228225 from shlipsey3/reports-faq-updates-022223

reports-faq-updates-022223

Author: prmerger-automator[bot]

articles/active-directory/reports-monitoring/reports-faq.yml

@@ -9,7 +9,7 @@ metadata:
   ms.workload: identity
   ms.topic: faq
   ms.subservice: report-monitor
-  ms.date: 02/02/2023
+  ms.date: 02/22/2023
   ms.author: sarahlipsey
   ms.reviewer: besiler
   ms.collection: M365-identity-device-management
@@ -80,21 +80,11 @@ sections:
         answer: |
           Azure AD may redact part of an IP address in the sign-in logs to protect user privacy when a user may not belong to the tenant viewing the logs. This action happens in two cases: first, during cross tenant sign ins, such as when a CSP technician signs into a tenant that CSP manages. Second, when our service wasn't able to determine the user's identity with sufficient confidence to be sure the user belongs to the tenant viewing the logs.
 
-      - question: |
-          I selected the **Load More** button in the Azure portal sign-in logs, but no more results appeared. Why is that happening?
-        answer: |
-          This is a known issue with a fix on the way from Azure AD engineering, where if during a 24-hour period in the results of your query has no sign-ins, no sign-ins will appear when you select **Load More**. If your tenant is impacted by this issue, select the **Load More** button multiple times. You can also work around this issue by increasing the scope of your query so that each 24-hour period in your response has sign-ins.
-
       - question: |
           I see "PII Removed" in the Device Details of a user in my sign-in logs. Why is that happening?
         answer: |
           Azure AD redacts Personally Identifiable Information (PII) generated by devices that don't belong to your tenant to ensure customer data doesn't spread beyond tenant boundaries without user and data owner consent.
 
-      - question: |
-          I clicked the Load More button in the Azure portal Sign-in logs, but no more results appeared. Why is that happening?
-        answer: |
-          This is a known issue with a fix on the way from Azure AD engineering where if a 24h period in the results of your query has no sign-ins, no sign-ins will appear when you click Load More. If your tenant is impacted by this issue, you can load more results by clicking the Load More button multiple times. You can also work around this issue by increasing the scope of your query so that each 24h period in your response has sign-ins.
-
       - question: |
           I see duplicate sign-in entries / multiple sign-in events per requestID. Why is that happening?
         answer: |