[Microsoft Entra] Fixing Azure portal references

MicrosoftGuyJFlo · MicrosoftGuyJFlo · commit 6cd869629878 · 2023-09-25T12:12:46.000-04:00
diff --git a/articles/active-directory/architecture/4-secure-access-groups.md b/articles/active-directory/architecture/4-secure-access-groups.md
@@ -154,7 +154,7 @@ Learn more:
 
 * [Overview of Microsoft 365 Groups for administrators](/microsoft-365/admin/create-groups/office-365-groups?view=o365-worldwide&preserve-view=true)
 * [Create a group in the Microsoft 365 admin center](/microsoft-365/admin/create-groups/create-groups?view=o365-worldwide&preserve-view=true)
-* [Azure portal](https://portal.azure.com/)
+* [Microsoft Entra admin center](https://entra.microsoft.com)
 * [Microsoft 365 admin center](https://admin.microsoft.com/)
 
 ### Microsoft 365 Groups roles
diff --git a/articles/active-directory/conditional-access/policy-migration-mfa.md b/articles/active-directory/conditional-access/policy-migration-mfa.md
@@ -1,6 +1,6 @@
 ---
 title: Migrate a classic Conditional Access policy 
-description: This article shows how to migrate a classic Conditional Access policy in the Azure portal.
+description: This article shows how to migrate a classic Conditional Access policy.
 
 services: active-directory
 ms.service: active-directory
diff --git a/articles/active-directory/conditional-access/require-tou.md b/articles/active-directory/conditional-access/require-tou.md
@@ -87,7 +87,7 @@ The scenario in this quickstart uses:
 
 In the previous section, you created a Conditional Access policy requiring terms of use be accepted. 
 
-To test your policy, try to sign in to the [Azure portal](https://portal.azure.com) using your test account. You should see a dialog that requires you to accept your terms of use.
+To test your policy, try to sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) using your test account. You should see a dialog that requires you to accept your terms of use.
 
 :::image type="content" source="./media/require-tou/57.png" alt-text="Screenshot of a dialog box titled Identity Security Protection terms of use, with Decline and Accept buttons and a button labeled My TOU." border="false":::
 
diff --git a/articles/active-directory/devices/assign-local-admin.md b/articles/active-directory/devices/assign-local-admin.md
@@ -111,5 +111,5 @@ Additionally, you can also add users using the command prompt:
 
 ## Next steps
 
-- To get an overview of how to manage devices, see [managing devices using the Azure portal](manage-device-identities.md).
+- To get an overview of how to manage devices, see [managing device identities](manage-device-identities.md).
 - To learn more about device-based Conditional Access, see [Conditional Access: Require compliant or Microsoft Entra hybrid joined device](../conditional-access/howto-conditional-access-policy-compliant-device.md).
diff --git a/articles/active-directory/devices/concept-device-registration.md b/articles/active-directory/devices/concept-device-registration.md
@@ -60,6 +60,6 @@ Another user wants to access their organizational email on their personal Androi
 
 ## Next steps
 
-- [Manage device identities using the Azure portal](manage-device-identities.md)
+- [Manage device identities](manage-device-identities.md)
 - [Manage stale devices in Microsoft Entra ID](manage-stale-devices.md)
 - [Register your personal device on your work or school network](https://support.microsoft.com/account-billing/register-your-personal-device-on-your-work-or-school-network-8803dd61-a613-45e3-ae6c-bd1ab25bf8a8)
diff --git a/articles/active-directory/devices/concept-directory-join.md b/articles/active-directory/devices/concept-directory-join.md
@@ -86,5 +86,5 @@ Microsoft Entra join can be deployed by using any of the following methods:
 - [Plan your Microsoft Entra join implementation](device-join-plan.md)
 - [Co-management using Configuration Manager and Microsoft Intune](/mem/configmgr/comanage/overview)
 - [How to manage the local administrators group on Microsoft Entra joined devices](assign-local-admin.md)
-- [Manage device identities using the Azure portal](manage-device-identities.md)
+- [Manage device identities](manage-device-identities.md)
 - [Manage stale devices in Microsoft Entra ID](manage-stale-devices.md)
diff --git a/articles/active-directory/devices/concept-hybrid-join.md b/articles/active-directory/devices/concept-hybrid-join.md
@@ -56,5 +56,5 @@ Use Microsoft Entra hybrid joined devices if:
 
 - [Plan your Microsoft Entra hybrid join implementation](hybrid-join-plan.md)
 - [Co-management using Configuration Manager and Microsoft Intune](/mem/configmgr/comanage/overview)
-- [Manage device identities using the Azure portal](manage-device-identities.md)
+- [Manage device identities](manage-device-identities.md)
 - [Manage stale devices in Microsoft Entra ID](manage-stale-devices.md)
diff --git a/articles/active-directory/devices/device-join-out-of-box.md b/articles/active-directory/devices/device-join-out-of-box.md
@@ -59,7 +59,7 @@ To verify whether a device is joined to your Microsoft Entra ID, review the **Ac
 
 ## Next steps
 
-- For more information about managing devices, see [managing devices using the Azure portal](manage-device-identities.md).
+- For more information about managing devices, see [managing device identities](manage-device-identities.md).
 - [What is Microsoft Intune?](/mem/intune/fundamentals/what-is-intune)
 - [Overview of Windows Autopilot](/mem/autopilot/windows-autopilot)
 - [Passwordless authentication options for Microsoft Entra ID](../authentication/concept-authentication-passwordless.md)
diff --git a/articles/active-directory/devices/device-join-plan.md b/articles/active-directory/devices/device-join-plan.md
@@ -216,7 +216,7 @@ Choose your deployment approach or approaches by reviewing the previous table an
 
 ## Configure your device settings
 
-The Azure portal allows you to control the deployment of Microsoft Entra joined devices in your organization. To configure the related settings, on the **Microsoft Entra ID page**, select `Devices > Device settings`. [Learn more](manage-device-identities.md)
+The [Microsoft Entra admin center](https://entra.microsoft.com) allows you to control the deployment of Microsoft Entra joined devices in your organization. To configure the related settings, brose to **Identity** > **Devices** > **All devices** > **Device settings**. [Learn more](manage-device-identities.md)
 
 <a name='users-may-join-devices-to-azure-ad'></a>
 
diff --git a/articles/active-directory/devices/enterprise-state-roaming-faqs.yml b/articles/active-directory/devices/enterprise-state-roaming-faqs.yml
@@ -59,7 +59,7 @@ sections:
         answer: |
           When multiple Microsoft Entra accounts from different Microsoft Entra tenants are on the same device, you must update the device's registry to communicate with the Azure Rights Management service for each Microsoft Entra tenant.  
           
-          1. Find the GUID for each Microsoft Entra tenant. Open the Azure portal and select a Microsoft Entra tenant. The GUID for the tenant is on the Properties page for the selected tenant (https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Properties), labeled **Directory ID**. 
+          1. Find the GUID for each Microsoft Entra tenant. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com), browse to **Identity** > **Overview** > **Properties** > **Tenant ID**.
           2. After you have the GUID, you'll need to add the registry key
              **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\SettingSync\WinMSIPC\<tenant ID GUID>**.
              From the **tenant ID GUID** key, create a new Multi-String value (REG-MULTI-SZ) named **AllowedRMSServerUrls**. For its data, specify the licensing distribution point URLs of the other Azure tenants that the device accesses.
diff --git a/articles/active-directory/devices/enterprise-state-roaming-group-policy-settings.md b/articles/active-directory/devices/enterprise-state-roaming-group-policy-settings.md
@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
 
 Use these Group Policy and mobile device management (MDM) settings only on corporate-owned devices because these policies are applied to the user’s entire device. Applying an MDM policy to disable settings sync for a personal, user-owned device will negatively impact the use of that device. Additionally, other user accounts on the device will also be affected by the policy.
 
-Enterprises that want to manage roaming for personal (unmanaged) devices can use the Azure portal to enable or disable roaming, rather than using Group Policy or MDM.
+Enterprises that want to manage roaming for personal (unmanaged) devices can use the Microsoft Entra admin center to enable or disable roaming, rather than using Group Policy or MDM.
 The following tables describe the policy settings available.
 
 > [!NOTE]
diff --git a/articles/active-directory/devices/enterprise-state-roaming-troubleshooting.md b/articles/active-directory/devices/enterprise-state-roaming-troubleshooting.md
@@ -76,7 +76,7 @@ Enterprise State Roaming requires the device to be registered with Microsoft Ent
 
 Under certain conditions, Enterprise State Roaming can fail to sync data if Microsoft Entra multifactor authentication is configured. For more information on these symptoms, see the support document [KB3193683](https://support.microsoft.com/kb/3193683). 
 
-**Potential issue**: If your device is configured to require multifactor authentication on the Azure portal, you may fail to sync settings while signing in to a Windows 10 or newer device using a password. This type of multifactor authentication configuration is intended to protect an Azure administrator account. Admin users may still be able to sync by signing in to their Windows 10 or newer devices with their Windows Hello for Business PIN or by completing multifactor authentication while accessing other Azure services like Microsoft 365.
+**Potential issue**: If your device is configured to require multifactor authentication on the Microsoft Entra admin center, you may fail to sync settings while signing in to a Windows 10 or newer device using a password. This type of multifactor authentication configuration is intended to protect an Azure administrator account. Admin users may still be able to sync by signing in to their Windows 10 or newer devices with their Windows Hello for Business PIN or by completing multifactor authentication while accessing other Azure services like Microsoft 365.
 
 **Potential issue**: Sync can fail if the admin configures the Active Directory Federation Services multifactor authentication Conditional Access policy and the access token on the device expires. Ensure that you sign in and sign out using the Windows Hello for Business PIN or complete multifactor authentication while accessing other Azure services like Microsoft 365.
 
diff --git a/articles/active-directory/devices/faq.yml b/articles/active-directory/devices/faq.yml
@@ -71,7 +71,7 @@ sections:
         answer: |
           This operation is by design. In this case, the device doesn't have access to resources in the cloud. Administrators can perform this action for stale, lost, or stolen devices to prevent unauthorized access. If this action was performed unintentionally, you need to re-enable or re-register the device using the steps that follow:
           
-          - If the device was disabled in Microsoft Entra ID, an administrator with sufficient privileges can enable it from the Azure portal  
+          - If the device was disabled in Microsoft Entra ID, an administrator with sufficient privileges can enable it in the Microsoft Entra admin center  
             > [!NOTE]
             > If you're syncing devices using Azure AD Connect, hybrid Azure AD joined devices will be automatically re-enabled during the next  sync cycle. So, if you need to disable a Microsoft Entra hybrid joined device, you need to disable it from your on-premises AD
           
diff --git a/articles/active-directory/devices/how-to-hybrid-join-verify.md b/articles/active-directory/devices/how-to-hybrid-join-verify.md
@@ -25,11 +25,11 @@ Here are three ways to locate and verify the hybrid joined device state:
 1. Open Windows PowerShell.
 2. Enter `dsregcmd /status`.
 3. Verify that both **AzureAdJoined** and **DomainJoined** are set to **YES**.
-4. You can use the **DeviceId** and compare the status on the service using either the Azure portal or PowerShell.
+4. You can use the **DeviceId** and compare the status on the service using either the Microsoft Entra admin center or PowerShell.
 
 For downlevel devices, see the article [Troubleshooting Microsoft Entra hybrid joined down-level devices](troubleshoot-hybrid-join-windows-legacy.md#step-1-retrieve-the-registration-status)
 
-## Using the Azure portal
+## Using the Microsoft Entra admin center
 
 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com)ntra.microsoft.com) as at least a [Cloud Device Administrator](../roles/permissions-reference.md#cloud-device-administrator).
 1. Browse to **Identity** > **Devices** > **All devices**.
diff --git a/articles/active-directory/devices/hybrid-join-control.md b/articles/active-directory/devices/hybrid-join-control.md
@@ -58,7 +58,7 @@ Use the following example to create a Group Policy Object (GPO) to deploy a regi
       1. Key Path: **SOFTWARE\Microsoft\Windows\CurrentVersion\CDJ\AAD**.
       1. Value name: **TenantId**.
       1. Value type: **REG_SZ**.
-      1. Value data: The GUID or **Tenant ID** of your Microsoft Entra instance (This value can be found in the **Azure portal** > **Microsoft Entra ID** > **Properties** > **Tenant ID**).
+      1. Value data: The GUID or **Tenant ID** of your Microsoft Entra instance (This value can be found in the **Microsoft Entra admin center** > **Identity** > **Properties** > **Tenant ID**).
    1. Select **OK**.
 1. Right-click on the Registry and select **New** > **Registry Item**.
    1. On the **General** tab, configure the following.
diff --git a/articles/active-directory/devices/manage-device-identities.md b/articles/active-directory/devices/manage-device-identities.md
@@ -1,6 +1,6 @@
 ---
-title: Manage devices in Microsoft Entra ID using the Azure portal
-description: This article describes how to use the Azure portal to manage device identities and monitor related event information.
+title: Manage devices in Microsoft Entra ID using the Microsoft Entra admin center
+description: This article describes how to use the Microsoft Entra admin center to manage device identities and monitor related event information.
 
 services: active-directory
 ms.service: active-directory
@@ -15,7 +15,7 @@ ms.reviewer: myra-ramdenbourg
 
 ms.collection: M365-identity-device-management
 ---
-# Manage device identities by using the Azure portal
+# Manage device identities using the Microsoft Entra admin center
 
 Microsoft Entra ID provides a central place to manage device identities and monitor related event information.
 
@@ -149,7 +149,7 @@ The exported list includes these device identity attributes:
 
 ## Configure device settings
 
-If you want to manage device identities by using the Azure portal, the devices need to be either [registered or joined](overview.md) to Microsoft Entra ID. As an administrator, you can control the process of registering and joining devices by configuring the following device settings.
+If you want to manage device identities by using the Microsoft Entra admin center, the devices need to be either [registered or joined](overview.md) to Microsoft Entra ID. As an administrator, you can control the process of registering and joining devices by configuring the following device settings.
 
 You must be assigned one of the following roles to view device settings:
 
diff --git a/articles/active-directory/devices/manage-stale-devices.md b/articles/active-directory/devices/manage-stale-devices.md
@@ -51,7 +51,7 @@ If the delta between the existing value of the activity timestamp and the curren
 
 You have two options to retrieve the value of the activity timestamp:
 
-- The **Activity** column on the [devices page](https://portal.azure.com/#blade/Microsoft_AAD_IAM/DevicesMenuBlade/Devices).
+- The **Activity** column on the all devices page.
 
     :::image type="content" source="./media/manage-stale-devices/01.png" alt-text="Screenshot listing the name, owner, and other information of devices. One column lists the activity time stamp." border="false":::
 
@@ -129,9 +129,9 @@ Disable or delete Microsoft Entra registered devices in the Microsoft Entra ID.
 > - Deleting a Microsoft Entra registered device in Microsoft Entra ID does not remove registration on the client. It will only prevent access to resources using device as an identity (e.g. Conditional Access).
 > - Read more on [how to remove a registration on the client](faq.yml)
 
-## Clean up stale devices in the Azure portal  
+## Clean up stale devices  
 
-While you can clean up stale devices in the Azure portal, it's more efficient, to handle this process using a PowerShell script. Use the latest PowerShell V2 module to use the timestamp filter and to filter out system-managed devices such as Autopilot.
+While you can clean up stale devices in the Microsoft Entra admin center, it's more efficient, to handle this process using a PowerShell script. Use the latest PowerShell V2 module to use the timestamp filter and to filter out system-managed devices such as Autopilot.
 
 A typical routine consists of the following steps:
 
@@ -222,4 +222,4 @@ Any authentication where a device is being used to authenticate to Microsoft Ent
 
 Devices managed with Intune can be retired or wiped, for more information see the article [Remove devices by using wipe, retire, or manually unenrolling the device](/mem/intune/remote-actions/devices-wipe).
 
-To get an overview of how to manage devices, see [managing devices using the Azure portal](manage-device-identities.md)
+To get an overview of how to manage devices, see [managing device identities](manage-device-identities.md)
diff --git a/articles/active-directory/devices/overview.md b/articles/active-directory/devices/overview.md
@@ -57,5 +57,5 @@ Getting devices in to Microsoft Entra ID can be done in a self-service manner or
 - Learn more about [Microsoft Entra registered devices](concept-device-registration.md)
 - Learn more about [Microsoft Entra joined devices](concept-directory-join.md)
 - Learn more about [Microsoft Entra hybrid joined devices](concept-hybrid-join.md)
-- To get an overview of how to manage device identities, see [Managing device identities using the Azure portal](manage-device-identities.md).
+- To get an overview of how to manage device identities, see [Managing device identities](manage-device-identities.md).
 - To learn more about device-based Conditional Access, see [Configure Microsoft Entra device-based Conditional Access policies](../conditional-access/concept-conditional-access-grant.md).
diff --git a/articles/active-directory/devices/plan-device-deployment.md b/articles/active-directory/devices/plan-device-deployment.md
diff --git a/articles/active-directory/devices/troubleshoot-device-windows-joined.md b/articles/active-directory/devices/troubleshoot-device-windows-joined.md
