Merge pull request #246404 from MicrosoftGuyJFlo/NameRemoval

[Microsoft Entra ID] Devices - update filenames

Author: v-regandowner

.openpublishing.redirection.active-directory.json

@@ -1320,6 +1320,41 @@
       "redirect_url": "/azure/active-directory/privileged-identity-management/pim-configure",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/active-directory/devices/howto-hybrid-join-downlevel.md",
+      "redirect_url": "/azure/active-directory/devices/how-to-hybrid-join-downlevel",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/active-directory/devices/howto-hybrid-join-verify.md",
+      "redirect_url": "/azure/active-directory/devices/how-to-hybrid-join-verify",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/active-directory/devices/howto-hybrid-azure-ad-join.md",
+      "redirect_url": "/azure/active-directory/devices/how-to-hybrid-join",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/active-directory/devices/concept-azure-ad-join-hybrid.md",
+      "redirect_url": "/azure/active-directory/devices/concept-hybrid-join",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/active-directory/devices/azuread-joined-devices-frx.md",
+      "redirect_url": "/azure/active-directory/devices/device-join-out-of-box",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/active-directory/devices/azuread-join-sso.md",
+      "redirect_url": "/azure/active-directory/devices/device-sso-to-on-premises-resources",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/active-directory/devices/azureadjoin-plan.md",
+      "redirect_url": "/azure/active-directory/devices/device-join-plan",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/articles/active-directory/devices/concept-azure-managed-workstation.md",
       "redirect_url": "/security/compass/concept-azure-managed-workstation",

articles/active-directory/architecture/ops-guide-auth.md

@@ -117,7 +117,7 @@ Like a user in your organization, a device is a core identity you want to protec
 
 - Avoiding friction, for example, with MFA, when the device is trusted
 - Blocking access from untrusted devices
-- For Windows 10 devices, provide [single sign-on to on-premises resources seamlessly](../devices/azuread-join-sso.md).
+- For Windows 10 devices, provide [single sign-on to on-premises resources seamlessly](../devices/device-sso-to-on-premises-resources.md).
 
 You can carry out this goal by bringing device identities and managing them in Azure AD by using one of the following methods:
 

articles/active-directory/architecture/protect-m365-from-on-premises-attacks.md

@@ -152,7 +152,7 @@ Owners of groups that are used for access should be considered privileged identi
 
 Use Azure AD capabilities to securely manage devices.
 
-Deploy Azure AD joined Windows 10 workstations with mobile device management policies. Enable Windows Autopilot for a fully automated provisioning experience. See [Plan your Azure AD join implementation](../devices/azureadjoin-plan.md) and [Windows Autopilot](/mem/autopilot/windows-autopilot).
+Deploy Azure AD joined Windows 10 workstations with mobile device management policies. Enable Windows Autopilot for a fully automated provisioning experience. See [Plan your Azure AD join implementation](../devices/device-join-plan.md) and [Windows Autopilot](/mem/autopilot/windows-autopilot).
 
 - **Use Windows 10 workstations**.
   - Deprecate machines that run Windows 8.1 and earlier.

articles/active-directory/architecture/resilience-with-device-states.md

@@ -28,7 +28,7 @@ When a PRT requests access to an application, its device, session, and MFA claim
 
 ## How do I implement device states?
 
