From ad8e4e2959aaa78c2ceba261256cf0cdf589113f Mon Sep 17 00:00:00 2001
From: illumiN8i <44124235+illumiN8i@users.noreply.github.com>
Date: Tue, 18 Feb 2025 10:03:54 -0500
Subject: [PATCH] Update android-migration-guide.md

changed "device" to "devices" to match how it's displayed in Intune
---
 Teams/rooms/android-migration-guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Teams/rooms/android-migration-guide.md b/Teams/rooms/android-migration-guide.md
index a58935fd6b..18d6fc6a14 100644
--- a/Teams/rooms/android-migration-guide.md
+++ b/Teams/rooms/android-migration-guide.md
@@ -57,7 +57,7 @@ When creating an enrollment profile, verify it doesn't conflict with any enrollm
 
 1. Sign in to the Intune Management Console with an account with Intune administrator permissions: [https://intune.microsoft.com/](https://intune.microsoft.com/).
 2. Select **Devices** > **Enrollment** > then **Android**.
-3. Under **Enrollment Profiles**, select **Corporate-owned, user-associated device**.
+3. Under **Enrollment Profiles**, select **Corporate-owned, user-associated devices**.
 4. Select **Create policy**.
 5. Use the following settings for the profile configuration: