Merge pull request #248276 from alexbuckgit/alexbuckgit/docutune-autopr-20230815-012944-0626238-ignore-build

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

Author: ttorble

articles/active-directory/devices/overview.md

@@ -27,7 +27,7 @@ There are three ways to get a device identity:
 - Azure AD join
 - Hybrid Azure AD join
 
-Device identities are a prerequisite for scenarios like [device-based Conditional Access policies](../conditional-access/require-managed-devices.md) and [Mobile Device Management with the Microsoft Intune family of products](/mem/endpoint-manager-overview).
+Device identities are a prerequisite for scenarios like [device-based Conditional Access policies](../conditional-access/concept-conditional-access-grant.md) and [Mobile Device Management with the Microsoft Intune family of products](/mem/endpoint-manager-overview).
 
 ## Modern device scenario
 
@@ -58,4 +58,4 @@ Getting devices in to Azure AD can be done in a self-service manner or a control
 - Learn more about [Azure AD joined devices](concept-directory-join.md)
 - Learn more about [hybrid Azure AD joined devices](concept-hybrid-join.md)
 - To get an overview of how to manage device identities in the Azure portal, see [Managing device identities using the Azure portal](manage-device-identities.md).
-- To learn more about device-based Conditional Access, see [Configure Azure Active Directory device-based Conditional Access policies](../conditional-access/require-managed-devices.md).
+- To learn more about device-based Conditional Access, see [Configure Azure Active Directory device-based Conditional Access policies](../conditional-access/concept-conditional-access-grant.md).

articles/active-directory/devices/plan-device-deployment.md

