Skip to content

Commit ef812cf

Browse files
"Azure Portal" to "Azure portal" [two instances]
1 parent 8a971d6 commit ef812cf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/devices/hybrid-azuread-join-federated-domains.md

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

190190
### Using the Azure portal
191191

192192
1. Go to the devices page using a [direct link](https://portal.azure.com/#blade/Microsoft_AAD_IAM/DevicesMenuBlade/Devices).
193-
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).
193+
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).
194194
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.
195195
4. If the **Registered** column contains a **date/time**, then Hybrid Azure AD Join has completed.
196196

0 commit comments

Comments
 (0)