Merge pull request #248282 from alexbuckgit/alexbuckgit/docutune-autopr-20230815-021356-4521322-ignore-build

[BULK] DocuTune - Update stale local links (part 11)

Author: v-ccolin

articles/active-directory/privileged-identity-management/pim-deployment-plan.md

@@ -93,11 +93,11 @@ In case the role expires, you can **extend** or **renew** these assignments.
 
 ## Plan the project
 
-When technology projects fail, it’s typically because of mismatched expectations on impact, outcomes, and responsibilities. To avoid these pitfalls, [ensure that you’re engaging the right stakeholders](../fundamentals/deployment-plans.md) and that stakeholder roles in the project are well understood.
+When technology projects fail, it’s typically because of mismatched expectations on impact, outcomes, and responsibilities. To avoid these pitfalls, [ensure that you’re engaging the right stakeholders](../architecture/deployment-plans.md) and that stakeholder roles in the project are well understood.
 
 ### Plan a pilot
 
-At each stage of your deployment ensure that you are evaluating that the results are as expected. See [best practices for a pilot](../fundamentals/deployment-plans.md#best-practices-for-a-pilot).
+At each stage of your deployment ensure that you are evaluating that the results are as expected. See [best practices for a pilot](../architecture/deployment-plans.md#best-practices-for-a-pilot).
 
 * Start with a small set of users (pilot group) and verify that the PIM behaves as expected.
 
@@ -148,7 +148,7 @@ Follow these tasks to prepare PIM to manage Azure AD roles.
 
 List who has privileged roles in your organization. Review the users assigned, identify administrators who no longer need the role, and remove them from their assignments. 
 
-You can use [Azure AD roles access reviews](./pim-create-azure-ad-roles-and-resource-roles-review.md) to automate the discovery, review, and approval or removal of assignments.
+You can use [Azure AD roles access reviews](./pim-create-roles-and-resource-roles-review.md) to automate the discovery, review, and approval or removal of assignments.
 
 ### Determine roles to be managed by PIM
 
@@ -210,7 +210,7 @@ Minimize Owner and User Access Administrator assignments attached to each subscr
 
 As a Global Administrator you can [elevate access to manage all Azure subscriptions](../../role-based-access-control/elevate-access-global-admin.md). You can then find each subscription owner and work with them to remove unnecessary assignments within their subscriptions.
 
-Use [access reviews for Azure resources](./pim-create-azure-ad-roles-and-resource-roles-review.md) to audit and remove unnecessary role assignments. 
+Use [access reviews for Azure resources](./pim-create-roles-and-resource-roles-review.md) to audit and remove unnecessary role assignments. 
 
 ### Determine roles to be managed by PIM
 
@@ -254,7 +254,7 @@ When these important events occur in Azure resource roles, PIM sends [email noti
 
 ### Approve or deny PIM activation requests
 
-[Approve or deny activation requests for Azure AD role](azure-ad-pim-approval-workflow.md)- A delegated approver receives an email notification when a request is pending for approval.
+[Approve or deny activation requests for Azure AD role](./pim-approval-workflow.md)- A delegated approver receives an email notification when a request is pending for approval.
 
 ### View audit history for Azure Resource roles
 
@@ -313,5 +313,4 @@ Configure PIM for Groups members and owners to require approval for activation a
 
 * If there is PIM-related issues, see [Troubleshooting a problem with PIM](pim-troubleshoot.md).
 
-* [Deploy other identity features](../fundamentals/deployment-plans.md)
-
+* [Deploy other identity features](../architecture/deployment-plans.md)

articles/active-directory/privileged-identity-management/pim-email-notifications.md

@@ -133,4 +133,4 @@ Privileged Identity Management sends emails to end users when the following even
 ## Next steps
 
 - [Configure Azure AD role settings in Privileged Identity Management](pim-how-to-change-default-settings.md)
-- [Approve or deny requests for Azure AD roles in Privileged Identity Management](azure-ad-pim-approval-workflow.md)
+- [Approve or deny requests for Azure AD roles in Privileged Identity Management](./pim-approval-workflow.md)

articles/active-directory/privileged-identity-management/pim-how-to-change-default-settings.md

@@ -115,7 +115,7 @@ You can require users to enter a support ticket number when they activate the el
 
 You can require approval for activation of an eligible assignment. The approver doesn't have to have any roles. When you use this option, you must select at least one approver. We recommend that you select at least two approvers. There are no default approvers.
 
-To learn more about approvals, see [Approve or deny requests for Azure AD roles in Privileged Identity Management](azure-ad-pim-approval-workflow.md).
+To learn more about approvals, see [Approve or deny requests for Azure AD roles in Privileged Identity Management](./pim-approval-workflow.md).
 
 ### Assignment duration
 

articles/active-directory/privileged-identity-management/pim-how-to-configure-security-alerts.md

@@ -45,7 +45,7 @@ Severity: **Low**
 | --- | --- |
 | **Why do I get this alert?** | Users that have been assigned privileged roles they don't need increases the chance of an attack. It's also easier for attackers to remain unnoticed in accounts that aren't actively being used. |
 | **How to fix?** | Review the users in the list and remove them from privileged roles that they don't need. |
-| **Prevention** | Assign privileged roles only to users who have a business justification. </br>Schedule regular [access reviews](./pim-create-azure-ad-roles-and-resource-roles-review.md) to verify that users still need their access. |
+| **Prevention** | Assign privileged roles only to users who have a business justification. </br>Schedule regular [access reviews](./pim-create-roles-and-resource-roles-review.md) to verify that users still need their access. |
 | **In-portal mitigation action** | Removes the account from their privileged role. |
 | **Trigger** | Triggered if a user goes over a specified number of days without activating a role. |
 | **Number of days** | This setting specifies the maximum number of days, from 0 to 100, that a user can go without activating a role.|
@@ -68,7 +68,7 @@ Severity: **Low**
 | | Description |
 | --- | --- |
 | **Why do I get this alert?** | The current Azure AD organization doesn't have Microsoft Entra Premium P2 or Microsoft Entra ID Governance. |
-| **How to fix?** | Review information about [Azure AD editions](../fundamentals/active-directory-whatis.md). Upgrade to Microsoft Entra Premium P2 or Microsoft Entra ID Governance. |
+| **How to fix?** | Review information about [Azure AD editions](../fundamentals/whatis.md). Upgrade to Microsoft Entra Premium P2 or Microsoft Entra ID Governance. |
 
 ### Potential stale accounts in a privileged role
 
@@ -79,7 +79,7 @@ Severity: **Medium**
 | --- | --- |
 | **Why do I get this alert?** | This alert is no longer triggered based on the last password change date of for an account. This alert is for accounts in a privileged role that haven't signed in during the past *n* days, where *n* is a number of days that is configurable between 1-365 days. These accounts might be service or shared accounts that aren't being maintained and are vulnerable to attackers. |
 | **How to fix?** | Review the accounts in the list. If they no longer need access, remove them from their privileged roles. |
-| **Prevention** | Ensure that accounts that are shared are rotating strong passwords when there's a change in the users that know the password. </br>Regularly review accounts with privileged roles using [access reviews](./pim-create-azure-ad-roles-and-resource-roles-review.md) and remove role assignments that are no longer needed. |
+| **Prevention** | Ensure that accounts that are shared are rotating strong passwords when there's a change in the users that know the password. </br>Regularly review accounts with privileged roles using [access reviews](./pim-create-roles-and-resource-roles-review.md) and remove role assignments that are no longer needed. |
 | **In-portal mitigation action** | Removes the account from their privileged role. |
 | **Best practices** | Shared, service, and emergency access accounts that authenticate using a password and are assigned to highly privileged administrative roles such as Global administrator or Security administrator should have their passwords rotated for the following cases:<ul><li>After a security incident involving misuse or compromise of administrative access rights</li><li>After any user's privileges are changed so that they're no longer an administrator (for example, after an employee who was an administrator leaves IT or leaves the organization)</li><li>At regular intervals (for example, quarterly or yearly), even if there was no known breach or change to IT staffing</li></ul>Since multiple people have access to these accounts' credentials, the credentials should be rotated to ensure that people that have left their roles can no longer access the accounts. [Learn more about securing accounts](../roles/security-planning.md) |
 

articles/active-directory/privileged-identity-management/pim-how-to-renew-extend.md

@@ -194,5 +194,5 @@ They can also renew expired role assignments from within the **Expired** roles t
 
 ## Next steps
 
-- [Approve or deny requests for Azure AD roles in Privileged Identity Management](azure-ad-pim-approval-workflow.md)
+- [Approve or deny requests for Azure AD roles in Privileged Identity Management](./pim-approval-workflow.md)
 - [Configure Azure AD role settings in Privileged Identity Management](pim-how-to-change-default-settings.md)

articles/active-directory/privileged-identity-management/pim-perform-roles-and-resource-roles-review.md

@@ -23,7 +23,7 @@ Privileged Identity Management (PIM) simplifies how enterprises manage privilege
 
 If you are assigned to an administrative role, your organization's privileged role administrator may ask you to regularly confirm that you still need that role for your job. You might get an email that includes a link, or you can go straight to the [Azure portal](https://portal.azure.com) and begin.
 
-If you're a privileged role administrator or global administrator interested in access reviews, get more details at [How to start an access review](pim-create-azure-ad-roles-and-resource-roles-review.md).
+If you're a privileged role administrator or global administrator interested in access reviews, get more details at [How to start an access review](./pim-create-roles-and-resource-roles-review.md).
 
 ## Approve or deny access
 
@@ -50,5 +50,5 @@ Follow these steps to find and complete the access review:
 
 ## Next steps
 
-- [Create an access review of Azure resource and Azure AD roles in PIM](pim-create-azure-ad-roles-and-resource-roles-review.md)
-- [Complete an access review of Azure resource and Azure AD roles in PIM](pim-complete-azure-ad-roles-and-resource-roles-review.md)
+- [Create an access review of Azure resource and Azure AD roles in PIM](./pim-create-roles-and-resource-roles-review.md)
+- [Complete an access review of Azure resource and Azure AD roles in PIM](./pim-complete-roles-and-resource-roles-review.md)

articles/active-directory/privileged-identity-management/pim-resource-roles-approval-workflow.md

@@ -76,4 +76,4 @@ Here's some information about workflow notifications:
 ## Next steps
 
 - [Email notifications in Privileged Identity Management](pim-email-notifications.md)
-- [Approve or deny requests for Azure AD roles in Privileged Identity Management](azure-ad-pim-approval-workflow.md)
+- [Approve or deny requests for Azure AD roles in Privileged Identity Management](./pim-approval-workflow.md)

articles/active-directory/privileged-identity-management/pim-resource-roles-configure-role-settings.md

@@ -109,7 +109,7 @@ You can require users to enter a support ticket number when they activate the el
 
 You can require approval for activation of an eligible assignment. The approver doesn't have to have any roles. When you use this option, you must select at least one approver. We recommend that you select at least two approvers. There are no default approvers.
 
-To learn more about approvals, see [Approve or deny requests for Azure AD roles in Privileged Identity Management](azure-ad-pim-approval-workflow.md).
+To learn more about approvals, see [Approve or deny requests for Azure AD roles in Privileged Identity Management](./pim-approval-workflow.md).
 
 ### Assignment duration
 

articles/active-directory/privileged-identity-management/pim-resource-roles-overview-dashboards.md

@@ -38,4 +38,4 @@ Below the charts are listed the number of users and groups with new role assignm
 
 ## Next steps
 
-- [Start an access review for Azure resource roles in Privileged Identity Management](./pim-create-azure-ad-roles-and-resource-roles-review.md)
+- [Start an access review for Azure resource roles in Privileged Identity Management](./pim-create-roles-and-resource-roles-review.md)

articles/active-directory/privileged-identity-management/pim-troubleshoot.md

@@ -37,5 +37,5 @@ Assign the User Access Administrator role to the Privileged identity Management
 ## Next steps
 
 - [License requirements to use Privileged Identity Management](subscription-requirements.md)
-- [Securing privileged access for hybrid and cloud deployments in Azure AD](../roles/security-planning.md?toc=%2fazure%2factive-directory%2fprivileged-identity-management%2ftoc.json)
+- [Securing privileged access for hybrid and cloud deployments in Azure AD](../roles/security-planning.md?toc=/azure/active-directory/privileged-identity-management/toc.json)
 - [Deploy Privileged Identity Management](pim-deployment-plan.md)