starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #3578] [Feature Request]: Ability to deploy AOSP Policies in Intune for migration from Android device administrator #1598

New issue

Closed

opened 2026-03-02 13:45:29 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:45:29 +03:00

Owner

Originally created by @HappyEarthDay on GitHub (Feb 5, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3578

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

Per this message, android device admin is being retired. There are a couple of simple steps that are required to facilitate a migration to AOSP. https://learn.microsoft.com/en-us/MicrosoftTeams/rooms/android-migration-guide

We can already deploy configuration profiles and autopilot profiles via CIPP, but we can't deploy Android enrollment profiles for AOSP which is the only required step for the migration. I would want CIPP to be able to create two profiles. In the Intune portal, it is done via Devices > Enrollment > then Android and one policy under each of:

Corporate-owned, user-associated device
Corporate-owned, userless devices

For example, our MSP creates two policies to ensure that Teams devices (for us, Yealink phones) using device administrator are automatically migrated to AOSP when the firmware is released. We use a naming convention similar to this:

MSP Baseline - Android User-based Device Enrollment
MSP Baseline - Android Userless Device Enrollment

These two policies are created with the default settings via the wizard, but we'd love to deploy them to all clients via CIPP to eliminate manual labor. While a normal policy deployment option would be great, having these available in Standards would be even better :)

PowerShell commands you would normally use to achieve above request

No response

Originally created by @HappyEarthDay on GitHub (Feb 5, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3578 ### Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole. [Per this message](https://techcommunity.microsoft.com/blog/intunecustomersuccess/intune-ending-support-for-android-device-administrator-on-devices-with-gms-in-de/3915443#:~:text=Microsoft%20Teams%20certified,further%20migration%20guidance.), android device admin is being retired. There are a couple of simple steps that are required to facilitate a migration to AOSP. https://learn.microsoft.com/en-us/MicrosoftTeams/rooms/android-migration-guide We can already deploy configuration profiles and autopilot profiles via CIPP, but we can't deploy [Android enrollment profiles for AOSP](https://techcommunity.microsoft.com/blog/microsoftteamssupport/moving-teams-android-devices-to-aosp-device-management/4140893) which is the only _required_ step for the migration. I would want CIPP to be able to create two profiles. In the Intune portal, it is done via Devices > Enrollment > then Android and one policy under each of: - **Corporate-owned, user-associated device** - **Corporate-owned, userless devices** For example, our MSP creates two policies to ensure that Teams devices (for us, Yealink phones) using device administrator are automatically migrated to AOSP when the firmware is released. We use a naming convention similar to this: - MSP Baseline - Android User-based Device Enrollment - MSP Baseline - Android Userless Device Enrollment These two policies are created with the default settings via the wizard, but we'd love to deploy them to all clients via CIPP to eliminate manual labor. While a normal policy deployment option would be great, having these available in Standards would be even better :) ### PowerShell commands you would normally use to achieve above request _No response_

kerem

2026-03-02 13:45:29 +03:00

closed this issue
added the
enhancement

no-priority

no-activity
labels

kerem commented

2026-03-02 13:45:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 15, 2025):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

@github-actions[bot] commented on GitHub (Feb 15, 2025): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

kerem commented

2026-03-02 13:45:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 1, 2025):

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions[bot] commented on GitHub (Mar 1, 2025): This issue was closed because it has been stalled for 14 days with no activity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#1598

No description provided.

Rows
Columns