Hello !
So far we have been deploying with SCCM, deferring works pretty well : when a user choose to defer, he gets prompted again at the next fast retry tick.
Question : how it should work in intune deployment context ?
Thanks for sharing your experience 
Thanks for the feedback @Adrian_Scott !
A 8 hour window will be very ok for us i think. If it's the default Intune Behavior with the Psadt deferring process, then all will be fine
I think the deferral scheme will eventually be revisited.
There's too many things behind the scenes that need to be nailed down first.
FWIW, We use Intune for all our software deployments (to our entire Windows estate) and we (or I) 'standardised' on 3 deferrals for all our app deployments (when wrapped in PSADT - but this is partly laziness on my part as I reuse the same deferral code in each deployment script).
3 deferrals works great for us as it gives the user an opportunity to close an open app that needs an update or defer up to a maximum of 3 times, which generally deploys the majority of updates that fixes security flaws within 3 days. Less than 3 is possibly not enough for some users, and more than 3 can lead to devices drifting from our core deployed software version(s).
We have not found any adverse effects of this, as the PSADT deferral tracks the Intune 8 hour window. This is helped by educating our users to shutdown their device between days / uses (which fixes many other issues 
) , so in general they only get prompted again the next time the Intune Management Engine starts up (i.e. after the machines next startup), Personally I've not experienced seeing the prompt re-appear within the 8 hour window.
