Configure Managed Home Screen
The page’s authoring metadata changed, and the description for excluding apps from the silence setting was revised.
A cross-product view of Microsoft Intune changes related to App management.
The page’s authoring metadata changed, and the description for excluding apps from the silence setting was revised.
During onboarding, the Intune, Microsoft Authenticator, and Company Portal apps are installed as required apps on dedicated devices, in addition to fully managed and corporate-owned work profile devices.
The documentation now states that failed macOS app installations are retried at the next agent check-in, with up to three retries while the app remains assigned.
The app-exclusion setting description now spells out “Managed Home Screen” instead of using the abbreviation “MHS” when referring to authentication.
The guide now states that app configuration policies support only MDM-managed apps and cannot configure DDM apps. The setup steps were also renumbered.
The documentation now warns that re-uploading an existing VPP token for DDM causes available app assignments to be lost. It recommends creating a new Apple Business token for DDM and using MDM for available assignments and apps requiring app configuration policies.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, and its subservice metadata changed from `core-infrastructure` to `core-infra`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article’s metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, and its subservice metadata changed from `core-infrastructure` to `core-infra`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article’s metadata changed from `microsoft-endpoint-configuration-manager` and `core-infrastructure` to `configuration-manager` and `core-infra`.
The documentation metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation replaces `ms.subservice: core-infrastructure` with `core-infra` and `ms.service: microsoft-endpoint-configuration-manager` with `configuration-manager`.
The page metadata now uses `core-infra` instead of `core-infrastructure` and `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The iOS app protection settings reference updated the Screen capture entry, documenting that Block prevents capture of work or school data, while Allow is the default and permits capture and sharing without restrictions.
The article metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` service identifiers.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` for its subservice and service values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK subservice.
The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The reference documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.
The page metadata changes ms.service from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The document’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page's `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; the `sdk` subservice remains unchanged.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `sdk` subservice.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, paired with the existing SDK subservice.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK classification.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The documented metadata value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.
The page metadata now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The documented `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager, while ms.subservice remains sdk.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The documentation changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.
The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The page metadata now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The documentation metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the service classification.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The reference page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; its `ms.subservice` remains `sdk`.
The SetIsExpired method page now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for its service metadata.
The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `sdk` subservice remains unchanged.
The documentation’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains paired with it.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The page metadata changed `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice classification.
The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `ms.subservice` value remains `sdk`.
The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; the `sdk` subservice remains unchanged.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.
The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.
The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the SDK subservice classification.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice pairing remains.
The ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager while the SDK subservice pairing remains.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
The page now uses `ms.service: configuration-manager` with `ms.subservice: sdk` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, paired with `ms.subservice: sdk`.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.
The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK service metadata.
The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; `ms.subservice: sdk` remains unchanged.
The documentation now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The documentation metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager.
The page's ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `sdk` subservice pairing.
The article changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice pairing.
The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the `sdk` subservice classification.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains paired with it.