Skip to main content

014: Quiet Time

Implementation Effort: Low – The technical setup is simple, but policy design should align to worker personas and support expectations.

User Impact: Medium – Users may see fewer after-hours notifications from managed productivity apps on supported mobile devices.

Overview​

Quiet time settings in Microsoft Intune can suppress notifications from supported managed apps such as Outlook and Teams during defined periods. This is not a primary security enforcement control, but it can improve user adoption of managed apps and support healthier boundaries for mobile workers without requiring users to disable protection features. In a Zero Trust deployment, quiet time is most useful when it complements app protection, app configuration, and mobile productivity standards rather than replacing them.

Quiet time assets

image

image

image

Implementation Guidance​

  1. Decide which user populations genuinely need quiet time settings, such as knowledge workers in specific regions or shifts. Avoid broad default deployment if teams have very different business-hour patterns.
  2. Review whether the managed app model, app configuration, and app protection design for Outlook and Teams is already standardized; quiet time should ride on top of a well-governed mobile app baseline.
  3. Pilot notification behavior across supported iOS and Android scenarios before wide rollout. Validate local-time handling, weekend schedules, and user expectations.
  4. Coordinate with HR and business stakeholders if quiet time is being positioned as a work-pattern or wellbeing feature rather than only an app setting.
  5. Document exceptions for on-call or incident-response populations that must continue receiving after-hours notifications.
  6. Review support documentation so users understand whether quiet time is tenant-managed or controlled by local app settings.

Reference​