Document Theme and Wallpaper customization options

[toniyang0820]

Added section on Theme and Wallpaper customization for Microsoft Edge on iOS and Android.

[prmerger-automator]

toniyang0820 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Nicholas S. White (@nicholasswhite)

[learn-build-service-prod]

Learn Build status updates of commit 74e1bc2:

✅ Validation status: passed

File	Status	Preview URL	Details
intune/app-management/configuration/configure-edge-ios-android.md	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 2ab7cd8:

✅ Validation status: passed

File	Status	Preview URL	Details
intune/app-management/configuration/configure-edge-ios-android.md	✅Succeeded

For more details, please refer to the build report.

[Regan Downer (v-regandowner)]

Ileana Wu (@ilwu-microsoft)

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[prmerger-automator]

toniyang0820 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Nicholas S. White (@nicholasswhite)

[Copilot]

Pull request overview

Adds documentation for controlling Microsoft Edge mobile Theme/Wallpaper customization via Intune app configuration, plus updates the MAM→MDM policy mapping and corrects a link reference definition formatting issue.

Changes:

• Documented a new Theme and Wallpaper customization configuration key (com.microsoft.intune.mam.managedbrowser.ThemeAvailable).
• Added the corresponding entry to the MAM→MDM policy mapping table (EdgeThemeEnabled).
• Fixed the “Microsoft Intune admin center” link reference definition line so it renders correctly.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Shannon Leavitt (ShannonLeavitt)]

toniyang0820

Thank you for your contribution. MSec technical documentation now follows a self-serve model. For Microsoft-internal contributions, please submit changes through the corresponding private repo instead of a public PR. This enables build validation, Policheck, staged content review, and contributor sign-off before publishing. For more details, see the MSec Docs Self-Serve Playbook.

#please-close
@MicrosoftDocs/public-repo-pr-review-team