Update device restrictions for Android Enterprise#5041
Merged
MandiOhlinger merged 8 commits intoMicrosoftDocs:mainfrom Apr 21, 2026
Merged
Update device restrictions for Android Enterprise#5041MandiOhlinger merged 8 commits intoMicrosoftDocs:mainfrom
MandiOhlinger merged 8 commits intoMicrosoftDocs:mainfrom
Conversation
Clarified the implications of enabling the Overview button in kiosk mode, including potential access to device settings without authentication.
Added warning about security and configuration settings for Managed Home Screen.
Updated the link for device restriction settings to a relative link
Contributor
|
Learn Build status updates of commit a0361fa: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
Author
|
Maybe good to know that prmerger-automator doesn't pickup PR's that are created as draft, and marked "Ready for review". See: #5037 |
Updated the date for device restriction settings and clarified the warning regarding the Overview button and end-user access to device settings.
Contributor
|
@Daniel-H123 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit b9cbd71: ✅ Validation status: passed
For more details, please refer to the build report. |
Updated the date and revised the warning section for clarity.
Contributor
|
Learn Build status updates of commit 30d249e: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
|
Learn Build status updates of commit 0255e69: ✅ Validation status: passed
For more details, please refer to the build report. |
Reinstate the explanation of how the Managed Home Screen app configuration policy and device configuration restrictions policy work together, emphasizing the importance of device restriction settings for security.
Contributor
|
Learn Build status updates of commit 6dc5f3e: ✅ Validation status: passed
For more details, please refer to the build report. |
MandiOhlinger
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarifies kiosk security implications when using Managed Home Screen in Microsoft Intune.
Changes
Why
This change helps administrators better understand the security impact of certain kiosk configurations and reduces the risk of unintentionally deploying insecure kiosk setups due to incomplete or distributed configuration requirements.