Skip to content

Commit de303a1

Browse files
committed
cleanup
1 parent 17fa140 commit de303a1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ sections:
5151
- question: |
5252
Do I need to be a Global Administrator to see the activity logs in the Azure portal or to get data through the API?
5353
answer: |
54-
No, you can also access the reporting data through the portal or through the API if you're a **Security Reader** or **Security Administrator** for the tenant. **Global Administrators** will also have access to this data.
54+
No, the [least privilege role](../roles/delegate-by-task.md) to view audit and sign-in logs is **Reports Reader**. Other roles include **Security Reader** and **Security Administrator** for the tenant. You can also access the reporting data through the portal or through the API if you're a Global Administrator.
5555
5656
- question: |
5757
What is the data retention for activity logs (Audit, Sign-ins, and Provisioning) in the Azure portal?
@@ -115,7 +115,7 @@ sections:
115115
- question: |
116116
I am seeing User IDs in the username field of my sign-ins log. Why is this happening?
117117
answer: |
118-
With the passwordless authentication, User IDs will be used as the username. To confirm this scenario, look at the details of the sign-in event in question. The *authenticationDetail* field will say *passwordless*.
118+
With passwordless authentication, User IDs appear as the username. To confirm this scenario, look at the details of the sign-in event in question. The *authenticationDetail* field will say *passwordless*.
119119
120120
- name: Conditional Access
121121
questions:

0 commit comments

Comments
 (0)