-* Enable [hybrid Azure AD Joined](../devices/hybrid-azuread-join-plan.md) and [Azure AD Join](../devices/azureadjoin-plan.md) for company-owned Windows devices and require they be joined, if possible. If not possible, require they be registered. If there are older versions of Windows in your organization, upgrade those devices to use Windows 10.
+* Enable [hybrid Azure AD Joined](../devices/hybrid-azuread-join-plan.md) and [Azure AD Join](../devices/device-join-plan.md) for company-owned Windows devices and require they be joined, if possible. If not possible, require they be registered. If there are older versions of Windows in your organization, upgrade those devices to use Windows 10.
 * Standardize user browser access to use either [Microsoft Edge](/deployedge/microsoft-edge-security-identity) or Google Chrome with [supported](https://chrome.google.com/webstore/detail/windows-10-accounts/ppnbnpeolgkicgegkbkbjmhlideopiji) [extensions](https://chrome.google.com/webstore/detail/office/ndjpnladcallmjemlbaebfadecfhkepb) that enable seamless SSO to web applications using the PRT.
 * For personal or company-owned iOS and Android devices, deploy the [Microsoft Authenticator App](https://support.microsoft.com/account-billing/how-to-use-the-microsoft-authenticator-app-9783c865-0308-42fb-a519-8cf666fe0acc). In addition to MFA and password-less sign-in capabilities, the Microsoft Authenticator app enables single sign-on across native applications through [brokered authentication](../develop/msal-android-single-sign-on.md) with fewer authentication prompts for end users.
 * For personal or company-owned iOS and Android devices, use [mobile application management](/mem/intune/apps/app-management) to securely access company resources with fewer authentication requests. 

articles/active-directory/architecture/secure-fundamentals.md

@@ -89,7 +89,7 @@ Some legacy scenarios required a human identity to be used in *non-human* scenar
 
 * **Device objects** represent devices that are associated with an Azure AD tenant. Device objects contain attributes that have the required information about the device. This includes the operating system, associated user, compliance state, and the nature of the association with the Azure AD tenant. This association can take multiple forms depending on the nature of the interaction and trust level of the device.
 
-  * **Hybrid Domain Joined**. Devices that are owned by the organization and [joined](../devices/concept-azure-ad-join-hybrid.md) to both the on-premises Active Directory and Azure AD. Typically a device purchased and managed by an organization and managed by System Center Configuration Manager.
+  * **Hybrid Domain Joined**. Devices that are owned by the organization and [joined](../devices/concept-hybrid-join.md) to both the on-premises Active Directory and Azure AD. Typically a device purchased and managed by an organization and managed by System Center Configuration Manager.
 
   * **Azure AD Domain Joined**. Devices that are owned by the organization and joined to the organization's Azure AD tenant. Typically a device purchased and managed by an organization that is joined to Azure AD and managed by a service such as [Microsoft Intune](https://www.microsoft.com/microsoft-365/enterprise-mobility-security/microsoft-intune).
 

articles/active-directory/architecture/security-operations-devices.md

@@ -24,7 +24,7 @@ Devices aren't commonly targeted in identity-based attacks, but *can* be used to
 
 * [Azure AD joined](../devices/concept-azure-ad-join.md)
 
-* [Hybrid Azure AD joined](../devices/concept-azure-ad-join-hybrid.md)
+* [Hybrid Azure AD joined](../devices/concept-hybrid-join.md)
 
 Registered and joined devices are issued a [Primary Refresh Token (PRT),](../devices/concept-primary-refresh-token.md) which can be used as a primary authentication artifact, and in some cases as a multifactor authentication artifact. Attackers may try to register their own devices, use PRTs on legitimate devices to access business data, steal PRT-based tokens from legitimate user devices, or find misconfigurations in device-based controls in Azure Active Directory. With Hybrid Azure AD joined devices, the join process is initiated and controlled by administrators, reducing the available attack methods.
 

articles/active-directory/authentication/concepts-azure-multi-factor-authentication-prompts-session-lifetime.md

@@ -131,7 +131,7 @@ The following table summarizes the recommendations based on licenses:
 
 |              | Azure AD Free and Microsoft 365 apps | Azure AD Premium |
 |------------------------------|-----------------------------------|------------------|
-| **SSO**                      | [Azure AD join](../devices/concept-azure-ad-join.md) or [Hybrid Azure AD join](../devices/concept-azure-ad-join-hybrid.md), or [Seamless SSO](../hybrid/how-to-connect-sso.md) for unmanaged devices. | Azure AD join<br />Hybrid Azure AD join |
+| **SSO**                      | [Azure AD join](../devices/concept-azure-ad-join.md) or [Hybrid Azure AD join](../devices/concept-hybrid-join.md), or [Seamless SSO](../hybrid/how-to-connect-sso.md) for unmanaged devices. | Azure AD join<br />Hybrid Azure AD join |
 | **Reauthentication settings** | Remain signed-in                  | Use Conditional Access policies for sign-in frequency and persistent browser session |
 
 ## Next steps

articles/active-directory/authentication/howto-authentication-passwordless-security-key-windows.md

@@ -28,7 +28,7 @@ This document focuses on enabling FIDO2 security key based passwordless authenti
 | Compatible [FIDO2 security keys](concept-authentication-passwordless.md#fido2-security-keys) | X | X |
 | WebAuthN requires Windows 10 version 1903 or higher | X | X |
 | [Azure AD joined devices](../devices/concept-azure-ad-join.md) require Windows 10 version 1909 or higher | X |   |
-| [Hybrid Azure AD joined devices](../devices/concept-azure-ad-join-hybrid.md) require Windows 10 version 2004 or higher |   | X |
+| [Hybrid Azure AD joined devices](../devices/concept-hybrid-join.md) require Windows 10 version 2004 or higher |   | X |
 | Fully patched Windows Server 2016/2019 Domain Controllers. |   | X |
 | [Azure AD Hybrid Authentication Management module](https://www.powershellgallery.com/packages/AzureADHybridAuthenticationManagement/2.1.1.0) |   | X |
 | [Microsoft Intune](/intune/fundamentals/what-is-intune) (Optional) | X | X |

articles/active-directory/authentication/howto-authentication-use-email-signin.md

@@ -60,7 +60,7 @@ In the current preview state, the following limitations apply to email as an alt
     * When a user is signed-in with a non-UPN email, they cannot change their password. Azure AD self-service password reset (SSPR) should work as expected. During SSPR, the user may see their UPN if they verify their identity using a non-UPN email.
 
 * **Unsupported scenarios** - The following scenarios are not supported. Sign-in with non-UPN email for:
-    * [Hybrid Azure AD joined devices](../devices/concept-azure-ad-join-hybrid.md)
+    * [Hybrid Azure AD joined devices](../devices/concept-hybrid-join.md)
     * [Azure AD joined devices](../devices/concept-azure-ad-join.md)
     * [Azure AD registered devices](../devices/concept-azure-ad-register.md)
     * [Resource Owner Password Credentials (ROPC)](../develop/v2-oauth-ropc.md)

articles/active-directory/conditional-access/concept-conditional-access-grant.md

@@ -33,7 +33,7 @@ Administrators can choose to enforce one or more controls when granting access.
 - [Require multifactor authentication (Azure AD Multifactor Authentication)](../authentication/concept-mfa-howitworks.md)
 - [Require authentication strength](#require-authentication-strength)
 - [Require device to be marked as compliant (Microsoft Intune)](/intune/protect/device-compliance-get-started)
-- [Require hybrid Azure AD joined device](../devices/concept-azure-ad-join-hybrid.md)
+- [Require hybrid Azure AD joined device](../devices/concept-hybrid-join.md)
 - [Require approved client app](app-based-conditional-access.md)
 - [Require app protection policy](app-protection-based-conditional-access.md)
 - [Require password change](#require-password-change)