@@ -45,7 +45,7 @@ The key benefits of giving your devices an Azure AD identity:
 
    > [!VIDEO https://www.youtube-nocookie.com/embed/NcONUf-jeS4]
 
-* Improve user experience – Provide your users with easy access to your organization’s cloud-based resources from both personal and corporate devices. Administrators can enable [Enterprise State Roaming](enterprise-state-roaming-overview.md) for a unified experience across all Windows devices.
+* Improve user experience – Provide your users with easy access to your organization’s cloud-based resources from both personal and corporate devices. Administrators can enable [Enterprise State Roaming](./enterprise-state-roaming-enable.md) for a unified experience across all Windows devices.
 
 * Simplify deployment and management – Simplify the process of bringing devices to Azure AD with [Windows Autopilot](/windows/deployment/windows-autopilot/windows-10-autopilot), [bulk provisioning](/mem/intune/enrollment/windows-bulk-enroll), or [self-service: Out of Box Experience (OOBE)](https://support.microsoft.com/account-billing/join-your-work-device-to-your-work-or-school-network-ef4d6adb-5095-4e51-829e-5457430f3973). Manage devices with Mobile Device Management (MDM) tools like [Microsoft Intune](/mem/intune/fundamentals/what-is-intune), and their identities in the [Azure portal](https://portal.azure.com/).
 
@@ -55,7 +55,7 @@ Consider your organizational needs while you determine the strategy for this dep
 
 ### Engage the right stakeholders
 
-When technology projects fail, they typically do 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, they typically do 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. 
 
 For this plan, add the following stakeholders to your list:
 
@@ -72,7 +72,7 @@ Communication is critical to the success of any new service. Proactively communi
 
 ### Plan a pilot
 
-We recommend that the initial configuration of your integration method is in a test environment, or with a small group of test devices. See [Best practices for a pilot](../fundamentals/deployment-plans.md).
+We recommend that the initial configuration of your integration method is in a test environment, or with a small group of test devices. See [Best practices for a pilot](../architecture/deployment-plans.md).
 
 You may want to do a [targeted deployment of hybrid Azure AD join](hybrid-join-control.md) before enabling it across the entire organization.
 
@@ -124,7 +124,7 @@ Conditional Access <br>(Require hybrid Azure AD joined devices) | | | ![Checkmar
 
 Registered devices are often managed with [Microsoft Intune](/mem/intune/enrollment/device-enrollment). Devices are enrolled in Intune in several ways, depending on the operating system. 
 
-Azure AD registered devices provide support for Bring Your Own Devices (BYOD) and corporate owned devices to SSO to cloud resources. Access to resources is based on the Azure AD [Conditional Access policies](../conditional-access/require-managed-devices.md) applied to the device and the user.
+Azure AD registered devices provide support for Bring Your Own Devices (BYOD) and corporate owned devices to SSO to cloud resources. Access to resources is based on the Azure AD [Conditional Access policies](../conditional-access/concept-conditional-access-grant.md) applied to the device and the user.
 
 ### Registering devices
 

articles/active-directory/devices/troubleshoot-hybrid-join-windows-current.md

@@ -29,7 +29,7 @@ To troubleshoot other Windows clients, see [Troubleshoot hybrid Azure AD-joined
 This article assumes that you have [configured hybrid Azure AD-joined devices](hybrid-join-plan.md) to support the following scenarios:
 
 - Device-based Conditional Access
-- [Enterprise state roaming](./enterprise-state-roaming-overview.md)
+- [Enterprise state roaming](./enterprise-state-roaming-enable.md)
 - [Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-identity-verification)
 
 
@@ -149,7 +149,7 @@ Possible reasons for failure:
 
 -  The service connection point object is misconfigured or can't be read from the domain controller.
    - A valid service connection point object is required in the AD forest, to which the device belongs, that points to a verified domain name in Azure AD.
-   - For more information, see the "Configure a service connection point" section of [Tutorial: Configure hybrid Azure Active Directory join for federated domains](hybrid-azuread-join-federated-domains.md#configure-hybrid-azure-ad-join).
+   - For more information, see the "Configure a service connection point" section of [Tutorial: Configure hybrid Azure Active Directory join for federated domains](./how-to-hybrid-join.md#configure-hybrid-azure-ad-join).
 - Failure to connect to and fetch the discovery metadata from the discovery endpoint.
    - The device should be able to access `https://enterpriseregistration.windows.net`, in the system context, to discover the registration and authorization endpoints.
    - If the on-premises environment requires an outbound proxy, the IT admin must ensure that the computer account of the device can discover and silently authenticate to the outbound proxy.
@@ -163,7 +163,7 @@ Possible reasons for failure:
 | --- | --- | --- |
 | **DSREG_AUTOJOIN_ADCONFIG_READ_FAILED** (0x801c001d/-2145648611) | Unable to read the service connection point (SCP) object and get the Azure AD tenant information. | Refer to the [Configure a service connection point](hybrid-join-manual.md#configure-a-service-connection-point) section. |
 | **DSREG_AUTOJOIN_DISC_FAILED** (0x801c0021/-2145648607) | Generic discovery failure. Failed to get the discovery metadata from the data replication service (DRS). | To investigate further, find the sub-error in the next sections. |
-| **DSREG_AUTOJOIN_DISC_WAIT_TIMEOUT**  (0x801c001f/-2145648609) | Operation timed out while performing discovery. | Ensure that `https://enterpriseregistration.windows.net` is accessible in the system context. For more information, see the [Network connectivity requirements](hybrid-azuread-join-managed-domains.md#prerequisites) section. |
+| **DSREG_AUTOJOIN_DISC_WAIT_TIMEOUT**  (0x801c001f/-2145648609) | Operation timed out while performing discovery. | Ensure that `https://enterpriseregistration.windows.net` is accessible in the system context. For more information, see the [Network connectivity requirements](./how-to-hybrid-join.md#prerequisites) section. |
 | **DSREG_AUTOJOIN_USERREALM_DISCOVERY_FAILED** (0x801c003d/-2145648579) | Generic realm discovery failure. Failed to determine domain type (managed/federated) from STS. | To investigate further, find the sub-error in the next sections. |
 | | |
 
@@ -206,8 +206,8 @@ Use Event Viewer logs to look for the phase and error code for the join failures
 
 | Error code | Reason | Resolution |
 | --- | --- | --- |
-| **WININET_E_CANNOT_CONNECT** (0x80072efd/-2147012867) | Connection with the server couldn't be established. | Ensure network connectivity to the required Microsoft resources. For more information, see [Network connectivity requirements](hybrid-azuread-join-managed-domains.md#prerequisites). |
-| **WININET_E_TIMEOUT** (0x80072ee2/-2147012894) | General network timeout. | Ensure network connectivity to the required Microsoft resources. For more information, see [Network connectivity requirements](hybrid-azuread-join-managed-domains.md#prerequisites). |
+| **WININET_E_CANNOT_CONNECT** (0x80072efd/-2147012867) | Connection with the server couldn't be established. | Ensure network connectivity to the required Microsoft resources. For more information, see [Network connectivity requirements](./how-to-hybrid-join.md#prerequisites). |
+| **WININET_E_TIMEOUT** (0x80072ee2/-2147012894) | General network timeout. | Ensure network connectivity to the required Microsoft resources. For more information, see [Network connectivity requirements](./how-to-hybrid-join.md#prerequisites). |
 | **WININET_E_DECODING_FAILED** (0x80072f8f/-2147012721) | Network stack was unable to decode the response from the server. | Ensure that the network proxy isn't interfering and modifying the server response. |
 | | |
 
@@ -261,7 +261,7 @@ Use Event Viewer logs to locate the error code, sub-error code, server error cod
 
 | Error code | Reason | Resolution |
 | --- | --- | --- |
-| **ERROR_ADAL_INTERNET_TIMEOUT** (0xcaa82ee2/-894947614) | General network timeout. | Ensure that `https://login.microsoftonline.com` is accessible in the system context. Ensure that the on-premises identity provider is accessible in the system context. For more information, see [Network connectivity requirements](hybrid-azuread-join-managed-domains.md#prerequisites). |
+| **ERROR_ADAL_INTERNET_TIMEOUT** (0xcaa82ee2/-894947614) | General network timeout. | Ensure that `https://login.microsoftonline.com` is accessible in the system context. Ensure that the on-premises identity provider is accessible in the system context. For more information, see [Network connectivity requirements](./how-to-hybrid-join.md#prerequisites). |
 | **ERROR_ADAL_INTERNET_CONNECTION_ABORTED** (0xcaa82efe/-894947586) | Connection with the authorization endpoint was aborted. | Retry the join after a while, or try joining from another stable network location. |
 | **ERROR_ADAL_INTERNET_SECURE_FAILURE** (0xcaa82f8f/-894947441) | The Transport Layer Security (TLS) certificate (previously known as the Secure Sockets Layer [SSL] certificate) sent by the server couldn't be validated. | Check the client time skew. Retry the join after a while, or try joining from another stable network location. |
 | **ERROR_ADAL_INTERNET_CANNOT_CONNECT** (0xcaa82efd/-894947587) | The attempt to connect to `https://login.microsoftonline.com` failed. | Check the network connection to `https://login.microsoftonline.com`. |

articles/active-directory/devices/troubleshoot-primary-refresh-token.md

@@ -467,4 +467,4 @@ The following procedure describes how to capture traces by using the [Time Trave
 [server-errors]: #common-server-error-codes-aadsts-prefix
 [view-event-ids]: #method-2-use-event-viewer-to-examine-azure-ad-analytic-and-operational-logs
 [alt-login-id]: /windows-server/identity/ad-fs/operations/configuring-alternate-login-id
-[hybrid-azure-ad-join-plan]: ./hybrid-azuread-join-plan.md
+[hybrid-azure-ad-join-plan]: ./hybrid-join-plan.md

articles/active-directory/enterprise-users/TOC.yml

@@ -9,9 +9,9 @@
 - name: Quickstarts
   items:
   - name: Add users to Azure AD
-    href: ../fundamentals/add-users-azure-active-directory.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+    href: ../fundamentals/add-users.md?context=/azure/active-directory/enterprise-users/context/ugr-context
   - name: Assign licenses to users    
-    href: ../fundamentals/license-users-groups.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+    href: ../fundamentals/license-users-groups.md?context=/azure/active-directory/enterprise-users/context/ugr-context
   - name: Set groups expiration    
     href: groups-quickstart-expiration.md
   - name: Set groups naming policy    
@@ -24,22 +24,22 @@
   expanded: true
   items:
   - name: Compare default user permissions    
-    href: ../fundamentals/users-default-permissions.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+    href: ../fundamentals/users-default-permissions.md?context=/azure/active-directory/enterprise-users/context/ugr-context
   - name: Group-based licensing basics    
-    href: ../fundamentals/active-directory-licensing-whatis-azure-portal.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+    href: ../fundamentals/licensing-whatis-azure-portal.md?context=/azure/active-directory/enterprise-users/context/ugr-context
   - name: Manage access with groups    
-    href: ../fundamentals/active-directory-manage-groups.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+    href: ../fundamentals/concept-learn-about-groups.md?context=/azure/active-directory/enterprise-users/context/ugr-context
 - name: How-to guides
   expanded: true
   items:
   - name: Users
     items: 
     - name: Create a user 
-      href: ../fundamentals/add-users-azure-active-directory.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/add-users.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Create users in bulk
       href: users-bulk-add.md    
     - name: Manage user profiles
-      href: ../fundamentals/active-directory-users-profile-azure-portal.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/how-to-manage-user-profile-info.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Add custom data using extensions - Microsoft Graph
       href: /graph/extensibility-overview?toc=/azure/active-directory/enterprise-users/toc.json&bc=/azure/active-directory/enterprise-users/breadcrumb/toc.json
     - name: Assign custom security attributes
@@ -49,33 +49,33 @@
     - name: Share user accounts
       href: users-sharing-accounts.md
     - name: Assign users to admin roles    
-      href: ../fundamentals/active-directory-users-assign-role-azure-portal.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/how-subscriptions-associated-directory.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: User management enhancements
       href: users-search-enhanced.md
     - name: Delete users in bulk
       href: users-bulk-delete.md
     - name: Restore a deleted user    
-      href: ../fundamentals/active-directory-users-restore.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/users-restore.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Restore users in bulk
       href: users-bulk-restore.md
     - name: Revoke a user's access
       href: users-revoke-access.md
     - name: Close an account in an unmanaged directory
       href: users-close-account.md
     - name: Add guest users  
-      href: ../external-identities/what-is-b2b.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../external-identities/what-is-b2b.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Restrict guest user access
       href: users-restrict-guest-permissions.md
     - name: Clean up unmanaged accounts
       href: clean-up-unmanaged-accounts.md 
     - name: Clean up stale guest accounts
       href: clean-up-stale-guest-accounts.md
     - name: Dynamic groups and guests   
-      href: ../external-identities/use-dynamic-groups.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../external-identities/use-dynamic-groups.md?context=/azure/active-directory/enterprise-users/context/ugr-context
   - name: Organization (tenant)
     items:
     - name: Azure AD tenant organizations    
-      href: ../fundamentals/active-directory-whatis.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/whatis.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Delete a tenant    
       href: directory-delete-howto.md
     - name: Multiple tenants    
@@ -89,13 +89,13 @@
     - name: Self-service sign-up    
       href: directory-self-service-signup.md
     - name: Azure AD Connect    
-      href: ../hybrid/whatis-hybrid-identity.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../hybrid/whatis-hybrid-identity.md?context=/azure/active-directory/enterprise-users/context/ugr-context
   - name: Groups
     items: 
     - name: Learn about groups and access rights  
-      href: ../fundamentals/concept-learn-about-groups.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/concept-learn-about-groups.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Manage access with groups
-      href: ../fundamentals/how-to-manage-groups.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context  
+      href: ../fundamentals/how-to-manage-groups.md?context=/azure/active-directory/enterprise-users/context/ugr-context  
     - name: Manage groups PowerShell for Graph (v2)   
       href: groups-settings-v2-cmdlets.md
     - name: Manage groups with PowerShell MSOnline    
@@ -141,7 +141,7 @@
   - name: Licenses
     items:
     - name: Assign licenses to users    
-      href: ../fundamentals/license-users-groups.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/license-users-groups.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Use Admin center to assign licenses to groups
       href: licensing-admin-center.md
     - name: Assign licenses to a group
@@ -163,7 +163,7 @@
   - name: Sign-in
     items:    
     - name: Customize company branding    
-      href: ../fundamentals/how-to-customize-branding.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/how-to-customize-branding.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Sign-in options
       href: signin-account-support.md
     - name: Home Realm Discovery
@@ -177,7 +177,7 @@
   - name: Troubleshoot
     items:
     - name: Get support for Azure AD    
-      href: ../fundamentals/how-to-get-support.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
+      href: ../fundamentals/how-to-get-support.md?context=/azure/active-directory/enterprise-users/context/ugr-context
     - name: Troubleshoot groups   
       href: groups-troubleshooting.md
     - name: Troubleshoot group licensing