From 84566685e1d26efac93446207c72f7fc356ef9b1 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Mon, 4 May 2026 09:59:25 -0400
Subject: [PATCH] Update custom OS settings documentation (#44537)

Clarify the availability of the 'Resend' button for Android certificates
and explain the differences in profile delivery mechanisms.
---
 articles/custom-os-settings.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/articles/custom-os-settings.md b/articles/custom-os-settings.md
index 338a88e31d..7c3ee1955e 100644
--- a/articles/custom-os-settings.md
+++ b/articles/custom-os-settings.md
@@ -148,6 +148,8 @@ Also, some settings from the profile might be overridden by another configuratio
 
 The error message will provide the reason from the Android Management API (AMAPI) for why certain settings are not applied. Possible reasons are listed in the [AMAPI docs](https://developers.google.com/android/management/reference/rest/v1/NonComplianceReason).
 
+Note that the "Resend" button is only available for certificates. Fleet pushes certificates via Fleet's Android app. Other configuration profiles don't have the "Resend" button because othey are sent via a different mechanism: the host checks in for these profiles periodically similarly to Apple declaration (DDM) profiles, rather than Fleet pushing them. 
+
 ## Broken profiles
 
 If one or more labels included in the profile's scope are deleted, the profile will not apply to new hosts that enroll.