Skip to content

Commit 4e690a6

Browse files
Azure Portal > Azure portal (twice)
1 parent ce80149 commit 4e690a6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/devices/hybrid-azuread-join-manual.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -555,12 +555,12 @@ Here are 3 ways to locate and verify the device state:
555555
1. Open Windows PowerShell.
556556
2. Enter `dsregcmd /status`.
557557
3. Verify that both **AzureAdJoined** and **DomainJoined** are set to **YES**.
558-
4. You can use the **DeviceId** and compare the status on the service using either the Azure Portal or PowerShell.
558+
4. You can use the **DeviceId** and compare the status on the service using either the Azure portal or PowerShell.
559559

560560
### Using the Azure portal
561561

562562
1. Go to the devices page using a [direct link](https://portal.azure.com/#blade/Microsoft_AAD_IAM/DevicesMenuBlade/Devices).
563-
2. Information on how to locate a device can be found in [How to manage device identities using the Azure Portal](https://docs.microsoft.com/azure/active-directory/devices/device-management-azure-portal#locate-devices).
563+
2. Information on how to locate a device can be found in [How to manage device identities using the Azure portal](https://docs.microsoft.com/azure/active-directory/devices/device-management-azure-portal#locate-devices).
564564
3. If the **Registered** column says **Pending**, then Hybrid Azure AD Join has not completed. In federated environments, this can happen only if it failed to register and AAD connect is configured to sync the devices.
565565
4. If the **Registered** column contains a **date/time**, then Hybrid Azure AD Join has completed.
566566

0 commit comments

Comments
 (0)