Mobile Offline Profiles are not fully solution aware, and best practices require manual management across environments. The MS Learn documentation implies portability, but this can be misleading without clarifying the unmanaged layer limitations.

• Microsoft Learn mentions “Move a mobile offline profile between environments,” but this is misleading because there is no native solution-based deployment mechanism for these profiles. Instead, moving them requires manual recreation or using tools like Configuration Migration Tool or XrmToolBox Data Transporter.
• The inability to remove unmanaged layers further confirms that these profiles do not behave like solution-aware components.

Documentation Issue

The Microsoft learn article currently states that profiles can be moved between environments, which is misleading. The reality is:

• There is no out-of-the-box solution-aware mechanism for Mobile Offline Profiles.
• Movement requires manual recreation or data migration tools.

Making Mobile Offline Profiles solution-aware should be part of the roadmap. Documenting the Field Service Mobile Offline Profile can be a significant effort due to the large number of tables and columns involved. While maintaining the out-of-the-box configuration is generally recommended, it’s not always feasible in every scenario. Can this be addressed in the documentation going forward and also suggesting the best practices