Microsoft Preference

To ease the implementation of interactive settings screens without the need to interact with device storage or manage the UI, Google has released the androix.preference API, as part of the AndroidX Jetpack library. Each Partner will be implementing its own Setting App based on the reference AOSP Settings App which is based on androidx.preference API. Admin Android Preferences settings are implemented using the Jetpack androidx.preference API but access is protected under an admin session which must be established before being able to read or modify them.

An extension library for com.microsoft.preference based on androidx.preference enables automatic synchronization of the preference data by means of Synchronization Manager/Service so that the client does not need to directly interact with Synchronization Manager/Service but can use the “Google-way” of interacting with preferences.

In case Partner decides not to use Microsoft com.microsoft.preference extension classes which already handle the value’s persistence on the device, the API (ISettingsSynchronization) shall allow the client application to register a listener/callback for the incoming synchronization evets from the remote device and to implement by itself in the client application the logic for storing the values.

The default admin password is initially set by the Partner (Partner) Agent based on the Teams Admin Center configuration. The user can set a new admin password which will be updated in the local storage and can be synchronized between the Partner paired devices, but it will not be propagated back to the Teams Admin Center.