Skip to content

Commit 4df1403

Browse files
committed
image-cleanup
1 parent 257c2a8 commit 4df1403

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

articles/active-directory/reports-monitoring/howto-use-recommendations.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,8 @@ Some recommendations may require a P2 or other license. Refer to the [Recommenda
4141

4242
## How to read a recommendation
4343

44+
To view the details of a recommendation, sign in to Azure using a least-privileged role for read-only access.
45+
4446
Each recommendation provides the same set of details that explain what the recommendation is, why it's important, and how to fix it.
4547

4648
The **Status** of a recommendation can be updated manually or automatically by the system. If all resources are addressed according to the action plan, the status automatically changes to *Completed* the next time the recommendations service runs. The recommendation service runs every 24-48 hours, depending on the recommendation.
@@ -53,7 +55,7 @@ The **Priority** of a recommendation could be low, medium, or high. These values
5355

5456
The **Impacted resources** for a recommendation could be things like applications or users. This detail gives you an idea of what type of resources you need to address. The impacted resource could also be at the tenant level, so you may need to make a global change.
5557

56-
![Screenshot of a recommendation's status, priority, and impacted resource type.](./media/overview-recommendations/recommendation-status-risk.png)
58+
![Screenshot of a recommendation's status, priority, and impacted resource type.](./media/howto-use-recommendations/recommendation-status-risk.png)
5759

5860
The **Status description** tells you the date the recommendation status changed and if it was changed by the system or a user.
5961

0 commit comments

Comments
 (0)