Skip to content

Commit d1435d4

Browse files
Merge pull request #244684 from AjayBathini-MSFT/patch-91
(AzureCXP) fixes MicrosoftDocs/azure-docs#112005
2 parents 11dfd7e + 8e101e4 commit d1435d4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/devices/concept-azure-ad-register.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ The goal of Azure AD registered - also known as Workplace joined - devices is to
4848

4949
Azure AD registered devices are signed in to using a local account like a Microsoft account on a Windows 10 or newer device. These devices have an Azure AD account for access to organizational resources. Access to resources in the organization can be limited based on that Azure AD account and Conditional Access policies applied to the device identity.
5050

51-
Administrators can further control these Azure AD registered devices by enrolling the device(s) into Mobile Device Management (MDM) tools like Microsoft Intune. MDM provides a means to enforce organization-required configurations like requiring storage to be encrypted, password complexity, and security software kept updated.
51+
Azure AD Registration is not the same as device enrolment. If Administrators permit users to enrol their devices, organisations can further control these Azure AD registered devices by enrolling the device(s) into Mobile Device Management (MDM) tools like Microsoft Intune. MDM provides a means to enforce organization-required configurations like requiring storage to be encrypted, password complexity, and security software kept updated.
5252

5353
Azure AD registration can be accomplished when accessing a work application for the first time or manually using the Windows 10 or Windows 11 Settings menu.
5454

0 commit comments

Comments
 (0)