[GH-ISSUE #1269] Intune > Device Management > Devices Table issues #709

Closed
opened 2026-03-02 12:44:32 +03:00 by kerem · 4 comments
Owner

Originally created by @BNWEIN on GitHub (Dec 16, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1269

Description

Issue 1:
"AutoPilotEnrolled" column is always empty. No sign/symbol showing when a device is AutoPilot Enrolled, even though the devices do show under Intune > AutoPilot > AutPilot Devices

Issue 2:

Choosing the "LoggedOnUser" column causes an repeatable error

image

Environment data

Self Hosted Azure
Frontend: 2.19.0
Backend: 2.8.0
Originally created by @BNWEIN on GitHub (Dec 16, 2022). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1269 ### Description Issue 1: "AutoPilotEnrolled" column is always empty. No sign/symbol showing when a device is AutoPilot Enrolled, even though the devices do show under Intune > AutoPilot > AutPilot Devices Issue 2: Choosing the "LoggedOnUser" column causes an repeatable error ![image](https://user-images.githubusercontent.com/28929905/208192786-55e6c2a6-f303-40ee-90d9-97f7cde4dc69.png) ### Environment data ```PowerShell Self Hosted Azure Frontend: 2.19.0 Backend: 2.8.0 ```
kerem 2026-03-02 12:44:32 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 16, 2022):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:1355668725 --> @github-actions[bot] commented on GitHub (Dec 16, 2022): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@BNWEIN commented on GitHub (Dec 16, 2022):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug

<!-- gh-comment-id:1355693177 --> @BNWEIN commented on GitHub (Dec 16, 2022): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug
Author
Owner

@github-actions[bot] commented on GitHub (Dec 16, 2022):

Great! I assigned you (@BNWEIN) to the issue. Have fun working on it!

<!-- gh-comment-id:1355693867 --> @github-actions[bot] commented on GitHub (Dec 16, 2022): Great! I assigned you (@BNWEIN) to the issue. Have fun working on it!
Author
Owner

@KelvinTegelaar commented on GitHub (Dec 21, 2022):

Fixed in dev

<!-- gh-comment-id:1361273976 --> @KelvinTegelaar commented on GitHub (Dec 21, 2022): Fixed in dev
Sign in to join this conversation.
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#709
No description provided.